Founder × Forward Deployed Business Builder

The answer is a role that holds market selection, sales execution and the operating process together, and returns evidence and results to the founder's decisions rather than splitting the work across three functions.

"Forward deployed" describes proximity: the builder works inside the company's daily operation, understands its constraints and stays involved until decisions are running in the field. "Business builder" describes breadth: what to sell, to whom, through which channel, then turning that choice into sales activity and operating routines, and feeding what happens back into the next decision.

When research, sales and operations are separate people, customer reactions never reach the plan and approvals pile up on the founder. The founder sets direction; the builder connects evidence, execution and process so that direction becomes revenue.

The answer is to define the founder's non-delegable work first, then hand everything else to the builder with the authority to act.

Starting from "what can we delegate" never converges. Starting from "what only the founder can do" does. Four things stay with the founder: deciding (approvals of pricing, contracts, publication and sending), meeting (buyers and partners), judging (the quality of a counterpart) and negotiating (the final terms). Our own operating rule follows the same order: fix what stays with a person, then hand preparation, research, drafting and reporting to a documented process.

The right column has to arrive in a state the founder can use without rework. If the founder's review time does not fall after the handover, the division is nominal and the founder is rebuilding the material in their head. Whether the split works is measured by the founder's review time, not by the number of tasks handed over.

Authority follows responsibility. A builder who can view the CRM but not update it, or who must request approval for every partner email, returns the transfer work to the founder. Grant access and decision rights for the right column at the start.

The answer is that the durable deliverable is the process that produces the result again next cycle, with the founder's involvement limited to the decisions in the left column.

One delivery explains the role better than a definition. For an event operator (company name withheld) running a startup support program, application data from three forms, 472 rows in total, was reconciled on a shared applicant ID, 211 valid applications were confirmed after removing 42 rows of incomplete, dummy and internal test entries, and 84 CRM records were written (17 new, 67 updated), with 30 unchanged records deliberately left untouched. Seven charts across seven dimensions and three phases were delivered with a reusable procedure. Manual effort for the same output was estimated at 17 to 23 hours against roughly 1 to 2 hours of actual session time, an estimated reduction of about 90 percent. The comparison is an estimate, not a controlled experiment, and the rate should not be applied to other tasks. A rebuild of one aggregation took an additional 1 to 1.5 hours and is recorded as part of the work.

The builder's scope in that delivery was the reconciliation rules, the quality filter, the differential update, the aggregation and the procedure for next time. The founder's scope was approving the exclusion criteria and deciding how the results would be used. The result was useful once; the procedure is useful every cycle, and that is what the founder is paying for.

The answer is to write three things down before the work starts: the scope table, the authority granted, and how completion will be judged.

Completion is judged on the record, not the report. Do not trust a success message alone: count the records and check the key fields where they were saved. A submitted option that the system silently ignores, leaving a field empty while returning success, is the kind of failure that only a check of the record catches.

Terms are agreed at the same time. "Outreach" may mean drafting or sending; "lead" may mean an inquiry to the company or a candidate for a client program. Define each term's boundary and agree that undefined terms are escalated to the founder rather than guessed. Scope, authority and the completion test are cheap to agree in the first month and expensive to settle in the sixth.

Three things to do this week. Write the four things the founder keeps. Trace one piece of work the founder is currently doing by hand, from the first screen opened to the final approval. For that one piece, draft the scope, the authority needed and the completion test on a single page. How the daily process is built around it is covered in building your Japan launch system. What the role looks like when hired in-house is in what makes an effective Japan business lead.