St. Pierre · Builder Onboarding Packet

Welcome, Collens.

Your job is to automate every process in the St. Pierre pipeline except sales — so the machine runs without Akash being the bottleneck. This packet gives you the whole picture, your first-week mission, and the six-week plan. Read it top to bottom once, then keep it open while you work.

Role: Automation Builder / Operator Terms: $1,000/mo · ~20 hrs/wk · 30-day trial Week-1 goal: the maintenance layer live — scorecard + board + your workspace

Section 1

The 60-second version

Who we are: St. Pierre is a done-for-you demand agency. We book qualified inspections for home-services contractors — foundation repair, waterproofing, crawl space, concrete leveling. Akash is the founder.

What you're here to do: take every repeatable process in our pipeline — client onboarding, the custom audits we send prospects, content production, reporting, ad management — and turn it into automation. The one lane you don't touch is sales; Akash keeps that.

The mindset: the goal is to remove Akash as the bottleneck in everything that isn't selling. If a task can run without a human — or with a human only clicking "approve" — that's your target.

Your first week Before we build anything big, we stand up a maintenance layer so we can see and manage the work: a weekly scorecard with owners, a simple project board, and your own cloud workspace. Ship that in week one and you're set up to build fast for the next five.

Section 2

Who we are & why it matters

Contractors don't have a leads problem — they have a hiring-confidence problem, hidden by rented leads that vanish the day they stop paying. St. Pierre gives them demand they own: a predictable flow of qualified, booked inspections.

The offer, in one line

Clients pay $975/week for up to 5 qualified, booked homeowner inspections. If we miss a week, a credit applies automatically — before the client asks. That promise only works if the machine behind it is reliable, which is exactly why we're automating it.

Why this role matters

Right now too much of the pipeline runs through Akash by hand. Every process you automate buys back his time so he can do the two things only he can do: sell, and steer the business. You're building the engine that lets St. Pierre grow without adding headcount for every new client.

Section 3

Your role & where you fit

You're an Automation Builder / Operator. You're strong where we need it: GoHighLevel, n8n, webhooks, automation, funnel plumbing, documentation, and QA. Over time we also want you thinking about whether the output is actually good — not just whether the workflow runs.

Here's the clean split of who owns what:

Akash keeps	You automate
Sales — outbound, lead nurture, prospecting, and closing calls. Reviewing scorecards and setting direction. Hiring and managing builders.	Client onboarding, the custom audits, content production (no founder video), distribution, reporting, ad management — and eventually AI agents that run the whole pipeline.

One important change We are parking founder talking-head content for now. Don't build anything that needs Akash on camera. When we make content, it's static images, carousels, motion graphics, and AI UGC — formats that don't need him in the room.

A few principles about the team: you keep one task in flight at a time, you pull the next from the board when you finish, and every piece of work comes back with a clear hand-back (Section 5). This is a 30-day trial and we want you to pass it — there are no hidden tests.

Section 4

The pipeline & your territory

This is the full St. Pierre business pipeline (you'll see it live at team.stpierre.ai). A lead flows left to right. Your territory is everything shaded yours; Akash owns sales.

Stage	What happens	Owner
Creative Ops	Produce the ads — scripts, design, UGC (B2B for us, B2C for clients).	yours
Marketing	Run and optimize Meta campaigns; manage spend; scale winners.	yours (automate)
Setter	Qualify inbound leads, power-dial, book calls, run recovery/no-show follow-up.	Akash (you build the drafts/tracking)
Sales	Strategy calls, close, collect payment.	Akash
Client Ops	Onboard a paying client — GHL + FB page + campaigns live within 48h; QA; transfer leads.	yours
Client Success	Weekly check-ins, escalations, renewals, at-risk recovery.	yours (automate reporting)

Good news: a big data layer already exists — Meta metrics, GHL conversations, contact tags, and appointments already sync into our database automatically every night. You're not starting from zero; you're building the action automations on top of data that's already flowing.

Section 5

How the work works

The loop is simple and it repeats:

Pull a ticket from the board (this week, your foundation tasks below).
Send a 24-hour plan first. Before you build, post what you'll do, what you'll touch, and when you expect to finish.
Build it safely. Sandbox and test data first — never live accounts, never someone else's original files.
Hand it back in the five-part format below.
Akash reviews — pass, small fix, or follow-up — then you pull the next task.

Two rhythms to keep

End every day with a daily update (template in Section 12). Two minutes; it's how we stay in sync without meetings.
Blocked more than 30 minutes? Don't go quiet — send a short Loom with the exact blocker and the decision you need. Surfacing blockers fast is a strength here.

The hand-back format (memorize this) 1) Link to the output · 2) What I changed or built · 3) How to re-run it · 4) What failed · 5) What I still need from Akash.

Section 6

The golden rule (safety)

★ The one rule that matters most You get full context immediately — docs, examples, access to read the brain. You get live control only after proof. Until you've shipped clean work and documented it, nothing you build sends, posts, or spends on a live account.

During your proof phase, please do not:

Post, schedule, boost, or send on Instagram, YouTube, Meta, ManyChat, or any scheduler.
Make live edits in GoHighLevel or n8n, or any live database writes, schema changes, or token/credential work.
Send emails, SMS, DMs, or calendar invites as Akash. (Setter follow-ups you build are drafts for Akash to send — never auto-send.)
Deploy anything (homepage, funnel, dashboard) or spend on ads.
Put any password, token, or API key into a doc, chat, Loom, screenshot, or repo.
Grant access to yourself or anyone else.

If you think you need a live account Stop and write the exact ask — what you need, why, and what it would change. Don't grant it mid-task. Any approved live change gets logged with rollback steps and verification first. (We don't use Slack — it's deprecated.)

Section 7

Your tools & what you can touch

Green means build here now; grey means read-only context; red means held until after your proof.

Tool	What it's for	Day-1 access
Codespace + brain client	Your cloud workspace; reads our project/task database (the "brain").	Sandbox / read
Project board	Where tickets live and hand-backs return.	Build + use
GoHighLevel	CRM, funnels, follow-up, the $1 path — the heart of onboarding + nurture.	Read / test location
Facebook / Meta Business	Ad accounts, pages, campaigns — the marketing lane.	Read / sandbox
n8n	Workflow automation for ingestion, onboarding steps, and handoffs.	Sandbox / duplicated
Existing skills library	The automations already built (data syncs, audits, monitors) — your starting inventory.	Read first
Content tooling	Static / carousel / motion-graphic / AI-UGC generators (no founder video).	Sandbox
Live sends · ad spend · credentials vault	Publishing, money movement, secrets.	Held until proof

Part of week one is Akash walking you into GHL, Facebook, and the existing skills so you can see what's already built and where the gaps are.

Section 8

Setup: your first day

Confirm the basics. Reply to Akash with your working hours/overlap window and your Loom link.
Get your workspace. Akash sets up your Codespace, brain access, and your Codex/Claude subscription (and how it's paid). Run the setup check so you know your access works and is correctly limited.
Get walked into the tools. GoHighLevel, Facebook, and the existing skills library — so you can see what exists.
Read the pipeline. Open team.stpierre.ai and trace one lead from ad → booked → paid → onboarded → retained.
Send your 24-hour plan for the week-1 foundation tasks (Section 9).

Section 9 · the plan

Your first six weeks + the vision

We build in phases, lowest-hanging fruit first. Week one is a foundation so we have a way to see and manage the work. Then we automate the highest-value part of the pipeline, then outbound, then production and ad-buying.

Right now — Week 1: your foundation mission

Weekly scorecard system + ownersEvery pipeline lane already has one number (new ads, cost-per-qualified-booked-call, booked calls, cash, cost-per-lead, churn). Put them in one weekly scorecard and assign an owner to each. This is our maintenance layer.
A simple project board (kanban)Where you manage your own projects, Akash can drop new ones in, and anyone can see what's moving.
Your workspace + accessCodespace with brain access working, your Codex/Claude set up, and the setup check passing.
Tool onboarding + a gap mapGet into GHL, Facebook, and the existing skills — then write a short list of what already exists vs. where the low-hanging automation gaps are.

The six-week arc

Phase	Weeks	What you build
Foundation	W1	Scorecard + owners · project board · workspace + access · tool onboarding & gap map.
Phase 1 — the $1→$975 machine	W2–3	Map the full lead→close + recovery workflows, then automate client onboarding (Cash Collected → Live in 48h) and build the custom audit engine (see keystone below).
Phase 2 — outbound	W3–4	Pre-fill the audits for high-value target lists and send them outbound; test new entry points — Instagram DMs, Messenger, and lead forms.
Phase 3 — production + buying	W4–6	Stand up the no-meat content engine (static, carousel, motion, AI UGC), wire distribution + reporting back to the scorecard, and start autonomous media buying (raise/lower spend, split test vs. scale, graduate winning creatives, split-test headlines & angles).

★ The keystone — build it once, reuse it everywhere The custom audit engine is the highest-leverage thing you'll build. When someone pays the $1 or books, it generates and delivers a personalized set: an AI-readiness audit, bottleneck audit, brand audit, the 1M→10M growth system, the guarantee, and a customized VSL/demo for their business. Build it once and it powers three things: nurturing $1 buyers toward $975, outbound to cold high-value lists, and future lead magnets.

Where this is going (month 2–6)

Fully autonomous media buying — the system manages test vs. scale campaigns, graduates creatives, and runs multivariate tests on headlines, captions, creatives, and angles on its own.
Lead-magnet testing at scale — each audit, each engine, and the full "1M→10M" guide/book becomes its own lead magnet and interactive experience.
AI agents running the pipeline — as clients sign, agents take over onboarding, lead-flow QA, attribution, reporting, and client updates stage by stage.

A full interactive version of this timeline (the Gantt) accompanies this packet — ask Akash for it.

Section 10

What a strong start looks like

Dimension	What "great" looks like
Following the plan	You use what already exists, work in the sandbox, and honor the held-access rules.
Technical execution	Your scorecard, board, and first automations actually run — and you can debug or clearly document them.
Judgment	Your gap map shows you understand where the real leverage is, not just busywork.
Documentation	Your notes and Looms are clear enough that someone else could re-run the work.
Operating behavior	You surface blockers fast with a concrete ask instead of going quiet until a deadline.

The fastest way to stand out: make the process repeatable and visible, not just the finished output. We're hiring an engine builder.

Section 11

Logistics: hours, pay, comms

Pay & hours: $1,000/month, part-time, around 20 hours/week.
Trial: 30 days, with the week-1 foundation as your first proof checkpoint.
Subscriptions: your Codex/Claude tooling is set up and paid through St. Pierre — Akash will sort the access and billing with you on day one.
Communication: a daily update every working day (template below), plus a Loom whenever you're blocked more than 30 minutes. No Slack — it's deprecated.
Async by default: we run on clear written updates and short Looms, not meetings.

Section 12

Your checklist & daily template

Day 1

Confirm hours + share your Loom link
Get Codespace + brain access; pass the setup check
Get walked into GHL, Facebook, and the skills library
Trace one lead through team.stpierre.ai end to end
Send your 24-hour plan for the foundation tasks

Days 2–5 · Foundation build

Stand up the weekly scorecard + assign owners
Stand up the project board
Write the "what exists vs. gaps" map
Send a daily update each day
Hand back in the 5-part format; list any access you still need

Daily update template

Daily update — Collens

Date:
Hours worked today:

1. What shipped today:
2. Link to output:
3. What I changed or built:
4. What I checked:
5. What is blocked:
6. What I need from Akash:
7. What I am doing next:
8. Loom link, if the work is not obvious:

Rules:
- If blocked more than 30 minutes, send a Loom with the exact blocker and the decision needed.
- Do not wait silently.
- Do not touch live accounts, sends, workflows, publishing, credentials, or ad spend
  unless Akash approved the exact action first.

That's it Read it once, start on Day 1, and get the maintenance layer live. Welcome to St. Pierre — glad you're here.