Framework · Sales Engineering

The Prospect Flow

An 8-step locked flow that separates research and planning from build.

The problem

Most solo operators selling consulting or build work burn full days per prospect. Research lives in a tab. Offer construction lives in a head. The proposal gets typed at midnight before the meeting. Each prospect is treated like the first prospect, because there's no process — there's just effort.

The cost isn't just time. It's that the build itself gets compromised. Builders pulled into research lose flow. Builders pulled into offer construction lose architectural clarity. By the time the contract is signed, the same person who needs to ship has been three other people first.

The fix is not to work harder. It's to separate the lanes — and to do it explicitly enough that the separation survives ambiguity.

The thinking

Pre-sale activities are research, synthesis, and presentation. Post-sale activities are planning and building. These have different cognitive shapes. Mixing them on the same person at the same time means neither is done well.

The separation runs deeper than scheduling. It's a separation of tools. Research and offer construction live in one environment — the second brain, where context compounds. Build lives in a different environment — a fresh project folder with builder-specific frameworks. The build folder doesn't pull from the brain; the brain doesn't pollute the build folder.

Stated as an iron law: Ziggy plans. Asad builds. The split is not advisory — it's structural.

The framework

Eight steps. Same shape, every prospect:

  1. 01. Asad shares prospect info — name, contact, what's already known. Verbal or chat handoff.
  2. 02. AI research — Instagram, Facebook, LinkedIn, YouTube, public web. Build full footprint dossier. Notes inline.
  3. 03. Produce the offer document. A through Z. Smallest wins to most technical moonshots. Canonical 35-item, 4-tier structure with star-marked anchor offers and recommended phasing.
  4. 04. Convert the offer document into a polished web artifact using the design stack. Deployed as a real URL. The prospect doesn't read a PDF — they navigate a site built for them.
  5. 05. Pitch the prospect using the polished artifact. Discovery call + close.
  6. 06. Prospect selects one or more offers. Signed offer + payment.
  7. 07. The plan for the selected offer. Architecture, sequencing, deliverables, milestones. Lives in a fresh project folder.
  8. 08. Build inside the fresh folder. The build environment is sovereign. The brain stays out.

Evidence

The flow ran end-to-end on a coaching-academy prospect over a four-day window. Step 2 surfaced a 158K-follower verified Instagram presence the founder hadn't mentioned — turned out to be the highest-leverage angle. Step 3 produced a 35-offer menu across four tiers, with anchor offers marked and a recommended phasing. Step 4 deployed as a live editorial-doc site at a real URL — bilingual, paper-cream aesthetic, mobile-responsive.

The pitch artifact alone shifted the conversation. The prospect's reaction was visceral — "this looks like something a real agency made." The build hadn't started yet. The flow itself was the differentiator.

Steal this

If you sell custom work, two moves transfer. First: write down your prospect flow as numbered steps and lock it. The act of writing it down reveals the steps you skip. Most solo operators have a flow — they just haven't made it visible to themselves. Make it visible, and you can see where it leaks.

Second: separate the research environment from the build environment. Different folders. Different toolchains. Different times of day if you can. The cost of context-switching between "understand this person" and "build their thing" is higher than it feels. Two clean lanes beat one frantic one.

Related