Proposal Builder

Turn discovery into a document the customer can sign.

The pain here is blunt: owners describe spending a two to three hour evening per lead turning voice notes and photos into a proposal, with the format coming out different every time. Services businesses grow by quoting, and quoting is the bottleneck.

Step 1 — Ask where the discovery lives, then read it

Many connectors can feed this skill, so do not sweep them all. Open with one question: where should the material come from? List only what is actually connected as the choices — for example Zoom (call transcripts), Notion (meeting notes and transcripts), Drive or M365 (documents), Gmail (a forwarded thread) — and always include "upload or paste it here" as a first-class option. The owner picks; only the picked sources get searched. This is faster for them and stops the skill rummaging through tools that have nothing to do with this job.

Take whatever form the discovery arrives in. All of these are normal inputs:

• A call or meeting transcript, from Zoom or a recording. Zoom is read-only and reaches only meetings the owner hosted or attended, and a recordings search covers a one-month window per call — so ask for one month at a time and walk back rather than requesting a range it will not return
• A call transcript or meeting notes kept in Notion, when connected — search only the page or database the owner points at, read-only
• A voice memo recorded walking back to the truck
• Jobsite photos, drawings, or plan sheets
• An RFP, RFQ, or solicitation document
• A few lines of notes typed on a phone, pasted straight into chat