How long does the capstone take?

It is a project, not a quiz, so it runs in days rather than minutes — but you are not starting cold. By now you have built most of these artifacts inside the five modules, so the capstone is mostly integration and polish: making the cold opener, the proposal, and the Arabic renewal offer sound like one company saying one thing. Most people who have worked the modules need a few focused days; spread across a few sittings it becomes the week's real work rather than an exercise.

Who grades the capstone, and how?

You do, and so does anyone whose judgment you trust. Score your sales system against the master rubric in this guide, then hand the same rubric to a manager or a peer on another team and compare reads. That is the point of writing the bar down: the rubric and the senior-sales-leader bar work in a one-to-one review exactly as they would in a classroom, and nothing here is scored automatically or recorded anywhere.

Do I use the sample account or my own?

Both work, and for a team we recommend your own. Bring a real account and the capstone doubles as deployable work — you walk out with a deal you actually advanced and a sales system you keep and run, which is day-one ROI rather than a coursework artifact. If you would rather learn on neutral ground first, use the sample — Mizan selling to Najd Logistics — worked through the whole track, then redo it for your own account afterwards.

Do I have to do the capstone, or can I stop after the modules?

You can stop — each module stands alone and leaves you with a usable artefact. The capstone is worth doing when you suspect the pieces don't yet cohere, which is the failure the modules can't catch on their own: five deliverables that each look fine and don't add up to one system. If you can already point at the through-line running through all five, you have what the capstone was going to teach you.

Is there a certificate for this?

No. There is no certificate, no exam, and no credential — this site does not issue one, and nothing here is scored automatically or recorded anywhere. What the capstone gives you is the work itself: the finished artifact it asks for, and the rubric you scored it against. In a hiring or a budget conversation a real deliverable with real sign-offs on it does more than a badge would, because the person across the table can read it and judge the work for themselves.

Account-in-a-Box — the Sales capstone

You have worked the five modules — the foundation, the outreach engine, running the deal, the big play, and measure and forecast. Each one ended with a graded artifact: a value narrative and a qualification rubric, a prospecting system, a discovery-and-proposal, an account play, a forecast with the loop closed. The capstone is where those five stop being five.

This is the integrative project. One brand, proven on one account, end to end — a complete sales system where every layer inherits the same value narrative and the same proof, in English and Arabic, from the cold opener to the renewal offer. That is a higher bar than five modules completed, and it is what the track was for: someone who has actually done this is not someone who read it, but someone who took an account from cold to won-and-growing on a system that coheres.

The capstone is not five assignments stapled together. It is one test: does the whole system hold as a single company saying a single thing, all the way through one account? A reader should not be able to tell that the cold email, the proposal, and the Arabic renewal offer were drafted in different sessions for different stages. Integration is the grade — coherence across the whole system, not five separate deliverables that each look fine alone.

The brief

Produce a complete sales system for one brand, and prove it by taking one account from cold to won-and-growing. We recommend your own — the capstone then doubles as a deal you actually advance and infrastructure you deploy (see Bring your own account) — or the sample, Mizan selling to Najd Logistics, the GCC bookkeeping brand and the prospect threaded through the whole track, if you would rather learn on neutral ground.

You already know the Desktop motion: open the account’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 fact-checks on request; you own every number, and a person clears the commercial gate before anything reaches the buyer.

Capstone deliverable — Account-in-a-Box (one brand, one account, end to end)

1. The foundation (Foundation / M1)
   - value-narrative.md — problem, pillars with proof, cost of nothing
   - icp.md + rubric — fit signals, disqualifiers, a scoreable score
   - battlecards.md — the hardest objections, honest reframes
   - value-narrative-ar.md — the Arabic value story, authored not translated

2. The outreach engine, running (Engine / M2)
   - the repeatable flow: qualify → research → write → sequence → log
   - a researched cold opener + a multi-touch sequence — EN + AR — on-narrative

3. Running the deal (Deal / M3)
   - a discovery capture that scores the account against the M1 rubric
   - a proposal priced ONLY from pricing.md, the commercial gate applied

4. The big play (Play / M4)
   - an expansion plan for the won account — every line an owner + a date
   - the deal-desk, legal, and Arabic sign-off gates as their own rows

5. Measure & the loop (Measure / M5)
   - a pipeline/forecast read: which deals are real, against the number
   - the loop closed: one versioned edit fed back into value-narrative.md

6. A short reflection
   - where Claude genuinely helped, and where your judgment was needed
   - one number you fact-checked, killed, or rewrote because a person had to

Every piece must inherit #1. That inheritance is the whole assignment.

The reflection is not a formality. Naming where you overrode the draft — the price you would not let go out without deal-desk, the ROI figure you marked [NEED] until you could source it, the Arabic line you re-authored because the translation read foreign — is part of the proof that you ran Claude well rather than letting it run you.

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 system that coheres in four places and drifts in the fifth still reads as two companies to the buyer, and a buyer deciding whether to trust you with their books reads drift as risk. The bar throughout is a single question: would a senior sales leader hand this proposal to a client, and put this number in the forecast?

Master rubric — Account-in-a-Box
Each criterion: meets / nearly / not yet. The bar: a senior sales leader
would hand this proposal to a client and put this number in the forecast.

1. Consistency — every piece sounds like one company
   meets One value story across all of it; a reader can't tell which
            pieces — opener, proposal, Arabic offer — were drafted in
            different sessions or different languages.
   nearly Mostly coherent, but one or two pieces drift in story or wording.
   not yet Reads like several reps — the cold email and the proposal don't
            sound related.

2. Clarity — one problem killed, proof-backed throughout
   meets One core promise carries the whole account; every claim traces
            to real proof; no pillar rests on an adjective.
   nearly The promise is there but blurs at the edges, or a claim or two
            ships without evidence behind it.
   not yet Different pieces sell different things; proof is thin or absent.

3. Used Claude well — drafted fast, fact-checked, a person decided
   meets Claude clearly did the heavy lifting, but every stat, price, and
            date was verified, the commercial gate held, and the reflection
            shows real human judgment overriding the draft where it mattered.
   nearly Mostly sound, but a number slipped through unchecked, or the
            judgment calls are asserted rather than shown.
   not yet Reads as raw model output — confident, unverified, undecided.

4. Arabic quality — an authored peer, not a translation
   meets The Arabic reads native: authored register, localized proof and
            objections, cleared the same deal-desk gate as the English.
   nearly Competent but translation-flavored, or the proof wasn't localized.
   not yet English run through translation; reads foreign; skipped sign-off.

5. Completeness — the whole system, coherent end-to-end
   meets All six parts present and connected: the brief feeds discovery,
            discovery feeds the proposal, the win feeds the expansion plan,
            the forecast feeds the foundation. One system, not six folders.
   nearly A part is missing, or present but disconnected from the rest.
   not yet A pile of deliverables, not an account.

Notice that three of the five criteria are about coherence between pieces, not the quality of any single piece. That is intentional. The modules already graded each artifact on its own; the capstone grades the seams.

Bring your own account

Use your own account. We recommend it for one blunt reason: the capstone stops being coursework and becomes two things at once — a deal you actually advance and infrastructure you keep. The system you assemble — the value story in both languages, the qualification rubric, the battle-cards, the outreach engine, the proposal apparatus, the forecast loop — is real infrastructure your team keeps and runs, and the account you run it on is a live deal moving down the pipeline. That is day-one ROI: the assessment, the portfolio piece, and the actual work are the same artifact.

The sample — Mizan selling to Najd Logistics — is here for when neutral ground is the point: a new rep learning the system, or a seller who wants to practice the integration once before doing it for real. Najd Logistics is worked through every module — scored a strong fit in M1, researched in M2, run as a deal in M3 — so you can study the moves on an account with no quota attached, then turn around and do it for your own. Either path clears the same rubric.

What you earn

Clearing the rubric means one thing, and it is the thing worth having: proof that you can run a whole account on a coherent system, not just describe the moves.

Two honest notes about how that judgement is made:

Have a person grade it. Hand the master rubric above to someone whose judgment you trust — a manager, a peer on another team — and have them score your sales system against it and say what is weak. The rubric and the senior-sales-leader bar are the useful part, and they work just as well in a one-to-one review as in a classroom.
It is not an accreditation-body badge. Its weight is the work behind it: a complete, coherent sales system that clears a professional standard. That is a real thing to point at — and a more useful one than a quiz score.

Nothing is gated, scored automatically, or recorded anywhere. What you take away is the system you built and an honest read on where it is weak.

What good looks like

The detailed examples live in the five modules. What the capstone adds is the through-line — the same value narrative visibly threading every layer of one account. Here is the Najd Logistics Account-in-a-Box at a glance, one or two lines per stage, so you can see the inheritance the rubric is really grading:

Najd Logistics — Account-in-a-Box at a glance

Through-line "Your books, done and trustworthy, without hiring an
               accountant." Lead pillar: trustworthy, not just fast —
               9,000+ GCC businesses; VAT-return-ready exports the FTA
               accepted without amendment in the 2025 cohort.

Foundation value-narrative.md + icp.md + battlecards.md, EN + AR. Najd
               scores 6/6 fit, 0 disqualifiers → STRONG. The Arabic story
               authored Gulf-natural — «عندي محاسب» leads, warmest.

Outreach The cold opener leads with the trust promise, not features:
               "close all three branches in one VAT-ready view." Sequence
               re-timed Sun–Thu; the Arabic opener pre-empts the accountant.

The deal Discovery surfaces the real pain (month-stale numbers, a
               weekend lost per VAT quarter). Proposal priced from pricing.md
               — Multi-branch AED 499 + 3×79 = AED 736/mo — anchored on the
               AED 1,000+ penalty. The number cleared deal-desk before send.

The big play Won. Expansion plan for the Q3 4th branch (+AED 79/mo) and
               the annual upgrade — every line an owner + a date; deal-desk,
               legal, and the Arabic sign-off are their own gated rows.

Measure Did "trustworthy" close better than "fast" this quarter? The
               forecast read feeds exactly one versioned edit back into
               value-narrative.md. The loop closes; the system learns.

Read it top to bottom and the test is obvious: the trust promise from the foundation is still load-bearing in the proposal price and the forecast question. Nothing drifted. That is what “meets” on consistency and completeness looks like — not five strong deliverables, but one promise that survives all the way from the cold opener to the renewal.

Now ship it

You have the brief, the rubric, and the bar. The capstone is not harder than the modules — it is the modules, run together for one account, with the seams made to hold. Pick the account, open the folder, and assemble the system Claude drafted and you decided.

Two things to keep beside you as you build: the Foundation toolkit — the sales CLAUDE.md and the templates every later piece is built on, so the whole system inherits one source of truth — and, if you are rolling this across a team rather than working through it yourself, the operating guide, the data, deal-desk, and sign-off layer that belongs underneath a team putting real deals through Claude.

Build the system and clear the rubric. The work is the point — and the work is what you keep.