Decision FrameworkDecision layer

inbound: Buy vs Skip (Email-Integrated Agency Delivery)

IF your agency already ships code against REST APIs or a TypeScript SDK and needs inbound mail parsed into structured JSON webhooks, THEN inbound's $4/mo Default tier (5,000 emails) is a low-risk pilot, and you should step up to Pro at $15/mo (50,000 emails, 50 domains) once two or more client domains are live. IF the client expects a no-code inbox they can reconfigure without a developer, THEN skip inbound entirely, because there is no end-client UI and every routing change runs through the API.

By InnovaAI ResearchPublished

API Management
Decision Frame

inbound: Buy vs Skip (Email-Integrated Agency Delivery)

“IF your agency already ships code against REST APIs or a TypeScript SDK and needs inbound mail parsed into structured JSON webhooks, THEN inbound's $4/mo Default tier (5,000 emails) is a low-risk pilot, and you should step up to Pro at $15/mo (50,000 emails, 50 domains) once two or more client domains are live. IF the client expects a no-code inbox they can reconfigure without a developer, THEN skip inbound entirely, because there is no end-client UI and every routing change runs through the API.”

When is it the right choice?
  • Your delivery team writes TypeScript or calls REST endpoints directly, so the SDK and CLI remove integration work rather than adding a learning curve.
  • A retainer client needs inbound mail parsed into CRM fields or routed to staff inboxes, and the $1,800 Email Intake Starter (16h setup) fits inside an existing support agreement.
  • You are building an AI agent mailbox that must reply inside the original thread, and In-Reply-To plus References header handling is a requirement you would otherwise build yourself.
  • You need catch-all routing across many client addresses on one domain, which the Pro tier's 50 domains covers before you reach Growth at $39/mo for 300 domains.
  • The client's volume is predictable and modest, so the 5,000-email Default tier at $4/mo absorbs the pilot without a procurement conversation.
When should you skip it?
  • The client's marketing or ops staff expect to add routing rules themselves, since inbound exposes no no-code interface for end clients.
  • Your agency has no developer on the account and would need to subcontract every webhook change, turning a $15/mo Pro plan into recurring billable hours.
  • The requirement is outbound transactional sending only, which inbound's receive, parse, and reply-in-thread scope does not address.
  • Client email volume sits far above 200,000 emails/mo, pushing you past the Scale tier at $79/mo into a conversation the published tiers do not cover.
  • You need AI-evaluated guard rules for filtering, which sit on higher plans and add cost beyond the entry tiers you were scoping.
api-management
Open the inbound courseinbound decision recordBrowse the Academy

More on inbound

More for API Management