For edtech founders
Ship what learners and institutions actually use.
Teachers are overwhelmed. Administrators want LMS integration. Budget cycles are annual. Engagement metrics misrepresent learning. The edtech pattern, and how to design around it.
The pattern in edtech teams
You built a product that demos beautifully and that pilot users love. Six months in, the schools that signed up are not renewing. The corporate learning customers are renewing but engagement is flat. Time-on-platform is being mistaken for learning.
The product roadmap is split between three buyers: the learner, the teacher or admin, and the procurement office. Each wants different things. The team is building for all three and shipping for none of them.
The bottleneck is not features. It is that nobody has explicitly decided whose problem the product is built to solve first, and what counts as solved.
What we bring to edtech teams
01
Decisions on which buyer the product serves first
The Clarity Sprint forces explicit choices on whose workflow comes first, what completed-learning success means, and which features serve the buyer vs. which serve the learner. Documented, signed, traceable.
02
Institutional integration realities
LMS integration (LTI, Canvas, Moodle, Google Classroom), SSO with school identity providers, FERPA and COPPA-aware data handling, gradebook export shapes that work with what schools already use. The integration patterns are the moat.
03
Engagement metrics designed for learning, not time-on-platform
We design the metric for outcomes you can defend in a renewal conversation. Mastery rate. Completion against a goal. Time-to-competency. The metrics that earn the next year of budget, not the metrics that look good in a dashboard.
What this has looked like
Pattern 1
K-12 edtech, pilots not renewing
Pilots loved the product in the first month and quietly stopped using it by month three. Teachers said the gradebook export was painful and the LMS integration was broken.
Mapped the teacher workflow. Rebuilt LMS sync as the first-class data flow. Designed gradebook exports that matched what districts actually needed. Renewal posture flipped because the product earned its way into the existing workflow instead of asking teachers to change theirs.
Pattern 2
Corporate learning, engagement flat at 30 days
Mandatory completion rates were strong. Voluntary engagement after the mandatory period dropped to single digits. The team kept adding course content.
Diagnosed that the product had no recurring use case after the initial certificate. Designed a competency-tracking loop tied to performance review cycles. Voluntary engagement recovered because the platform served a real ongoing job-to-be-done instead of just course delivery.
If this sounds like your edtech build
Start with a Clarity Sprint. Two weeks, fixed price. You leave with explicit decisions on which buyer is served first, what learning success means, and what to actually build next.