Qualification to proposal card
Fields, fit/no-fit, discovery, proposal, and follow-up for a service studio. Print it next to the scorecard. Traffic is not this page.
One row per inbound. If it cannot fill these fields, it is not qualified. Do not send a proposal to learn the fields.
Review the no-fit pile monthly. If everything is a fit, your who-line is mush.
flowchart LR
I["Inbound"] --> Q["Qualify"]
Q -->|Fit| D["Discovery"]
Q -->|No fit| X["Polite exit"]
D --> P["Proposal"]
P --> F["Follow-up"]
Qualify (must fill before a call is “sales”)
- They match the who-line
- Named job (website, brand, automation, search). Not “maybe later.”
- Timing window they said out loud
- They can buy (budget band or “we have an owner”). No invented numbers.
Discovery
- The constraint they named (message, site, demand, follow-up, capacity)
- What they use now
- What would make this a good 90 days
- What would make them regret hiring anyone
Fit / no-fit
- Fit: we can name the job, the owner, and a first deliverable
- No-fit reason (written, sent politely, not ghosted)
- Maybe is a date, not a personality
Proposal and follow-up
- Dated artifact they can accept (PDF or scoped email). Not a vibe.
- In / out / change-order rule on the artifact
- Follow-up dates on the card. Two touches, then a close-the-loop note.
- CRM fields: source, qualify date, fit, proposal date, next date, owner