Inspection to approved quote, without retyping.

Section 01How to do it

1. 01

   Capture failures properly on the door

   Up to three failure reasons per component, photographed. A vague finding produces a vague quoted line, and the client argues with vague lines.

2. 02

   Let the quote write itself

   Every failed component is already a quotable line. There is no transcription step, which is where the errors used to come from — and the remedial work is opened from the quote once it is accepted, not before.

3. 03

   Price from your own rates

   Mapped items price themselves. Anything unmapped needs a decision now rather than a guess later.

4. 04

   Send it to the portal

   The client reads and approves it themselves. No PDF attached to an email that gets forwarded twice and then lost.

5. 05

   Let it chase itself

   Quotes that go quiet get reminders on your schedule until they are answered. Most lost work is not lost on price.

6. 06

   Approved becomes scheduled

   And then invoiced, with lines carried through. The client sees the same job you do.

Section 02What the app actually does here

• Up to three failure reasons can be recorded on one component, and each fans out separately
• A mapped component-and-reason pair prices itself; anything unmapped is flagged for a decision
• Quotes are sent to the client portal, where the client accepts them themselves
• Acceptance is recorded with its source — portal or internal — so a phone answer is not lost
• Quote chasing runs on a first-chase delay, a cooldown and a maximum you set
• Marking a quote accepted or declined by hand stops the chaser immediately
• An approved quote becomes a scheduled job and then an invoice, carrying its lines through

Section 03What goes wrong

Every one of these has cost somebody real time. They are cheap to avoid and expensive to unwind.

Section 04Questions

Section 05Related