The Replacement Recovery Diagnostic

The fee is fixed rather than hourly because what is being bought is an answer, not a number of hours. The work is several working sessions on the shop's own estimate records, conversations with the people who write and chase those estimates, and a written report that is kept whatever the conclusion turns out to be.

It is priced to stand on its own, and that matters more than it looks. A diagnostic sold cheaply has to be paid for somewhere, and the only place left is the build. That creates quiet pressure to recommend a build every single time. At three thousand dollars the diagnostic pays for itself, which leaves the recommendation at the end free to be whatever the evidence actually says, including that nothing should be built at all.

The price also buys access, and access is the real cost on the other side. System permissions, employee time, and the owner's own attention are not free to give. A number low enough to be casual tends to produce an engagement nobody takes seriously.

It is not a deposit and it is not credited against the build. Paying for a diagnosis and then paying for the treatment is how it works everywhere else that diagnosis is taken seriously.

The Recovery Build

This is lower than a build of this size would normally be, and the reason is sequencing rather than generosity. The mapping, the interviews and the implementation planning already happened inside the diagnostic. Charging for that work twice would be charging for the same hours twice.

There is no version of this that skips the diagnostic. Building a recovery process without first knowing where the estimates actually die is guessing with someone else's money, and the usual price of guessing is a system nobody ends up using.

The figure covers one location on a supported system, currently ServiceTitan, Housecall Pro or Jobber. A materially different data environment, extra locations, or a bridge that has to be hand built get scoped separately rather than absorbed quietly and resented later.

What the seventy five hundred buys is the managed implementation work itself: configuring the documented fix, building the workflows, setting up the handoffs, testing them, and launching the thing into daily use.

Whether that number makes financial sense is a question about the shop's own figures, not about the price on its own. The arithmetic to run is realistically recovered replacement jobs, multiplied by the average replacement ticket, multiplied by gross margin. That produces an expected monthly contribution profit. The diagnostic tests that arithmetic against the shop's actual estimate history and operating numbers instead of against an assumption.

Revenue is not profit, and the difference matters here. Two recovered jobs are additional revenue first. The comparison that counts is contribution profit after direct job costs and after the Kopikat fee.

The diagnostic has to confirm fit and scope before the Recovery Build is purchased. Seven thousand five hundred dollars is the current managed build price, and it is not a statement that every shop qualifies for the build.

Managed Recovery Operations

This is not a software subscription and it is not the price of sending follow up messages. Sending messages is the cheap part and always has been.

It pays for somebody being responsible after launch. Watching the population of unresolved estimates, running the process, keeping ownership and handoffs straight, deciding what gets worked first, handling the exceptions the rules do not cover, keeping the measurement honest, reviewing attribution, reporting, and changing the operation as evidence comes in.

It sits deliberately at the low end of what managed work of this kind costs, because the economics are still being proven. The monthly pays for operating and proving the machine, not for a result that has already been demonstrated somewhere else. That is an honest description of where this stands, and the number reflects it.

Major expansions are their own scope. Additional branches, a move to a different system, new business lines and large integrations get quoted separately rather than folded in and rushed.

The monthly is for ongoing operating responsibility once the diagnostic and the implementation path are clear: monitoring, follow up, adjustments, handoffs and accountability, held by this firm rather than added to somebody's already full week.

Four thousand dollars a month should be judged against expected incremental contribution profit, not against gross recovered revenue. The same shop specific arithmetic applies: recovered jobs, multiplied by average ticket, multiplied by gross margin, less the ongoing fee and the other variable costs the work creates.

No number of recovered jobs is promised here, and no return is guaranteed. The figures a shop should use are its own.

Standalone Build, not currently available

Standalone Build, not currently available. No standalone build price is published, and there is no purchase or scheduling path for it.

The honest reason is evidence. Kopikat Research needs more shops and more completed implementations before it can describe the true range of scope, complexity and price for a build handed over without ongoing responsibility attached. Publishing a number before that would be a guess wearing a price tag.

A shop is not stuck in the meantime. The diagnostic blueprint is delivered either way, and it can be implemented by the shop's own people or handed to another vendor if Kopikat Research declines to build it.

A shop may inquire about future availability. No payment or activation is being accepted for this option at this time.