new-client-launch: signed to live
What it does
Section titled “What it does”Takes a client from signed contract to live traffic with a measurement baseline, in the right order, without you having to remember the order.
It sequences: Brain onboarding → market research → offer scorecard → tracking and signal verification → the money page → the angle map → hooks and concepts → the creative batch → the policy check → the launch spec → the first weekly readout as your baseline.
Its non-negotiable is a three-legged hard gate. Nothing launches on:
- Unverified tracking. You would be spending real money learning nothing.
- An unscored offer. Traffic does not fix an offer that does not work.
- A missing or blocked policy verdict. Finding out post-ban is the expensive way.
None of the three substitutes for another. If any leg fails, the run ships LAUNCH-BLOCKED and names the specific fix path rather than launching anyway.
When to reach for it
Section titled “When to reach for it”- A new client just signed and you want the whole runway handled in one pass.
- A new product or offer on an existing account that needs its own launch.
- You want the baseline set correctly so week-two performance means something.
Where it runs
Section titled “Where it runs”The research, gates and specs run in both. The money-page build step needs the desktop app, because it renders and QAs a real page.
What it needs from you
Section titled “What it needs from you”- The client’s URL and their offer, price and CTA.
- Account access: ad account, pixel/dataset, analytics, and store or CRM. It records the identifiers once so nothing has to ask again.
- Your declared conversion shape, because the budget math and the baseline metrics both follow it.
- Real proof: a case study metric, testimonials, a guarantee. It will not invent these.
What you get back
Section titled “What you get back”A launch runbook: the three gate verdicts up front, the offer scorecard, the money page live, the angle map with its ranked territories, the creative batch, the policy verdict per platform, the copy-pasteable launch structure with its budget arithmetic, and the baseline readout. Plus a cost ledger for the run.
A worked example
Section titled “A worked example”You: “Take examplebrand from signed to live.”
Gate 1 tracking:
RED. Purchase events double-firing with no dedup. Result:LAUNCH-BLOCKED. Gates 2 and 3 still run and report: offer scores 6.2 of 10, with the guarantee named as the cheapest available upgrade; policy verdictPOLICY-CLEARon Meta,RESTRICTEDon Google for the supplement vertical. Fix path: the tracking fix plan, with its dated retest. Everything downstream is built and waiting; only the launch itself is held.
Tips & gotchas
Section titled “Tips & gotchas”- A blocked launch is the skill working. It is cheaper to fix tracking on Tuesday than to spend three weeks of budget optimizing against numbers that were never real.
- It is an orchestrator, not a second opinion. It reads the component skills’ own gates. If you disagree with a verdict, argue with the skill that produced it.
- This is the one-time-per-client deep run. Weekly operation moves to weekly-account-os afterward.
- Give it real proof up front. The offer scorecard and the page both stall on missing case studies and testimonials, and neither will fabricate them.
Related skills
Section titled “Related skills”Sequences business-brain-builder, apollo, offer-architect, tracking-doctor, signal-surgeon, page-architect, angle-architect, hook-matrix-forge, concept-lab, policy-compliance-gate, meta-launch-architect and weekly-readout. Hands off to weekly-account-os.