Pre-seed: make the problem specific.
An early company may have a compelling insight before it has a finished product. At this stage, a useful conversation begins with the person experiencing the problem, the work they are trying to complete, and the alternatives they use today. The aim is to make the opportunity concrete enough to test.
A founder does not need to pretend that every assumption has been resolved. Customer interviews, a focused prototype, or an early experiment can reveal which part of the idea deserves further development. Explain what was tested, what changed your understanding, and which question is now the most important.
The use of capital should reflect that uncertainty. A narrowly defined first use case, an initial product, and the capabilities needed to test them can be more informative than a broad roadmap that tries to serve every potential customer.
Seed: establish a reason to adopt.
Once a product exists, the central question becomes how it earns a place in the customer’s life or business. Interest, a pilot, and a repeat purchase are different forms of evidence. Each tells part of the story, but none should be presented as something it has not yet demonstrated.
For an enterprise product, understand the path from an interested user to an approved deployment. Integration work, security reviews, budget ownership, training, and support can all influence adoption. A product that solves a real problem still needs a workable commercial and operational path.
Useful milestones might concern repeated use, conversion from a pilot, the time required to onboard a customer, or a clearer understanding of delivery costs. The right measure depends on the business. Define it before using it to justify a larger plan.
Seed+: make progress repeatable.
We use seed+ to describe the next early-stage chapter: a business with emerging evidence of traction that is strengthening its product, commercial approach, and operating foundations. The label is less important than the quality of the progress behind it.
A small group of committed customers can be valuable, but founders should understand what is unusual about those relationships. Did they rely on the founder personally? Did implementation require extensive customization? Are customers using the product in a comparable way? These questions help distinguish a repeatable model from a series of individual successes.
Capital at this stage should connect to the constraint that matters most. That could mean deeper product capability, a more effective route to customers, stronger retention, or a team able to deliver without adding complexity at the same pace as revenue.
Make the milestone useful to a decision.
A milestone should change what the company knows or can do. “Hire more people” describes an activity. “Build the capability to onboard customers consistently” describes a business objective. Both may belong in the plan, but the relationship between them should be clear.
Consider an illustrative data-software startup. An initial milestone could establish whether one customer segment needs the workflow. The next could test whether that segment uses a working product repeatedly. A later milestone could demonstrate that another team can sell and implement it using a documented process. These are examples, not requirements for every company.
Discuss the assumptions, resources, and timing behind the proposed milestone. Also explain what you would learn if it were not reached and which choices would remain available. That makes the use of capital easier to assess.
Keep the capital relationship aligned.
Ooventive has supported startups since 2009. Our early-stage focus spans pre-seed, seed, and seed+, while our broader investment perspective extends across AI, data, enterprise software, digital trust, and industry transformation.
We invest our own capital and manage capital for investors. An opportunity must be understood in the context of the relevant capital model, and managed capital must also fit the agreed mandate. The company’s needs, investment structure, responsibilities, and expectations belong in the same conversation.
A useful introduction starts with your current stage, the evidence you have, and the next proof point. Be clear about what the capital would enable and the conversation you want to have.
- What has the company demonstrated at its current stage?
- Which uncertainty should the next use of capital resolve?
- What would make customer adoption and delivery more repeatable?
An expression of Ooventive’s investment perspective, not a statement about a specific investment or portfolio company.
Share your perspective