You have worked the five modules — the foundation, from idea to prototype, signal to decision, the roadmap pipeline, and planning & the board. Each one ended with a graded artifact: a product-context doc, a market-landscape read, and a codebase map; a validated v1 spec and a clicked, decided prototype; a roadmap signal weighted by real customers and a decision memo that survived its own counter-argument; a compounding stakeholder-update system and a roadmap-ready memo chained from request to recommendation; a quarterly plan with a real cut list and a board narrative built before the slides. The capstone is where those five stop being five.
This is the integrative project that earns the credential. One company, one product organization, end to end — a complete system where the spec gets pressure-tested against the same anti-focus the board narrative cites, where the roadmap memo’s demand evidence is the same synthesis the quarterly plan’s themes are built from, and where the board’s numbers are the same ones the stakeholder update already sent. That is the thing “Certified Founders & PMs with Claude” attests, and it is a higher bar than five modules completed: a certified founder or PM is not someone who watched the track, it is someone who can run a complete product organization where every commitment traces to evidence and every figure that reaches a stakeholder has already survived the second question.
Five modules teach you the moves. The capstone proves you can run them as one system — a complete product organization where the context doc, the validated spec, the decided bet, the roadmap memo, and the board narrative all inherit the same source of truth. A reviewer should not be able to tell that the context doc, the feature spec, and the May board narrative were drafted in different sessions for different problems. Integration is the grade, not five separate artifacts that each look fine alone.
The brief
Produce a complete product organization for one company, and prove it by running that company’s product operation from a real customer signal to a committed, board-ready roadmap item, end to end. We recommend your own company — the capstone then doubles as deployable infrastructure you keep and run (see Bring your own company) — or the sample, Mizan’s product organization, the GCC bookkeeping SaaS whose co-founder and Head of Product, Dana Al-Qassimi, is threaded through the whole track, if you’d rather learn on neutral ground.
You already know the Desktop motion: open the company’s folder in Claude Desktop, approve each read in the “Ask permissions” prompt, and assemble the system in the chat and the file pane. No terminal on this path. Claude drafts fast and states facts and estimates with total confidence; you own every claim that leaves the folder. A person decides the anti-focus, the out-of-scope line, the bet to fund, the recommendation to commit, and the cut list — Claude is never one of those four roles.
Capstone deliverable — Roadmap-in-a-Box (one company, one product
organization, end to end)
1. The foundation (Foundation / M1)
- product-context.md — the user, the bets, the anti-focus, the
constraints
- market-landscape.md — competitors incl. non-consumption, an honest
win/lose read, the chosen wedge
- codebase-map.md — verified, naming real files
2. From idea to prototype (Validate / M2)
- spec.md — a v1 spec for one real feature, edge cases decided, an
out-of-scope line checked against the anti-focus
- prototype.html + decision-note.md — clicked, honest
3. Signal to decision (Decision / M3)
- feedback-signal.md — themes weighted by distinct customers, real
quotes, ranked bets
- decision-memo.md — a recommendation that survived its own
counter-argument
4. The roadmap pipeline (Roadmap / M4)
- one week's stakeholder update, internal + investor versions, no
invented numbers
- roadmap-feature.md — a request chained from demand verdict to a
red-teamed, roadmap-ready memo
5. Planning & the board (Board / M5)
- quarterly-plan.md — a locked frame, scored initiatives, a real
cut list, a capacity check
- board-package — a locked arc, a metrics-backed outline, a
pre-read, rehearsed hard questions, a consistency pass
Every piece must inherit #1. That inheritance is the whole assignment.The integration is not a formality. A reviewer will read the roadmap memo and check whether its out-of-scope line cites the same anti-focus product-context.md states. They will read the quarterly plan and check whether its committed themes trace to the same feedback-signal.md the roadmap memo cites as demand evidence. They will read the board narrative and check whether its headline numbers are the ones the stakeholder update already sent. Where those seams hold, the system works. Where they drift, the capstone flags a revise.
How it’s assessed — the master rubric
Five criteria, each scored meets / nearly / not yet. One “nearly” anywhere is a revise, not a pass — because a product organization that’s coherent in four places and drifts in the fifth still means a commitment reaches a board unchecked, and that is exactly when coherence matters most. The bar throughout is a single question: would Dana Al-Qassimi — or the most skeptical co-founder you know — sign her name to this spec, this memo, and this number?
Master rubric — Roadmap-in-a-Box
Each criterion: meets / nearly / not yet. The bar: would a skeptical
co-founder sign their name to this spec, this memo, this number?
1. The foundation is actually load-bearing
meets The anti-focus in product-context.md is cited by name in
at least one later out-of-scope line. The wedge in
market-landscape.md is cited in the board narrative. No
later artifact contradicts the foundation it inherits from.
nearly The foundation exists and is mostly consistent, but one
later artifact restates a priority slightly differently
without flagging the deviation.
not yet Later modules read as if the foundation were never opened —
priorities, the anti-focus, or the wedge are reinvented or
ignored.
2. Every commitment traces to evidence
meets The roadmap memo's demand claim, the quarterly plan's
theme, and the board narrative's headline all point to the
same underlying synthesis — not three separately-asserted
versions of "customers want this."
nearly Most commitments trace cleanly, but one initiative appears
in the quarterly plan without a named evidence source.
not yet Commitments are asserted without a traceable source
anywhere. A reviewer has no way to check a claim short of
taking it on faith.
3. Data safety
meets Customer-identifying data stayed in the workspace
throughout — feedback is de-identified with [customer-n]
labels, the codebase read stayed confidential, and no cap
table or unreleased financial detail appears in a
submitted artifact.
nearly One artifact contains an un-redacted customer detail that
should have been de-identified, or a confidential figure
that should have stayed in the approved workspace.
not yet Raw customer identities or confidential financial detail
appear directly in a submitted artifact.
4. Arabic quality (bilingual founders)
meets Any Arabic artifact — the context doc, a spec, the board
pre-read — is authored in Arabic from the same underlying
facts, not translated from the English draft. Numbers stay
Western numerals; both languages cite the same figures.
nearly Competent but translation-flavored, or the Arabic and
English versions could plausibly cite different numbers.
not yet English run through translation. Reads foreign. Or the
Arabic pieces were omitted where they were called for.
5. Completeness
meets All five modules' artifacts are present and coherent. The
board narrative's hardest question has an answer grounded
in a real artifact from an earlier module. A new hire
could pick up this folder and understand the company's
current bet without asking you a question.
nearly A phase is present but disconnected — a quarterly plan
that doesn't actually feed the board narrative it should
have informed.
not yet Fewer than five phases, or phases present but not
connected to each other.Notice that four of the five criteria grade the seams between phases, not the quality of any single document. The modules already graded each artifact alone; the capstone grades whether the context, the spec, the decision, the roadmap memo, and the board narrative hold together as one product organization.
The five gates — what each module proved
The foundation (M1) proved that you can ground a company’s strategy in something concrete rather than a vibe. The reviewer checks that product-context.md names a real anti-focus with reasons, that market-landscape.md includes the non-consumption competitors and an honest win/lose read, and that codebase-map.md traces a real flow naming actual files — not a plausible-sounding guess about code nobody opened.
From idea to prototype (M2) proved that you can turn a request into a decided, scoped feature before a single engineer is pulled in. The reviewer checks that the spec’s out-of-scope line ties back to the foundation’s anti-focus, that the edge cases carry stated resolutions rather than “use judgment,” and that the prototype’s decision note is honest — including a genuine “not yet” where that’s the real call.
Signal to decision (M3) proved that you can tell a real pattern from a loud minority, and defend a recommendation that’s already survived its own counter-argument. The reviewer checks that every kept theme carries real quotes from distinct, de-identified customers, that the decision memo names explicit priorities before comparing options, and that a genuine steelman of the opposing view appears and was actually weighed.
The roadmap pipeline (M4) proved that you can keep stakeholders informed without inventing a number, and chain a request to a recommendation that survives scrutiny. The reviewer checks that the stakeholder update carries [TODO: confirm] rather than a fabricated figure for anything unsupplied, and that the roadmap-feature memo’s eng scope names real files an engineer could verify, not a guess about effort.
Planning & the board (M5) proved that you can run your company’s two highest-stakes recurring moments as a discipline, not a scramble. The reviewer checks that the quarterly plan’s cut list names a real reason per exclusion, that the board outline’s every claim ties to a number you supplied (or is honestly flagged [NEED: …]), and that the hard-questions prep includes the genuinely uncomfortable ones, answered honestly.
Bring your own company
Use your own company. We recommend it for one blunt reason: the capstone stops being coursework and becomes two things at once — the actual product infrastructure your company runs on, and the credential that proves you built it to a professional standard. The context doc, the validated spec, the roadmap pipeline, the planning-and-board discipline — this is not a portfolio artifact, it is the system you open on Monday morning. That is day-one ROI: the assessment and the operational work are the same artifact.
The sample — Mizan’s product organization — is here for when neutral ground is the point: a founder or PM who wants to practice the integration once before rolling it out on a live company, or a team buyer who wants a worked reference to show the team what the output looks like before committing to the build. Either path clears the same rubric.
Sample brand: Mizan’s product organization {#sample-brand-mizan}
Mizan is a GCC bookkeeping SaaS with roughly 9,460 active customers, a co-founder and Head of Product — Dana Al-Qassimi — who runs the product organization across the company’s other functions, and a Q1–Q2 2026 story that runs through every module in the track. Use it as your sample and the full arc is already threaded for you:
The foundation captured Mizan as it actually is — bookkeeping for GCC SMBs, betting on billing trust, GCC-compliance depth, and an Arabic-native product, explicitly not chasing enterprise or multi-currency this phase. The market read named the regional cloud rival and “a spreadsheet plus an external accountant” as the real competitors, and staked Mizan’s wedge on Arabic-native, compliance-first bookkeeping. The codebase map traced Mizan’s renewal pipeline — billing/renewals.ts firing the charge, billing/webhooks.ts calling Stripe, invoice.ts generating the record — the same billing module Engineering’s Bilal Al-Mansouri was modernizing that quarter.
The validate module responded to the thing the foundation flagged as a risk made real: a March 1 billing incident. Dana specced and prototyped “flag a charge” — a self-serve dispute button plus a support triage view — with an out-of-scope line (no automatic refund) checked directly against product-context.md’s billing-trust bet, and a decision note honest about the one UI fix the prototype actually needed before it was worth building.
The decision module synthesized the fallout: 11 distinct customers from the March 1 incident (the same incident Support found via ticket triage and Data independently root-caused via a quality audit — two teams, two methods, one confirmed cause), plus a real, smaller pattern asking for native VAT export. The decision memo weighed building VAT export natively against integrating a third-party tool, recommended native on the compliance-depth priority, and survived a skeptic’s steelman that six eng-weeks should have been bought, not built.
The roadmap pipeline ran Mizan’s May 2026 stakeholder update — MRR at AED 508,000, Active Customers at 9,460, logo churn down to 1.2%, the same numbers Data’s Maya Haddad reported and Finance’s Youssef Hamdan reconciled into the board pack — stated plainly alongside the lowlight: 11 customers double-charged before the fix shipped. The roadmap-feature chain ran the flag-a-charge request from demand verdict through to a red-teamed, eng-scoped, roadmap-ready memo.
The planning and board module set Q2’s frame — billing trust is the one thing the quarter must move, given the CSAT slide from 4.7 to 4.2 — committed the flag-a-charge safeguard, native VAT export, and the Q2 save-flow, and named a real cut list (enterprise SSO, custom branding, a mobile app — each with a reason). The board narrative locked a four-sentence arc around the May close (revenue 512k, spend 472k, net +40k, ARR 6.1M), cited the same CSAT and incident numbers the stakeholder update already sent, and rehearsed the hardest question — “why should we trust the fix holds?” — with an answer grounded in the actual engineering postmortem, not a reassurance.
Run all five phases on Mizan and the capstone story is complete: one company, one chain of trust from a customer signal to a board the founder can stand in front of. Then run it again on your own company, and the infrastructure is yours.
What the certificate honestly means today
Clear the rubric and you earn “Certified Founders & PMs with Claude” — a verifiable page at /cert/[id] you can share and add to LinkedIn. It is the credential of the team track: proof that you can run a complete product organization on a coherent system, not just describe the moves.
Here is the honest state of it today:
- A person grades it, now. In a cohort or concierge run, a reviewer scores your product organization against the master rubric above and tells you what is weak and what to revise. The rubric and the skeptical-co-founder bar are the product, and they are hand-gradeable today — that is the deliberate first step, not a placeholder.
- AI-assisted grading on the same rubric is next, not a claim we make yet. When it ships, it grades against this exact rubric — the bar does not move, the reviewer does.
- It is not an accreditation-body badge. Its weight is the work behind it: a complete, coherent product organization a reviewer judged against a professional standard. That is a real thing to point at — and a more useful one than a quiz score.
No automated verification or paywall is wired behind this today that the line above does not describe. The certificate means what the work means.
What’s next
After the certificate, keep two things beside you as you run the system: the Founders & PMs operating guide — the decision-and-data-safety layer that belongs underneath a founder putting real strategy, customer feedback, and board material through Claude — and the foundation toolkit from Module 1, the product-context.md and market-landscape.md files that every later commitment inherits. When your strategy genuinely shifts, update those two files and the whole system updates with them.
A manager dashboard — a team view of who is certified and where the roadmap pipeline stands — is in the roadmap and is not a claim we make today. When it ships, it lands directly into the planning system you built here.
The next capability track is your call. If your company’s board pack leans on the same close this story reports, the Finance & Ops track covers the reconciliation and controls discipline underneath those numbers. If the engineering quarter this roadmap commits is the one you want to understand more deeply, the Engineering track covers reading and shipping inside the codebase this module only mapped.
Build the system, clear the rubric, and the certificate is yours — because the work is.