$ stayupfront --pricing
[ prices land when the beta does ]

No per-seat. Add the whole company.

We haven't published prices yet — on purpose. Here's what we've already decided we won't do.

This isn't a "contact sales" page. It's the list of pricing decisions we've already made, before the numbers are even locked.

$ stayupfront --principles

What we're committing to

Five decisions we've already made about how StayUpfront is priced — even though the numbers aren't locked.

1

No per-seat pricing.

Add the whole company. The engineer who shipped the change, the founder who sold the deal, the ops person who owns the runbook — they all belong in the tool, and not one of them costs you a seat. This is the one we'll defend.

And Sue — the AI inside StayUpfront — doesn't take a seat either. You don't add her to your bill; she's already here.

2

One bill, per organisation.

Billing follows your organisation, not your headcount — one account covers the whole team, and most teams only ever need a single organisation. You're not stitching together per-person licences; you're paying for the org.

3

The whole suite is included.

Support, incidents, monitoring, status pages, customer portals — all of it comes with your account. There are no modules to buy and nothing good held back for a higher tier. You get the tool, not a starter slice of it.

4

Usage and limits are the scaling axis — not headcount.

The things that cost real money or real resources — AI calls, SMS, how many portal pages you build — are what the pricing follows. The defaults are generous; when you genuinely outgrow one, you extend that single limit for a price. We're setting those limits with our first customers, which is part of why the numbers aren't up yet.

5

When the numbers are locked, they go here.

No "contact us to find out." When the model's set, the prices get published on this page, in public, for everyone to read. And if they ever change, we'll say so ahead of time.

$ stayupfront --why-no-per-seat

Why we won't charge per seat

Per-seat pricing is the default in the support, status, and incident world. For a small B2B team it's also the killer cost: every person you add multiplies the bill, so the price of the tool tracks the size of your team instead of the value you get from it.

Worse than the cost is what it does to behaviour. You start sharing one login. You decide not to give the new hire access because it's another line on the invoice. You treat customer ops as a one-person job because one person is what you're paying for. None of that is good for your customers — and all of it is the pricing model talking, not you.

Customer ops isn't a department for a team our size. When something breaks, the person who can actually fix it might be the engineer who shipped the change or the founder who sold the deal — not whoever happens to hold the support seat. Pricing that taxes you for inviting them is pricing that fights the way small teams actually work.

There's an honest reason underneath the principle, too. StayUpfront's data model is built around your organisation and your products — not around individual users. There's no seat to count. Charging per seat would be a pricing layer bolted on top of an architecture that was never shaped that way. We'd rather the pricing match how the product is actually built.

$ stayupfront --not-claiming

What we're not claiming

A short list of things this page deliberately doesn't say, so you know the principles above are bounded and considered — not marketing.

We're not claiming to be the cheapest. Depending on how much you use, we might not be — and we'd rather be honest than promise a number we haven't set. The claim is aligned, not cheapest.

We're not claiming "unlimited everything." AI and SMS cost real money per use, so the defaults are generous, not infinite. "Unlimited" would be a lie we'd have to walk back the first time someone's usage spiked.

We're not claiming the prices are locked. They aren't yet. What's locked is the shape — no per-seat, usage-based, published here when ready. The numbers come with the beta.

$ stayupfront --signup
[ private beta · shaping the product ]

Prices land when the beta does. You'll see them first.

The numbers get set with the people who actually use the product — that's why they're not up yet. Private beta is a few weeks out, and I'm letting people in a small group at a time. If you're in early, you'll see the pricing before the rest of the market does — and you'll have a say in whether it's right.

Drop your email

Direct email from Rob when your slot's ready. No drip sequence.

I could have put a price on this page. A made-up number would have looked more finished. But I'd rather set the price with the people who actually use the product than guess at it now and quietly change it later. So the numbers aren't here yet — the principles are. When they land, they'll land right here, in public. And the one I'll defend whatever they turn out to be is no per-seat: I've watched too many small teams ration access to their own tools, and I won't build pricing that punishes you for inviting the right person.

— Rob Gough, Founder