The change order nobody billed. The lead nobody called back.
Both of those happened on somebody's phone, in a chat your software never saw.
I ran operations in the trades on AccuLynx, JobNimbus, CompanyCam, Raken and Dropbox. Now I build contractors one system that fills the gaps and works where their people already are — on the phone, in WhatsApp and text.
- We find where the money is leaking out of your operation.
- We put a number on the biggest one. Your numbers, not an industry average.
- If the leak isn't worth what it costs to fix, I'll tell you that on the call. I'd rather lose the build than sell you one you don't need.
- I show you what it would take to close that leak, in writing.
- Nothing gets sold to you in your conference room. It's a video call.
Five places the money goes. There are more.
Four of these never show up on a software bill, which is exactly why nobody fixes them. The fifth one is the bill — and it is the only one you can already see.
The call nobody answered
Saturday, 7:40 in the evening. Storm damage. It rings out. He doesn't leave a message — he is already dialing the next name on the map. You never find out the call happened.
The estimate nobody chased
You sent it Tuesday. He wanted it. Nobody called him back. Three weeks later he went with whoever did.
The change order nobody billed
Two sheets of bad decking. The crew replaced them, said so in a group chat, and it never reached an invoice. You ate it.
The proof you couldn't find
The photos exist — on somebody's phone, in a thread from six weeks ago. Now there is a dispute and you are scrolling.
The platform you can't change
You bought the one that does everything, and it does. It also bills you per person, and there are about four screens your team actually opens. The way your company does the thing it does best isn't in there — and it isn't going to be, because you are one customer out of thousands and that feature has to make sense for all of them.
You already know which of these is yours. The call is where we put your number on it and work out whether it costs less to fix than to keep.
I paid for the same stack you're paying for.
You're paying for a platform that does ten things and using it for four. We paid for Raken and used it for exactly one job — getting daily reports out. That one job was painful enough that they went out late, when they went out at all.
My subs sent me job photos in WhatsApp, because that's where they already were. To get them anywhere useful I downloaded them to my phone, opened CompanyCam, found the project, uploaded them, sorted them by location, then put them wherever else they needed to be. Hours a week, moving pictures between two apps that both worked fine on their own.
That's what costs you — not the subscription. The step that got skipped, the report that never went out, the customer who got four answers from four people and decided you're sloppy.
The office and the field, on the same system.
Below is a working demo you can open and click through right now — no signup, no salesperson. This is not what I would install for you. It is one made-up company in one trade, built to show what these tools can do.
What I sell is the shaping, not the shape. Roofing, HVAC, plumbing, windows, electrical, solar, general contracting — the core is the same and the part on top is yours. Open the demo and hit Build yours to pick your trade and see what changes.
Five steps. You know the number before anything starts.
-
1
We find your biggest leak
One video call, nothing to prepare. I ask what you can already see, then go looking for what you can't.
-
2
I watch your people work
Office manager, estimators, crew leads. Not a demo — watching how the job actually gets done today.
-
3
You get a written price
What it costs, how long, what's in it — before you commit. Bigger jobs split into phases you approve one at a time.
-
4
I move your data
Your history comes across, and nothing gets switched off on day one. How that works ↓
-
5
I stay on and keep building
Real build hours every month, and a one-page list of exactly what shipped.
One build. Then a monthly you can count.
Price this against the hire, not against a software bill. An office coordinator runs $49,000–$55,000 in most markets — call it $62,000 loaded, every year. Check that against your own payroll; that is why the number is here.
The middle plan is $60,000 a year plus the build once, and the monthly doesn't start until your system is live — so year one carries fewer than twelve of them. Year one runs close to the hire. Every year after costs less — and unlike the hire, it doesn't quit, it doesn't take the process with it, and every month it does something it couldn't do the month before.
No charge per seat. Hire someone tomorrow and the number doesn't move.
That is the floor, and it is what a straightforward build costs. Most of what contractors ask me for scopes out between $9,500 and $18,000. Anything bigger gets split into phases you approve one at a time — so you are never handed one big number, and every phase leaves you something you can use.
Nothing at signing. Your contract lists the deliverables with a price on each one, so the build fee is broken down before anything starts.
Then it goes like this, every time: I build a piece, we get on a call and I show you that piece working on your own data, you pay for it, and then I make it live. If I don't deliver it, there is nothing to ask for back — you haven't paid for it yet.
Then, every month. All three include hosting, monitoring, fixes and support. What changes is how much gets built — counted in hours, listed every month so you can check it.
Running
- Anything that breaks, I fix — not billed against your hours
- Hosting, monitoring, backups, security
- New fields, new reports, document changes
- Your team can send as many tickets as they want
Building
- Everything in Running
- About one new tool, or two full process automations
- One build at a time, so things actually finish
- We sit down with your team every quarter to pick what's next
Working
- Everything in Building
- An agent that picks up the 7:40 Saturday storm call, asks the right questions and books the inspection
- Trained on your codes, your jurisdictions, your data
- We watch what it does and correct it — that's the part nobody tells you about
These three are for a system your company runs on. If what you want is one tool — something that just chases invoices — that is a different build with its own number, and we scope it on the call. Maintaining the two is not the same job.
The monthly is billed at the start of each month once your system is live. Hours don't roll over, and outside costs — servers, texts, app store — pass through at cost, never marked up.
There is no commitment on the build — you pay per deliverable, after you have seen it. The commitment is on the monthly, and it starts when your system goes live: 90 days, then month to month. On the middle plan that is three months at $5,000. I'd rather you see that number here than work it out yourself.
None of this is your money back — I don't offer that, and I'd rather say so than dress up terms as a refund. These are the things you can hold me to instead.
- You pay nothing until a piece of it is built and you have watched it run. Deliverable by deliverable, priced in the contract before anything starts.
- The build is quoted in writing before you commit — this page shows you the floor, the call gets you the number.
- Ninety days is the whole commitment. After that it's month to month, 30 days' notice, no exit fee.
- Your data is in your own database, and I'll show you the export button before you pay me a dollar.
- If a month goes by and nothing shipped, tell me and I'll credit it — the monthly list makes that easy to check.
- I won't sell this to your competitor — one company per market, per trade, and it's a clause in your contract.
Need more than your plan covers? It gets quoted as a one-off, or you move up for the months it takes — same as a change order.
Outside costs go through at cost. I don't mark them up.
Servers. Text messages. An app-store account if you want the app under your own name. Those come from the company that provides them, at what they charge, as their own line on your invoice — with an estimate in your proposal so nothing is a surprise.
Rather run the app under my account? Then there is no app-store fee at all.
When this isn't for you
Under about a million a year, or running one crew? Buy something off the shelf. It's a couple hundred a month and it'll do the job fine.
This is for companies where the off-the-shelf tools already broke, and you've got four or five of them held together with a spreadsheet in the middle.
The things you're already thinking.
I got burned by a software guy before.
Most contractors I talk to have been. The reason that happens is that the money moves before the work does — so here, it doesn't. If I don't deliver, there is nothing to chase, because you haven't paid for it yet. That is the whole difference, and the terms above spell out how it works.
Why 90 days and not month to month from day one?
Because that is how long it takes to be worth anything. The first weeks are moving your data and training your people; the system only starts telling you things once it has a couple of months of your work inside it. If I let you leave at day 30 I would be handing you a half-trained team and a system that never got to prove itself — that is a disservice, not flexibility.
You will not be guessing by then either. You pay for each piece of the build only after you have watched it run on your own data, so you see the value before the 90 days ever starts. After it, month to month, 30 days' notice, no exit fee.
What happens if you get hit by a bus?
Fair question, and today the honest answer is that it is me. So here is what that actually means for you, rather than a reassuring sentence.
Your system runs in your account on your database — not on a platform I control and not on anything only I can log into. It is built on ordinary tools any competent developer already knows, and it ships with the documentation to pick it up. You are not inheriting something exotic that dies with one person.
What that does not give you is a name, and I know that is the part you actually want. I am hiring, and when there is a second person you will meet them. Until then, ask me on the call what happens to your system if I am not here — you should get a specific answer from anyone you are considering, and if you do not, that tells you something.
Will my guys actually use it?
That's the real risk, and it's why I sit down with them before I build anything. Most custom software fails because someone designed it in an office and handed it down. I don't turn the old system off until your office manager says the new one is better.
Who else like me has done this?
One company, in roofing — the one I came up in. You'd be the second, whatever trade you're in, and I'm not going to dress that up. What I won't do is put a client list on a website — you wouldn't want yours on one either. On the call I'll show you what I've built, and I'll give you names and numbers of people in the trades who know my work, so you can go ask someone who isn't me.
How long does it take?
Small builds, three to four weeks. You'll get the real timeline with your written quote. Bigger ones get split into phases, so you always have something working.
Why is there a monthly?
Because software isn't a thing you buy once. It's a thing someone runs. The monthly is me hosting it, watching it, fixing it, and building the next piece. You get a one-page list of what shipped, every month, so you can see what you paid for.
Still got a question I didn't answer?
Forty-five minutes on video. You'll leave knowing where your operation is losing money, what that leak is worth in a year, and an honest answer about whether it's worth fixing.