Choosing the Simply Managed AI offer that fits

The six offers solve different starting problems. Self-Serve is $297 per month with no setup fee. Solo is $5,000 setup plus $500 per month. Startup SaaS is a separate $5,000 prototype setup plus $500 per month for ongoing vibe coding. Team is $12,500 setup plus $1,250 per month. Brokerage is $25,000 setup plus $2,500 per month. Enterprise is custom-scoped — call us so security, integrations, governance, and rollout are priced around the actual requirement.

Self-Serve — run the operating core on your clock

• Pod-guided onboarding with no setup fee.
• A five-role AI operating core around the tools you already use.
• A monthly subscription you can cancel without an implementation contract.

Solo — a managed operating team for one operator

• One owner, one primary book of business, and one operating cadence.
• Lead response, nurture, and a weekly pipeline brief.
• The five-role operating core is configured around the tools already in place.

Startup SaaS — prototype once, then keep vibe coding

• The $5,000 setup scopes and builds a working SaaS prototype around the agreed core flows.
• The $500 monthly plan keeps an AI developer aligned with the product, backlog, and earlier decisions.
• Launch operations, support triage, and product cadence grow around what you ship.

Team — two to ten people sharing one book of business

• Shared inbox coverage and team routing — inquiries find the right owner without everyone watching everything.
• Shared delivery and content cadence — one calendar, one set of approval boundaries, one exception report.
• The economics that matter: setup gross margin ≥55%, monthly gross margin ≥60% — guarded by fixed scope and change orders when reality diverges.

Brokerage — governed routing and oversight

• Multi-agent rollout with routing rules and approval layers.
• Controls and audit trails that survive personnel changes.
• Quarterly workflow ROI review across the governed operating scope.

Enterprise — custom scope, security, and governance

• Multi-team rollout with routing rules, approval layers, and audit controls.
• Security and integration requirements are mapped before a price is promised.
• Dedicated implementation and support are sized to the organization, so Enterprise starts with a call rather than checkout.

How to decide in one conversation

1. Name the first outcome: an operating core, a SaaS prototype, a shared-team cadence, or an organization-wide rollout.
2. Name the systems and people involved: one builder, one team, or multiple departments with security and governance requirements.
3. Name the approval boundary: who can approve product changes, client-facing work, access, and policy? Those answers place the offer.