Collins — Start Plan & Your First 6 Weeks
2026-07-13 · Role: first Builder, St. Pierre Digital · You accepted on the Jul 13 call. Terms: $1,000/month, paid weekly at $250. Part-time, about 20 hours a week for the first month. We ramp toward full-time in about a month if it's working. Start: Jul 14. First proof after week 1.
Your mission in one line
Your first job is to automate client onboarding and launch client campaigns. Build the repeatable path from signed-and-paid to a working CRM, tracked lead flow, and a first campaign staged Paused. Then run the client's first six weeks from the same playbook. Akash keeps sales, spend approval, and off-script client sends.
Your first build project: automated client onboarding
Start this on Day 1. The live Onboarding + Campaign Launch SOW is your job packet and wins over older onboarding notes. It includes the build, launch gate, six-week client-delivery loop, scorecard, testing, rollback, and every linked system.
How your day runs
- 1–2 PM: you and Akash meet live, every day during the ramp.
- 2–4 PM: your focused build time.
- 4 PM: you post a short end-of-day report in Slack (#daily-reports).
Slack is our team chat. You join on day 1. Channels: #daily-reports (your report + numbers), #client-onboarding (your first build), #call-ins (booked calls), #notes (quick thoughts), #documents (file links). WhatsApp stays only for quick pings until you're set up in Slack. The full day plan is in the Daily Operating Rhythm.
One thing to confirm at kickoff: you're on Philippines time, Akash is on Eastern time. We fix whose clock the 1 PM meeting is on so we're never off by a day.
Getting started — your steps, in order
| # | Step | Who | When |
|---|
| 1 | Reply with your Gmail (for invites), your GitHub username, and your working hours and time zone. Start date is set: Jul 14. | You | Now |
| 2 | Access lands by invite or seat — never a shared password: GitHub Codespace, brain (shared memory database, read), Slack, Google Drive, GoHighLevel (test/read), Meta (read), AI seat. | Akash | 24–48h after your reply |
| 3 | 20-minute kickoff call — confirm your week-1 focus, get the template walkthrough, and meet your first build. | Both | On/near Jul 14 |
| 4 | While access is pending: read, don't build — the list below. Batch your questions into one list. | You | Days 1–2 |
| 5 | Run the setup check (workspace opens, brain tables readable, vault confirmed blocked). Report green or red. | You | Day 1 with access |
| 6 | Ship your first full daily slate (see Week 1). | You | Week 1 |
Reading list (in this order)
- Operating brief — the rules and the funnel. This page wins over anything older.
- Builder Vision Handoff (2026-07-13) — in your packet: where all 7 systems are now and where they're headed.
- Daily Operating Rhythm (2026-07-13) — in your packet: the daily meeting, Slack, the scoreboard, the metrics you own, and your end-of-day report. This is how every day runs.
- The builder board — your cards are DAILY-1, DAILY-2, SALES-ENG. Click each for its side card: what "done" means, what's done so far, blockers, and next actions.
- Once you have workspace access:
canonical-brand.html · Content OS v2.2 · the locked copy contract · the ads-autopilot daily loop.
What you own — the first 6 weeks
Weeks count from Jul 14. The shape below is the default plan. You own re-ordering it; the outcomes and gates don't move.
Week 1 — Shadow one onboarding + map the real path
- Watch one manual onboarding end to end. Record every input, click, owner, output, and failure point.
- Confirm the current GHL snapshot, client fields, bot, calendar, tracking, and campaign-launch gates.
- Friday proof: current-state map + ranked automation backlog + test plan. No production automation yet.
Week 2 — Build the manifest + client-facts automation
- Turn signed-and-paid client facts into one validated intake manifest.
- Push the client facts into a test location and read every value back.
- Proof: rerunning creates no duplicates and reports missing inputs clearly.
Week 3 — Automate CRM, bot, calendar, and lead response
- Create/apply the GHL account and snapshot; configure the bot, calendar, phone, stages, and safeguards.
- Proof on 5477: one lead, one contact, one scripted reply, one booking, one owner, one next action.
Week 4 — Stage the first campaign + prove tracking
- Build the Meta campaign from the approved offer/creative pack and keep every object Paused.
- Prove browser + CAPI events, destination, consent, CRM routing, and mobile preview.
- Deliver the one-screen launch brief. Akash alone approves spend.
Week 5 — Rehearse the whole runner + launch the first client
- Run signed-and-paid → onboarding → Paused campaign twice in test with zero duplicates.
- Use the first real client only after Akash approves access and launch.
- Begin the six-week client-delivery scorecard in the SOW.
Week 6 — Harden + hand-back
- Document every stage, proof, failure mode, owner, and rollback. Nothing depends on memory.
- Trial scorecard: onboarding time, manual touches, duplicate rate, launch defects, and hours removed from Akash.
- Hand back the stable runner and the next six-week improvement plan.
Rules that never bend
- You decide HOW; Akash sets the outcome. You'd rather cut video by hand in CapCut than use AI — that's fine. We only build an AI template when the same template repeats a lot. Six hours once beats thirty minutes every day.
- Access is by invite or seat, never a shared password. If a tool has no seat, Akash sets it up through the vault — never pasted in chat.
- Three work modes: auto (reversible + logged), auto-with-gate (do it all, queue exactly ONE human task), report-only. Every outside change is logged with a rollback.
- Never touch: the SMS worker (live compliance issue — build around it), the ad account's money (Akash-only), the command-center launcher, and the scoreboard tables.
- Messages: automated messages go to opted-in form-fillers only — never cold numbers. Live tests only to the test phone.
- Nothing is ever sent as Akash. Client- and prospect-facing sends are drafted for his OK.
- Brand: only @alexstpierre on ad images. Every hook names foundation and waterproofing. Bolding is all-or-nothing per format. Founder face and voice stay parked unless Akash restarts it.
Open decisions Akash owes you (ask at kickoff)
- The 1 PM meeting time — confirm whose zone, so it works for both of us.
- Newsletter cadence: Akash wants daily; the 07-12 checklist locked weekly for now, while email deliverability is fixed.
- AI-UGC direction: which avatar/video approach to standardize on.
- Handle re-render: the latest r2 statics reuse the old @stpierre_ai handle — confirm the re-render before they hit Meta.
Companion docs: Builder Vision Handoff (2026-07-13) · Daily Operating Rhythm (2026-07-13) · builder board · operating brief. Akash's side of this plan lives in the private onboarding runbook.