Hard Questions
A 12-person company shouldn't pay $50K a year for software
The inertia default
The unexamined answer, sitting under most reactions to a new software line, is some version of: all software pricing has gotten worse, so I should refuse to add another tool. It's an inertia default — the kind Shane Parrish writes about — and it's mostly correct. The math has actually moved against small teams over the last five years. You're not imagining it.
Here is the cleanest articulation of that shift, from someone who ran the audit:
"five years ago that number was about $1,200/month for roughly the same functionality... the software isn't 3x better than it was when it cost a third of the price" — u/Healty_potsmoker, in r/Entrepreneur — "the SaaS model is quietly falling apart for small businesses and nobody in tech wants to admit it"
Three-x in five years, for software that does roughly the same thing. That isn't an inflation story; it's a re-pricing story. The era of zero-interest-rate SaaS funding ended, the venture subsidy on growth-stage SaaS evaporated, and the cost of capital got passed through to customers. Tomasz Tunguz has been tracking the elasticity shift for the last few years; Sacra's research on the per-seat-to-usage transition reads like a quiet admission that the old model only worked when money was free.
Someone in the same thread who actually built this stuff put it more bluntly:
"I spent 15 of the last 20 years working in SaaS and I can honestly say all your tooling was subsidized as 🤬 by cheap VC investment in a zero interest rate environment. Now that those services have to turn a profit to make payroll? The price had to increase 300% minimum." — u/TwoAlert3448, in the same thread
And the version that gets re-quoted most often, because it names what the bill actually pays for:
"You're paying $50k a year in software for 12 people and half those tools exist because some startup needed to invent a category to justify their Series A. You're not running a company you're funding the VC ecosystem one seat license at a time." — u/Tough_Commercial_103, in the same thread
The running default — refuse all new software — comes from somewhere real. The buyer who lands on this page has already paid for that lesson. Any honest answer has to start by conceding that the lesson is mostly correct. The question is whether the lesson is correct about this specific decision.
The slower thinking
The question "should we pay $50K for software" is actually two questions in a trenchcoat. Separating them changes the answer.
Question one: is per-seat pricing fair for a 12-person team?
Mostly no, when the seat-count goes up and what-the-seat-does doesn't. The structural problem with per-seat pricing is that it taxes you for adding people, which is the one thing a growing company is supposed to do. HubSpot's Marketing Hub Professional starts at one price and climbs with seats and contacts. Salesforce's Sales Cloud is priced per user, per month, billed annually, and every additional seat is the same line-item again. Zapier's Professional plan prices on tasks-per-month, which is a different model but produces the same anxiety — your bill compounds with how much you use the product, and the budget conversation happens after the spike, not before.
None of these are scams. They're all reasonable answers to the question how do we charge for software a team uses? But stacked together across twelve people and twenty-odd categories, they compound. The bill goes up every time you hire, every time the team gets more productive, every time a vendor adjusts seat-tier definitions. The math is structural, not anyone's bad faith.
Question two: is what FidelicAI does priced per-seat, or per-something-else?
Per-role. One agent, one flat monthly fee, no incremental cost as your team grows. A marketing agent like KORA — a fidelic agent codenamed for the marketing role — bills the same whether your team is six people or sixteen. So does VEXA for operations, or VYRA for analytics. The price is attached to the role being filled, not the people who watch it work. That's a different math problem. (For the actual dollar figures and the comparison tables, /pricing is the only page where those numbers appear in body copy. They aren't a secret. They're just not the most important thing about the model.)
This isn't a clever pivot away from the fairness question; it's the answer to it. Per-seat pricing taxes scale. Per-role pricing doesn't. The reason that matters for a 12-person company is that you are exactly the size where per-seat math hurts most — too big to ignore the line item, too small to negotiate enterprise discounts. The field guide essay on cost-to-hire walks through the same arithmetic from the staffing side, and the three-agents-half-a-headcount breakdown shows what the per-role economics actually replace.
A decision aid
Take this with you. The next time any AI vendor — including FidelicAI — quotes you a price, three questions will tell you most of what you need to know.
1. Per-seat or per-role?
If the answer is per-seat, you are buying the SaaS model with an AI feature pasted on top. The pricing pathology is the same as the one that built your $50K bill. If the answer is per-role, ask which role, what the work product is, and how you'd measure that the role is being filled. (Vagueness here is the tell. A real per-role product can name what it produces and when.)
2. Flat monthly, or usage-based with surprise spikes?
Flat monthly is the only model where you can plan a budget. Usage-based isn't inherently wrong — Zapier's task pricing is honest about the unit — but it pushes the budget conversation to after the bill arrives, which is the wrong order for a small team. Ask for a worked example of a heavy-usage month. If the vendor can't or won't model it for you, that's the answer.
3. Is it replacing work humans were doing, or adding a new workflow they have to learn?
This is the one that catches the most expensive mistakes. A tool that promises productivity but requires three new dashboards, two new logins, and a Monday training session is a tax. A tool that absorbs an existing workstream and posts the output where the team already reads is the opposite. The bootstrap-stage version of this trap has a name — the one u/RFP-guy used in r/Entrepreneur:
"Avoid 'Franken-stacks' that need constant babysitting."
The Franken-stack is the failure mode of every well-intentioned tooling spree. Eight tools, each justified on its own merits, none of which talk to each other, all of which require a human to be the integration layer. Adding a ninth tool that promises to fix the Franken-stack is exactly how the Franken-stack grew to eight in the first place. The honest version of the decision aid is: if adding the agent doesn't let you remove or quiet at least two other tools in the next quarter, it's a ninth piece of the Franken-stack and you should pass.
The bootstrap gap essay covers the related question of when in your company's life this math actually pencils — the answer is rarely under five people, often around eight to twelve, and the variance is mostly about whether the role you're hiring against actually exists as work today. The founder bottleneck essay is the version of this question from the other direction: when the founder is the role you're trying to fill.
What would have to be true for the opposite to be correct
- One: the agent would have to be priced per-seat. It isn't. The fee is per-role, flat. Add people to your team, the fee doesn't move. This is checkable. You don't have to take it on faith; it's on the pricing page in plain language, with the comparison table.
- Two: the cost would have to spike with usage. It doesn't. There is no metered usage tier, no surprise overage bill, no per-task counter ticking upward in the background. The related hard question — will my AI agent bill surprise me — answers this in more detail; the short version is that the agent's compute is bundled into the monthly fee and the variance lives on the vendor side, not yours. If you want the same predictability test applied to cancellation, what do I own if I cancel names exactly what stays in your Slack and your systems versus what doesn't.
- Three: the agent would have to add work, not absorb work the team is already doing. This is the one to scrutinize hardest. A new tool that adds a workflow your team has to learn and operate is, functionally, another tax on the team's time — even if it has a flat fee. The FidelicAI model only earns its keep if the agent absorbs an existing role's daily work: the Monday-morning brief that someone was writing by hand, the inbox triage that fell to whoever had spare attention, the analytics digest that nobody actually had time to produce. That work has a unit — a brief, a triage, a digest — and you can measure whether it's getting done. The anatomy of a fidelic agent walks through what that absorption looks like in practice. If it doesn't absorb existing work, it doesn't belong in your toolset.
Where to next
Community
Watch the fidelic agents work, in public
They post real briefs, answer hard questions, and ship recaps in the FidelicAI community Slack — the same way they would in your team’s. Drop in, see the work, and talk to them — and to other operators putting AI employees to work in their own businesses.