GAIN AI / Practice 02 — Systems & Consulting
The quotes are in a notebook. The pipeline is in someone's head. The bid was lost on a form nobody signed, and nobody can tell you why the last twelve deals died. None of that is a software problem. It is a record problem, and software only helps after the record exists.
I build the operating system a small company is missing — on your data, your trades, your customers — and then I sit with your team until they run it without me.
Whether this is you
You quote from memory. Two crews price the same scope differently, and the exclusions change depending on who wrote the proposal that day.
You cannot say why you lost. Six months of losses and no record of whether it was price, timing, responsiveness or scope. So nothing changes.
Alternates die on the vine. You price the extra work, the customer never says no, and nobody follows up. That money is just gone.
Bids get lost on paperwork. A missed addendum, an unsigned acknowledgment, a form nobody caught. Not the price. The paperwork.
The job disappears after the sale. Change orders, lien waivers, certificates, punch lists and the referral ask all live in a truck and three text threads.
Margin arrives months late. You find out what the job actually earned long after you could have done anything about it.
What gets built
Each of these is a working piece of a business, not a feature. They connect, but a company that only needs two does not pay for six.
Accounts, properties, contacts, pipeline and every touch logged. Stage-by-stage, with weighted forecast next to gross so the number on the wall means something.
The field that pays for it: loss reason. Six months of that column is the most useful sales report a small company will ever read.
Your scopes written once, properly — narrative, inclusions, exclusions, warranty language, target margin — then reused on every job instead of rewritten from memory.
The part clients keep: the exclusions. Written before the crew mobilizes so a disagreement happens across a desk instead of across a scaffold.
One record becomes a document. Cover letter, conditions observed, priced scope, alternates held out of the base total, exclusions, assumptions, terms and an acceptance block.
What changes: the second proposal takes minutes, and the tenth one is still as careful as the first.
Public bid tracking with the fields that actually decide responsiveness — deadlines, mandatory pre-bid, submission method, bonding, wage rules, addenda — plus a compliance matrix with a row for every requirement and a named person on the verification.
The uncomfortable feature: a scored go/no-go with named disqualifiers, so the system will tell you not to bid.
Schedule, crew, change orders, permits, lien waivers, certificates of insurance, punch list, invoice, payment, satisfaction and the thirty-day referral ask.
Why it exists: most systems stop at Closed Won, which is exactly where the money starts leaking.
Weekly pipeline digest, stuck-deal alerts, deadline warnings, first-touch sequences, and margin by job as the job runs rather than at year end.
The rule: automation goes in after the first real month of use, not before, so it automates what actually happens.
How an engagement runs
Most small businesses have already been sold a tool that nobody uses. The difference here is not the build quality. It is that somebody stays long enough for the way the work gets done to actually change.
Typically 2–4 weeks
We map what exists before we build anything. What is tracked, what is in someone's head, what lives in a truck. Then the system gets built on your actual data — your trades, your scopes, your customers, your pricing — and populated, not left as an empty shell for you to fill on a Sunday.
You end this stage with a working system holding real records, and a written scope of what it does and does not do.
90 days
This is the part that makes the difference, and it is the part most vendors skip. Working sessions on your live deals with your people. Not a training video about where the buttons are — your actual quote, your actual bid, your actual stuck job, run through the system while I watch and correct.
By the end of ninety days your team is asking better questions of the data than I am. That is the exit criterion, and it is a real one.
Month to month, ends when you say
Optional, and genuinely optional. New scopes as you add trades, new automations as patterns emerge, proposal and bid support on the pursuits that matter, and a quarterly read of what the pipeline data is actually telling you.
Some clients need this indefinitely. Some need it for a quarter. A retainer you cannot cancel is a retainer that stopped earning its keep, so this one is month to month.
Engagements are scoped and quoted individually, because a two-person painting crew and a fifteen-truck mechanical contractor are not the same build and should not carry the same number. Bring the problem to a fifteen-minute call and you will get a straight answer on scope, timeline and cost — including a straight answer if the honest recommendation is a $50-a-month tool instead of me.
A real build
The system on the right is running for a New Mexico commercial contractor and exists as a working demonstration environment I can walk you through on a screen share. It is not a mockup and not a slide.
Two things surprise people. The scope library — every scope written once with its exclusions and warranty language — turns out to be the most valuable piece, because it is where the change-order arguments get settled in advance. And the solicitation module will actively tell you to walk away from a bid, with the reason written down, which is worth more than any pursuit it approves.
Ask for the walkthrough on the call. Ten minutes, and you will know whether the shape fits your business.
Fit
Saying this out loud saves us both a proposal. If you are in the right column, tell me on the call and I will point you somewhere better.
Governance
A system that makes work faster and accountability looser is a liability wearing the costume of a productivity gain. These are standing rules, because the downside lands on the client and not on me.
Nothing pre-fills or executes a certification, an affidavit or a sworn disclosure. On a public bid a false certification is a debarment exposure and, on some forms, a criminal one.
A requirement is met when a named person checked it against the source and dated the row, not when a tool wrote a paragraph about it.
Licenses, insurance limits, bonding capacity, safety ratings, references. Each is a certification the moment it enters a proposal, and each is what a template carries forward silently.
I own the engine, the schema and the method. You own your customer, prospect and bid data, and you get a clean export whenever you ask, including on the way out.
Start here
Fifteen minutes. You describe how work moves through your business today, I tell you what I would build and roughly what it takes. If the honest answer is that you do not need me, you will hear that on the call rather than in a proposal three weeks later.