The Recovery Build

Why it only follows the diagnostic

The Diagnostic defines the work. We agree one workflow, the available platform features, the delivery schedule, and acceptance criteria before payment. The $7,500 price applies only when that defined scope is feasible.

That scope states where the workflow starts and ends, when work stops or passes back to your team, and who takes over when the assigned person is absent. We check the required features, permissions, and access for the people who will use it. A new app or custom integration is not assumed to be part of the Build.

What the $7,500 covers

• One agreed estimate follow up workflow, with reason, ownership, and next action fields
• A working queue, handoff rules, and team credit assignment and reporting under the shop’s agreed rules
• Written operating instructions, a handover to your named process owner, and two staff training sessions
• Acceptance checks for agreed roles, access, handoffs, and exceptions, followed by 14 calendar days of stabilization after handover

Extra locations, data migration, custom software or integrations, and software or messaging charges are outside the fixed fee. Any additional work is quoted and agreed before it begins.

What determines whether this price makes sense

The answer comes from the shop's own figures, not the price on its own.

• The volume of unsold replacement estimates the diagnostic actually counted
• The average replacement ticket the shop's own records show
• The gross margin on that work, taken from the shop's numbers rather than an industry figure
• Which records support an appropriate next action, and which still require clarification
• Available installation capacity and the work the shop wants to take on
• Whether the people and the system can carry the process once it is built

The arithmetic, in plain language

Use completed work and the shop’s actual job costs to assess contribution. Recorded involvement does not by itself prove that the process caused a sale. Subtract the costs of follow up and the engagement, including the team’s upkeep time. Any forecast needs explicit assumptions; the quoted value of open estimates is not an expected return.

Revenue is not profit

Account for equipment, labor, and other direct job costs before comparing the value of additional work with the engagement fee. Use your shop’s actual costs and state the assumptions behind any forecast. If a job would displace scheduled work, compare the contribution from both jobs. A larger ticket is not automatically the better job.

How your team checks and keeps it

Acceptance checks whether the next person can find the customer’s context, see prior contact, and carry out the assigned action using their normal account and device. We agree the scenarios before payment, including the relevant handoffs, an absent owner, a changed customer decision, and a request to stop contact. The checks cover the roles and access included in the scope, with sensitive information restricted appropriately.

Your named process owner receives the operating instructions, configuration and access notes, agreed reporting definitions, and any open items with a responsible person. Your shop keeps its records and can run the process after handover.

What stabilization covers

The 14 calendar days after handover cover correcting defects against the approved scope. The support channel, coverage, and response expectations are agreed before purchase. New requirements or ongoing operation need a separate agreement. There is no automatic monthly service.

If the diagnostic says Kopikat should not build it

That recommendation is given plainly when it is the answer.

The shop receives the blueprint and may implement it internally or through another vendor. The Build can also be handed over to your team without a monthly service. Read the handover options.