The Business Model Is the Product

Today we’re announcing a new business model for Blue.

Starter is $99 — once. Growth is $299 — once. Scale is $999 — once. Pro is an optional $500-a-year add-on for teams that need an enterprise-level feature set.

That’s the change. What follows is the detail of what you get, how we can sustain it, and — for readers who care — why we think the SaaS subscription model wasn’t right for a company like ours.

The new pricing

Three tiers. One-time payments. You pay once, you own the tier forever.

• Starter is $99 once — 5 users, 5 workspaces, 5,000 records, 10GB of storage.
• Growth is $299 once — 30 users, 25 workspaces, 25,000 records, 100GB of storage.
• Scale is $999 once — 150 users, 100 workspaces, 100,000 records, 500GB of storage.

No renewal. No per-user math. If your team grows, you upgrade to the next tier — which, again, is a one-time payment. The tier you own doesn’t get more expensive because the calendar moved forward.

For context: 30 users on Monday.com at $12/user/month is $4,320 per year. Every year. The same 30 users on Blue Growth is $299. Once.

We put hard caps on the things that actually cost us money, like storage and compute (number of records, automations, webhooks, dashboards, etc.). We don’t have a structural edge on storage — we use the same vendors as everyone else and pay similar prices — so storage is where the tier limits land hardest.

The Pro plan is the point

On top of the base tier, we offer a single optional add-on: Pro, at $500 per year, flat.

Pro is the reason the whole model works.

We didn’t design Pro as a premium tier for enterprise customers who have budget to burn. We designed it as feature parity — at $500 per year — with the Enterprise tiers that competitors charge $20-$40 per user per month for.

Inside Pro you get:

• Scheduled automations — recurring jobs, daily/weekly/monthly triggers
• Conditional automations — if-this-then-that logic for when records meet or stop meeting certain criteria
• Record-level permissions — who can see and edit which rows, down to the field
• Hot Memory Caching — we aggressively cache your data so even large workspaces load instantly
• Up to 150 custom fields and up to 50 dashboards per workspace
• Saved views with team-level sharing
• Bulk actions across views and records
• Audit logs for compliance and governance
• White-label — your domain, your brand, no Blue logo
• Compliance addenda — HIPAA, GDPR, FERPA, financial services

Every one of those features is table stakes at “Enterprise” in the tools we compete with — enterprise tiers that start at $25,000 a year, with minimum commits, annual contracts, and sales-assisted onboarding.

We priced Pro at $500 flat because if you’re doing anything even moderately serious with Blue — running a real CRM, managing a hiring pipeline, operating a real business — Pro pays for itself in week one. In concrete dollar terms, it’s among the best deals in business software right now.

That’s the lever. Base tier is cheap and permanent. Pro is where the value concentrates. As Blue grows, we expect the price of Pro to compound in the customer’s favor — we’ll lower it, or widen it, not raise it.

How we can afford to price like this

You might be wondering how any of this is sustainable. $99 for business software is cheaper than a team lunch. How do we run a real engineering organization on numbers like these?

Part of the answer is that we cut our infrastructure bill by around 85% last year.

For most of Blue’s life we ran on cloud infrastructure — our API on Render, our database on AWS Aurora, the whole managed stack. We paid the cloud tax: premium pricing on managed services, data transfer fees, autoscaling markups. It was fine when we were small. It stopped being fine as we grew.

In early 2026 we migrated Blue off the cloud and onto dedicated servers at Hetzner, in Germany. I’ve written about that migration here. The short version: we pay roughly one-tenth of what we were paying before, and we get an order of magnitude more computing power under the hood. The servers themselves aren’t magic — that’s just what you get when you buy hardware directly and run it yourself, instead of renting it from someone with a 10x markup baked into every line item.

That cost base is what lets us sell Blue at these prices and still run a profitable business. The one-time pricing model doesn’t work if you’re paying AWS-tier infrastructure margins. We took the hard path on infrastructure so we could offer the simple path on pricing.

What about bigger customers

A question I get all the time: how do you make money selling Blue for $299?

The honest answer is that our enterprise tier now makes up the majority of our revenue. The smallest enterprise customers pay $30,000 a year. These are organizations with hundreds of users, complex permission requirements, custom integrations, dedicated support, and compliance obligations we handle under separate contracts.

Enterprise for Blue is a real product with a real sales motion, real service, and real margins.

These customers don’t just value the feature set of Blue, but they value:

• The speed of support with dedicated group chats with engineers and the Blue team.
• The ability to host Blue on dedicated infrastructure and their own databases.
• The ability to work closely with us to shape the future of the platform and the roadmap.

But we didn’t want growing the enterprise side to mean abandoning the other end.

The same product that runs a $30K-a-year enterprise account also runs a five-person agency, and both customers benefit from the same underlying platform. We’ve had a strict policy of one codebase for all customers since the beginning, so we’ve never branched the codebase off for any Enterprise customer. That’s why we can offer Pro at $500 per year for all customers, regardless of their underlying plan.

Pricing Blue out of reach for the agencies and nonprofits and small businesses that have been with us for years would have made us worse at serving enterprise too, because the product wouldn’t get the breadth of use that stress-tests it. Right now, we get hundreds of emails a week on product ideas, bug reports, and suggested improvements. We read all of them, and we ship hundreds of changes per month — an average of 22 commits to production per day.

There’s a second-order effect too. By putting the Pro feature set — which is basically the enterprise feature set — in reach of every customer at $500 a year, we get thousands of users stress-testing features that historically only enterprise accounts would have touched. Scheduled automations, conditional workflows, record-level permissions, audit logs, white-label deployments — these used to get feedback from a small user base by definition. Now they get the same scrutiny as the rest of the product. The enterprise side of Blue gets better faster because thousands of non-enterprise customers are running the same code.

The tiered one-time model plus Pro gives us both. Enterprise customers get what they need at the price they expect. Small teams get a tool they can afford to own outright with optional enterprise-level features if they want. And we aren’t forced to optimize the product for one group at the expense of the other.

I don’t owe anyone a return

There’s one more piece to why this works, and it’s the most personal.

Earlier this year I bought back the last of my minority investors. Blue, the company, is now 100% mine.

That matters because it means nobody is waiting on a return.

• There’s no board pushing for quarterly growth.
• There’s no investor who needs a liquidity event by a certain date.
• There’s no shareholder letter that has to explain why revenue-per-customer has flattened.
• I don’t need Blue to triple in value over the next three years.
• I don’t need to exit.
• I don’t need to keep the company pointed at any particular number.

What I need is to make a good living, build something I’m proud of, and keep our customers happy enough that they tell their friends.

That’s the whole set of obligations. It happens to be a set that aligns very cleanly with selling durable software at honest prices to people who actually use it.

This isn’t a moral claim — plenty of people with investors do honest work. It’s a structural one. The shape of who owns a company shapes what the company optimizes for.

This model isn’t an experiment

Roughly 14,000 of our customers bought Blue on AppSumo over the past few years as a one-time purchase. They’ve been using it exactly like this — pay once, own it — for years. They’re happy. They use the product. They recommend it. The model works. Some of them even became Enterprise clients.

What we’ve done now is generalize it. One-time payments aren’t a promotional mechanic tied to a specific marketplace anymore. They’re how Blue is sold. They’re how Blue will be sold going forward.

Why we did this

The business model a software company picks decides what you get.

It decides which features ship first. It decides who the company answers to. It decides how it treats you when your renewal is three days away and you’re trying to decide if you still need the tool. It decides whether the price goes up every year, who has power over whom, and what happens to the product when growth slows.

Most people think business models are boring finance details. They’re not. They’re the single most important design decision a software company makes — and they’re the one customers almost never see.

When I launched Blue eight years ago, we charged $30 per month per organization. No tiers. No usage limits. $30/mo for the whole thing.

I picked that number out of a hat. I looked at a few competitors, averaged something, rounded down, and called it done. There was no model, no unit-economics spreadsheet, no careful thought about CAC (Cost of Customer Acquisition) or LTV (Lifetime Value) or any of the things founders are supposed to think about. Thirty bucks felt fair and I wanted to ship.

The unit economics didn’t work. At $30/mo per organization, it took months to recoup what we were spending to acquire a customer. Support costs ate into the margin. Cloud server costs ate into the margin. A customer with 50 users paid the same $30 as a customer with 2 users — so the small customer was effectively subsidizing the big one, while we absorbed the infrastructure bill. I wasn’t losing money fast, but I wasn’t building anything sustainable either.

So we moved to per-seat pricing. $7 per user per month. Like everyone else. That fixed the worst of the economics. But it joined Blue to the same business model every other SaaS tool uses, and the model shapes the product whether you want it to or not.

Here’s what the per-seat, per-month subscription model does to the companies running it.

The average B2B SaaS company spends somewhere between $600 and $2,000 to acquire a single customer. Ads, sales reps, content marketing, conferences, SEO, email sequences — acquisition is expensive, and it’s expensive on purpose, because the math is supposed to work out over time.

That customer then pays you some amount per month. If the payback period is, say, twelve months, a customer has to stick around for a full year before the company breaks even. Everything after that is profit.

This is called the SaaS J-curve. Acquisition cost is the hole; retention and expansion are what fill it back up and then push above the line. Churn before the payback period ends and the company lost money on that customer. Churn right after and the company made nothing.

There are two ways to work inside that math: make the hole smaller, or make the recovery steeper.

Making the hole smaller is hard. Ads get more expensive every year. Competition drives up CAC. SEO takes years to compound.

So most SaaS companies reach for the other lever: steepen the recovery. Raise prices. Add tiers. Push users into bigger plans. Gate features behind “Enterprise.” Renegotiate at renewal. Add usage-based line items. Quietly bump the per-seat price every year. This is the playbook. Every tool in your stack is doing some version of it, whether you’ve noticed or not.

The subscription-per-seat-per-month model isn’t a pricing mechanism. It’s a scoreboard. It’s how the company measures itself. And when the scoreboard says “seats and expansion revenue,” that’s what the company optimizes for — not the product, not the customer’s actual problem, but the scoreboard.

Once you see this, you can’t unsee it. Every frustration you’ve had with a SaaS vendor — the upsell emails, the feature you had last year now locked behind a more expensive tier, the price hike with thirty days’ notice — isn’t the company being mean. It’s the business model working as designed.

One qualifier before I close: I don’t think venture capital is evil and I don’t think SaaS subscription pricing is a scam. Plenty of businesses genuinely need venture capital — they’re risky, they require years of upfront work, they build markets that don’t yet exist. Software is a bit different now, especially with AI tools accelerating what a small team can build, but that’s a shift, not a judgment. This post isn’t against anyone else’s model. It’s an explanation of ours.

Onward

If this sounds like a step backwards from “how software is supposed to work” — maybe “how software is supposed to work” was always the specific model that served a specific generation of investors. It isn’t a law of physics. It’s a design decision.

We made a different one.

This change lands alongside a complete rewrite of our legal foundation, which formalizes a lot of what I’ve described here — how we use data, how we handle enforcement, how long we retain things, and what we won’t do. The two go together.

See the new pricing and pick a tier. If you’re already on a subscription, your current plan is grandfathered — we’ll reach out separately about what that means for you.

Eight years in, Blue is still a calm, focused, independent company. The business model I just picked is how I plan to keep it that way.

— Manny