Working notes / Growth systems
How I approached the lead handoff.
Acquisition is only part of my work. I also build the workflows around what happens after someone gets in touch: understanding the inquiry, deciding what matters, and preparing the next conversation.
Keep the reasoning visible.
In the example below, fit, timing, decision-making authority, and completeness each contribute to the score. You can see how the result is reached.
Leave room for missing context.
An incomplete inquiry needs a follow-up question. The example treats that differently from an inquiry outside the intended audience.
Keep a person in the loop.
A score helps prioritize attention. The draft and CRM preview stop at human review, so the next action stays a deliberate decision.
An illustration of the approach
One inquiry, step by step.
I made this interactive example to show the logic. It uses fictional leads and fixed rules; it is not a live client system or an AI model. Nothing is sent or saved.
Walk through an exampleWorked example / Fictional data
Follow one lead through.
Choose a fictional inquiry and follow each decision. See which leads need a sales conversation, more context or a different route. Nothing is sent or saved.
Demo Agency A
Insurance agency · 8-person team
“I manage our agency. We need to bring leads and call records into one CRM this month. Can we see a demo?”
Fictional example · No personal data
- 01Input
- 02Qualify
- 03Score
- 04Draft
- 05CRM preview
Step 1 of 5
A new inquiry arrives.
The input carries the business context and the request. Continue to see what should happen before a sales rep follows up.
The wider workflow: six functions
Six functions, one workflow.
Select a functionAcquisition
The top of the funnel runs on a schedule. Campaign structures, audience logic, and budget pacing for Google and Meta are set once, then the system adjusts bids and rotates creatives on its own and flags anything that drifts so I can step in.