team.stpierre.ai / builder brief

Collins Builder Brief

Read this first. It is the smallest useful map of what St. Pierre is building, what Collins owns, what Akash keeps, and where to click when a question appears.

Executive summary

St. Pierre sells booked inspections to foundation and waterproofing contractors.
Akash owns offer, sales, money calls, and final trust judgment.
Collins owns the systems layer: scorecards, agents, workflows, QA, docs, and handoffs.
The job is to remove Akash from the how, not create more things for him to manage.

The rule

If the work does not create a reusable system, a visible scorecard, a cleaner handoff, or first-cash movement, cut it or park it.

1. Start here

Understand the mission and the split: Akash sells; Collins builds the operating layer.

2. Open the board

Use the builder board for active work. Do not turn this brief into a second task list.

3. Open the SOW

Only open the SOW for the lane you are working on now.

4. Report by scorecard

Daily update = what moved, what is blocked, who owns next, what should stop.

Builder Board

start

The active backlog and priority stack. This is the source of what to do next.

6-Week Gantt

order

The phase order: foundation -> $1 to $975 machine -> outbound -> no-founder production.

Pipeline Map

context

The business flow: marketing, creative, setter, sales, client ops, and client success.

The nine scorecards Collins is building toward

1. Static image productionBatch approved image ads and proof posts.

2. Motion graphic productionMotion variants from the same tested ideas.

3. Carousel productionSwipe-through proof, diagnosis, and belief assets.

4. YAP / Micro YAP productionOne recording becomes clips, hooks, captions, and briefs.

5. Onboarding agentPaid client to setup checklist without Akash chasing.

6. Fulfillment agentLaunch, tracking, 24/48/72h checks, and issue flags.

7. Finance agentCash, invoices, runway, renewal risk, and payment status.

8. Reporting agentClient proof, risk, next actions, and weekly report prep.

9. Scorecard systemDaily huddle view: current number, target, owner, next move.

First build bias: scorecard system, onboarding agent, and fulfillment agent first. Those expose the real blockers fastest.

Current state vs target state

Lane	Now	Target	First useful output
Static	Direction exists; production depends on Akash taste.	Weekly batch can ship from standards and examples.	10 approved static concepts with hook labels.
Motion	Conceptual lane, not a repeatable template set.	Motion variants come from the same idea bank as statics.	3 reusable motion templates with export rules.
Carousel	Role is clear; workflow is not formalized.	One idea becomes a clean hook -> proof -> CTA sequence.	Carousel structure and 3 examples.
YAP	Akash has raw thinking; outputs are manual.	One recording creates clips, hooks, captions, and briefs.	Transcript-to-output checklist.
Onboarding	Path is defined but still owner-dependent.	Paid client reaches launch prep without Akash checklist chase.	Missing-info tracker and test client run.
Fulfillment	Launch checks are known but not packaged.	Each client has campaign, creative, tracking, and next action visible.	24/48/72h QA loop.
Finance	Runway pressure is visible; rhythm is not simple enough.	Cash and payment risk surface before emergency.	Weekly finance view.
Reporting	Scorecard concept exists; client proof needs structure.	Reports show proof, risk, and next actions without manual assembly.	Red/yellow/green report template.
Scorecard	Cockpit exists; huddle view needs sharper owner/target lanes.	Daily huddle reviews nine lanes, not a task dump.	One-page huddle scorecard.

What St. Pierre is becoming

AI agents do repeatable execution: drafts, data pulls, checks, routing, scoring, and reporting.
Builders manage agents: prompts, workflows, data joins, QA, rollback, dashboards, and docs.
Humans own trust: sales calls, client recovery, expectation resets, money decisions, and final judgment.
The company is managed by scorecard. Green numbers mean humans stay out of execution. Red numbers mean the owner improves the system that produced the miss.

The build order

Phase	Builder output	Open when needed
Foundation	Scorecard + owners, project board, access check, tool gap map.	Builder board
Phase 1 - sales proof	Custom audit engine that turns contractor context into useful proof assets.	Custom Audit Engine SOW
Phase 1 - delivery	Client onboarding automation from cash collected to launch prep.	Onboarding Automation SOW
Phase 2	Outbound packets and destination tests after the first system works.	6-week Gantt
Phase 3	No-founder production, reporting loops, and media-buying support.	Creative Engine SOW

Review gates and safety rules

Gate	Owner	Rule
Sales relationship	Akash	AI can prep. Akash owns calls, close, and final send as Akash.
Claims and public proof	Akash	No unsupported claim ships. Early creative needs taste/claim review.
Live client go-live	Akash + builder	Build against test data first. Real clients go live only after review.
Money, account access, permissions	Akash	Do not change money, credentials, billing, or permissions without explicit approval.
Reversible system work	Builder	Can move when logged, tested, reversible, and visible on the scorecard.

Where to click when you have a question

What do we sell?Offer, pitch, objections, and sales anchors. Where does this live in the business?Pipeline overview and stage maps. How does creative move?Creative request to ready-for-launch flow. How do ads get tested?Ad ideas, winners, losers, and scale path. How does onboarding work?Cash collected to launched campaign. What happens after launch?Month 1, Month 2, Month 3, risk, churn, retention. What systems already exist?Automation and scheduled work map. What are the ad rules?Meta naming, geo, duplication, and QA standards. Where is the GHL plumbing?CRM, lead tracking, bot, CAPI, and onboarding infrastructure. Where is performance data?Campaign metrics, audits, creative briefs, launch QA. Can I trust the data?Data freshness and integrity monitor. What is broken or drifting?Reliability and drift board.