THE LATTICEMETHODa five-stage course launch process

Every course I build goes through the same five stages, in the same order. You’ll always know which stage we’re in, what I’m doing, and what I need from you.
01
CLARIFY
02
STRUCTURE
03
AUTOMATE
04
LAUNCH
05
EMBED & OPTIMIZE

Stages 01 to 04 are Lattice Launch. Stage 05 is Lattice Keep.

01
A course plan made of sticky notes: who it is for, the promise, modules, emails and access
02 · Who it's for, and the promise · Illustration: The Lattice House

CLARIFYKnow what you're building before you build it.

We decide who the course is for, what it promises, and which platform fits how you already work. If you’re on the wrong platform, this is where I’ll tell you.
You bring
Your content or outline, who it's for, and your launch goal
You get
A written course brief and a platform recommendation
Time
[TIME]

STRUCTUREThe shape that holds everything else.

Modules, lessons and learning paths, mapped in order. We set the access rules (drip, gated or open) and design the first day a student spends inside.
You bring
Lesson files, videos and worksheets
You get
A course map you approve before anything is built
Time
[TIME]
02
A hand-drawn course map with five stages and a sticky note about drip access
03 · The course map you approve · Illustration: The Lattice House
03
A tablet showing a course lesson, next to a note: students in, emails sending, you teaching
04 · When someone pays, they get in · Illustration: The Lattice House

AUTOMATEEvery trigger, mapped and tested.

Payments, access, emails and integrations get connected, then tested until they behave. When someone pays, they get in. When someone joins, they get welcomed.
You bring
Logins to your platform, payment and email tools
You get
Working automations and a map of what triggers what
Time
[TIME]

LAUNCHSteady on the day you promised.

Before the doors open, I test every path a student can take: buying, logging in, finding lesson one, getting the right emails. Then we go live on the date you announced, and I stay close for the first 30 days.
You bring
Your launch date and announcement plan
You get
A live course, a build record, a walkthrough of your backend, and 30 days of launch support
Time
[TIME]
04
A pre-launch QA checklist on a clipboard with student paths ticked off
05 · Every student path, tested · Illustration: The Lattice House
05
A Lattice Keep monthly report with a bar chart and a handwritten note
06 · A Keep report, month two · Illustration: The Lattice House

EMBED & OPTIMIZELaunch day is day one.

With Lattice Keep, I stay in the backend after launch. Student issues get handled, automations get checked, and each month we improve one thing that moves completion, retention or revenue.
You bring
Your next ideas and what students are telling you
You get
A short monthly report and a quarterly improvement plan
Term
3 months to start
EXPLORE KEEP →

TWO WAYSIN

NEW LAUNCH

Launch + Keep

Your content is ready and the course doesn’t exist yet. We run all five stages, starting with Clarify.
EXPLORE LAUNCH →
Two course maps side by side: a tangled before version and a tidy after version
07 · A takeover, before and after · Illustration: The Lattice House
TAKEOVER

Handoff + Keep

Your course is running and it’s become a drag. I take over the backend, stabilize what’s breaking, then move into Keep.
EXPLORE KEEP →

NOT SURE WHEREYOU'D START?

The Lattice Audit tells you which stage your course is in and what to fix first.

START THE LATTICE AUDIT
or book a call