AAW · Internal · Training session, 14 Jul 2026

Khlark's Lane, Step by Step

The full handoff, start to finish. Bella Cache is the real example. Ei is almost done with her images. That means Khlark is one step away from doing the marriage himself.

Right now Bella Cache · images ~done · next up: the marriage (step 10) · nothing pushed to GHL yet
The full pipeline — one idea to one live brand13 steps, 2 owners
1Ryan books call
2Discovery
3Mockup
4Payment
5Onboarding
6Launch call
7Follow-up
8Content
9Images
10Marriage
11Push
12QA
13Live
 at the launch call, the baton passes 
Sergio — sells the brand Khlark — builds, launches, maintains Where Bella Cache sits today

What Khlark inherits

Sergio's half, steps 1–6

Khlark doesn't need to run this half — he needs to know what lands on his desk when it's done. Sergio wins the client (Ryan books the call, discovery, mockup, payment, onboarding) and closes it out on the phone at the launch call. Everything after that is Khlark's file. Regina Ayars just came off her launch call — she's a second live example sitting at step 7 right now.

Khlark's lane

Steps 7–13, worked on Bella Cache

Once he owns the file, this is the order it moves in. Every step below shows what's actually true for Bella Cache right now — the real file names, the real folders, the real dates.

7
Khlark

First follow-up call

Khlark meets the client fresh off the launch call — introduces himself as the person who takes it from here, sets expectations for the six-month build.

Bella Cache
Juanita's launch call was 2026-06-02. Her file is already past this step — content and images are underway.
8
Claude writes

Content — six months

Claude drafts the full run: weekly blogs + biweekly newsletters, each one a markdown file with a title, a category, and a publish_target date already assigned from the 24-month calendar.

Bella Cache — drafts/blog/
2026-07-week-1-the-day-i-started-sketching.md · category: Stories · publish_target: 2026-07 week 1
9
Ei makes them

Images

Ei works from the brand's Image Guide — the approved anchor photo, plus copy-paste prompts for every shot the six months will need. Target is 90+ kept images per brand. She drops winners in the folder; nobody makes her name or file them.

Bella Cache
Guide: bella-image-guide.pages.dev · anchor: MASTER-LOCKED.jpg · status: nearly done

10 · The marriage

drafts/blog/2026-07-week-1-the-day-i-started-sketching.md
Khlark — this is the one to teach

Content and images get built on separate tracks by two different people. The marriage is where Khlark brings them together into one file: the right image, matched to the right story, locked to the right date. Nothing is live until all three legs are in the same document.

Words
Claude's draft — "The Day I Started Sketching"
Image
Ei's approved anchor — MASTER-LOCKED.jpg
Date
From the 24-month calendar — 2026-07, week 1
Before — content only
---
title: "The Day I Started Sketching"
category: Stories
publish_target: 2026-07 week 1
author: "{{FOUNDER_NAME}}"
slug: the-day-i-started-sketching
status: draft
---
After — married
---
title: "The Day I Started Sketching"
category: Stories
publish_target: 2026-07 week 1
hero_image: MASTER-LOCKED.jpg
author: "{{FOUNDER_NAME}}"
slug: the-day-i-started-sketching
status: draft
---
The judgment call: a script (tag_hero_images.py) can auto-match most files by slug and category — but Khlark is the one who checks it actually makes sense: does this image belong to this story, on this date, for this brand's voice. That check is the real skill. Auto-match gets it close; Khlark gets it right.

This is not one file. This is the real count.

You just saw one married file. Here is how many Bella Cache actually has sitting in her folder right now, counted today — every single one needs the same check before it can go live.

78
blog posts
39
newsletters
390
social posts
109
images ready
Total pieces to push, one brand 507
Where the 390 social posts come from: every blog and newsletter auto-spawns 3 social posts (announce + quote + echo) via aaw-social-spawn, plus roughly 50 hand-crafted standalone posts (founder voice, behind-the-scenes, customer story snippets with no blog tie-in). Khlark isn't marrying 390 posts by hand — the spawn tool inherits the parent post's hero image automatically. He's marrying the 117 blogs + newsletters; the social layer follows for free.
How often it goes out — every client, every month, forever
✍️
2
blog posts
a month
📧
1
newsletter
a month
📱
~91
social posts
a month, about 3 a day
Total, every month, per client~94
Updated 2026-07-14: this is the current standard, from the new build system (12 blogs + 6 newsletters + 546 social over a 6-month build). It replaces the old cadence — the numbers above the fold on this page (Bella's 78 blogs / 39 newsletters / 390 social) are what Bella actually has in her folder from before this change, not a preview of the new rate.
11
Khlark

Push + schedule

Once every file is married, Khlark loads it into the client's GHL sub-account and schedules it — the first post always at least 30 days out, so there's a real audit window before anything goes live.

Tool
push_to_ghl.py · images first, then blogs, then newsletters, then social
12
Ahtsham verifies

QA check

Ahtsham checks the push landed right — forms, domains, socials, author names — and gives phone support to the client. Khlark points him at what to check; Ahtsham doesn't drive the build.

13
Khlark watches

Live

First post fires on schedule. Khlark confirms it published, then the brand runs on its own for a while — until the runway needs refilling.

Khlark also owns — ongoing

Not one-and-done
Keep content fedSix months runs out. Khlark lines up the next six before it does — never let a client go quiet.
Facebook likesRuns the vanity/likes campaigns himself, on ad accounts he sets up, so each client's pages look alive.
Improve the dashboardHe uses it every day. Over time, he helps make it better.

Who Khlark calls in

He coordinates — they specialize
Images

Ei

All product images, hard ones especially. Khlark can back her up on simple shots only.

QA + phone

Ahtsham

Verifies the push, handles technical phone support. Khlark tells him where to look.

Content + pages

Claude

Writes the six months, builds every page. Khlark directs and approves.

The Dashboard

Khlark's main tool, every day
AAW Customer Command
aaw-inbox.pages.dev
Passwordaawteam2026

This is where Khlark works every day. One page, every client.

👥
Every client, in one listAll brands, in one place. No searching around.
💬
Every conversationTexts and emails from clients, in order, easy to read.
📌
What's next, for each oneOne line per client: the next thing to do.
🟡
Inventory clients marked goldClients holding physical stock stand out in a different color.
How to use it: open it first thing, every day. Check "New clients" at the top. Check the team queue. Reply to anything waiting. That's the whole habit.
Content Runway tracker
aaw-content-runway.pages.dev
Second tool. Shows who's running low on content before they go quiet.
Who Does What map
aaw-team-map.pages.dev
The team, in one picture. Good to keep open on day one.