Internal · Execution Reference

Arcus Service SOP

The month-to-month playbook for actually running the account — product reference, the recurring build/optimize loop, and the decision rules — so delivery holds together the same way regardless of tier. This is Bryant's working reference, not client-facing.

01

Product & Machine Reference

Every category gets tested every month (SOW Section 06) — but they don't all sell the same way. This is what's different about each one.

CategoryBuyerChannel angleCurrent stateTesting angle
DTF (flagship)Self-directed small-business owner, browses Facebook for equipmentMeta is a native fitOnly category tested in 2 yearsOffer-led — trade-in, starter bundle — split broad vs. narrow audience
UV PrintersSimilar SMB buyer, adjacent use cases (signage, promo goods)Untested on MetaZero ad historyMirror DTF's early angles; use DTF's CPL as the benchmark to beat
Dye SublimationBigger financial commitment — buyer deliberates longerMeta for awareness, email for nurtureZero ad history despite having productEducation-led creative — what it does, ROI framing — not a direct offer first
Accessories & SuppliesExisting customers restocking — lower ticket, high frequencyRetargeting / email, not cold prospectingNever advertised standaloneFeed into retargeting + email flow content, not top-of-funnel spend
High-ticket flatbed (~$45k)Production/enterprise buyer, not the typical $20k mom-and-popNeeds account-based targeting — by company/industry, not demo aloneBroad demo targeting underperforms — reps report ~49/50 passTest company/employer targeting and adjacent verticals (e.g. varsity athletics, signage) instead of "textile high income" only
Trade-In OfferOwner of an aging or competitor machineWorks inside any category's page/creative, not a standalone channelExists as policy, never used as ad messagingDedicated trade-in lander — the clearest concrete offer to test first
This reference is what makes "Offer Testing" and "Audience Testing" (SOW Section 03) concrete instead of abstract — each row is a different lever to pull.
↑ Back to contents
02

Monthly Cycle

The Build-Out Timeline (SOW Section 08) describes month one. This is the same loop, repeating every month at whatever volume the tier calls for.

Week 1

Plan

  • Pull last month's ranked CPL by category
  • Set this month's machine/offer priorities
Week 2

Build & Launch

  • Pages + matched creative built, approved, live
  • UTM tagging applied, campaigns launched
Week 3

Read

  • Sales-quality sync — real closes, not just cheap leads
  • Early winners get budget; early losers get cut
Week 4

Report & Reweight

  • Month report: spend, leads, CPL, closes
  • Next month's allocation set from real data
↑ Back to contents
03

Landing Page Build SOP

  1. Pull this month's priority machine, offer, or audience angle from the plan
  2. Gather assets — existing product photography, spec sheet, any relevant founder-content clips
  3. Draft the structure fast — one clear offer, one CTA, mobile-first; this should take minutes of thinking, not hours
  4. Build to the same bar as the Pioneer 24 concept already shown — that's the quality floor, every tier, every page
  5. QA: mobile check, form/CTA works, UTM tagging applied, claims match the specific machine or offer on that page
  6. If the page carries a bold, untested claim (SOW Section 04, Message & Positioning) — route through Arcus sign-off before it goes live
  7. Publish, tag, and launch the matching creative the same day
↑ Back to contents
04

Creative Production SOP

Pulled from the tier's shared monthly pool (SOW Section 05) — not split evenly across pages by default.

↑ Back to contents
05

Optimization Rules

Rules of thumb, not rigid triggers — judgment still applies, especially on small samples.

Frequency

A creative crossing roughly 3x average frequency without a CPL improvement gets refreshed or retired — this is the same threshold the account diagnostics (SOW Section 02) flagged as the sign Pulse's ads had gone stale.

Rising cost-per-lead

CPL trending up two weeks running on a specific page or category — pause that page's spend, redirect budget to the current best performer, and revisit the angle before relaunching.

New page, early days

Don't kill a new page in its first 3–5 days at low spend just because it hasn't proven out yet — let it reach a minimum sample before judging it.

Winning angle

Once an angle proves out in one category, test it in the adjacent categories before assuming it's category-specific — this is exactly the "why gate it to one machine" gap Pulse left on the table.

↑ Back to contents
06

Email Flow SOP

Growth & Scale, or Starter add-on
↑ Back to contents
07

Founder Content Session SOP

  1. Schedule quarterly — about 30 minutes, single take, mic'd, Vic and/or Brian
  2. Prepare a shot list in advance: which machines, which floor areas, which talking points
  3. Cut into one long-form piece plus multiple short clips for ads, LinkedIn, and email
  4. File into a running asset library tagged by topic and machine, so future months pull from it instead of re-shooting
↑ Back to contents
08

Reporting SOP

Weekly snapshot

Spend, leads, and cost-per-lead, broken out by machine category — sent regardless of tier.

Sales-quality sync

Review the past week's (or two weeks', at Starter) leads with the sales team — which closed, which are progressing, which were junk. Feed this back directly into the next optimization cycle, not just into the report.

Strategy call

Review the report, set next month's category priorities, and revisit whether the current tier still fits the spend level.

Day-90 report

The one that actually matters for renewal: baseline vs. current Meta-attributed closed revenue (not just CPL), ranked cost-per-lead by category, and a recommended next-quarter allocation.

↑ Back to contents
09

Tier Scaling Reference

The SOP above doesn't change by tier — only the dials do.

 StarterGrowthScale
Landing pages / mo51830
Creative pool / mo152032
Email marketingAdd-onIncludedIncluded, full mgmt
Founder content sessionAdd-onQuarterlyQuarterly
Sales-quality syncBi-weeklyWeeklyWeekly
Strategy callMonthlyMonthlyBi-weekly + Slack
↑ Back to contents