Ask yourself what stops if you take two weeks off.
That list is your system. Right now it lives in your head.
We find the most expensive thing on that list, fix it in 30 days, and hand it over in accounts with your name on the invoice.
Who we do this for
Owner-run services businesses — facilities, janitorial, maintenance, hospitality — usually between twenty and a couple of hundred people, where nobody’s job title contains the word “systems” and you’ve become the person who knows how everything connects.
If you have an in-house development team, you don’t need us. If you’re pre-revenue, we’re too expensive. We’d rather say that now than on the third call.
01 Find it
A short, fixed-fee engagement — we tell you the fee before you commit, and it isn’t billed by the hour. We map how work actually moves through your business, not how the org chart says it does. You get one page naming the single most expensive thing that’s stuck, and what it’s costing you.
That cost is a projection. We build it from your numbers, we show the arithmetic, and we tell you which assumptions it’s sensitive to. It’s there to make a decision fundable, not to be a promise.
If the ground needs mapping before anyone builds anything, this scales up into a full strategy and roadmap — current state, a phased plan, a build-versus-buy matrix, and budget and timeline ranges you can put in front of a lender or a board.
02 Fix one thing, live in 30 days
One thing. Working and in production inside thirty days. You own it.
What a 30-Day Fix can look like:
- Scheduling and dispatch that isn’t a group text — who’s going where, visible to the office and the crew, without three people re-typing it.
- Invoices that go out the day the job closes — not the Friday after somebody remembers.
- Your numbers in one place — one view across sales, operations and delivery, with a short digest in your inbox each morning so you know where things stand before your first meeting.
- An assistant on your website that works out what a visitor actually needs, captures the serious ones, and files them against a real person instead of a form nobody reads.
- A portal your customers can see into — documents, messages, scheduling and job status, so “where are we on this?” stops arriving by phone.
We fix one at a time, deliberately. The reason most systems projects fail is that they tried to fix everything.
03 We’ll run it
If you’d rather have the outcome than another system to look after, we operate it month to month. We monitor it, we fix it when it breaks, and you get a monthly report showing what it did and what it cost to run.
What we won’t do is promise you a response time we haven’t earned. If you need someone reachable at five on a Saturday morning, tell us early — that’s a different arrangement, and we’ll give you a straight answer about whether we can be that.
Cancellable whenever you like, and you keep what’s built either way. That’s the whole point of building it in your accounts.
04 Or we build the whole thing
When several pieces have to land together: your domain and email, your website, the internal hub your team works out of, your customer records and how work reaches them, and one place to administer all of it. Assembled as a single system rather than five subscriptions that don’t talk to each other.
Bounded scope, quoted per engagement, same ownership rule.
Two promises that hold across all four
You own the accounts. Every system we build lives in accounts registered to you, billed to you, with your name on them. You can end this on a Friday and still be working on Monday. It’s worth checking whether that’s true of the setup you have now.
A person approves anything that goes out in your name. No software we build posts publicly or sends a message as you without someone approving that exact content first. Where something talks to your customers directly — a website assistant, say — you set what it may and may not say, and you see every conversation.
What the first conversation is
An hour, no charge, no deck. You describe where the work gets stuck; we tell you whether it’s the kind of thing we fix and what finding out would involve. If it isn’t, we’ll say so and point you at whoever does it better.
Book an hourplaceholder — no booking link wired
What we need from you
Five open items. Two should go to outside counsel rather than being settled internally, and nothing publishes until those come back.
Is “pilot” doing gate-avoiding work on the market-signal product?
Its legal packet says don’t sell or invoice a first paid tenant until the terms of service exist. A client is live on three feeds sourcing real purchases off the output, with no confirmed invoice, and all three delivery databases are titled “(pilot)”. The pattern that caught us on DC Deal Intel has all its preconditions present here — what’s missing is an answer about intent. If the label is being used to mean the gate doesn’t apply, that’s routing around a known gate.
The liability cap is scoped by product name, not by activity
The Governance Readiness Review is being held for a cap, while six lines that write to client CRMs, publish to their social accounts and feed their sourcing decisions ship without one. Nothing was renamed to escape anything — but attaching the gate to a label rather than to the risk produces a liability posture that looks addressed because one product carries a cap.
Does a price go on the page?
No number appears anywhere. For this buyer that’s real friction — owner-operators anchor on price, and its absence reads as expensive. The ladder forbids restating figures as settled, but a “starts at” with operator confirmation may be permissible. It’s one edit — it drops into the first paragraph of line 1.
How hard do we sell the monthly retainer?
The page currently declines to promise a response time, which is the honest position while the fleet runtime sits on one machine — it went dark for six days this month. Selling monthly care into an operations business eventually needs a real commitment, and that needs the runtime moved first.
The proof and the chosen buyer don’t overlap yet
Every verified outside-client reference sits in the infrastructure vertical this page excludes. The only client inside the chosen buyer profile is still in onboarding. Three options: hold this profile through a thin-proof window and sell on the bounded offer, follow the proof to infrastructure instead, or run both as two sequenced pages. The recommendation is to hold — but only if that onboarding client converts into a named, permissioned reference reasonably soon.