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 that earns the credential. 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 the thing “Certified Sales with Claude” attests, and it is a higher bar than five modules completed: a certified seller is not someone who watched the track, it is 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
Clear the rubric and you earn “Certified Sales 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 whole account on a coherent system, not just describe the moves.
Here is the honest state of it today, because the credential is only worth what it honestly claims:
- A person grades it, now. In a cohort or concierge run, a reviewer scores your sales system against the master rubric above and tells you what is weak. The rubric and the senior-sales-leader bar are the IP, 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 sales system 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 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 certifying 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, clear the rubric, and the certificate is yours — because the work is.