Two weeks, assessed. Ten modules taught you the pieces one at a time — the queue alone, one angry customer alone, one channel alone. This is what happens when they all break in the same week, for a brand you have never supported before, with more arriving than you can finish. You are marked on judgement and on what you chose to leave undone. Not on tidiness.
Ijeoma Chukwu founded Mira Home four years ago — handmade ceramics and homeware out of a small Lagos studio, shipping across Nigeria and, since this year, into Ghana. She ran support herself from launch until three weeks ago, when a feature on a popular lifestyle page sent a month's worth of orders in four days. She hired you cold, this week, with no handover, because the inbox alone became more than one person could hold — and then, two days before you started, a batch of bowls shipped with visible glaze flecks that some customers read as damage and others read as the handmade character Mira Home has always sold on.
Every earlier drill in this course handed you one broken thing at a time. This one hands you a brand that has been quietly breaking for four unattended days, all at once.
You've been brought in — cold, no relationship built up over nine modules the way Tolu's was with Bumi Naturals. Everything you know about Mira Home, you'll learn from what's sitting in front of you today: the ticket queue across three channels, one public complaint that's picking up replies, a return policy that never anticipated this exact situation, and a chatbot Ijeoma set up herself last month without asking anyone to check what it was actually saying.
This is deliberate. Every brand you support after this course will start exactly like this — a stranger's backlog, no context you didn't build yourself, and a limited window before something in it actually costs a customer, or the brand's reputation, real money. The capstone is not harder because the tasks are new. It's harder because nothing has been warmed up for you first.
Sixty-odd tickets across three channels, a public thread gaining replies by the hour, a policy grey area with real money on either side of the answer, and ten AI-drafted replies that need checking before any of them go out — this is engineered to exceed what a careful person can fully complete in the time given. What you triage, what you leave undone, and how you explain that choice in the walkthrough is being assessed as closely as the work itself.
Five inputs, all live at once, exactly as they'd arrive on a real first week covering someone else's launch fallout. Use every module's disciplines — nothing here is solvable with only one module's toolkit.
Rather than being handed a pre-built dataset, construct a realistic version of each input yourself — sixty-ish invented tickets across three channels, a real comment thread with a dozen replies, Mira Home's actual return-policy text with its real gap, ten AI-drafted replies with three genuine invented-policy errors planted in them, and a week of ticket numbers that tell an honest, specific story. This is itself part of the assessment: a capstone built on inputs you designed with real judgement about what a bad week actually contains is a stronger piece of work than one built on a thin or unrealistic version of the mess.
Treat this as live, not static — new tickets, a new reply on the public thread, a follow-up question from Ijeoma partway through, arriving while you're still working through the original backlog. Real brand weeks don't pause while you catch up, and neither should this one.
Every deliverable draws on a specific earlier module. None of them are new skills — this is entirely about applying what you already have, under real pressure and without a handover.
The judgement log isn't just module 2's triage categories copy-pasted — it's your own reasoning about which of Mira Home's sixty tickets was the one that actually mattered most, argued in your own words, including exactly how you resolved the glaze-fleck grey area and why. The three-way check on the AI replies isn't a checkbox exercise — it's catching a specific invented discount before it costs Ijeoma real money, and being able to explain precisely how you caught it.
Submitting the six deliverables is not the end of the capstone. A short walkthrough — five minutes presenting the work, followed by being challenged on it — is where the judgement behind the deliverables actually gets tested, not just the finished output.
A polished deliverable proves you can produce good work. A well-handled challenge proves you can defend the thinking behind it — which is what a real founder is actually trusting you with.
Not a tour of all six deliverables in equal depth — that's too much for five minutes and dilutes the parts that matter most. Instead: the single hardest judgement call you made this week, what you chose to leave undone and why, and one thing you'd do differently with another day.
Expect direct questions that press on the actual judgement, not just the output — the kind a real founder, or a course assessor standing in for one, would genuinely ask:
Not defensiveness, and not instant capitulation either. A well-handled challenge sounds like: stating the reasoning plainly, acknowledging genuinely if the challenge reveals something that was actually missed, and holding the decision if it was actually right and the reasoning still holds under pressure. This is the same three-way check discipline from module 7, turned on your own judgement instead of an AI tool's output.
Every capstone gets challenged, including strong ones — it's built into the format deliberately, not triggered by a weak submission. Treat a hard question as a normal part of the format, not a signal you're about to be told you failed.
Not on whether all sixty tickets got answered, whether the public thread got a reply within the hour, or whether every deliverable is fully polished. On whether the judgement behind a genuinely bad week's worth of decisions was sound, defensible, and honestly reported.
Every module's drill tested one discipline under one kind of mess. This tests whether all ten disciplines survive contact with each other, at once, under real pressure, for a brand you've never supported before — which is the actual job, on the actual first week of any real engagement. That is the entire promise of this course's title: a rep whose ticket doesn't come back, because the judgement behind it holds up.
You now have a complete, honestly-labelled portfolio piece spanning every module in this course — exactly the kind of proof of work module 10.3 described, built under real assessed pressure rather than a practice exercise. Use it. It is, quite literally, the proof that the support you provide is not easily replaced.