2026-04 · Heddle
A pre-launch SaaS built with my wife, whose exam-prep course is the anchor customer. Exam generation first, then memberships and blueprints replacing an admin password, then a semester orchestrator with a public syllabus. The launch push was shelved in July; the blueprint model became first-class data in September.
135
merges on the surface to date
n/a
pilot programs launched: no metric captured
n/a
records under management: no metric captured
When
Part of an arc of 3 merges on heddle, 2026-05-15 to 2026-05-17. The whole arc, derived from the record
walkthrough
The landing page's promise and the sign-in behind it: a magic link or Google, and an account that can say who did what.
2026-10-01 · The studio recorder against production (www.jakelawrence.xyz): headless Chromium, 390 by 844 at 2x, the site's own bumpers and music, nothing staged · on the Case Studies channel
Small exam-prep and credentialing programs track cohorts, exams, and completions in spreadsheets and office documents that cannot answer a question a semester later: which blueprint, which exam version, who was enrolled, who signed off.
Two people, nights and weekends, no funding, one anchor customer whose course was already running on the standalone pipeline. Every feature had to survive the question of whether it made the record more defensible.
Treat the exam blueprint and the exam membership as the data model, not the UI. #430 replaced admin-password auth with exam_members and exam_blueprints; #445 and #451 built the semester orchestrator and a public syllabus viewer on top of them; Phase 2 (#2316) made credential blueprints first-class data rather than configuration.
Rejected
A shared admin password
It is how the first version worked. It cannot say who did what, so it could not survive an audit question, and real memberships replaced it.
A generic LMS integration
Programs do not lack courseware; they lack a defensible record of who was certified against which blueprint.
An exam generator, a public landing page, self-serve sign-up and login, memberships and blueprints, a semester orchestrator with a public syllabus viewer, and Phase 2 credential blueprints as data. Pre-launch.
The landing page was the second merge, and the launch push was shelved by July (#1921). Credential blueprints became first-class data two months later (#2316), which is the order it should have gone in from the start: schema, then product, then the page that sells it.
supabase/exam_blueprints_schema.sqlsupabase/heddle_events_schema.sqldocs/surfaces/heddle-app.mdnpm run heddle:agent-evalsHeddle exam generator + /crss/bank Supabase hardening
#281 · 2026-04-20 · feature · +1,540 −247, 11 files
Add /heddle public landing page
#367 · 2026-05-15 · feature · +1,775 −5, 23 files
heddle: self-serve sign-up + login at /heddle/login
#371 · 2026-05-15 · feature · +1,234 −66, 18 files
heddle: exam_members + exam_blueprints, replace admin-password auth
#430 · 2026-05-17 · feature · +808 −55, 10 files
heddle: semester orchestrator + public /syllabus (foundation)
#445 · 2026-05-18 · feature · +2,036 −4, 9 files
heddle: orchestrator step 7 — publish + public /syllabus viewer
#451 · 2026-05-18 · feature · +1,969 −2, 11 files
docs: shelve the Heddle launch push + shutter the /lcl roadmap
#1921 · 2026-07-09 · docs · +206 −22, 9 files
Heddle Phase 2: credential blueprints as first-class data
#2316 · 2026-09-03 · feature · +5,596 −694, 58 files
Checked at build against the published corpus.
www.jakelawrence.xyz/research/case-study-library/heddle
Cite: Lawrence, J. (2026). Heddle: credentialing infrastructure for exam-prep programs that run on spreadsheets. jakelawrence.xyz case study library.
I build the AI tools and automations a team adopts, and the full-stack apps and data pipelines under them, and ship them to production. Tell me the problem in a sentence and I'll give you an honest read on fit within a day.
Work with me →