Founding Sales for Founder-Led B2B Selling

Scenario

DispatchLoop routes delivery exceptions for regional operators. Three friendly pilot customers use it without paying. Two report fewer unresolved exceptions, but there is no agreed baseline. The founder wants an outreach email and a job description for a VP of Sales.

Weak first draft

DispatchLoop is an AI-powered logistics platform for all transportation companies. Our pilots love it and we save every operator 50% of dispatch costs. We are hiring a VP of Sales to establish our go-to-market strategy and close enterprise accounts. Our outreach will say: Want to see the future of logistics? Book a demo of our intelligent platform.

The draft turns sentiment into an outcome claim, defines an unusably broad market, skips the willingness-to-pay question, and assigns discovery of the motion to a new leader.

Improved working packet

Stage assessment: Value creation remains incompletely evidenced. Free adoption is observed, customer reports of improvement are reported, and willingness to pay is unknown. Validate a business result with the existing pilots while preparing founder conversations about a paid engagement. Do not call the motion repeatable or publish the 50% claim. 2

Initial profile hypothesis: Regional delivery operators with dispatch staff manually assigning recurring exceptions across several routes. Start with the operations manager responsible for resolution and establish who approves software spending. Route expansion is a possible timing signal, subject to discovery. Exclude operators with rare exceptions or an existing system that resolves the problem satisfactorily. 3

Value argument: Dispatchers currently coordinate exceptions through calls and spreadsheets. Delays can leave ownership unclear. DispatchLoop proposes routing an exception to an owner and surfacing unresolved work. The prospect must confirm the current process, cost, and gap before the founder presents the solution. 3

Illustrative economics: If discovery validates 40 monthly hours of avoidable coordination and a $30 hourly labor rate, the capacity-value estimate is $1,200 monthly. At a proposed $400 monthly price, the gross capacity value is three times the fee. This is not $1,200 of cash savings: released time, adoption, and implementation effort remain unverified. The calculation is a package convention for making the business case inspectable.

Outreach draft, assuming the expansion signal is verified:

Subject: Exception handoffs after your route expansion

Hi Maya, your announcement describes three added delivery routes. Are dispatchers still assigning delivery exceptions through calls and spreadsheets? DispatchLoop routes each exception to an owner and shows unresolved work. We are testing whether that reduces coordination time. Would a 20-minute conversation about your current exception process be useful next week?

Discovery branches:

• If coordination is manual, ask for the last exception that remained unresolved and who handled it.
• If the current tool works well, ask what remains unsatisfactory. Stop the pitch if there is no relevant gap.
• If ownership is unclear, ask what the delay caused and how frequently that happens.
• If the pain matters, ask who would evaluate a change and approve payment. 3

Demo and commitment: Walk through detection, assignment, escalation, and resolution of one exception matching the prospect's account. Summarize the acknowledged gap, then ask whether a defined paid evaluation would be appropriate. Confirm procurement and implementation responsibilities before treating agreement as a sale. 23

Next experiment: The founder and pilot operations leads establish a baseline and measure coordination time and unresolved exceptions over an agreed four-week window. In parallel, the founder conducts six conversations with independently qualified non-beta accounts. The six-call batch and four-week window are illustration choices, not Kazanjy thresholds. Review whether customers validate useful improvement and whether any qualified buyer agrees to a paid engagement. If outcomes disappoint, investigate delivery before adding more prospects. 23

Hiring decision: Defer the VP role as a mechanism for inventing the motion. If appointment setting or onboarding constrains learning, consider scoped support while the founder keeps ownership of selling and method development. 2

Rules that made the difference

Separating value creation from value exchange removed the false claim that free pilots proved sales readiness. Narrowing organization and persona improved qualification. Discovery preceded screens. The economics separated capacity from cash. The next experiment paired payment learning with delivered value instead of using a hire to conceal uncertainty. 23