Custom software
Software off the shelf was made for everybody, so it was not made for you. We build the other kind, anything from a full CRM to an estimating tool or a proposal generator, around how your team already works. You see it working before you decide anything.
What custom software means here
Have your own developers? We set up the tools and hosting, review your code, and train your team.
Replace what you have outgrown
A patchwork of apps, spreadsheets and group chats becomes one system, retired one phase at a time.
A plumbing and HVAC company, module by module, in use today:
Tools that do one job
An estimating tool, a proposal generator, a calculator or a checker. Useful before a customer ever calls.
What staying costs
Once on the invoice, again in the hours spent working around it. Real numbers from an importer we scoped this summer, seven people on staff.
a year
to get an answer
a month
the usual way
None of it is a technology problem. It is what happens when software is built for everybody and its author is not yours to call.
Your numbers
Every subscription, license and seat the office runs on.
Across the team. Re-typing, chasing, copying between tools.
Wage plus payroll cost, near enough.
What this year costs you on the current way
$35,552a year
Three years on the current way is $106,656, and the hours are the part most businesses never put a number on.
Your figures, your estimate. Nothing here is sent anywhere, and we go through these with you during scoping.
Not vibe coders
AI writes a lot of our code. It does not know which permissions matter, or what breaks when two people edit the same record. We were coding before these tools existed.
Built a prototype in one of these? Good. Bring it.
We will tell you what it needs before real customer data goes in.
Where a prototype stops
A demo has one user who can do everything.
Three copies: live, off site, and your own Google Drive.
Passed compliance at a law firm and a financial services company.
What works with 20 records has to work with 20,000.
QuickBooks, your phones, your calendar. A prototype stops at the screen.
Contracts and invoices from the app, with no PDF subscription.
When it breaks on a Friday, a person who finds the line.
What the tools leave out, measured
How a project runs
Your part is showing us how things work today. We do the building.
A recorded call through a normal day in the tools you use now.
A working version on your own data, before anything is priced.
Each phase ends with something your team can use. Stop after any of them.
The new system runs beside the old one until it matches.
Same-day answers in business hours, and anything that stops your team comes first.
What goes into a full build
Working pieces in order, each running beside your current tool until it matches. One module per phase, from a CRM in use today.
Stop after any phase and keep what is built. Nobody buys an idea here.
Your own data, before any quote. You judge the software, not a deck.
Ends with
A fixed price for phase one
The board the office lives in, in your dispatcher's own words.
Ends with
The office schedules in the new system
Dictated on the truck, cleaned up into an invoice line.
Ends with
Techs close jobs in it
What is on each truck, what each job used, what to reorder.
Ends with
Parts are tracked per truck
Invoices, receivables aging and the QuickBooks sync.
Ends with
Billing runs in it
Generated inside the app. No PDF subscription.
Ends with
The old tools are switched off
Time on each side
Your side
One recorded walkthrough, then a weekly meeting. Your team stays in the old tool until the new one matches.
Our side
On the last build we scoped: about three months alone, or six weeks to something operable with your team alongside us.
Two ways to run it
Some want it handed over finished. Some have a builder already halfway there. You can start on one and switch.
We build it
Your team builds, we guide
Who writes the code
We build it
We do, from the recorded walkthrough onward.
Your team builds, we guide
Your team does, in a repository several people can work in at once.
What we set up
We build it
Hosting, the database, the backups and the connections.
Your team builds, we guide
The repository, hosting, accounts and AI tools, and how to use them without running up the bill.
Your time
We build it
A weekly meeting.
Your team builds, we guide
A weekly meeting, plus whatever your builder puts in.
Who hosts
We build it
We do, on infrastructure you can move away from.
Your team builds, we guide
You do, on your own accounts.
When something breaks
We build it
Same-day answers in business hours.
Your team builds, we guide
Your team first, and we are on call.
What you own
We build it
The code built for you.
Your team builds, we guide
The whole repository, from day one.
Start with your team, hand it to us if they run out of time. Same repository either way.
How we decide what to build
The system uses the names your team already uses for things.
A process that is not broken does not get redesigned.
Anything typed twice is the first thing to go.
What slows your team down every day gets fixed before the impressive extras.
Success is your team doing the same job in fewer steps.
What you are protected from
Buying software built for you means betting on the people who build it. The answers, before you ask.
What if we stop working together?
Your data, your branding and the code written for you. We are the garage. You are the car.
What if you two get hit by a bus?
Money set aside and a contractor holding codebase access, so it can be serviced without us. In writing, not on trust.
What if the whole thing goes down?
Live, off site, and your own Google Drive. Encrypted in transit and at rest, in the setup that passed compliance at a law firm and a financial services company.
Where your data lives
What it costs
Quoted after you have seen it working. A fixed price per phase, weighed against what the current way already costs you. By the phase, not the hour. Hosting and support flat for the company, never per seat.
How many we take
A system your whole team runs on is not something to do at volume. If we are full, we will say so instead of taking your deposit.
Thirty minutes: walk us through what your team re-types, chases or works around. We will tell you whether custom software is the answer, or whether something off the shelf would do.
