Most education software serves one customer — the student — which is exactly why it doesn’t last: the university never sees retention, the employer never sees a pipeline, so no one keeps paying for it. The six-month mandate was to design the opposite: a four-sided value loop where students, the university, and employers each gain, and each gain funds the next. There was no template for it. This is how it was built — and what held it together was running product, go-to-market, and operations as one motion, not three.
Worked against a real institutional analysis — Central Connecticut State University (New Britain, CT). CCSU figures are public record (IPEDS / U.S. Dept. of Education College Scorecard). Pilot outcomes are the engagement’s model; employer partners shown by sector.
A platform that only helps the student creates no reason for anyone else to invest. The instinct is to add features. The actual fix is structural — make every party’s win depend on the next party’s win.
Student-only tool. The university sees a cost, not retention. The employer sees nothing. Funding dries up; the product churns out.
A loop. Student gains drive university retention; retention produces an employer pipeline; employer investment funds richer student gains. Self-reinforcing.
Start from the outcome each side needs, then build only what produces it. Four parties means four outcomes — and the product is whatever closes the gap between them. Below, each node is a party; the line under it is the outcome it must get for the loop to turn.
A four-sided loop can’t be handed off in pieces — the product design sets the pricing, the pricing sets what a university will commit to, and the operating model is what makes the pilot actually run. Holding all three at once was the job.
One front door per side of the loop — built around an identity score as the shared spine, with an early-warning view so retention can be acted on weeks ahead.
The evidence case — the institution’s own outcome data plus a workforce-corridor ROI model — sized to a two-cohort pilot a risk-averse buyer could say yes to.
Pricing benchmarked across EdTech categories, the founding-team operating cadence, and the CRM & investor-pipeline discipline to keep the raise and the pilot on track.
Modeled against CCSU’s real profile — ABET-accredited engineering, dual NSA cybersecurity designations, the region’s top teacher pipeline — scoped to the minimum that could run the loop end-to-end: two 12-week cohorts, 500 students.
Reference implementation of the product strategy. CCSU institutional figures are public record (IPEDS / College Scorecard); pilot outcomes are the engagement’s bottoms-up model, not a live deployment. Named employer partners are shown by sector.