21 November 2026
In short
What does it take to build a SaaS product in Birmingham?
Turning an internal system into a SaaS product in Birmingham usually means selling to firms you compete with, which raises liability and regulatory questions early. GTX Digital builds tenancy, billing and onboarding before any new feature, because those three decide whether it becomes a business.
- The second customer is the test. The first one is you.
- Selling to peers means selling to people who will compare notes.
- Decide what you are liable for before the first contract.
- Charge for something the customer can count without asking you.
- Sell it by hand to two firms before building anything.
Think this applies to your business?
We will tell you straight whether it is worth doing, what it would take, and what we would do instead if it is not.
Thinking about selling your internal system? Book a technology review. We will tell you whether it is a product or a very good internal tool with ambitions.
A lot of Birmingham firms are sitting on software they built for themselves and suspect is worth money. Sometimes it is. Here is how to find out before you spend.
It is not a product until somebody else's process fits it
Your internal system fits your firm perfectly. That is why it works, and it is exactly what makes it hard to sell.
Two firms doing the same work do it differently. Different file-opening rules, different approval thresholds, different names for the same stage. Your software has your version of all of that baked in, usually in places nobody documented.
So the question is not whether other firms have your problem. They do. It is whether they have it in a shape your software already fits, and the only way to find out is to put it in front of one.
Sell it manually first. Find two firms like yours, set them up by hand, and charge them something real. Two months of that teaches you more than any amount of planning, and what it usually teaches is which of your assumptions were house style rather than professional practice.
## You will be selling to people who compare notes
This is what makes a professional-services product different here, and it changes how you behave.
Birmingham's professional community is large but well connected. Your first ten customers will know each other, sit on the same committees and talk at the same events.
That cuts both ways. A product that works spreads faster than any marketing. A product that loses somebody's data is finished before you have finished apologising.
It also means your worst customer sets your reputation. The firm that gets poor support will mention it, and the mention will travel further than it would in a bigger market.
Decide what you are liable for
A question that does not arise when software is internal, and arrives immediately when it is sold.
| The question | What "ready" looks like | What loses the deal |
|---|---|---|
| If the tool is wrong, who is responsible? | Stated plainly in the contract, with a cap | A conversation nobody has had |
| Are you processing their client data? | A data processing agreement already drafted | "We'll sort that out later" |
| What is your uptime commitment? | A number, measured, with what happens if you miss it | "It's been fine so far" |
| What happens if you stop trading? | An export they can run themselves, any time | Silence |
Have those written before the first conversation. The firms that win this work are not the ones with the best answers; they are the ones who have the answers ready.
Our SaaS product development page covers how we stage this, and the Birmingham page for it has the local version.
The three things that are not features
The features exist. You have used them for years. The budget goes somewhere else entirely, and none of it demos well.
Separation comes first: one customer's data kept from another's, enforced at the data layer rather than remembered in each query. "We always add a filter" is a convention, and conventions get forgotten by whoever joins next year.
Then money. Subscriptions, upgrades, failed cards, the awkward credit, VAT. It is dull, unforgiving, and where trust is lost fastest.
Then getting a firm started without you. If a new customer needs six weeks and a developer, you have bought yourself a job rather than built a product, and you will find that out at customer four rather than customer two.
## Your buyers can estimate your costs
This is the awkward part of selling to peers, and it is worth planning for.
A firm that runs its own systems has a rough idea what yours costs to operate. Price purely as a markup on cost and somebody will say so, usually in a negotiation.
So price against what the problem costs them instead. Hours written off, work redone, the compliance step that delays a bill. That number is larger than your running cost and it is the one worth talking about.
Then pick what you charge for, and pick something the customer can count without asking you. Per matter or per job works because they already count those. Per user is simple, and it quietly punishes them for giving access to more of their staff.
Expect to be too cheap at first; almost everyone is. Raising a price for new customers is easier than explaining an increase to the firms that backed you early, so leave yourself room.
## It changes the firm, not just the software
Selling software is a different trade to the one you are in.
You will need someone who handles customers, a way to take money monthly, and a tolerance for requests that would suit one firm and nobody else.
That last one is the hard discipline. Every product that drifts back into bespoke did it by saying yes to the fourth customer's special case. Ask for it as configuration, or say no.
There is a partnership question too. Time spent on the product is time not spent on fee-earning work, and the firms that do this well decide up front whose time it is and how it is counted.
What the first year actually looks like
- Two firms paying for a manual version, within three months.
- Separation, billing and self-serve onboarding built before any new feature.
- The liability, data and exit answers written down before the first contract.
- A support commitment you can keep during your own busy season, not a generous one you cannot.
- A roadmap decided with customers in the room rather than in a partners' meeting.
If the system you would start from is held together with workarounds, fix that first. Legacy software replacement in Birmingham covers doing it without stopping the day job, and customer portal development in Birmingham covers the simpler version if what you need is a window rather than a product.
We work across professional services and manufacturing businesses here, and our work in the city is on the Birmingham page. If you want a straight answer about whether yours is a product, ask us.
Common questions
Is our internal tool actually a product?
Find out by selling it by hand to two firms like yours. If they will pay something real for a clumsy manual version, you have a product.
What do peer firms ask before buying?
Where their data sits, who can see it, what happens if they leave, and what you are responsible for if it is wrong. Have the answers written down before the first conversation.
How should we price it?
Charge for something the customer can count without asking you. Per matter, per user or per site works when they already measure it.
Next step
Start with a technology review, not a proposal.
A short, structured conversation about where your systems are costing you time, margin or growth — and what the realistic options are. No pitch deck.