What we do and what it costs
One task. One number. A fixed price and an end date.
Every build has a pass/fail number written into the scope, and a measurement taken before we change anything. If we cannot measure it, neither of us can tell afterward whether it worked, and we would rather say so up front.
One-day teardown $4,500 fixed · one day, written finding inside five business days
We map one task end to end with the people who do it, whether that is submittals, change orders, or RFIs, and time it on real packages. You get a ranked list of what to fix and what each fix is worth per year. You own the finding whether or not you ever hire us again.
Credited in full against a build started within 60 days. It exists so neither of us has to guess at the scope of the bigger thing.
Fixed-scope build $18,000 to $35,000 · four to six weeks
One task and one number, both written into the scope with you, timed before and timed after. The kind of thing we mean: triaging a submittal log, checking an addendum against the base documents, pulling spec sections into a schedule your estimator can price from, or checking an equipment schedule against the one-line and the panel capacity. Built against your documents, on your box, during the engagement.
Half up front, half on acceptance, and acceptance is the number in the scope document rather than our opinion or yours. The box itself is a separate line item, bought at cost (about the box).
Larger programs
Several tasks, one after another, each with its own pass/fail number. Priced after a teardown, and never as an open retainer.
What we will not do
No staff augmentation. We are not a body shop. If what you need is a pair of hands inside your team, we are the wrong call, and we will say so in the first ten minutes.
No hourly. Hourly has no defined end, and it means every tool we build that makes the work faster cuts our own invoice. That is a bad incentive to hand somebody you are hiring to make something faster.
Nothing we cannot measure. If we cannot count the thing before and count it again after, there is no way for you to know whether the money did anything, and we will not take work we cannot be graded on.
The first step
What actually happens if you say yes.
The whole thing, spelled out — including where your documents go, what it costs, and what happens if it turns out to be worth nothing.
You name one task
The addendum one. The submittal one. The one where somebody retypes a schedule into a spreadsheet. You do not need to know what the fix is; naming the job and the person who owns it is enough to start.
If you need an NDA in place before documents move, we will sign a mutual one.
We walk it with your team, stopwatch in hand
Whoever runs it walks us through a real package — they know where it hurts; we bring the stopwatch. Real cycle times, and the sequence people actually follow rather than the one in the procedures binder. Where documents are involved, we would rather work on real ones, and where they cannot leave your network, we bring the machine to them, or we work on your side of the wall.
Tell us what should happen to any files afterward — deleted, returned, or never copied off your network in the first place. Your files are used for your job and nothing else unless you opt in, in writing. If you do, they stay on hardware we control and never go to an outside AI service. Nothing about your company appears on this site.
You get it in writing inside five business days
The task mapped end to end the way your team actually runs it, what each step costs you per year, a ranked list of what to fix, and what a fix would take. We go through it with you before it is final, so anything we misread gets corrected. Yours to keep, and yours to hand to somebody else if you would rather they built it.
Including the parts we could not measure and the parts we got wrong. That list is the most useful part for us, and it is how you know the rest is straight.
Then you decide, with a number in front of you
If a build makes sense, the teardown fee comes off it in full, as long as the build starts within 60 days. If a build does not make sense, we part on good terms, and you still have the map. If the honest answer is that this task is not costing you enough to be worth fixing, that is in the document too, in writing, and it is the cheapest way to find out.
If it earns nothing, you have lost a day and the fee, and you know something about your own operation that you did not know on Monday.
The work we go after
Every company has a job that is one person, reading, at 11 p.m.
Not “inefficiency.” A specific hour, with a name attached to it. These are the four questions we ask in the first conversation. A good answer is a name, a duration, and a failure, and that is a scoped piece of work.
What happens when an addendum lands?
Who opens it, what do they do with it, and how long until the field knows? The base documents still say the old thing, and they will keep saying it until somebody reads both.
What was the last thing installed wrong because two documents disagreed?
And what did it cost? Not a productivity number. A change order, a demo-and-rehang, a delay you carried.
Where has somebody already tried to fix this?
Every company has a graveyard. What was bought and why it did not stick. That history tells us more than a wish list, and it can turn up a budget line that already existed once.
If that job takes a quarter of the time, who notices?
And what do they do with the time? If nobody notices, there is nothing to fix, and we will tell you so on the day rather than three weeks into a build.
Pick the task somebody does alone at 11 p.m.
Start free: send a closed-out set you already know and grade what comes back. Or book the day: one task, one written finding you own.
Teardown: $4,500, fixed. Credited in full against a build started within 60 days. Grading a closed-out set costs nothing, and you hear back inside five business days.
In the email: answer any one of the four questions above in a few lines, or tell us the job you would send. Straight to us at info@redgorge.com.