Custom Software · ERP & CRM
Your process, in software. Not your process, bent to fit software.
We build the part that is specific to you and integrate the rest. You own the code and the data outright.
Custom software just got affordable.
For twenty years, the answer to “can you build exactly what we need?”
was a number that ended the conversation. Six figures. Twelve months. A
team of five.
That changed. AI-assisted development has collapsed the cost of building custom software, not the quality, the cost. Work that used to occupy a team for a year now takes one experienced engineer a few months.
That changed. AI-assisted development has collapsed the cost of building custom software, not the quality, the cost. Work that used to occupy a team for a year now takes one experienced engineer a few months.
The catch: AI writes code, it doesn’t understand your business. Someone
still has to know what to build, how your warehouse actually receives goods,
why your accountant needs that one field.
That part hasn’t changed. That’s the part we’ve been doing since 2004.
That part hasn’t changed. That’s the part we’ve been doing since 2004.
We only build the gap
Rebuilding what already works is how these projects get expensive.
What we build
The four that pay for themselves quickest.
The part nobody sells
Whatever your business does that no standard product has a screen for.
Usually it is currently a spreadsheet with three years of history and one
person who understands the formulas.
The layer between systems
Accounting, shop, warehouse and CRM each hold a piece of the truth. We
build the layer that keeps them agreeing, so nobody reconciles four exports
on a Friday.
Portals for people outside
Where your customers, suppliers or field staff do their part themselves
instead of emailing someone who retypes it. This is usually the piece with
the most obvious payback.
Getting off the spreadsheet
Migrating the thing your operation actually runs on into something with
permissions, history and backups, without losing the flexibility that made
the spreadsheet win in the first place.
How it works
Three steps. You can stop after any of them.
Assessment
One to two weeks, fixed price. We look at how you actually work, not at
the org chart. Where the time goes, where the errors come from, what a
system would have to do. You get a written plan with costs and priorities.
If we turn out not to be the right fit, you keep the plan.
Pilot
Four to eight weeks. We build the highest-value piece first and put it
in front of real users. You see working software early, and you can stop
here. Nobody signs a twelve-month contract on a promise.
Rollout
We extend the system, migrate the rest, train your team, and stay reachable.
You own the code and the data. No lock-in, and no surprise renewal that
quietly doubles.
Who this is for
This is for you if
- You run a company of roughly 10–200 people and you make the decisions.
- Your business runs on spreadsheets, email, and a system that half-fits.
- You’ve been quoted for custom software before and walked away from the number.
- You want to own what you paid for.
Probably not, if
- What you actually need is a standard product configured properly.
- Nobody internally can spare the hours to tell us how the work really happens.
Questions we get asked
- Isn’t custom software much more expensive than a standard product?
- It used to be, reliably. AI-assisted development has changed the arithmetic: work that occupied a team for a year is now a few months for one experienced engineer. Compare it against the real cost of the standard route, which is licences plus implementation plus the consultant who configures it plus the processes you change to suit it.
- Should we replace our whole ERP?
- Almost certainly not, and we will say so early if that is where you are heading. Accounting, payroll and stock control are solved problems and the standard products are good. What is worth building is the part that is specific to how you make money, which is usually a fraction of the whole.
- Who owns the code?
- You do, outright, along with the data and the infrastructure it runs on. It is in the contract, and it is the reason we can say there is no renewal conversation where the price quietly doubles. If another developer takes it over next year, nothing needs our permission.
- What happens if you disappear?
- A fair question to ask a small studio. The answer is boring technology, conventional structure and documentation written for a stranger. We use the stacks a competent developer already knows rather than anything clever, precisely so that replacing us is an inconvenience rather than a crisis.
- How long does it take?
- You see working software in the first two months, because the pilot is a real piece of the system and not a mockup. A full rollout across a mid-sized company usually runs six to twelve months, in pieces you can use as they land rather than one delivery at the end.
- Can it talk to the systems we already have?
- That is most of the job, and the answer is usually yes. Modern systems have APIs, older ones have file exports and databases, and there is almost always a way in. Where a vendor has genuinely locked the door we will tell you what that costs to work around before you commit.
Which spreadsheet is holding your company together?
Call the office nearest you. We’ll tell you whether it’s worth building or whether a standard product would do. No sales sequence.