Ops Manager Cheat Sheet — every surface, what to check, what to do

1 Read this first

You own three things: sales ops (the records and queues behind Akash's calls), delivery ops (every homeowner lead from ad to client outcome), and general ops (the machines, the trackers, the problems list). Akash sells. Everything else is yours.

Five things always stay with Akash: money, messages sent as him, public-facing changes, account access, and deleting data. Everything else is reversible. Do it, log it, report it.

Day-one access to ask Akash for

• The Sales Center key and the B2C board key. Each page asks once, then the browser remembers it.
• The passcode for the rooms (CX, finance, scorecard, sales room).
• A Supabase login for the issue register and the change ledger.
• Meta Business Manager access for the ad accounts and the pages.
• Drive access to "Proven B2C Ads by Niche".

2 Your daily loop (about 20 minutes, before 9:15)

• 1Command Home - read the six weekly numbers and the fleet health strip. Anything red goes on the issues list today.
• 2B2C Board - open "Needs reply" and "Unreachable". Anyone who gave a name and phone and is stuck did not get transferred. Fix the transfer, then find out why.
• 3Client lane - every lead transferred to a client with no client action after 48 hours gets a nudge that asks them to mark it in their portal.
• 4Sales Center - clean the records only. Every conversation Akash worked yesterday needs an outcome and a dated next action. You do not message prospects as Akash.
• 5B2C Scoreboard, Markets tab - spend that is not turning into replies and qualified leads is the bottleneck of the day.

3 The core surfaces

These are the pages you live in. Keys and passcodes are listed in section 1.

4 Delivery ops: what to audit and how

The lead path is: ad, Messenger conversation, name and verified phone, transfer to client, client books, outcome recorded. Your job is to prove each step happened, not to assume it.

Where the truth lives for each question

Rules that are already enforced by the system, so do not re-decide them

• Once a lead has a name and a verified phone, it transfers. Chase texts to complete or transferred leads are blocked at send time.
• One text script for everyone, slot-filled. Never a custom message per lead.
• Never send the same link twice in 48 hours. Never force a channel switch.
• Geography never disqualifies a lead. Non-English does. Out-of-coverage conversations close silently.
• Opted-out leads are never handed to a client.

5 Sales ops: what you run for Akash

The offer of record: a $0-down seven-day trial of ten booked appointments, then prepaid appointment blocks at a flat price per appointment. Cold-call trial rung is three appointments for $450. Never invent terms. Send anyone asking to the Sales HQ launcher.

6 Media pipeline: a new foundation repair pack every week

You publish one new pack of foundation repair creatives every week. The scoreboard tells you what won last week; the pack is your bet for next week.

The weekly cycle

• 1Monday: read. B2C Scoreboard, Creatives tab, All time and Last 7 days. Rank by cost per qualified lead. Note the hook and the on-screen surface of the top three.
• 2Tuesday to Wednesday: build. Video pack: staged b-roll, Eric voiceover with the mandatory tempo and pause treatment, red karaoke captions burned from the script, clips looped to the read, an A/B silent control. Image pack: 20 image copies in 2 formats, 3 captions (Full, Punch, Alt open) and 2 headlines each, inside one ad set.
• 3Thursday: stage. Ads are created PAUSED in the existing campaign as a new "Pack N" ad set, a duplicate of Pack 1 with the videos swapped. Contact sheet goes to Akash.
• 4Friday: launch. After Akash approves the sheet, run the launch QA, then activate. Nothing gets turned off when a new pack launches; the campaign budget reallocates on its own.
• 5Following Monday: score it. The pack is the row on the Creatives tab. Winners get reused across markets; losers get cut on evidence, never on taste.

Standards that are not up for debate

• One campaign per market. Budget at the campaign level, always. Ad sets inside a campaign are clones; only the creative pack changes.
• Never fewer creatives. If the per-ad budget looks thin, raise budget or extend the window.
• Ad accounts are per niche: one for concrete leveling, one for foundation repair, one for B2B. Confirm the account before any launch.
• Light backgrounds only, no dark creative. "Or you don't pay" stays in the copy.
• Proven finished ads live in Drive under "Proven B2C Ads by Niche". Reuse them with new audio before making anything from scratch.

7 Pages: one Facebook page per state

The strategy is one page per state, carrying every market in that state. From one page we can run foundation repair, concrete leveling, waterproofing and crawl space ads to any territory. The new naming standard is "[State] Foundation Repair & Waterproofing". Organic content is the same video, tweaked per niche and state.

Where the rollout stands today (from the rollout plan table, 57 markets)

Page spin-up checklist. A page is not live until all six are proven.

• 1Page created on the naming standard, and a row set in the rollout plan table.
• 2Lead Ads terms accepted on that page by a page admin in the browser. There is no API for it. Check every page in a wave, not just new ones.
• 3Page-scoped dataset created and shared to the right ad account, proven by a test event that returns "received".
• 4Page connected to the CRM. Two connections exist: the lead-form sync and the Messenger integration. A Messenger campaign needs the second. Akash clicks the grant. Proof is a real contact landing from that page id.
• 5The four routing rows: client record, park rows in the ZIP map, an enabled delivery destination, and the campaign-to-client map. Missing any one means leads are written correctly and delivered to nobody, with no error.
• 6No Instagram placement. None of the pages has an Instagram account, so Instagram traffic would land in an inbox nobody reads.

8 Client success: health and retention

Current clients and where they stand

• Level King Pro (Dallas, concrete leveling): paying, paused. Leads go by text through the CRM.
• AlphaLift Foundation Repair (Dallas): paused. Leads go by DripJobs card plus the portal.
• Able Concrete (Minneapolis): paused. Leads forwarded by hand.
• Arbuckle Waterproofing (Pittsburgh): upcoming. Scott is still a prospect; no auto-delivery.
• Everything else in the roster is a market test with no buyer. Leads park until a buyer signs.

9 Problems and projects: reactive and proactive

Reactive: the issue register. Table issues in Supabase. Every problem found by monitoring or by a person goes here with severity, owner and status. Intended stages: Open, In progress, Resolved, or Won't fix with a reason.

Change history: the ledger. Table change_ledger in Supabase. Every change to a live system carries who, what, why, before and after, and how to undo it. Read it when something looks different than yesterday. Write to it when you change anything outside your own notes.

Proactive: the project tracker. Command Home project cards, driven by the brain. Progress, next action, definition of done, proof. This is the only project tracker. Do not start a spreadsheet.

Decisions waiting on Akash. Decision cockpit. Keep "waiting on Akash" and "needs Akash's approval" as two separate lists.

• Found a problem: add an issues row the same day, with a severity and an owner.
• Fixed a problem: ledger row with the rollback, then close the issues row with the ledger id.
• Starting something new: a project card with a definition of done, not a task in your head.

10 Everything else that exists (open only for a reason)

11 Gaps, and what I recommend

These are the things Akash asked for that do not exist yet, or exist in a form that will mislead you.

Order to do them: triage the issue register first, because it tells you what is actually broken. Then the no-lead client lane, because clients are the revenue. Then the page renames, the list toggle, and the creative tags.