The program platform of a university startup incubator: five roles, data rooms, quarterly assessments, mentoring, events and venture snapshots
A university incubator’s whole program on one platform, built in PHP from a governed specification and running live: sign in as any of its five roles.
Larkspur Launchpad is the platform a university’s startup incubator runs its program on: the startups’ profiles and confidential data rooms, quarterly assessments that place each startup on a growth ladder, a community feed, events and lab space, a mentor network with matchmaking, and curated snapshots for investors and the university’s leadership. The specification was written from a real incubator’s requirements and anonymized into a fictional institution, Larkspur University, with fictional people and startups throughout.
It was also a test of the method on unfamiliar ground. Every earlier build had been TypeScript; this one was declared in PHP and Laravel, a stack the pipeline had never built in. The question was whether the governance carries over: the same specification-first contract, the same gates, the same refusal to call anything done that a gate has not graded.
The specification covers seventy requirements across nine areas of the program, each traced to the activity in the specification that produced it and each carrying criteria stated so that they can pass or fail. Its sharpest part is an access table that is the complete authorization model: who may see a data room, who may read a detailed snapshot, what an investor or a member of leadership never sees. Every route the application serves was held against it.
It also treats the demonstration as a feature rather than an afterthought: a seeded program with dated history, one-click sign-in as any seeded person, a reset that restores everything, and no outside services at all. Questions the specification left open were put to its owner and settled as written rulings before the build relied on them.
The build ran in three phases over two governed cycles in November 2026. Phases one and two laid the foundation and the core of every role’s work: profiles and data rooms, assessments, the feed, events and facilities, mentoring and administration. Phase three added the snapshots for investors and leadership, the program dashboard, the access and audit logs and the demonstration itself. Each cycle ended at a gate that graded every criterion up to that phase against the code.
It is a server-rendered Laravel 12 application on SQLite, with Blade pages and Alpine.js and nothing loaded from another host, deployed as a single container. Two hundred and sixty criteria were graded by the gates, and the suite stood at 2,596 tests at the close.
The gates said no before they said yes. Phases one and two came back to remediate at 180 of 186 criteria, the misses in upload limits and one kind of item in the approval queue; one remediation pass and a re-gate closed them. Phase three came back at 258 of 260, a roster detail and a refuted pass; both closed the same way. Each phase was accepted only after remediation, and the record keeps both verdicts.
Then the specification was read against the finished code by a reviewer who had not seen the build: all 243 statements of its specification, twenty-four findings, nine of them real and unrecorded. Four were fixed in code, among them a revocation the server should have refused and a password that should not have outlived demonstration mode; the owner ruled on the other five. A separate code review found nothing that should have stopped the merge, and the specification’s owner walked through every role at desktop and phone sizes before it was handed over.
What it is not is said plainly. It is a demonstration for one presenter at a time, not a production deployment: email goes to an in-app outbox rather than out, and every address in it is a sample. A few smaller items, among them a fuller seeded history, are written down for a next cycle rather than claimed.
The company is invented. The numbers are not: the estimate, the price and the measures of the software are as they stood.
Priced the conventional way
$56,430
~376 hours
the M6 estimate: the specification priced at standard AI-assisted rates, $150/hr blended
Priced like SaaS
$5,600 down
+$560 / month
Or own it outright: $28,200
260
Criteria the build was held to
seventy requirements; every criterion graded by a gate
5
Roles, each seeing only what it may
staff, founders, mentors, investors and university leadership
2,596
Tests at the close
PHP and Laravel, the method’s first build in the stack
Behind these numbers is the run itself — its gate verdicts, scorecards, rulings and phase reports, and how long and how much it took. All of it is available for review when you want to check it. Ask, and we will walk you through it.
A live demonstration: sign in as any of the five roles with one click, and reset it when you are done. The code is available on request rather than as a snapshot.
This build is evidence for one door on the homepage: Building something completely new. The method behind it is the same for every project.
Founders get this same build through 100Startups. If you’re building something new and can prove people will buy it, we build it with you. Every founder starts with our sales system, vhOS, free for three months, to show they can find demand and sell to it. Explore 100Startups
The other builds
The smallest possible project, run end to end, to show the method with nothing to hide behind.
A multi-role marketplace, regenerated from its spec eight times, because when building takes hours the spec is where you iterate.
An enterprise specification taken through the full cycle: six phases, every one gated, accepted after remediation, with the record of every no along the way.
Built before any contract, for a real prospective client, so the conversation could start from working software rather than a proposal.