01 / The starting point
What should each party bring to the first meeting?
A useful first conversation begins with the founder's unfair knowledge, not a grand list of services. The founder may know a customer, a product category, a community or a recurring failure in an industry. The builder should bring a method for turning that knowledge into evidence: people who can research, prototype, sell, recruit and coordinate the work.
Founders Factory describes a sequence from exploring a problem to developing a concept with a venture-design team, pitching an investment committee and building when the evidence warrants it. That is its own process, not a contract for every builder. High Alpha similarly describes ideas entering from founders, its team or partners. These examples show why the initial founder contribution can vary.
Before discussing ownership, both parties should write what is already known, what is assumed and what must be tested. A founder with real orders should not be treated like one with only an idea. A builder with manufacturing expertise but no relevant customer access should not claim a complete route to market.
02 / The first tests
How should the team decide what to build?
The first operating phase should reduce uncertainty in an ordered way. Interview people about the last time the problem occurred. Observe their workaround. Write down what they already pay, where time is lost and who controls the purchase. Then test the smallest credible promise through a prototype, pilot, pre-order or manual service where appropriate.
P&G's public innovation account describes identifying unmet consumer problems, looking for partners, developing and testing new brands. P&G is a large consumer company, not presented here as a venture builder. The transferable discipline is to connect customer evidence, product development and partner capability before spending at scale.
A good builder creates a decision record, not just a presentation. After each test, the team should state what changed, what remains uncertain, what it cost and whether to continue, revise or stop. This protects the founder from mistaking activity for progress and the builder from being asked to execute an untested thesis indefinitely.
03 / The operating map
Who does the work and who makes the decision?
Create a responsibility map before work begins. It should name an owner for research, product, supply, sales, finance and customer support, even if one person covers several areas. Give each owner an output, a due date and an escalation route. A task can be delegated while the decision remains with the founder, board or another partner, so both parts must be explicit.
For example, the builder might source three manufacturers and run sample tests while the founder approves the final product brief and supplier contract. The founder might lead customer interviews while the builder maintains the evidence log and pricing model. These are illustrative allocations, not a claim about Ospyr's current staffing.
Then distinguish reversible operating decisions from commitments that change the company's future. A limited pricing test can often be delegated. A new share issue, large borrowing or transfer of the brand might require formal consent. Agreements should define thresholds, not send every ordinary choice into an approval queue.
| Work | Named owner | Decision to record |
|---|---|---|
| Customer evidence | Who recruits and interviews users? | What would disprove the thesis? |
| Product | Who writes and tests the brief? | Who approves the first release? |
| Supply | Who vets and manages suppliers? | Who signs and owns the contract? |
| Commercial | Who sells and serves customers? | Who can change price or channel? |
| Finance | Who tracks spend and cash? | What requires founder or board consent? |
04 / The handoff
When should the new venture stop depending on the builder?
Shared specialists are most valuable when they help a young company learn quickly. They become a liability if the venture cannot later run its own customer, product and financial systems. Decide at formation which capabilities will be hired into the company, when ownership of records transfers and what support remains available after the first operating phase.
A handoff is more than a personnel change. The venture should own or have clear rights to its domain, brand, customer data, contracts, designs, code and product specifications. It should know how to run the weekly decision meeting without a studio representative. It should be able to explain its economics to a new investor without translating private spreadsheets held elsewhere.
Some builders remain shareholders and trusted partners for years. That does not require them to approve ordinary work forever. A healthy long-term relationship can shift from doing to advising while preserving clear investor rights. The exact balance must be documented and reviewed as the company changes.
- Write a 30-day evidence plan before a full build budget.
- Name task owners and decision owners separately.
- Keep the venture's data, contracts and intellectual property accessible.
- Agree which shared capabilities transfer to the company and when.