The plan below is not a list of milestones. It is a chain reaction in six links, where each link produces the exact ingredient the next link needs. The strategy works because every move is calibrated to remove the friction that has stopped every other contech startup from reaching the principal-side procurement conversation. Free first projects to get past buyer caution. Run-alongside positioning so nothing has to be replaced. Structural lock-in to make adoption irreversible after one project. Deep operational experience with the exact contracts the customers run, collapsing the sales cycle to peer-to-peer conversations. Two adjacent products already in market to extend runway and generate inbound. And a sequence of links that turns one published case study into the first principal embedding Nebula Verified in a tender. Eighteen months. Six links. April 2026 to September 2027. From a $3.5M SAFE cap, the base case is an infrastructure-layer company. The ceiling is the 50x to 100x outcome that infrastructure companies produce when they become the standard everyone has to use.
The day the SAFE closes, the company moves on three fronts at once, because each one depends on the other two. Eleven provisional patent families are consolidated and converted into international PCT applications before each priority window closes, defending twelve patent families across 150+ jurisdictions. The second live deployment is configured for a July go-live, putting a counterparty on the platform end-to-end for the first time. And the commercial infrastructure (pricing, contracts, onboarding flow, billing) is finalised so the second pilot converts to a paying subscription the moment it completes. None of these three are sequential. They are one event with three faces, and the SAFE pays for all three at once.
The first pilot, already complete, proved that Nebula can extract obligations and catch breaches against an internal baseline: 347 commitments tracked, 38 caught before breach, 11.5 hours saved per week, 94% extraction accuracy. That dataset is real and it is on the locked main page. But it is one half of the system. The second pilot is the first time both parties to a real infrastructure contract sit on the platform end-to-end, and that is the only configuration that produces every other engine. Without a counterparty on platform there is no Verify event because there is no second party to confirm fulfilment. Without Verify there is no Certify because Certify is the rating computed from verified events. Without Certify there is no procurement conversation because there is no rating to embed in a tender document.
The pilot is offered free. Not a demo, not a sandbox, a real contract with real obligations, real enforcement, and real cryptographically anchored records. Managers of infrastructure projects are conservative buyers, but they will try a tool for free on a single project when the team building it has deep operational experience with the exact contracts they run. Once the first project is on the platform, the obligation register, the enforcement history, and the proof ledger belong to that project. The counterparty now has a Nebula account with a reputation score. The next project they sign brings Nebula with them.
Peer outreach gets the first three to five pilots at near-zero acquisition cost. Content marketing gets the next thirty to fifty at low cost. The marketplace flywheel gets the rest. The bridge between peer-led and content-led is not a LinkedIn cadence. It is one published case study with real numbers from a real counterparty-confirmed deployment. Without that case study the LinkedIn content has nothing to point at and the inbound never starts. With it, every post for the rest of the eighteen months can reference it, every conference talk can show it, and every investor conversation can quote it.
Nebula is built by a team with deep operational experience running the same infrastructure contracts the customers run. The early sales motion is not a sales motion. It is a series of conversations between people with shared daily problems, anchored on a published case study with real numbers. The conversion rate on those conversations does not look like enterprise SaaS. It looks like a referral from a colleague. CAC is effectively zero through the first cohort.
The case study lands into the rooms that already exist. FCON26 Future of Construction Summit (Brisbane, May 2026). Engineers Australia Queensland Division technical evening (mid-2026). PMI Queensland Chapter event (mid-2026). All-Energy Australia (Melbourne, October 2026). FCON-Tech Sydney (October 2026). Australian Energy Week (Melbourne, June 2027). Every one of these rooms is filled with managers of infrastructure projects who already feel the pain Nebula solves. The conferences are not the engine. The case study is. The conferences are where the case study gets in front of the right ten thousand people for the cost of a speaker submission.
The second pilot converts to a paying subscription at the Professional tier ($199/month). Customers two through twenty-seven follow over the next six months, drawn from peer outreach in the first half and from inbound enquiries driven by the case study and conference circuit in the second half. By the end of Month 12 the platform is running on twenty-seven paying projects with monthly recurring revenue of approximately $7,980, climbing toward eighty paying projects and $19,440 MRR by Month 18. Breakeven hits at Month 16. The unit economics are already locked at $750 CAC, $17,250 LTV, 23:1 LTV:CAC, and 85% gross margin at scale.
The first project is free, so the cost of trying Nebula is zero. The lock-in is structural after project one, so churn is near-zero. The pricing tiers are calibrated to the customer's existing budget for project administration ($199 Professional, $1,500 to $2,000 Enterprise), so the buyer does not need a new line item. Deals close through peer conversations because the team and the customer share the same operational vocabulary and the conversation does not require translation. Adding the certification revenue layer from Month 12 onwards (per-contractor recurring fees of $500 to $1,500 per year for Nebula Verified) materially uplifts MRR beyond the conservative model on the financials page.
The seed round closes at $12M to $18M with an institutional lead at a target post-money valuation of $45M to $70M, a twelve to twenty times markup on the $3.5M SAFE cap. The first two hires join the following month (engineering and commercial, decided by where the data says the bottleneck is). And the first principal-side conversation begins: at least one Tier 1 Australian infrastructure procurement programme starts evaluating Nebula Verified as a tender factor. This is correctly placed at the end of the pre-seed runway and not the middle, because procurement cycles in Tier 1 Australian organisations run twelve to twenty-four months from vendor introduction to tender inclusion. A principal will not take a pre-seed startup with no paying customers seriously. A principal will take a seed-funded company with a published case study, twenty-seven paying customers, twelve patent families, and an institutional lead very seriously.
The credentials forged in links one through four are exactly what the principal meeting requires. The case study answers "does it work?". The paying customers answer "do people value it?". The patents answer "is it defensible?". The institutional lead answers "is the company real?". An infrastructure principal evaluating new vendor technology in 2027 will see all four answered before the first meeting begins.
This is the moment the eighteen months exist to produce. One Tier 1 Australian infrastructure principal writes "Nebula Verified preferred" or its equivalent into a live tender document. From that moment, every counterparty bidding on that principal's projects must be on Nebula or lose competitive advantage. The flywheel engages. The certification compounds because the data cannot be replicated on any other platform: it is generated inside Nebula's compliance engine during real project execution.
Once the certification has procurement value, the buyer is no longer the manager of the infrastructure project. The buyer is the procurement framework. Sales motion ends. Adoption is mandatory for any contractor that wants to bid. The contract execution layer becomes infrastructure, not software, and infrastructure does not trade at vertical SaaS multiples. ISNetworld built a multi-billion-dollar category on verifying paperwork. Nebula Verified certifies delivery instead, in a larger market, with structural network effects that compound from the first principal embedding outwards. From a $3.5M SAFE cap, a path to the infrastructure-layer outcome is 50x at $175M, 100x at $350M, and the ceiling sits well above that wherever the procurement standard takes hold across geographies and verticals. The Series A target of $40M to $60M at an infrastructure-multiple valuation is anchored on this transition.
Nebula's path to revenue runs through pilot conversions, which means the first paying Nebula customer arrives in early 2027. That is the chain reaction working as designed. But it is not the only revenue the company has. Two products built end-to-end by the founder are already in market and already generating revenue from day one. Together they extend the runway, validate the underlying AI infrastructure, and produce a continuous stream of inbound interest from the exact buyer persona Nebula needs.
Desktop document intelligence
Locus is a local-first desktop document intelligence application. Files never leave the user's machine. Only transformed fragments are sent to cloud LLMs via zero-retention APIs. v3.0.0 is shipping at locusdocs.com with three pricing tiers: Focus at $12 per month, Pro at $29 per month, and Command at $49 per month BYOK. Locus is revenue-generating today and breaks even at four paying users. It validates the AI document parsing capability that feeds directly into Nebula's extraction engine, and it serves as a customer on-ramp: professionals using Locus to analyse infrastructure contracts are natural Nebula buyers when the second project arrives.
Real-time AI work guidance
Compass is a real-time AI work guidance tool. Compass watches your screen as you work. Select any region, a drawing, a calc sheet, a spec, and Compass monitors what you type, prompting you to use the right formula per a standard, flag a non-compliant clause, or define a term correctly before it causes a downstream problem. In infrastructure projects, a missed standard reference can cost millions. Compass catches it at the desk. R&D stage. Launch targeted post-Seed.
Locus revenue subsidises Nebula's runway during the pilot onboarding period when the chain is still being forged. Every Locus user is also a warm lead for Nebula. Every Compass design partner is a pre-qualified case study candidate. The two adjacent products are not distractions from the Nebula roadmap. They are the runway extenders and the lead generators that make the eighteen months of pre-seed capital go further than $380K alone could.
| Link | Dates | What forges it | What it enables |
|---|---|---|---|
| 01 The launch | Apr - Jun 2026 | PCT conversion + second pilot configured + commercial machinery ready | The platform of every other link |
| 02 The proof | Jul - Oct 2026 | Second live deployment runs end-to-end with counterparty | The dataset that makes every engine real |
| 03 The case study | Oct 2026 - Feb 2027 | One published deployment + three peer presentations | The asset that replaces the sales team |
| 04 The first paying customers | Feb - Jul 2027 | 27 paying projects, ~$7,980 MRR, breakeven Month 16 | The boundary that opens institutional capital |
| 05 The seed and the first principal | Jul - Sep 2027 | $12M-$18M seed closes at 12-20x markup on SAFE cap, first principal meeting on calendar | The credentials that earn the embedding moment |
| 06 The embedding moment | Sep 2027+ | One Tier 1 principal embeds Nebula Verified in a live tender | The flywheel that runs without sales |
Every move in the eighteen months above is calibrated against the friction that has stopped every other contech startup from reaching the principal-side procurement conversation. The six strategic decisions below are why this chain reaction completes when others stall.
Nebula is not deployed to replace anything. It runs alongside the existing tools, the existing spreadsheets, the existing weekly meetings, the existing email chains. Nothing the manager already does has to stop. Nothing the manager already trusts has to be turned off. Nebula simply runs in parallel, on the same contract, and the manager checks in casually to see what it caught. If it catches things, the manager keeps using it. If it does not, they turn it off with one click and the project carries on exactly as it would have without Nebula in the room. The cost of trying it is not measured in dollars. It is measured in attention, and even attention is optional. Conservative buyers say yes to this conversation because there is nothing to say no to.
Not a demo, not a sandbox, not a time-limited trial. A real contract with real obligations, real enforcement, and real cryptographically anchored records. The financial cost of trying Nebula is zero, and combined with the run-alongside positioning above, the total cost of trying Nebula on the first project is zero in every dimension that matters to a buyer.
Once the first project is on Nebula, the obligation register, the enforcement history, and the proof ledger belong to that project. The counterparty now has a Nebula account with a reputation score. Leaving Nebula means leaving that record behind. The cost of switching grows every time the party signs something and keeps it. Zero risk in, real value out, and the value compounds with every project that gets added.
Nebula is built by a team with deep operational experience running the same infrastructure contracts the customers run. The first three to five conversations are peer-to-peer between people with shared daily problems, anchored on a published case study with real numbers. CAC for these conversations is effectively zero.
The bridge from peer-to-peer outreach to content-led inbound is not a content cadence. It is one published deployment with real numbers from a real counterparty-confirmed pilot. Once that case study exists, every LinkedIn post, every conference talk, and every investor conversation references it. The case study is the single piece of content that makes every other piece of content work.
Locus is already shipping. Compass is in development. Locus revenue subsidises the runway during pilot onboarding. Locus users are warm leads for Nebula. The two adjacent products turn $380K into eighteen months of operating runway plus a continuous lead generation stream that the SAFE alone could not buy.
The eighteen months above build the first turn of the flywheel. The five years that follow build the company that is irrational to compete with. Six plays compound on the same data asset, and each one is independently capable of becoming the company.
Once one Tier 1 principal embeds Nebula Verified in a pre-qualification framework, every counterparty on those projects must be on the platform. The certification cannot be replicated on any other system because the data is generated inside Nebula's compliance engine during real project execution. The network compounds from one principal outwards.
Reputation today tracks compliance: did you deliver on time? Contribution reputation tracks whether you actively helped the project succeed. Flagging a clash early, sharing lessons learned, resolving issues before they escalate. The system rates the interaction, credits the score, and notifies the win. Reputation becomes a measure of partnership, not just performance.
Nebula curates domain-specific intelligence relevant to each project. A battery storage project gets storage news, regulatory changes, standards updates. At platform scale, Nebula sees patterns no individual team can see: "14% of commissioning schedules across the platform are behind programme, common factor is inverter firmware delays." More projects on the platform means better intelligence, which attracts more projects.
A party with a verified score across forty agreements is demonstrably lower risk. Verified performance data feeds insurance underwriting and project finance lending. Underwriters and lenders become distribution partners. Nebula becomes a data provider to the financial industry the way Verisk became a data provider to property insurance.
Infrastructure disputes spend enormous time reconstructing what happened and when. Nebula's proof ledger is already an immutable timeline of every state change. Adjudication decisions reference Nebula proof records as evidence. Parties behave better because they know the record exists and is admissible. "The Nebula ledger shows..." becomes a phrase heard in adjudications.
Real-time visibility into delivery performance across hundreds of infrastructure projects. A fund evaluating an infrastructure developer checks their Nebula portfolio. A project finance lender requires Nebula as a condition of drawdown. Nebula transitions from a SaaS tool to the performance data layer for the built environment.
Every project tracked makes the rules sharper. Every party scored makes the certification more credible. Every principal who requires the certification pulls more parties onto the platform. Every paying customer extends the runway. The eighteen months above build the first turn of the flywheel. After Link 06, the wheel turns itself. Payment rails moved money. Nebula moves the record of what was actually done.