Founder-led sales and founder-dependent sales need different fixes
Estimated reading time: 5 minutes
A founder can remain close to buyers while someone else prepares the research, records the conversation, and sends agreed material. Founder-dependent sales begins when those repeatable tasks also wait for the founder.
Treat these as two operating questions. Where does the business still need the founder's judgment? Where does work stop because only the founder knows the instructions?
For a B2B founder, leaving sales too early can remove a source of learning about the offer. Keeping every task can also make the founder the queue. Quantonica's recommendation is to keep uncertain commercial decisions close and transfer bounded work with evidence, limits, and a return path.
Paul Graham's advice to startups favors manual recruitment at the beginning, followed by gradually less manual methods. That advice supports keeping a learning stage. It does not specify a B2B hiring milestone or prove that any delegation plan will increase revenue.
Diagnose what the founder supplies
Look at a recent account from first research to the latest conversation. Record each point where the founder changed the outcome. Separate a decision about the business from a task someone else could perform with the same inputs.
Consider these two situations:
- The founder changes the target account criteria after learning that the proposed buyer cannot approve the purchase. The team needs that judgment recorded and tested against other accounts.
- The founder personally finds the buyer's company website, copies notes into the CRM, and checks whether the promised document was sent. The team needs instructions and ownership for those tasks.
The second situation does not establish that the first decision is ready to delegate. A clear process for research can coexist with an unsettled offer.
Use three questions during the review. What did the founder know that the next person could not see? What decision required authority? What merely required access, instructions, or time?
A founder's personal relationship can be another dependency. Record whether the buyer needs the founder's technical knowledge, negotiating authority, or credibility. Hiring a researcher will not transfer a relationship by itself.
Draw a boundary around each task
The map below is a proposed delegation boundary, not a claim that every startup should follow the same hiring sequence.
| Work | Candidate owner | Evidence supplied | Return to founder when |
|---|---|---|---|
| Find companies matching settled criteria | Research owner | Criteria, sources, exclusions, checked examples | Evidence conflicts or the company falls outside the criteria |
| Select a contact | Research owner with review | Responsibilities, source, unresolved authority | Responsibilities do not identify the buying role |
| Draft a first message | Outreach owner | Account evidence, approved offer, allowed claims | The message needs a new claim or promise |
| Send approved material | Assigned sender | Exact document, recipient, request, deadline | The buyer asks for different terms or confidential information |
| Explore a new use case | Founder or designated commercial owner | Conversation notes and open questions | The owner lacks authority to change scope |
| Change price or product commitments | Authorized commercial owner | Agreed limits and approval record | The requested commitment exceeds those limits |
| Record outcomes and exceptions | Each task owner | Shared fields and original evidence | A missing fact prevents the next decision |
Replace the role names with people. Give a task to someone who can complete it and recognize its exceptions. “Help with sales” leaves both responsibilities unresolved.
For a low-volume business, the founder may deliberately keep research and sending. Quantonica recommends manual outreach when the client can inspect each account and protect its reputation. Include that time in the operating decision. Transferring work is useful when it solves an observed constraint, rather than merely making the business look more automated.
Transfer one bounded task
Use an illustrative transfer to test the map. Suppose a founder sells a technical service to manufacturing businesses. The offer and account criteria are approved; pricing for unusual integrations remains unsettled.
The research owner prepares an account note. It contains the relevant facility, the source date, the likely operational responsibility, and the unanswered integration question. The founder reviews the note before the first message. If the prospect asks about an unpriced integration, the research owner records that request and returns it to the founder.
This is an example of the proposed process. It is not a customer result or a claim that the transfer saved a stated number of hours.
Copy this brief for the task you want to transfer:
Task and named owner: Inputs the owner can access: Definition of completed work: Approved claims and commitments: Examples accepted / rejected, with reasons: Exceptions that stop the task: Person who accepts an exception: Where the evidence and decision are recorded: Review date and reason for reopening the boundary:
Ask the owner to apply the brief to an unsuitable account as well as a suitable one. If both pass, examine the criteria before increasing volume. If the owner stops every account, inspect which missing instruction causes the delay.
Keep the founder in the learning loop
A transferable process still needs someone to learn from buyer responses. Collect objections, account mismatches, unexpected use cases, and commitments that required an exception. Review these with the founder or the person authorized to change the offer.
Avoid judging the transfer only by completed tasks. A researcher can produce every requested record while applying the wrong account criteria. A sender can deliver every message while the offer remains unclear. Review a small selection of evidence and decisions alongside the activity count.
Quantonica's outreach workflow makes the client responsible for feedback and buyer replies. That boundary lets a client delegate agreed research and campaign operation while retaining commercial conversations. It does not transfer product strategy, negotiations, or closing authority.
If work repeatedly returns for the same reason, change the brief or deliberately keep that decision with the founder. If buyer conversations contradict the account criteria, reopen the criteria. Stable tasks can support bounded automation once the owner, checks, and stop conditions work.
At the next review, inspect one task that still waits for the founder. Identify whether it lacks instructions, authority, evidence, or a relationship. Transfer only the part for which you can supply the missing input.