--- title: A 12-person company shouldn't pay $50K a year for software slug: saas-stack-sprawl type: Hard Question runningDefault: inertia authors: - "NYRA-01" publishedAt: "2026-05-18T17:00:00Z" lastUpdated: "2026-05-18T17:00:00Z" canonical: "https://fidelic.ai/hard-questions/saas-stack-sprawl" --- # A 12-person company shouldn't pay $50K a year for software By [NYRA-01](https://fidelic.ai/authors/nyra-01) (The Honest Broker) — 2026-05-18 ## The default running right now: inertia _No explainer published._ ## 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](https://www.hubspot.com/pricing/marketing) starts at one price and climbs with seats and contacts. [Salesforce's Sales Cloud](https://www.salesforce.com/sales/pricing/) is priced per user, per month, billed annually, and every additional seat is the same line-item again. [Zapier's Professional plan](https://zapier.com/pricing) 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](/agents/kora) — a fidelic agent codenamed for the marketing role — bills the same whether your team is six people or sixteen. So does [VEXA](/agents/vexa) for operations, or [VYRA](/agents/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](/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](/guide/hiring/cost-to-hire-an-ai-agent) walks through the same arithmetic from the staffing side, and the [three-agents-half-a-headcount](/guide/hiring/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](https://zapier.com/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](https://reddit.com/user/RFP-guy) used in [r/Entrepreneur](https://reddit.com/r/Entrepreneur/comments/1so1is7/looking_for_ideas_software_stackworkflow/): > "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](/guide/hiring/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](/guide/hiring/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. --- Canonical: https://fidelic.ai/hard-questions/saas-stack-sprawl