Before You Hire a 'SaaS Development Agency,' Ask What You're Actually Building

Two companies can search the exact same phrase and want opposite things. One is building a product to sell to hundreds of other companies. The other just wants the spreadsheet everyone secretly runs the business on to stop being a spreadsheet. Most of what ranks for "SaaS development agency" is written for the first company. Most people typing that phrase are the second.

Two different projects, one search term

A multi-tenant product built to be sold needs billing, plans, tenant onboarding, an admin console for accounts you don't control, and support for strangers who signed up on a Tuesday. That's SaaS in the strict sense — software as a sold thing.

Then there's the other kind of project. One company's own tools. A dispatch board. A quoting tool. A dashboard finance actually trusts instead of double-checking against the version someone emails around. Nobody signs up for it from the outside. Nobody outside the company needs to be kept away from anyone else's data, because there is no anyone else.

If it's the first one, we're probably not your studio

Building a sellable product with billing and tenant onboarding is its own pattern, with its own tradeoffs. It deserves a studio that works in that pattern every day, not one that treats it as a side case.

We turn down projects a specialist would do better. That's a conversation we'll have with you on the first call, not the third, and not after a deposit clears.

What we actually build

Custom web applications for a company running its own operations. Role-based access, so a dispatcher and a controller see different things. Audit trails and approvals for the parts of the business that get audited. Reporting built for finance, not for a screenshot in a pitch deck. We migrate the data you already have out of spreadsheets and old systems instead of asking you to start from zero, and we write down how the thing works so your team isn't calling us every time someone new gets hired.

The stack is React, Node, and Postgres. Boring technology, on purpose — it's cheaper to run five years from now than whatever is exciting this year. Typical timeline runs 10 to 20 weeks, from $45,000. Not a floor we advertise and quietly abandon. A real number for a real kind of project, described in full here.

None of that needs billing plans or a signup flow for outside users. It needs to work for the people already on your payroll and survive contact with your actual data, which is always messier than the demo.

Why the two get confused

Conflating the two inflates the estimate for something that never needed it. You end up paying for multi-tenant architecture and an admin console for accounts you will never have, because the framework you got quoted against assumed you were building a product to sell, not fixing the thing your ops team complains about every Monday. That's the difference between scoping your own tool and scoping a company you're not building.

Discovery week settles it

We don't guess which category your project falls into on the sales call, and we don't want you guessing either. That's what discovery week is for: flat $4,800, credited back in full if you continue with us. It ends in a written scope, an architecture sketch, and a fixed estimate. Not a range. Not a "starting at."

Estimates come after discovery, not before. That's why the number holds. A studio that quotes off a first call is either padding the number to survive the unknowns, or getting it wrong and "adjusting" once work starts. Discovery also tells us, plainly, whether what you've described is an internal tool with a fixed shape or something closer to a product that needs a different kind of specialist entirely.

Turning down work is a filter, not a sales line

Saying no costs us money. A studio that never turns anything down doesn't have a filter, it has a sales process. We turn down projects a specialist would do better, or that an existing off-the-shelf product already solves for a tenth of the price. If your quoting problem is already solved by something sitting on a shelf, we'll tell you that instead of building a bespoke version of it at custom-software prices. You hear it in the first call. By the time a deposit clears, it isn't advice anymore, it's a sunk cost we let you make.

You own the code either way

Whichever category your project turns out to be, the terms don't change. You own the code outright from day one. Infrastructure runs in your own cloud account, not ours, through cloud and DevOps work built on your infrastructure. There's nothing to hand back later because there was never anything for us to hold.

If what you need is a system that runs your own business better, that's the conversation to have with us. If what you need is a product to sell to other companies, we'll say so plainly instead of taking the work anyway.