When does the per-seat fee from an outside ACA quoting platform become the engineering budget for a private one? Most agency principals do not know the number until they get the invoice for a team that has grown faster than the contract anticipated.
Key Takeaways
- Building a private ACA quoting tool that connects to the CMS Marketplace API and returns usable plan data is a realistic 8 to 12 week engineering project at minimum viable scope. Not a weekend project and not a $5,000 vendor configuration.
- The CMS Marketplace API is free to access for plan data and subsidy estimates. EDE certification adds months of compliance work if the agency needs enrollment from the private platform, not just quoting.
- The break-even calculation depends on agent count, feature requirements, and how much of the cost is recurring. Per-seat fees from platforms like Quotit and Connecture compound annually; a private build has a one-time cost plus ongoing maintenance.
- Most agencies that seriously evaluate the build option end up in one of two places: a private deployment through an engineering firm that already knows the CMS API, or a decision to continue with shared-infrastructure tools at their current scale.
- The largest ongoing cost of a private tool is not the initial build. It is maintenance when CMS updates plan data formats or the API specification changes mid-year, which happens every plan year.
The build conversation most agencies avoid until too late
The agencies that do this math usually start by adding up what they pay Quotit or Connecture per agent per year, then multiplying by the number of agents they expect to have in three years. The number gets large enough to prompt a conversation with a developer friend or an engineering firm. That conversation typically ends in one of two places: a realistic scoping document that doubles or triples the imagined build cost, or a private deployment with a team that already knows the relevant APIs.
The agencies that skip this conversation and just build often learn the same lesson on the far side of the build. A functioning quoting tool delivered in week 14 is not the end of the cost. It is the beginning of the maintenance cycle. For a realistic picture of what the growth inflection point looks like before it becomes a systems problem, read how to scale an ACA agency from 1 to 10 agents before AEP.
What building actually means
A minimum viable ACA quoting integration has three layers. The first is the CMS Marketplace API connection: authentication, plan data retrieval, and subsidy calculation. CMS provides this API free to access. The second layer is the quoting interface: input forms for ZIP, household size, ages, and income, and a results view that presents plan options in a way brokers and clients can act on. The third layer is everything the agency needs beyond a bare quote: PDF generation, branding, client intake, CRM integration, and any proprietary ranking logic.
Layer one takes roughly 2 to 4 weeks for a team familiar with federal API authentication and health data formats. Layer two takes another 3 to 6 weeks depending on design requirements. Layer three varies from a few weeks for a minimal implementation to months for a complete platform. The floor for a usable private build, including layer one and a functional layer two, is 8 to 12 weeks with experienced engineers.
Enrollment is a separate question. Completing an enrollment inside a private platform rather than routing the client to Healthcare.gov requires EDE certification, which is a CMS compliance process that adds months to the timeline and ongoing audit obligations. Most agencies that build a private quoting tool stop short of enrollment and complete that step on Healthcare.gov. For the full EDE picture, read what is EDE certification and is it worth it for solo agents.
The build vs. buy decision by agency profile
The decision depends primarily on agent count, workflow requirements, and whether the agency needs capabilities that shared tools do not offer. The table below covers the five profiles that come up most often in this conversation.
| Agency profile | Recommended path | Reason |
|---|---|---|
| Solo agent or small team, under 100 clients | Shared free tool | Engineering overhead and maintenance burden exceed any per-seat savings at this scale. |
| 5 to 20 agents, standard ACA quoting needs | Shared tool (paid or free tier) | Volume math does not yet favor a private build unless workflow customization is the primary driver. |
| 20 to 50 agents with custom intake forms, branding, or proprietary scoring | Private deployment | Per-seat fees begin to compound; custom workflow requirements do not fit shared-tool configuration options. |
| 50+ agents, insurtech, or call center with API requirements | Private build | Custom branding, SSO, API access, and proprietary data are table stakes at this scale. Shared-tool TOS typically does not cover API resale or white-labeling. |
| Resale platform or white-label product to offer to other brokers | Private build | Shared-tool terms of service do not permit white-labeling or resale. This use case requires a private platform. |
The maintenance reality most build conversations skip
CMS updates plan data formats, API endpoints, and subsidy calculation parameters every plan year. The update schedule is published, but the actual API changes sometimes arrive closer to the plan year change than the announced timeline suggests. A private platform built in February needs to be updated before November, every year, or it breaks during AEP.
The agencies that learn this the hard way are the ones that built in year one without establishing a retained engineering relationship. By October of year two, they are scrambling to find a developer who understands CMS API authentication and plan data formats on a 6-week deadline. The agencies that plan for ongoing maintenance as part of the original build budget are the ones whose tools survive into year three.
Mid-year API changes also happen, typically when CMS issues corrections to plan data or updates the eligibility calculation logic. A solo engineering project managed internally, without a team that monitors the CMS developer changelog, tends to catch these changes when something breaks rather than when the notice goes out.
Where QuoteTurbo fits in this decision
For most ACA agencies under 50 agents with standard quoting requirements, QuoteTurbo provides live CMS Marketplace data, APTC and SLCSP math, and PDF exports at no cost per quote and no per-seat fees. It is built and maintained by Devkrest, a custom software engineering firm. The product is not advertising-supported, does not sell data, and does not take carrier kickbacks.
When the agency has grown past what shared infrastructure supports, Devkrest builds private ACA, EDE, Medicare, and ICHRA platforms. That is a separate engagement, not a destination that using QuoteTurbo leads to. Brokers can use QuoteTurbo for the life of their agency without ever engaging Devkrest for a private build.
FAQ
Questions agency principals ask when evaluating whether to build a private ACA quoting tool.
How long does it take to build a minimum viable ACA quoting tool?
A working integration with the CMS Marketplace API that returns plan data, runs a subsidy estimate, and presents results in a usable interface is an 8 to 12 week project for an engineering team already familiar with the API. Starting from scratch with an unfamiliar team, scoping, procurement, API onboarding, and first working build typically takes 4 to 6 months. This is before any broker-facing UX work, PDF generation, or CRM integration.
What does the CMS Marketplace API provide for free?
The CMS Marketplace API provides plan data, premium estimates, and subsidy calculations based on household inputs including ZIP code, household size, ages, and estimated income. It does not include enrollment. To complete an ACA enrollment through a private tool rather than routing the client to Healthcare.gov, the platform needs to be EDE-certified, which is a separate and more involved process.
Is EDE certification required for a private quoting tool?
No. EDE certification is required for enrollment from a private platform. Quoting, subsidy estimation, and plan comparison can all be done via the CMS API without EDE certification. Most agencies that build a private quoting layer do not need EDE if they complete enrollment on Healthcare.gov after the quote conversation. EDE is relevant for platforms that want to keep the client entirely within their own interface through final enrollment.
What is the realistic ongoing maintenance cost after the build?
CMS updates plan data formats, API endpoints, and subsidy calculation parameters annually, typically ahead of each plan year. A private platform also needs to be maintained through any mid-year API changes CMS issues. Agencies that build a private tool without a retained engineering relationship often find themselves unable to update for a new plan year at the worst possible time, around October and November before AEP. Budget for ongoing engineering support proportional to the complexity of the build.
When does QuoteTurbo make more sense than building a private platform?
For most ACA agencies under 50 agents with standard quoting needs, QuoteTurbo provides live CMS Marketplace data, subsidy math, and PDF exports at no cost per quote. The build conversation becomes relevant when the agency needs proprietary branding that cannot be configured on a shared platform, custom intake workflows, API access for integration into other systems, or white-label capabilities. QuoteTurbo is built and maintained by Devkrest. Private builds for agencies and insurtechs are a separate engagement; using QuoteTurbo does not require or lead to one.
