Pricing
Priced by deployments.Not by traffic.
You pay for active customer environments. Calling your capabilities a million times costs the same as calling them once.
Every plan is free during launch.
Nothing below is charged today. Run a real customer deployment end to end, across every destination, before anybody asks you for a card. These are the prices when billing begins.
Count installations, not platform coverage.
One installation. One environment.
3 active installations3environments
Developer
Prove it works with your own product.
- Use any Available destination
- MCP, OpenAPI and repository sources
- Asana, Atlassian, ChatGPT, Claude, Cursor, Google Chat, HubSpot, Linear, Notion, Salesforce, ServiceNow, Slack, VS Code and Zendesk
- Hosted installation portal
- Validation and health monitoring
- Engagement briefs, graded on every publish
- Customer vocabulary and a generated user guide
Startup
Your first wave of enterprise customers.
- 25 active customer environments
- Everything in Developer
- Alert webhooks and email
- API keys for your own pipeline
- Adoption and unmet-request reporting
- Full audit history
Growth
Deployment as a repeatable motion.
- 150 active customer environments
- Everything in Startup
- Your customers' own databases as a source
- Generated adapter pull requests
- Priority support
- Custom deployment targets on request
Enterprise
Your own tenancy and terms.
- Unlimited customer environments
- Security review and DPA
- SAML, OIDC and enterprise SSOon request
- Dedicated infrastructureon request
- Roadmap input on new destinationson request
An environment is one customer, one product, one destination. It counts while it is installed. Disconnected environments do not.
If you use our AI, that part is charged on usage
about a cent a questionPoint a product at your own assistant and this never applies: the inference is between you and your provider, and Meetext charges nothing for it. Use the model we run instead and you pay what the model provider charges us, plus a small margin, on the questions actually asked.
Separate from your plan because it is the only cost here that moves. Model prices changed twice in the months before this page was written, and one of them is scheduled to double again. A fixed tier covering a moving cost either overcharges most people or quietly loses money on a few.
The Meetext Agent in your dashboard is included on every plan and runs on the same model, charged the same way on what it uses. Every answer it gives shows what it cost.
Every plan carries a monthly limit so a runaway cannot become a surprise. When it is reached our model stops answering and says so, and anything pointed at your own endpoint keeps working.
The economics of software FDEs
How much FDE work could
your team reclaim?
Estimate the engineering capacity spent getting customers live and keeping them working. Start with your rollout; adjust the underlying costs when you need to.
High-complexity example · $400,000/year engineering cost. Adjust assumptions to match your team.
Distinct platforms across your customer base. Explore destinations →
One-time work across all selected destinations, not per destination.
One installation per customer · Loaded engineering cost is adjustable below.
Estimated savings, year one
$3,308,889 DIY engineering
− $424,222 your engineering with Meetext
− $10,188 Growth software / year
− $4,500 AI usage / year.
- Ongoing savings / year
- $887,979
- Engineering capacity released, year one
- 12,981h
- Estimated plan
- Growth$849/mo · annual billing
Illustrative capacity value, not guaranteed cash savings. Includes the engineering you still do, the software and an AI usage estimate. Every assumption below is editable.
Start with a real deploymentHow the estimate is calculated
First year = setup + onboarding (including each customer's security review) + a year of operations (upkeep, support, incident triage, and building what customers ask for). Savings = in-house labor − remaining labor with Meetext − software − AI usage. Both sides use the same hourly cost. Ongoing estimates cover the same customer base, without repeating setup or onboarding. Training, third-party fees and tax are excluded.
Salary + overhead: $222/hour across 1,800 productive hours per year.
Optional: installations beyond one per customer. 75 total; used to check plan limits.
| Work | Build in-house | With Meetext |
|---|---|---|
| Build / setup · once | 1,960h | 16h |
| Customer onboarding · once | 7,200h | 225h |
| Upkeep, support, incidents and requests · each year | 5,730h | 1,668h |
| Total · first year | 14,890h | 1,909h |
Questions
Answers before you ask.
Still unsure whether it fits? Send us your setup and we will tell you honestly.
You need three things and only one of them is the assistant. An app registered with Slack, Teams or Google Chat and reviewed by them; a way to turn an incoming workspace id into the right customer with the right credentials, which must never be wrong once; and per-customer access to your own product, so the assistant answers as that customer rather than as you. Meetext provides the second and third and carries the message both ways, so what you build is the assistant. Your model, your prompt and your name on the bot, with nothing identifying Meetext to the person asking.
If you are asking because every enterprise customer needs weeks of engineering before they can use what they bought, a hire will solve it for the next two or three customers and then you will need another one. The work is roughly the same each time: the same OAuth flow, the same security questionnaire, the same validation, the same upgrade, against a different tenant. That part is a software problem. Hire for the judgement work, which is understanding what a customer actually needs, and make the repetition somebody else's infrastructure.
No. Connect an OpenAPI document, discover supported routes from a repository, or use a customer's database on eligible plans. Each source produces capabilities you approve before exposing them. Destination-specific permissions and setup requirements still apply.
Capability results are masked under your customer's policy, then pass through the hosted endpoint in memory to reach the destination. They are not stored. Execution is audited by argument name only and never by value, so Meetext records that a search happened and not what was searched for. A call waiting for a person's approval keeps its arguments only until it is decided. Credentials live in a secret manager under a name scoped to a single customer environment and are never shared between two customers.
Asana, Atlassian, ChatGPT, Claude, Cursor, Google Chat, HubSpot, Linear, Notion, Salesforce, ServiceNow, Slack, VS Code and Zendesk. See the integration directory for each destination's capabilities and setup requirements.
One customer, one product, one destination. It counts while it is installed. Disconnected environments do not count, and calling your capabilities more often never changes the bill.
You build the product.
We take it from here.
Connect a source, approve what ships and send your customer an install link. 2 customer environments free. No card required.