LoopSuit · Operator's Guide / 2026

Field manual · compiled 2026-07-11 · Saraev + Herk (newest videos) + Hormozi + your wiki

Everything you do to get this agency past $10k/mo.

One page, current as of July 2026, deprecations removed. Hover any framed block for a copy icon — it copies as Markdown. Full-context MD files for AI project knowledge live in Md docs/agency-guide-2026/.

900/day send capacity, warmed
2–3 lanes × ~300/day = the 900
gate: ≥5 meetings / 1,000 sends
verdicts at ~3 months, not 3 weeks

01North Star & daily rhythm

The whole strategy in one breath — everything else on this page serves it.

The one-paragraph strategy

Run 2–3 parallel cold-email ICP lanes (med spa · QSR/restaurants · +1) at ~300/day each — together that's the full 900/day fleet (10 domains × 3 mailboxes × 30/day/mailbox, once re-warmed) on the Instantly infra you already own. Each lane sells a named outcome through a paid Clarity Session (constraint-and-KPI audit) → fixed-price guaranteed build → Big-Head-Long-Tail maintenance. A lane lives or dies on ≥5 booked meetings per 1,000 sends. Reply data crowns the spearhead around day 21 — then 1-1-1 focus (one product, one avatar, one channel). Templates are human-approved once; AI only fills variables. Promotion before building, every single day.

WhenWhatTime
Daily Mon–SatReply queue — respond to all outstanding leads (approve drafts, never compose)~30 min
Daily Mon–SatLinkedIn — 20–30 connection requests / DMs to lane ICPs~30 min
Daily Mon–SatInstantly glance (bounce <5%) + one campaign improvement, however small~10 min
SundayDeterminations: funnel numbers → call variant winner → pick ONE next test → load next batch~45 min
Monthly1 public case study + pricing review (raise if closing >1 in 3)~2 h

Rule  Hormozi's Rule of 100 daily — 100 outreach touches or 100 minutes on the funnel. FSH hours don't count. Building doesn't count. Founder day shape: promotion first, delivery second, building last (4-4-4, scaled to your ~90 min).

02Cold outreach

The 4-part formula survives. Around it, five 2026 rules changed — including who writes the copy.

the email skeleton1. PERSONALIZATION — hook attention, prove a human wrote it 2. WHO AM I — credibility in ONE sentence, outcome-first 3. THE OFFER — specific, time-bound, risk-reversed 4. CTA — one action, lowest friction ("X or Y work for you?") 5–8 sentences. Plain text. No links, no HTML, no images.

ReversalAI doesn't write emails

Saraev's walk-back: heavy AI copy now pattern-matches as spam ("people that use AI really intensely tend to suck"). Humans write template banks once; AI only fills casualization variables ("Vancouver" → "East Van").

NewGive-before-ask

"Quick question" openers are dead — they extract value from a stranger. Order: credential/social proof → guarantee → low-friction time ask.

NewVoluntary disclosure

One deliberately off-topic personal line per email ("I'm from [city] originally — anyway…") breaks the AI-spam pattern and builds closeness. Yours: TD Bank, FSH, 2am builds. Sprinkle, don't wreck.

RuleThe visibility hierarchy

Fix in order: sender name → subject → preview text → offer. "If you get the email clicked, that's 90% of the battle." Never waste the preview on "Hi [Name],".

RuleCompression

Replace every term with a higher-info-density term; shave 20–30% length. Skimmable is a pattern interrupt.

DoTwo-step sequence

Day 0 + one bump (day 3–4). Follow-ups are C-tier with diminishing returns. Send 7am–7pm recipient time, Mon–Sat; Sunday is for numbers.

give-before-ask opener shape[personal/credential line] — I spent 3 years shipping TD Bank's mobile app; these days I build revenue-recovery systems for [vertical] like yours. [voluntary disclosure] I'm from [city] originally — anyway. [offer + guarantee] I'll [named outcome] in [timeframe] — and if we don't hit [KPI], you don't pay the balance. [CTA] Worth 15 minutes? Tue 3:30 or Wed 10 work?

Lists — the 2026 sourcing chain

  1. Apify "LeadsFinder"-type actor~$1.50–1.75 per 1,000 email-attached leads. The Apollo actor is dead; actors churn — treat them as swappable parts.
  2. MillionVerifier validation~60–70% pass → net $3–4 per 1,000 usable leads. Never skip; Instantly kills campaigns at 5% bounce.
  3. Dedup + your 7-stage pipelineClean → enrich → casualize → 19-col Instantly CSV. Personalization = your approved bank + variable fill.

Tiers  S: private lists (conference attendees, associations — his only 15–20% reply campaigns) · A: scarily specific personalization · B: custom-scraped > databases · C: follow-ups. Geography arbitrage is real: a Czech clone of a 0.5%-reply US campaign hit ~10% positive. Test one non-US lane.

Infrastructure numbers (July 2026)

ThingCurrent answer
Mailbox math30/day/mailbox · ~3 mailboxes/domain · testing cadence needs 20–30 mailboxes (you have 30 ✓)
Buying inboxesZapmail ~$3/mo or Instantly airmail. Never dedicated SMTP pools.
Warmup21 days (not 30) — or pre-warmed and send day one (~1.35× true cost). Re-bid the stack every 2–3 months.
A/B testing500–1,000 sends per variant, judged on reply rate, ONE variable per week. Big forks first, micro-iterations later.
Benchmarks0.5–1% booked-meeting rate is the target; 0.03% is bad-but-viable. When a campaign bombs: ~50–60% copy, ~20–30% list/mailbox, ~10% luck.
Lane gate≥5 booked meetings per 1,000 sends — or the lane dies. Verdicts at ~3 months (60-day market lag).

03Proposals & closing

A proposal is a test: "does this person understand my problem better than I can articulate it?"

DoctrineProblem-first, ≥50% diagnosis

Half the doc quantifies their pain in dollars before any solution appears. Price last, framed as investment. A 10-page diagnosis once turned a $5k deal into $100k+.

MathThree cost layers

Hard costs + opportunity cost + operational chaos. Reframe savings as revenue: "10 staff-hours = $5,000/mo of selling time recovered," never "$500 of wages saved."

2026The single-artifact close

Proposal + contract + Stripe + signature in one document, with a personal video walkthrough. Payment auto-books onboarding. Every extra step leaks ~10% of leads.

System3 decisions, 72 hours

Traditional close (SMB default): the call earns decision #1 ("worth solving?"); the proposal carries #2–3 inside a 72-hour price window. Automated follow-up until an explicit yes/no.

pricing rules· Value-based: charge 10–30% of the quantified annual pain (~20% mid) · Fixed-price first. NEVER retainers cold (100 retainer pitches ≈ 2 yes; 100 fixed-price ≈ 15 yes, 3 → retainers) · Never time-based build fees — flat $X for the outcome, 4–6 wk scope · Pay-per-meeting when asked: Rate = LTV × CVR(halved) × 15% e.g. $25k × 0.10 × 0.15 = $375/booked meeting · Guarantee ≈ 3× top line at 2–5% refund cost → charge 100% upfront · Price cap for builds: "total will not exceed $X" (pad 50%) · Raise prices when closing >1 in 3 · Never discount — cut scope · Time estimates: +30% buffer, multiples of 4 business days from Monday

EV  Every customized proposal in flight ≈ $4,000 expected value (5 × 20% close × $20k LTV). Track proposals-in-flight, not tasks done. — wiki: problem-first-proposal, dont-sell-retainers-cold

04Sales calls & objections

The Clarity Session is a constraint-and-KPI audit (Herk: "builders are pharmacists, consultants are doctors"). Consult, don't close.

RACE discovery spine — ask theseREACH "How are you currently reaching new customers?" ACQUIRE "What happens in the first 60 seconds after a lead comes in?" CONVERT "How do leads become paying customers? Where do they stall?" EXPAND "When did you last reactivate past customers?" Only sell systems that move one of the four. Anything else: smaller market, less urgency, lower price. Selling "savings" is the trap.

HormoziCLOSER script

Clarify why they came · Label the problem · Overview past attempts · Sell the vacation (never the flight — no process talk) · Explain away concerns · Reinforce the decision.

HormoziBANT before the pitch

Budget · Authority ("anyone else in this decision?") · Need ("what happens if you don't solve it?") · Timing. Unqualified in 5 min → downsell, not a 45-min pitch.

Map7 pains → 3 masters

Leads · speed-to-lead · closing · onboarding bottleneck · payroll bloat · bad software · owner chaos — all reduce to make money / save time / kill chaos. Quantify the bleeding one, in dollars, on the call.

FlowClarity Session

Map the customer journey → find the constraint (what caps revenue, not what annoys) → dollar-quantify → attach a KPI → close to a fixed-price pilot. Never a cold retainer.

The worked scenario (all scripts below use it)

Suppose you're selling…

Rebound — the lapsed-client reactivation system — to Maya, owner of a 6-chair med spa in Austin. Her numbers (from the Revenue Leak Calculator or the session itself): ~2,400 client records, ~700 lapsed 6+ months, average ticket $180 → she's leaking roughly $8–10k/month. Your asks: a $397 Clarity Session (from cold) or the $1,997 pilot (post-session), guaranteed: "reactivation system live in 14 days and 30 rebooked clients in 60 days, or the balance is refunded." Swap the nouns for the QSR lane (lapsed clients → Swiggy/Zomato invisibility, tickets → covers) and every script below still works.

Mock scripts — the famous objections

Blended from Miner's NEPQ word-tracks, Hormozi, and Saraev — adapted to a paid-diagnostic motion. Hover the underlined phrases for why each line works.

Objection 1"How much does it cost?" — asked way too early
Maya"Before we book anything — what does this cost?"
You"Yeah, that's not a problem. Builds like this run anywhere from $1.5k to $15k — it depends entirely on what we find, and that's exactly what the session pins down. The session itself is $397, and if you don't feel you got $397 of value out of the hour, I refund it — independent of anything else."
You"And honestly — the system that got this email into your inbox is the same kind of system we'd build for you."
Objection 2"That's too expensive." — after the pilot pitch
Maya"Two grand… that's a lot right now."
You(leaning in, concerned) "That could genuinely be a problem for you, then. Let me ask — if the funds weren't the issue, is this something you feel would work for you?"
Maya"I mean… yeah, probably."
You"Hm — why do you feel like it would, though?"
Maya"Because nobody's chasing those 700 people. They liked us, they just… drifted."
You"Right — and that drift is the $8k a month we measured. So the real question is how you'd free up the $1,997 once, so you can stop losing the $8k every month you told me about. Best case: the system's live in two weeks and 30 of those clients are back on your calendar in 60 days. Worst case: they're not, and the balance comes back to you. The only guaranteed outcome is that doing nothing keeps the leak open. What do you want to do?"
Objection 3"I need to think it over."
Maya"This sounds good, but let me think about it."
You"Yeah, that's not a problem. What's your timeframe for getting back to me — tomorrow, day after? Let's just put ten minutes on the calendar now so you're not chasing me down and I'm not chasing you."
Maya"Sure, Thursday morning works."
You"Booked. Oh — before I let you go — what specifically were you wanting to think through? Just so I know what questions you'll have Thursday."
Maya"Honestly… I'd want my manager Priya to be okay with it, she runs the front desk."
You"That makes sense — should Priya just join us Thursday, then? Fifteen minutes, I'll walk her through exactly what lands on her desk — which is almost nothing, that's the point."
Objection 4"I need to talk to my business partner."
Maya"I'd have to run this by my business partner first."
You"Of course. How does he feel about the lapsed-client situation — the $8k a month side of it?"
Maya"He's the one who keeps bringing it up, honestly."
You"Then let's not play telephone — would it help if the three of us did a 20-minute call and I walked him through the same numbers? And so I'm useful in that call — what do you think he's going to say?"
Maya"Probably that we tried a marketing agency before and it went nowhere."
You"Good — then I'll bring the two things an agency couldn't give you: a fixed price with an end date, and the refund clause if the 30 bookings don't show up."
Objection 5"Just send me some information." — the email classic
Maya"Can you just email me some info about it?"
You"Happy to. Just so I send the right thing and not a brochure dump — what's the main thing you'd want it to answer?"
Maya"Mostly what it'd cost and how much work it is for my staff."
You"Perfect — I'll send the med-spa one-pager: pricing, the 14-day timeline, and the part your front desk touches (about ten minutes a week). The pilot pricing in it holds for 72 hours — and let's say it covers what you need: what would you want the next step to be?"
Objection 6"We already work with an agency / have software."
Maya"We already pay a marketing agency, and the booking software has reminders built in."
You"Keep both — seriously. Honestly, I'm not even sure we could add anything yet — it depends what they're doing about the 700 people who already stopped coming. The agency brings new faces in the door; reminders catch people who already booked. Who's calling the ones who drifted — and what did that change in booked revenue last quarter?"
Maya"…Nobody, really. The reminders only go to people with appointments."
You"That's the gap. Reactivation isn't marketing and it isn't reminders — it's its own lane, and it's the cheapest revenue you have because these people already chose you once."
Objection 7"I'm slammed — call me back next month."
Maya"This month is crazy — try me again in a few weeks?"
You"Yeah, not a problem. Rather than us playing tag in three weeks, grab your calendar for a second — let's lock ten minutes on the 4th and I'll call you then."
Maya"Fine — the 4th at 10."
You"Done. And — small thing to sit with until then: the reason this works for busy months is that the system does the chasing, not you or your front desk. 'Slammed' is the problem it's for."
Objection 8"Won't AI messages feel robotic to my clients?"
Maya"My clients pay for a personal experience. AI texts feel… cheap."
You"You're right — most of it does, and most of it is. That's exactly why this isn't a chatbot blasting your list. Every message is one you approved, in your front desk's name and your voice — the system just picks who gets it, when, based on their visit history. Nothing goes out that you haven't read. Want to see the actual messages other spas approved?"

NEPQ (Jeremy Miner) — the verdict

Researched July 2026: his videos, book (The New Model of Selling), and the credible critiques. Short version: it's SPIN-with-feelings plus the best objection word-tracks on the market — steal three things, skip three things.

the NEPQ question ladder → mapped onto the $397 clarity sessionCONNECTION (min 0–3) "What made you grab this session, of everything else you could've spent the morning on?" SITUATION (3–10) "Walk me through what happens after a client's third visit — who follows up, and when?" PROBLEM (10–20) "How long has the follow-up been falling through?" → "Has that had an impact on you?" → "In what way?" → echo her emotional word back: "…Frustrating?" SOLUTION (—) "If those 700 people started rebooking on their own — what does the calendar look like in March?" CONSEQUENCE (~20) "And if nothing changes and the drift continues — where's the client base in two years?" ── FLIP: paid diagnostic means you now PRESCRIBE ────────────────── FINDINGS (20–35) Your numbers, her leak, the three fixes, the KPI. COMMITMENT (35–45) "Does this feel like it'd work for you?" → "Why do you feel like it would?" → "What would you want the next step to be?"

StealThe question ladder + gap

"The bigger the gap between where they are and where they want to be, the cheaper your solution seems." Run it for the first 15–20 minutes; her stated pain funds the whole pitch. The probing stack — "tell me more / walk me through / give me a specific example / how long has that been going on / has that had an impact on you / in what way?" — is gold with owner-operators, whose business pain is personal.

StealThe five tones

Curious (the workhorse — all discovery), confused ("hold on — how do you mean?" makes them expand), concerned (pain probes, "off the record…"), challenging (consequence questions, only after trust, last third of the call), playful (disarms). Slow the second half of every important question. Keep volume and speed flat; vary only pause and pitch.

StealThe objection loop

Agree ("yeah, that's not a problem") → book the specific next step (calendar commitment) → "before I go — what were you wanting to go over in your mind?" → the real objection surfaces → handle THAT one with questions, tied to her stated outcome. This loop is Objections 3, 4, and 7 above.

SkipStatus theater

"Just to see if I'd be available for you," waiting 3 minutes to call back, scripted stutters. Maya paid you — the authority is real, the games read as games. Keep the substance (specific booked next steps), drop the posture.

SkipFive-rung pain excavation

Miner's depth is calibrated to B2C life decisions (insurance, biz-opp). Spa and restaurant owners buy on time-back and revenue math — go one or two rungs down the pain ladder, then bring the numbers. Your consequence question is a dollar figure, not a feeling: "22 missed rebookings a month at $180 is $47k a year."

SkipFaked detachment

His sellers perform "I'm not sure we can help you." Yours is true: "If the numbers say this isn't worth building, I'll tell you that in the session — that's what the $397 buys." The honest version of his best frame is stronger than the theatrical one. Put it in the offer copy.

NEPQ signature phrasings — verified, adapted to loopsuit"I'm not sure we could even help you yet — it depends what [current provider] is doing about [the leak]." ← master disarm "Would you be opposed to…?" ← no-oriented ask (cold) "Would it be appropriate to…?" / "Would that help you?" "Yeah, that's not a problem." ← objection opener, always "How do you mean?" ← confused tone, they expand "What was it about [the calculator / the email] that caught your eye?" "Is there anything you'd change about how [follow-up] works right now, if you could?" ← the dissatisfaction-finder "How long has that been going on?" → "Has that had an impact on you?" → "In what way?" ← the pain ladder "What happens if you don't do anything about this and it gets worse?" "Why now, though?" ← they argue for urgency "Money aside — why do you feel like it would work, though?" "Before I go — what were you wanting to go over in your mind?" Say: "funds," "agreement," "feel." Never: "budget," "contract," "think."

Tone  Constant volume and speed (135–185 wpm); vary only pauses and pitch. Ask the closing question with raised pitch — then a massive silence. Damaging admissions first ("here's what sucks about this") — trust beats promise. And BANT's authority question early ("anyone else in this decision?") prevents Objection 4 from ever appearing.

Reminder: scripts are for internalizing, not reciting. The tooltips carry the mechanisms — learn those, and the words rearrange themselves naturally on a live call.

05Offers & positioning

The Hormozi layer — including the one warning that reshapes your ladder.

⚠ The Dead Zone (Hormozi, 2026)

The $1,500–3,000/mo services retainer for SMBs is a dead zone: volatile clients, 4–6 month stick, and they blame you for their own sales problems. Escape to either pole — never price in the middle.

Go DOWN · <$400/mo

Fully automated, near-zero delivery cost: monitoring, audits, self-serve tools. Entry-tier Rank Radar (India / small fleets) lives here.

dead zone
$1.5–3k/mo
Go UP · high-ticket

Big one-time builds for clients with a working sales process. Big Head ($2–7k+ fixed) + Long Tail ($250–500/mo consumable).

The exception — software is not a services retainer

The Dead Zone is about MANAGED SERVICES: monthly labor, ambiguous attribution, client blames you for their sales. Software with near-zero marginal delivery cost is exempt — it has no labor tail and the value is directly observable. Rank Radar at NA pricing ($1,500–2,500/mo per fleet) sits ABOVE the dead zone, not below it, because the buyer can attribute a rank drop to lost revenue without your help.

the one pricing architectureCLARITY SESSION — $1,500 (was $397) Paid diagnostic. Qualifies the buyer. Refunded if it does not surface three actionable opportunities. BLUEPRINT — from $4,000 Credited into the build. CUSTOM BUILD — from $12,000 (was $1,997) Fixed price, capped in writing, KPI guarantee. AI OPS RETAINER — from $2,500/mo (replaces $297 keep-alive) Monitoring + monthly improvements + one new workflow per quarter. EMBEDDED PARTNER — from $6,000/mo Published, not "by invitation." RANK RADAR — India ₹18–60k/mo · North America $1,500–2,500/mo Same product, different market. India for case studies and iteration speed; NA for revenue. FLEET AUDIT — $600 / ₹45,000 one-time The near-term revenue product. Credited against month one.
Dream outcome × Likelihood of achievement
Time delay × Effort required
= VALUE

Levers  Likelihood is a solo operator's cheapest lever — done-for-you delivery makes belief "go through the roof." And "latency beats magnitude 7 days a week" — "live in 7 days" out-sells "20% better eventually." Priority tier = half the time, add a zero.

DoObstacle bonus stack

Every objection → build the mini-solution once → it becomes a permanent named bonus: "I have a bonus specifically for that." Each bonus must feel worth the core offer.

DoName the result

"Empty-Chair Recovery Sprint" beats "AI automation package." Never change the deliverable; re-wrap the name quarterly to cure fatigue. A/B test 3–4 names.

DoGuarantees that print

"If you don't get X by Y, I will Z" — power lives in the Z. Clarity Session: unconditional value guarantee ("not $500 of value → refund" — claimed twice in years). Builds: conditional on access/data/SLAs.

DoLead magnets that deprive

Type: "reveal a problem" (calculator, audit ✓). Rule: fully solve problem A in a way that exposes problem B — the paid offer. Free content teaches WHAT/WHY; the offer sells HOW.

2026Proof is the AI-era moat

AI floods the market with identical advice; the differentiator is demonstrated results — live dashboards, documented ops, real case studies. (Why un-gating links-hub matters.)

2026Sell a department

"Bring your own agent": decompose a role into ~5 tasks, automate task-by-task, pitch "I'm your entire reactivation department." Department-shaped offers command department money.

Price diagnosis  Closing >80% = underpriced 3–4× · 60–80% = 2–3× · 30–40% = right · <30% = not a price problem (wrong avatar or broken pre-call motion). A 10% raise ≈ +25% net profit. Anchor first, anchor high; charge upfront; "10 months, get 2 free."

06The 2026 AI stack

Both creators independently dropped visual no-code in late 2025. The model is the framework now.

StackClaude Code is the harness

Routines = the n8n scheduler replacement; Managed Agents = the hosted tier. New automations native; working flows stay — tokens cost more than compute.

RuleNo wrappers

"Every additional framework is inversely correlated with money made." Skills only for repeated tasks (proposals, onboarding); voice-dump the rest with OCCD: Objective, Context, Constraints, Definition of Done.

CostManager + cheap workers

Frontier model plans/reviews (~5–15% of work); Sonnet/GLM-class execute at 1/5–1/10 price. Extract the expensive model's process into skills — "you can't keep the intelligence; you can keep the process."

HygieneContext discipline

Quality degrades ~250k tokens (Opus-class) — clear and hand off via session docs. Work in prompt-cache sprints; cap thinking effort by default; grep, don't full-read.

DangerVerify or it didn't happen

Real incidents: an agent blasted a discount code to a 150–200k list; another "sent" 25% of claimed emails. Scoped keys, hooks, human approval on anything outward. Worker ≠ judge.

MemoryMarkdown wiki, not vectors

Karpathy-style: raw/ → wiki/ + index + CLAUDE.md routing. Herk runs his whole business at this level. Ingest evergreen only; route to live sources for volatile data.

The metrics tracker (build first, feeds everything)

caveman spreadsheet — per lane, per daysends · replies · positive replies · meetings booked · meetings had · show-ups · proposals out · closes · $ collected (all different numbers — track each) computed: reply rate · close-to-reply · revenue-per-proposal · DoD growth jobs: Sunday determinations · day-21 lane verdict · bottleneck diagnosis (default bottleneck: top of funnel — the icebreaker)

07Deprecated — do NOT do these

Everything below was good advice once — including in your own wiki and April playbook. It isn't anymore.

DeadDo instead
Per-lead AI-written copy / icebreakersHuman-approved template banks; AI fills variables only
"Quick question" subjects & openersGive-before-ask; ambiguous friendly subjects
Judging A/B at 50–100 sends500–1,000/variant, reply-rate, one variable/week
Apollo-first sourcingApify actor + MillionVerifier ($3–4/1k usable)
Google Workspace inboxes · 30-day warmup · SMTP poolsZapmail/airmail ~$3/mo · 21 days or pre-warmed · re-bid quarterly
Fully autonomous reply/send botsDraft + one-click human approve, always
n8n/Make for new builds · agent wrappers · heavy skill librariesClaude Routines/scripts · few skills for repeated tasks
$1.5–3k/mo SMB management retainersBarbell: <$400/mo automated OR high-ticket Big-Head-Long-Tail
Hourly / monthly time-based build pricingFixed price + guarantee + price cap
Vector DBs / RAG rigs for business memoryMarkdown wiki + routing (level 2)
Personal branding from day oneShadow outreach + 2-hour minimum presence; content after customer #1
Selling "savings" automationsRACE revenue systems; reframe hours as revenue via opportunity cost

08The build queue

In priority order. Everything feeds, measures, or closes the funnel — nothing here is a new product.

  1. Funnel metrics trackerThe caveman spreadsheet, per lane, in System 0. The instrument that runs Sundays and the day-21 lane verdict.
  2. Single-artifact proposal machineProposal + contract + Stripe + signature in one doc, video walkthrough, payment auto-books onboarding, automated follow-up until yes/no.
  3. Reply queue (light)Five-bucket triage → voice-matched drafts from the approved bank → one-click approve. Possibly a Claude Routine. Never auto-send.
  4. Lead-pull scriptApify actor + MillionVerifier chained into the existing pipeline. Softens the Apollo bottleneck.
  5. Copy factory (reframed)Fable co-writes per-lane template banks — sequences, disclosure lines, subjects, objection replies, DM scripts. You approve once; the pipeline fills variables.

Shelf (build after customer #1)

Daily client check-in bot · onboarding/welcome routine · reactivation campaign ("we owe you $175" → case study 3 days later) · client reporting. Never build: sending infra, a CRM (spreadsheet first), dashboards nobody opens, framework wrappers.

LoopSuit AI · Operator's Guide 2026 · compiled 2026-07-11 by Fable · sources: Saraev main + Daily Updates (newest ~55 videos), Herk (newest 20), Hormozi (310-note vault + 2026), LoopsuitBrain wiki · full-context MD files: Md docs/agency-guide-2026/ · strategy: the Postmortem & War Plan artifact (v3.1) · re-verify against new videos every 4–6 weeks

Mentor mode · built around IST, FSH, Axiom, the gym, and a 2am hard stop

The operating day.

Same energy you already have — pointed in the right order. The rule underneath everything: promotion → delivery → building. Outreach happens before FSH; building happens only after both.

D1The honest read (your mentor's notes)

KeepThe crunch — move it earlier

Your one-day deep-shift style produces work Sandeep calls the best he's seen. Don't fight it — re-time it. New rule: the day a deliverable lands, open the file for 30 minutes (starts kill procrastination), then schedule the crunch within 48h — not at the deadline. Same quality, plus a buffer day, and "reliably early" is the exact evidence Sandeep needs for the $5k → $10–11k conversation after your 45 days.

AnchorSleep is a schedule, not a virtue

Sandeep already told you: end at 2am IST — that's still 4:30pm EST, nobody in Canada thinks you left early. The anchor is the wake time, fixed at 11:00, seven days. Everything else flexes; that doesn't. The 16-hour binges feel productive and cost you the next day — you've been paying 2 days for 1.

TruthThe Maker School gap is sends, not skill

The people posting $10–20k MRR at month 4–6 in Nick's community are not better designers, better builders, or better positioned — most can't design a button. The single variable between you and them is emails out the door. You felt relief when Leaptools ended because you already knew this is the right game. Now play it daily.

FixThe pedestal problem

Kinetic-typography videos that took days and got 3 likes — that's polish spent where volume was needed. New law: post more, polish less. A screenshot + a real number + 15 minutes beats a produced video. Proof accumulates; virality is irrelevant. (The LinkedIn tab has the posts pre-written so this costs you minutes.)

AxiomCapped, not killed

Axiom is real work with a real partner — it gets one deep day (Saturday, ~8h cap) plus one weekday evening. What it never gets: hours before the reply queue is done, or "one more test" past 2am. It's gated from the income goal by your own rule — the calendar should say so too.

JoyBuilding is the dessert

You don't need discipline to build — you need permission to. So the plan gives it to you: every day ends with a build block after promotion and delivery are done. Building as reward is sustainable; building as avoidance was the rut. And Cortex/portfolio work lives on Friday, scheduled, guilt-free.

D2Unblock this week (in order — #1 is today)

  1. Reactivate Instantly (today, 10 min)The card failed 4 days ago — every paused day is warmup decay. Fix billing first; nothing else works without it.
  2. Fix the Zoho app passwords (today, ~1h)Per mailbox: Zoho → Security → App Passwords → generate new → reconnect in Instantly → confirm warmup restarts. Warmup died, so assume the Zoho fleet needs 2–3 weeks of re-warm before real volume.
  3. Bridge with pre-warmed inboxes (today, 20 min)Don't wait 3 weeks to send. Buy 3–6 Instantly airmail / pre-warmed mailboxes (~$3–5/mo each) — the 2026 doctrine: send day one at ~1.35× true cost. Lane A starts on these while Zoho re-warms.
  4. The [VERIFY] pass (30 min)Open the copy banks, search [VERIFY-PERSONAL] and [VERIFY-PRICE], approve or edit. This is the only thing between you and loaded campaigns.
  5. Pull the lead lists (~1h)Lane A: 1,000–1,500 US med spa (Apollo filter from the goals doc, or LeadsFinder actor + MillionVerifier). Lane B: ~1,000 QSR/restaurant ops heads. Dedup both.
  6. Load campaign, schedule sends (~1h)Two-step sequence, 30/day/mailbox ramp, provider matching ON, "sent via Instantly" OFF. The moment sends are scheduled, LoopSuit has a live funnel for the first time ever.
  7. Start the caveman sheet (20 min)A Google Sheet beats waiting for the System-0 build: per lane per day — sends, replies, positive, meetings booked/had, proposals, closes. Fill it nightly at shutdown.

D3The day (IST) — illustrated

■ LoopSuit■ FSH■ Health / life■ Axiom
11:00
☀️Wake — fixed, 7 days a week—

Phone allowed for ONE thing from bed (Nick's habit): scan overnight replies, flag the hot ones. No building, no feeds.

11:30
🏋️Gym60 min

Before the laptop opens, or it doesn't happen — evenings always get eaten. This hour is also where call energy comes from; Clarity Sessions are performed, not attended.

12:30
🍳Food · shower · reset45 min

Eat like someone with an 8pm sales call.

13:15
🎯THE POWER BLOCK — promotion first, always90 min

Reply queue: answer every outstanding lead (30m) → LinkedIn: 20–30 DMs/connects (30m) → Instantly + sheet glance, bounce <5% (10m) → ONE campaign improvement, however small (20m). This block is the Rule of 100 and it is the job. Everything else today is funded by it.

14:45
🎨FSH deep block4.5–5 h

Canada is asleep — zero pings, pure make-time. Deliverable rule: same-day 30-minute open, crunch within 48h of assignment, ship a day early. Early is the raise argument.

19:30
🍛Dinner · people · off-screen60 min

Real break. The evening block works because this one exists.

20:30
📞US window opens — calls & flex block3 h

20:30 IST = 11am ET: Clarity Sessions, partner calls, and hot-reply conversations book HERE. No calls booked? This becomes the build block — Mon/Wed: LoopSuit build queue (tracker → proposal machine → reply routine). Tue: Axiom evening. Fri: content (post from the LinkedIn/X tabs, 30 min cap) + Cortex/portfolio time, guilt-free.

23:30
🤝Canada overlap — FSH sync & sends2 h

2pm ET: Sandeep, standups, feedback rounds, anything collaborative. Light work — reviews and replies, not deep design. US lanes are mid-morning; watch live replies land.

01:30
📊Shutdown ritual20 min

Fill the caveman sheet → note tomorrow's ONE campaign improvement → close every tab. The numbers you log here are the Sunday determination and the day-21 lane verdict.

02:00
🛑HARD STOP—

Sandeep's words: "we love the work — prioritize your sleep." 2am IST is 4:30pm ET; nothing you do after this hour survives contact with tomorrow. Lights out by 2:45.

D4The week

DayPower blockFSHEvening (20:30–23:30)
Monoutreach 90mdeep blockcalls / build queue
Tueoutreach 90mdeep blockAxiom evening (3h cap)
Wedoutreach 90mdeep blockcalls / build queue
Thuoutreach 90mdeep blockcalls / proposals out
Frioutreach 90mdeep blockcontent 30m Cortex / fun build
Satoutreach 60m—AXIOM DEEP DAY (8h cap, ends 23:00)
Sunoff till evening—determinations 45m nice time — actually off

Rule  The power block happens 6 days a week even on Axiom day, even mid-FSH-crunch, even on a Canada travel day — it's 60–90 minutes and it is the business. Miss everything else before you miss it.

D5The $10k CAD math (why this plan gets you there)

The gap is smaller than it feels

Floor: FSH $5,000 CAD. Gap to goal: $5,000 CAD ≈ $3,600 USD/mo. Two paths close it — one is capacity-capped, one isn't.

Path A — Services (capacity-capped). At revised pricing, ONE $12,000 build per quarter plus two AI Ops retainers at $2,500 closes the gap — versus 2–4 builds per month at old pricing. Same revenue, roughly a third of the delivery load.

Path B — Rank Radar (uncapped, the actual ceiling-lifter). 8–13 North American fleets at $1,500–2,500/mo = $12,000–32,500/mo recurring, with near-zero marginal delivery cost per additional customer. This is the only path in this guide where the tenth customer costs roughly the same to serve as the first.

The honest sequencing. Path A funds the runway. Path B is the business. Fleet Audits ($600) are the wedge into Path B — they are sellable today with only rank capture working, they generate the case studies, and they qualify buyers who can approve recurring spend. You don't need a miracle; you need the power block to happen ~78 times in a row.

Sept  Canada trip (Sept–Jan, T4 window): build the phone-only version of the power block NOW — reply queue and DMs work from anywhere; sends run themselves. The system should not notice you changed continents. That's also the test that it's a business, not a laptop habit.

Caveat  This holds for the FUNNEL, not for delivery. Sends, reply queue, and DMs are location-independent. Builds are not. Before September, either (a) have Rank Radar subscriptions carrying enough revenue that build volume can drop, or (b) plan the trip around a delivery gap. The system travels; the build capacity does not.

Proof posts, not thought leadership

LinkedIn: the builder who ships.

The positioning: never say you're one of the best product designers — post work that makes people conclude it. Real products, real numbers, zero AI-guru vocabulary. One post a week, 30 minutes, after the power block. Companies should discover you've been building in silence.

L1The rules

Cadence1/week, timeboxed

Friday evening block, 30-minute cap, post lands 6:30–7:30pm IST (= morning ET, your audience's coffee scroll). Content is channel #6 — it never displaces outreach.

FormatThe first line is the post

LinkedIn truncates at ~2 lines — the hook must survive the cut. One visual (real screenshot > produced video — the kinetic-typography lesson). Short paragraphs. No hashtag salad (0–3 max). Write to ONE reader: a founder or owner, not "my network."

BannedThe guru voice

No "🚀 excited to announce," no "AI won't replace you, people using AI will," no lessons-listicles about tools you haven't shipped with. If a sentence could appear on anyone's feed, it doesn't belong on yours.

EngineComments beat posts

10 minutes after posting: reply to every comment. Daily: 3–5 substantive comments on posts by design/AI builders your buyers follow — that's where profile visits actually come from.

L2The post bank (ready — personalize the [brackets], attach the screenshot, ship)

These are raw material, not scripts. The guide's own rule is post more, polish less — thirty pre-written posts become thirty posts you perfect instead of thirty days of shipping rough ones. Take one, spend fifteen minutes on it, ship it in whatever state it's in.

post 1 · rank radar (the product story)Restaurant brands live and die by where they rank on Swiggy and Zomato. Almost none of them can see it. So I built Rank Radar: it checks every outlet's rank on both apps, daily, by locality — against the 3 nearest competitors — and flags the moment something slips. Rating dip, broken listing, delisted bestseller: HQ knows the same day, not three weeks later through soft sales. Some things I learned building it: → Rank isn't a leaderboard, it's a tap. It drips orders when you're up and silently stops when you're down. → The painful cases are never the bad outlets. It's the good outlet that slipped to page 2 while everyone watched the sales report. → Ops teams run mystery diners for kitchens — and nothing for listings. Built with a Playwright polling engine, a fleet-view dashboard, and an owner-level overview page. Designed and shipped solo, end to end. [screenshot: fleet view] If you run a multi-outlet brand and want your outlets audited against your competitors — free, report either way — my DMs are open.
post 2 · the outbound engine (honest framing — it's yours)I spent the last months quietly building an outbound engine for my studio: ~30 mailboxes across 10 domains, a 7-stage lead pipeline that cleans, enriches, and personalizes at scale, a dedup engine, and a reply system where AI drafts and a human approves every send. Capacity: ~900 emails a day. The same category of system I build for clients who need pipeline. The counterintuitive lesson from the research phase: in 2026, LESS AI in cold email works better. AI-managed inboxes pattern-match hyper-optimized copy as spam instantly. So the system's rule is human-approved templates, AI fills only small variables — a machine that sounds like a person because a person wrote it. Infrastructure is a commodity. Taste in what to send isn't. [screenshot: pipeline dashboard, numbers blurred] If your business depends on outbound and it's all manual, this is exactly the kind of system I build. DMs open.
post 3 · cortex (the saas + waitlist cta)I gave myself one sprint to answer a question: can one designer, working alone with AI agents, ship a real SaaS — not a demo? The result is Cortex: an Obsidian-style knowledge graph in the browser. Your notes become nodes, connections become visible, and an AI layer helps you find what you actually meant to remember. What "designed and built solo" means now: → Design system, interactions, graph physics: mine → Backend, auth, data layer: built alongside AI agents → Time from first sketch to working product: [X days] The part that changed how I work: I stopped treating AI as autocomplete and started treating it as a build partner with infinite patience and zero taste. Taste stays my job. [screenshot/gif: the graph view] It's live behind a waitlist → [cortex-join link]. Referrals move you up the queue. I'd genuinely love to hear what you'd want a visual second brain to do.
post 4 · the silence post (proof dump — highest ceiling)I shipped 7 products in the last year and posted about almost none of them. Fixing that today. While working full-time as a product designer, I built — design AND code, end to end: → Rank Radar — Swiggy/Zomato rank monitoring for restaurant chains → Rebound — lapsed-client reactivation for med spas → Cortex — a visual second-brain SaaS (live waitlist) → A 900/day cold outbound engine with AI-drafted, human-approved replies → A legal case-tracking automation (Python + Claude + Telegram) → An internal collaboration hub for a design agency → An interactive proposal engine that turned client docs into experiences None of this went on LinkedIn because I kept telling myself "after one more feature." That was the wrong instinct. Proof compounds only when it's visible. So: one build, posted properly, every week or two. Starting now. [image: 7-product collage / grid] Which one should I break down first? 👇
post 5 · the ai-era designer workflow [VERIFY with Sandeep before naming FSH work]A client deck went through 40+ revisions across a team. Nobody could answer "what changed since Tuesday?" So instead of writing a status email, I built a tool: a visual diff for slide decks. Every version compared side by side, every change logged, all front-end, shipped in an evening. This is the part of "AI changed design work" nobody posts about. Not generating images — compressing the boring 20% of every project (status, changelogs, handoffs) into tools that take an evening to build and outlive the project. My rule now: if I explain the same thing twice, I build the thing that explains it. [screenshot: the diff tool, client work blurred] Designers: what's the status-update you're most tired of writing?
post 6 · rebound (the med spa problem)Most businesses think they have a lead problem. Usually they have a leak problem. A med spa I looked at had ~2,400 client records. Around 700 of those people came two or three times, liked the service, and quietly stopped coming. Nobody's job was to bring them back. At a $180 average ticket and a conservative 7% win-back rate, that's roughly $26,000 a year — sitting in the database, from people who already trusted them once. So I built Rebound: it segments the drifted clients by treatment cycle and spend, then re-engages them at the right moment — in the front desk's name and voice, with every message owner-approved before it sends. Nothing robotic goes out. Reactivation is the cheapest revenue most businesses have, and almost none of them work it. [screenshot: the segments view] If you run an aesthetics practice and want your actual number, I run it in a short working session. DMs open.
post 7 · the career arc (personal — highest engagement)Three years ago I was designing mobile banking screens for TD Bank, used by millions of people, and watching a lot of good design die in the handoff to engineering. I kept thinking: what if there was no handoff? What if the person who designed it just... built it? So I learned to ship the whole thing. Today I design AND build production products solo — Rank Radar, Rebound, Cortex, and internal tools for the agency I work with — with AI as the build partner and my taste as the thing that doesn't get outsourced. I've had roles end. The honest truth is that the last time it happened I felt relief — because I already knew I wanted to build things I control. Still designing full-time. But building in the open now. This is the start of that.
post 8 · court tracker (automation case study)A lawyer I built for was losing hours a week refreshing case portals to catch updates. So I built a system that watches the case sources, uses AI to read and summarize every change, and sends a plain-English update straight to Telegram — "Case X moved, here's what changed and what it means" — no portal, no dashboard, no app to open. Built with Python, the Claude API, and a Telegram bot. The pattern I keep coming back to: the best automation isn't a new tool you have to check. It's the work quietly showing up where you already are. What's the recurring thing in your week that a system should just... handle?
post 9 · interactive proposals (the craft flex)Most proposals are a PDF nobody finishes reading. For a recent engagement I built the proposal as an interactive experience instead — the client's problem quantified in their own numbers, the plan as something you move through, the pricing framed against the cost of doing nothing. Designed and built as a real web experience, not a slide export. Here's what I've learned: a proposal is a test. The client is silently asking "does this person understand my problem better than I can explain it myself?" Spend 80% of the document proving you do, and the price stops being the conversation. [screenshot: the interactive proposal]
post 10 · the "less AI" lesson (thought-provoking, not guru)Everyone's racing to put more AI into their outreach. After building a cold email system this year, I think that's backwards. Inboxes are AI-managed now. They pattern-match "perfectly optimized, every sentence is value" copy as spam almost instantly — because that's exactly what spam looks like in 2026. The emails that actually land are the ones a human obviously wrote. A little rough. One oddly personal line. No polish. So the system I built uses AI for the unglamorous parts — finding leads, enriching, routing replies — and keeps a human on the actual words. AI as the infrastructure, not the voice. The counterintuitive rule: the more AI floods a channel, the more the human touch is worth.
post 11 · building an AI operating system (the systems flex)I spent a while building myself a second brain. Scraped ~800 transcripts from the best operators I could find, distilled them into 786 linked, searchable notes, and wired it so I can query my own library while I work — "what does the data actually say about X" — and get a straight answer with sources. The lesson wasn't about note-taking. It was this: the bottleneck was never information. It was getting the right piece of it into my hands at the moment I needed it. That's what most "AI" should be doing for businesses — not generating more, but retrieving the right thing at the right time.
post 12 · what solo-building 7 products taught me (listicle done right)I shipped 7 products solo in the last year while working full-time. Not a flex — most people never post the lessons, so here are mine: 1. Building was never the bottleneck. Distribution was. I could build anything; I just wasn't telling anyone. 2. Taste is the moat. AI made building cheap, which means the thing that's scarce is knowing what's worth building and what "good" looks like. 3. Ship ugly, then polish. My most-polished project got 3 likes and took a week. Proof compounds; virality doesn't. 4. The boring 20% — status updates, changelogs, handoffs — is where the best small tools hide. 5. One document beats three. Every extra step between intent and money loses people. Which of these do you want the full story on?

Order  Post 4 (the silence post) goes first — it retro-frames everything and starts the series. Then roughly weekly, alternating a product post (Rank Radar, Rebound, Cortex, Court Tracker) with a lesson/personal post (the career arc, the "less AI" lesson, the 7-products list) so the feed never reads as one long ad. The med-spa math post (in linkedin/profile-and-pinned-post.md) stays pinned throughout. Anything touching FSH client work: clear the framing with Sandeep first.

The long game · 20–30 min/day cap · never displaces outreach

𝕏: build in public, quietly relentless.

Goal: in 12 months, be a recognized design-led builder in the Canada/US/India AI space. Not a growth hacker — the person whose ship-logs people check. X is where builders actually watch each other work; LinkedIn is where their companies find out.

X1The system

BioIdentity first

"Product designer who ships the whole thing. Building Cortex (visual second brain) + AI systems for real businesses in public. ex-TD Bank." Pin the Cortex thread once it exists.

CadenceSmall, daily, honest

1 ship-log post/day (3–5/week is the floor) — screenshot + one true sentence, 5 minutes, from the Friday/evening build blocks. 5 replies/day to builders in the design×AI space — replies are where followers actually come from at zero. 1 longer thread every 2 weeks (a real build breakdown).

PillarsFour, rotate

① Ship logs (what got built today, with the screen) ② Before/after UI (designer advantage — nobody else's logs look good) ③ Receipts (real numbers: sends, ranks, waitlist count — including the bad ones) ④ One-lesson posts (a specific thing learned building, never generic advice).

BannedThe BIP clichés

No "Day 1 of building 🚀," no follower-count posts, no engagement bait ("agree?"), no faked traction — the Cortex rule (no fake counters) applies to the feed too. Bad numbers posted honestly build more trust than good numbers implied.

FlagshipCortex is the show

Cortex is the perfect BIP vehicle: visual, consumer-facing, waitlist to point at. The agency work appears as anonymized systems posts (the outbound engine, the reply queue). Axiom stays off the feed until it's profitable — your own rule.

TruthHonest expectations

X compounds over 6–12 months and pays in relationships and inbound credibility — not clients this quarter. That's why it's capped at 30 min/day and lives AFTER the power block. 300 real builder-followers who trust your logs beat 10k passive ones.

X2The post bank — 17 ready posts

These are raw material, not scripts. The guide's own rule is post more, polish less — thirty pre-written posts become thirty posts you perfect instead of thirty days of shipping rough ones. Take one, spend fifteen minutes on it, ship it in whatever state it's in.

Paste as-is; swap only the [brackets] (a number, a link, or the media to attach). Lowercase-casual is intentional — it's the native X builder voice. Space them out: one a day, never two of the same pillar back to back.

01 · the opener (pin this)product designer for 7 years. the last 12 months I quietly shipped 7 products — design AND code, solo, around a full-time job. i'm going to post the build logs from here on out. real screens, real numbers, the failures included. first up: cortex, an obsidian-style knowledge graph SaaS, and the 900-emails-a-day outbound engine that runs my studio. no courses, no "AI will replace you" takes. just the work.
02 · cortex ship log — the physicscortex ship log. spent today making the knowledge graph *feel* right. the nodes were jittering — springs fighting the collision solver. fix wasn't more force, it was damping. now dragging a note and watching its connections follow feels like moving something physical. this is the 20% of the work nobody sees and the whole reason a graph tool lives or dies. [attach: 15-sec screen recording of the graph]
03 · cortex — the "why a graph" postevery notes app shows you a list. but your notes aren't a list. they're a graph pretending to be one — this idea connects to that one, this project touches three others, and you only remember the connection when you stumble back into it. cortex shows you the graph. notes become nodes, connections become visible, and an AI layer surfaces the link you forgot you made. building it in public. live behind a waitlist → [link]
04 · cortex — the build thread (every 2 weeks, longer)i built an obsidian-style knowledge graph SaaS in [X] days, solo, as a designer who codes. how it actually went, with receipts: 🧵 1/ premise: notes are a graph. every tool flattens them to a list. i wanted to build the graph you actually think in. [hero gif] 2/ design first. day one was pure feel — node physics, hover states, the little "aha" when a note snaps into a cluster. product taste is the moat now; the code is rentable. [before/after] 3/ the workflow: one expensive model orchestrates, cheaper agents build, i review like a design director with an infinitely patient team that has zero taste. taste stays my job. [screenshot of the loop] 4/ what broke: [honest failure + the fix] 5/ what's next: [next feature]. it's live behind a waitlist → [link], referrals jump the queue. logs continue tomorrow.
05 · rank radar — the alert that is the productthis one alert is the entire product: "[outlet name] dropped from #4 to #19 on zomato for 'biryani near me' overnight." restaurant brands lose orders like this constantly — a rank slip in one locality, at one time of day — and find out three weeks later through soft sales. rank radar watches every outlet on swiggy + zomato, daily, and catches it the same night. built the polling engine with playwright. [attach: screenshot of the alert]
06 · rank radar — fleet view designdesigning dashboards for people who manage 30 locations taught me one thing: the overview IS the product. built "fleet view" for rank radar — every outlet's aggregator rank on one screen, sorted by who's slipping, so an ops head sees the problem outlet in two seconds instead of opening 30 tabs. the hard part was never the data. it was deciding what NOT to show. [attach: fleet view screenshot]
07 · outbound engine — the reply queuemy inbox reply system now drafts responses in my voice from an approved bank, and i just tap ✓ or edit. handled 27 cold-email replies in 11 minutes this morning. every send was human-approved — nothing auto-fires — but the drafting is done for me. this is the boring infrastructure that actually makes outbound survivable for one person. [attach: reply queue screenshot]
08 · outbound engine — the counterintuitive lessoncounterintuitive thing i learned building a cold outreach system in 2026: use LESS AI in the actual emails, not more. inboxes are AI-managed now, and they pattern-match "perfectly optimized, every line is value" copy as spam instantly. the emails that land are the ones a human clearly wrote — a little rough, one oddly personal line, no polish. so my system's rule: humans write the templates, AI only fills small variables. a machine that sounds like a person because a person wrote it.
09 · the thesis post (pin-worthy)the designers who win the next 5 years won't be the ones who prompt the best. they'll be the ones who can hold taste AND ship the whole thing — design, frontend, backend, the deploy — without losing the vision in a handoff. i spent 3 years at a bank watching beautiful designs die in engineering translation. now i build the design and the product, end to end, and nothing gets lost. taste is the one thing AI can't rent you. everything else, it can.
10 · rebound — the reactivation mathevery med spa is sitting on money it can't see. ~700 clients who came 2-3 times, liked it, and quietly drifted. at a $180 ticket and a conservative 7% win-back, that's ~$26k/year — from people who already chose them once. nobody's job is to bring them back. so i built the system that does: segments the drifted list, messages them at the right point in their cycle, in the front desk's voice, every message owner-approved. reactivation is the cheapest revenue a business has. [attach: dashboard]
11 · proposal-as-one-document (a lesson)shipped a small thing today that i think about a lot: a proposal that is ALSO the contract, the payment page, and the signature — one document, one link. reason: every extra step between "yes" and "paid" leaks ~10% of buyers. separate proposal → separate contract → separate invoice = you lose a third of the people who already said yes. collapse the steps. the friction between intent and money is where deals quietly die. [attach: screen]
12 · court tracker — python + claude + telegrambuilt a legal case-tracking system for a client that lives entirely in telegram. python watches the case sources, claude reads and summarizes the updates, and the lawyer gets a plain-english ping — "case [X] moved, here's what changed and what it means" — instead of refreshing a portal. favorite kind of build: no app to open, no dashboard to check. the work just shows up where you already are.
13 · the visual diff tool (an evening build)a client deck went through 40+ revisions across a team and nobody could answer "what actually changed since tuesday?" so instead of writing a status email, i built a visual diff for slide decks — every version side by side, every change logged. all front-end, shipped in one evening. my rule now: if i explain the same thing twice, i build the thing that explains it. [attach: the diff tool]
14 · an honest failure post (post these — they build trust)spent 4 hours today chasing a bug that turned out to be me. [the outbound pipeline was silently dropping leads whenever a company name had an emoji in it — one unhandled character killed the whole row]. classic: i was debugging the clever part while the dumb part quietly failed. shipped the fix. lesson re-learned for the hundredth time: validate the boring inputs first. [attach: the fix, optional]
15 · cold campaign — week-1 receipts (post the real numbers)building in public means posting the numbers before they're good. med spa cold campaign, week 1: [X] sent, [X]% reply rate, [X] meetings booked. under my target of a meeting per ~150 sends. not panicking — you don't judge a variant under 1,000 sends. changing ONE thing (the subject line), sending 1,000 more, then reading the data. that's the whole game: volume, then judgment. [attach: sheet]
16 · building a second brain from 800 transcriptsi scraped ~800 youtube transcripts from the best operators i could find and fed them into a system that distills them into a linked, searchable knowledge base — 786 notes, cross-referenced, that i can query while i work. the surprising part: the value wasn't the notes. it was that i could now ask my own library "what does the data say about X" and get a straight answer with sources. a second brain that actually answers.
17 · the orchestration workflow (a "how i build" post)how i actually build now, as one person: i don't write most of the code. i orchestrate. an expensive model plans and reviews; cheaper agents do the heavy lifting in parallel; i sit in the middle as the director — deciding what's good, what ships, what gets torn up. it feels less like coding and more like running a studio where the staff never sleep and have no ego. my whole job is taste and judgment. that's the part that doesn't get automated.

Engage  The daily 5 replies matter more than the posts at zero followers: pick ~10 accounts at the intersection of design × AI × indie (peers slightly ahead of you, not mega-accounts), turn on notifications for 5, and reply with something only a builder would say. Almost nobody posting about AI can design, and almost nobody who can design ships — that gap is your whole edge.

Gamified · one block = one Power Block, run for real

The road to $10k, one run at a time.

Every block below is a real projection, not decoration — built from the same funnel assumptions as the rest of this guide. Drag the slider to any goal. Click a block to mark every run up to it done (click the frontier block to step back). Hover any block for what it's worth.

✓
Daily quest · 6× per week
The Power Block
⏱ 90 minutes · before FSH, always
🏆 Reward: +1 block on the grid · streak stays alive

🎯Set your target

Target monthly income (CAD, FSH + LoopSuit combined) $10,000

The funnel — one typical month at goal pace
How this is calculated (the honest assumptions)
This is a stage-by-stage funnel simulation, not one blended number. Per send: 85% deliverability (post-MillionVerifier, plain text) → 1.5% of delivered reply (realistic public-list rate) → 30% of replies are positive → 55% of positives book a call → 70% show up → 15% of held calls close a $12,000 build (was 25% at $1,997 — higher price, longer cycle, fewer closes; the tradeoff is explicit); 30–45% of held calls also pay the $1,500 Clarity Session. That chains to ≈0.2% booked-call rate (the guide's target band is 0.5–1%; 0.03% is "bad but viable") and ≈1 build per ~4,500 sends at maturity.

The real-life frictions are modeled too: copy maturity ramps 40% → 70% → 100% over the first ~9 weeks (you don't have winning copy on day one); sends ramp from ~60/day to the scenario's ceiling as your restarted warmup completes (full 900/day = 10 domains × 3 mailboxes × 30/day); there's a ~8-week pipeline lag from send to cash (reply → booking → close window — higher ticket stretches this vs the old ~4-week $1,997 cycle); AI Ops retainers churn ~6%/mo; and — the binding constraint everyone ignores — solo delivery capacity is capped at ~2–4 builds/month alongside FSH (~20–25h of real work per build against ~10–12h/wk of delivery time). That cap is why a pure services path isn't infinite. Above it, builds flatten and growth comes from the AI Ops tail stacking ~2 retainers/month — which is why very high services-only targets take so long and eventually go unreachable.

Rank Radar at NA pricing ($1,500–2,500/mo per fleet) is the primary ceiling-lifter — near-zero marginal delivery cost per additional customer, so it is not bound by the solo-build cap. Raising prices and templatizing delivery (the Rebound recipe → 4–6/mo) help Path A; Path B is what actually removes the ceiling. The model still refuses to assume you'll have those Rank Radar fleets before you've sold them.

Two different numbers, both shown: "monthly run-rate" includes project cash flow (builds + sessions at current pace — it stops if you stop sending); "durable recurring" is only FSH + AI Ops MRR (it keeps paying if you take a month off). The run-rate curve is more pessimistic than the old $1,997/25% model on close count — higher prices mean longer cycles and fewer closes — while each close carries more revenue and roughly a third of the old delivery load. USD→CAD ≈1.39. A projection, not a promise: the point is the shape of the curve, not the exact digit.

Phone pack · Vivek Singh / Vital Wires · synced to 18-slide peak-first deck

VW meeting script

Story first, roadmap second, proof always at hand. Don’t read slides. Close with a starting stage — not a price. Max 3 spoken sentences per slide — he interrupts.

Deck 18 slides Intro Shree → LoopSuit AI Ask Map → Propose → 48hr

Open the deck on the other screen. Speak from here.

Open deck ↗

Mindset

Vivek is ~50, consulting veteran, low retention, will interrupt — that’s engagement, not rejection. When he talks, stop presenting and converse; re-enter the deck at the nearest chapter.

You are the specialist he’s evaluating, not a vendor pitching up. Story first, roadmap second, proof always at hand.

Opener

One line of context — then straight into slide 01. Do not open with a bio.

“Shree and I have worked together on consulting engagements for a while — he’s seen my work up close.”

Then open slide 01. No bio dump. Frame: “I’ll start with one finished story — then we bring it back to Vital Wires.”

Room timing · ~20–25 min

~1–2 min — opener (Shree line) → slide 01
~7–9 min — Before → Rebuild → Guidelines → Hub (let him poke)
~2 min — The gap (“one method — here’s why it matters”) — stop if he objects; handle live
~4–5 min — Plan + skim Create / Launch / Control / Sell (don’t lecture every bullet)
~1 min — Channels: click website mock + SAP RISE Roundtable only
~3–4 min — Lead engine (+ Franchisee Shift / selected work if energy is high)
~3 min — How we start → How we work → The Ask → silence

If he hijacks

Stop presenting. Converse. Re-enter at the nearest chapter (Gap, Plan, or Ask). Full recovery lines live in VW Cheat → If he interrupts.

Slide speak lines

Aligned to the live 18-slide peak-first deck. Each slide: say → deeper ammo → if he asks. Don’t read — skim and speak. Max 3 spoken sentences.

01 Hero

Say

  • “Before I explain anything, let me just show you a piece of work — because it says more than a deck ever will.”
02 Blenz · Before

Say (~60–75s)

  • “This is Blenz — a Canadian beverage brand. History, stores, franchise footprint — the delivery was there.”
  • “The surfaces weren’t. This is what the market was seeing.” (Pause — let him look at both frames.)
  • “Four things they needed fixed: no scalable system — every asset reinvented; no brand guidelines — teams guessing; clinical look — safe, dated, not Gen Z; and the ask wasn’t a logo tweak — it was a full rebrand. That’s when I came on board.”
  • Bridge: “Twelve weeks later — this is what we shipped.”

Deeper ammo

  • Don’t trash the old brand — diagnose. Delivery was there; surfaces hadn’t caught up (mirrors Vital Wires).
  • Uncropped frames matter — he has to see clinical before the rebuild.

If he asks

“Why show a coffee brand to an enterprise firm?”

“You’re not buying coffee branding. You’re seeing how deep a brand system goes when one senior owns it end-to-end. Same discipline — different buyer.”

03 Blenz · Rebuild

Say (~45–60s + let media breathe)

  • “Twelve weeks. A complete rebuild — not a refresh.”
  • “One system end-to-end: packaging, merch, store interior, and the rules that hold it together.”
  • “This is the creative quality bar I’d hold Vital Wires to — enterprise substance deserves this craft on its surfaces.”

Deeper ammo

  • Every asset from one system — nothing designed twice.
  • Don’t narrate every frame — let the paper-bag / system media play.

If he asks

“You did ALL of this?”

“Design and direction, all mine. Production scales through my team and my tools — that’s coming next.”

04 Blenz guidelines

Say

  • “Not a logo drop — a complete brand book you can scroll.”
  • “Identity, packaging, merch, interiors — and the rules that keep it consistent.”
  • “Click inside and scroll if you want — depth of system, not a moodboard.”

Deeper ammo

  • This is what makes brand ONE-TIME to establish and ONGOING to enforce — the distinction Vivek’s world already thinks in.
05 Creative Hub

Say

  • “Then I built the tool their whole leadership works in.”
  • “Briefs, reviews, approvals — one owned place, not chats and folders. I designed it AND shipped it.”
  • Bridge: “Same pattern I’d install for Vital Wires brand work. Now — why this matters for you.”

Deeper ammo

  • Bespoke, not another Kanban. The agency owns it outright.
  • Feedback cycles: days → hours.

If he asks

“Who is this for?”

“A Canadian design agency I work with — their CEO and full leadership are active users.”

06 The gap

Enterprise delivery. Weak market signal. · 01 Referrals · 02 Surface · 03 Proof

Say

  • “Everything you just saw is one method — diagnose the surface, rebuild the system, install how the team runs it.”
  • “Here’s why it matters for Vital Wires: your delivery is enterprise-grade; your market signal doesn’t show it. Buyers meet your website and materials before they meet your team — and right now those surfaces don’t show the ROI you already deliver.”

Slide 06 pushbacks below — diagnose, don’t insult. If he goes full referrals → Objections #6.

If he asks · surfaces / website / “how do you know?”

“How did you come up with that? Are you saying our website is bad? We have case studies.”

“I’m not saying the site is broken — I’m saying the buyer journey starts there, before they meet your people. I haven’t done a full audit of Vital Wires yet; this is the pattern I see in enterprise consulting: strong delivery, packaging that doesn’t carry the same weight. Case studies help only if a buyer can find them fast, they sound like how deals actually close, and sales actually uses them in every proposal. If yours already do that, this card gets lighter — the presence sweep would show it side by side.”

“Why quieter? We post / we’re active on LinkedIn.”

“Quieter relative to the delivery — not ‘you don’t post.’ A firm can post every week and still look quieter than its wins deserve if the posts don’t carry proof, outcomes, and a clear why-Vital-Wires. Premium work behind quieter packaging usually means: generic capability language, thin or buried proof, decks that don’t feel like the caliber of the implementation. That’s the hypothesis. Happy to be wrong after a short side-by-side look.”

Hover / “shortlisted late or not at all” — “Says who?”

“That’s the buyer behavior I’m naming — they rush the site and materials first. Late shortlist is what happens when packaging doesn’t match delivery: they don’t feel the ROI in thirty seconds, so you enter late or not at all. I’m not claiming a secret look at your pipeline — I’m naming the risk that pattern creates. The sweep is how we check whether Vital Wires is in that pattern or not.”

If he asks · “What ideas do you have?” (don’t back off — give direction + Map)

01 Pipeline capped by referrals — “So what would you do?”

“Not replace referrals — arm them and add a second engine. Concretely: a diligence kit so every warm intro lands harder (site, one-pager, proof that matches the deal); then presence-plus-pipeline for verticals you already own — when SAP ships something or a regulation drops, that’s a campaign, not a hope. Exact mix depends on how deals close today — that’s Map, then a scoped proposal in forty-eight hours. I won’t invent a full GTM plan on this slide.”

02 Surface undersells substance — “Okay, what would you change?”

“First move is the sweep — website, LinkedIn, decks, collateral — working vs underselling, side by side. Directionally: sharpen positioning so a buyer feels the ROI in thirty seconds; make proof impossible to miss; make sales materials sound like how deals actually close. If the homepage is already strong, we leave it and fix what’s around it. I won’t redesign Vital Wires in the air — I’ll write the scoped fixes after Map.”

03 Proof stuck in memory — “What ideas for that?”

“Build a reusable proof library sales can grab without hunting Slack. Directionally: outcome one-pagers by vertical — not just logos; a small set of case frames that paste into every proposal; a rule that every closed win produces one reusable asset within a week. That’s how wins stop living only in people’s heads. Which formats matter most for Vital Wires — I’ll pin that in Map from how your deals actually close, then scope it in the proposal.”

Deeper ammo · slide 06

  • Frame = hypothesis + pattern, not “I audited you last night.”
  • Agree with what’s true (“you post,” “you have case studies”) then reframe quality/findability/use.
  • On “what ideas?”: always 2–3 concrete directions + “scoped after Map / 48hr proposal” — never only “I need to research.”
  • Bridge out: “That’s the gap. Next slide is the road — Create → Launch → Control → Sell.”
07 The plan

Say

  • “So the road has four stages. Create the foundation. Launch it so it’s seen. Control it so everything stays on brand. Sell — turn presence into pipeline. First two are one-time projects; last two are ongoing. You choose where we start.”
08 Create

Say

  • “Positioning, identity, website, proof. Nothing launches until the foundation is right — that’s the Blenz discipline you just saw.”
09 Launch

Say

  • “Shipped quietly is the same as not shipped. Launch is the announcement, the films, LinkedIn and email — the new brand actually landing in the market.”
10 Control

Say

  • “You know how consulting decks get made — cut-paste from three old decks at eleven pm before the client meeting. Control is the system that catches that: team produces, we check, on-brand ships. Every proposal, every deck, every post.”

Keep the cut-paste line verbatim — advisor anecdote; lands hard with an ERP consulting CEO.

11 Sell

Say

  • “And this is where it pays for itself. When SAP releases something or a regulation drops in a vertical you own, that’s a campaign waiting to run. Presence becomes conversations, conversations become pipeline — measured, so we double down on what converts.”
12 Channels

Say

  • “Day to day it looks like this — everywhere the firm communicates, kept consistent and alive.”

THEN CLICK EXACTLY TWO: website mock + events (SAP RISE Roundtable). Skip the rest unless asked.

13 Lead engine

Say

  • “And pipeline isn’t theory for me — this is my own outbound system. Nine hundred emails a day capacity, every lead researched and personalized by AI, every send human-approved. I run this for my own studio; it’s the same class of system I’d stand up for you.”

If he asks

“What’s the conversion / reply rate?”

“I’ll give you the honest number — my first test batch of 350 got a 4% reply rate, and I’m scaling volume now. I’d rather show you a working system and real early numbers than promise you a rate I haven’t earned yet.”

14 Franchisee Shift

Say

  • “One more, quickly — sometimes the marketing problem is a product problem. I led the full product design of this franchise-operations platform: HQ to franchisee, announcements, brand standards, one system instead of WhatsApp chaos.”
15 Selected work

Say

  • “The broader track record — TD Bank’s mobile app among them, seven years of product design.”

Flip-through. Don’t dwell.

16 How we start

Say

  • “One path, no package menu. We map priorities in a conversation, I send a scoped proposal within forty-eight hours, you approve before anything builds.”
17 How we work

Say

  • “Start small, expand only if it’s working. One senior partner accountable. And everything transfers — files, brand system, any tools we build. No hostage retainers.”
18 Close

Say

  • The Ask — then SILENCE.
“So — of the two starting points, brand foundation or presence-plus-pipeline: which feels like the right first ninety days for Vital Wires?”

Ask → silence. Don’t fill the pause.

The ask

Say this cleanly. Then stop talking.

“So — of the two starting points, brand foundation or presence-plus-pipeline: which feels like the right first ninety days for Vital Wires?”

End state

He saw real work · Map → Propose → Build understood · starting stage picked (or Map booked) · proposal within 48 hours · no price invented in the room · silence after the ask.

Objections

The eight answers live in one place — open that tab when he pushes back.

Open VW Objections ↗

Q&A — strong answers

Internalize. Don’t recite. Tone: calm, precise, peer-to-peer. Pricing / ROI / referrals / team size → VW Objections tab (once).

01“Are you selling me software or marketing?”
Vivek“Are you selling software or marketing?”
You“Marketing first — brand and presence for Vital Wires. Software when marketing needs a product underneath. Creative Hub and Franchisee Shift exist because I’ve hit problems you can’t solve with a Canva file. For Vital Wires I’d still start Create / Launch. Tools only if they clearly accelerate the marketing outcome.”
02“How do you work with our internal team / sales?”
Vivek“How do you work with our team?”
You“I don’t replace your delivery or your sales leadership. I make them easier to buy. Practically: focused loops with whoever owns brand and content; short loops with sales so proof matches how deals actually close; one review path so assets don’t die in chat. You stay the face of Vital Wires — I make the market materials and systems match that.”
03“Show me something live — not slides.”
Vivek“Show me something live.”
You“Yes.” (Blenz guidelines / Creative Hub / Lead engine.) “This is production work, not a pitch mock. When you’re done looking, I’ll bring it back to where Vital Wires should start.”
04“How is this different from Metavrash / Shree?”
Vivek“Isn’t this Metavrash?”
You“Shree introduced us — I’m grateful for that. This engagement is independent LoopSuit AI work: brand, presence, and pipeline systems for Vital Wires. Different scope, different accountability. If anything overlaps with Metavrash delivery, we keep lanes clean so you’re not paying twice for the same outcome.”
05“We’re enterprise / SAP-world. Do you get that buyer?”
Vivek“Do you understand enterprise buyers?”
You“Yes — and that’s why ‘pretty brand’ isn’t enough. Enterprise buyers judge you in the first thirty seconds of the site and the first page of a capability deck. I’ve shipped product design inside TD Bank’s mobile world — regulated, multi-stakeholder, high bar. Vital Wires already has the substance. We make the surfaces match.”
06“What about BeatRoute?”
Vivek“Should marketing cover BeatRoute too?”
You“Only if you want it in scope — I won’t force a BeatRoute pitch. Vital Wires brand and presence is the clear start. If later you want a product-led growth lane for BeatRoute, we map that separately. One starting stage at a time.”
07“What does the first ninety days look like?”
Vivek“What’s the first ninety days?”
You“Depends on what we pick today. Brand foundation: positioning and identity locked, website and proof that sell the delivery, sales materials sales will actually use. Presence-plus-pipeline: channels running on-brand, outreach your team can operate, measurement on what’s converting. Either way: Map → proposal within forty-eight hours → you approve → Build. Expand only when the first stage is working.”
08“Send me something — I’ll think about it.”
Vivek“Send me something. I’ll think about it.”
You“Absolutely — and so the proposal is useful, not generic: should we scope brand foundation or presence-plus-pipeline as the start? I’ll write to that and send it within forty-eight hours.” If he won’t pick: “Then let’s book fifteen minutes to Map priorities — so I’m not guessing.”

Do not say

  • Any price number
  • “MVP”
  • “Biryani Blues”
  • “vCMO / fractional CMO” — if HE names it, accept the frame
  • Rank Radar / Cortex — removed from deck; only if he asks what else you’ve built
  • Long METAVRASH backstory
  • “I’m just one person”
  • “Vinay” — his name is VIVEK

Vital Wires phone pack · LoopSuit AI · open anytime: #tab-vitalwires · cheat: #tab-vwcheat · objections: #tab-vwobj

Memorize this · nothing else · Vivek / Vital Wires

VW cheat sheet

The spine, five verbatim lines, and the full objection bank. Phone-ready.

8 spine beats 5 verbatim lines 8 objections

Full script with slide lines lives in VW Meeting.

Open VW Meeting ↗

The spine · 7 beats

Memorize this sequence. Story → gap → plan → proof → close.

  1. Blenz before — clinical / unscalable / no guidelines — full rebrand ask
  2. Blenz rebuild — twelve weeks, end-to-end system, quality bar
  3. Brand book — living guidelines, one-time establish / ongoing enforce
  4. Creative Hub — I designed it AND shipped it; leadership uses it daily
  5. “One method — here’s why for Vital Wires” — enterprise delivery, weak market signal
  6. 4 stages — Create / Launch = one-time · Control / Sell = ongoing
  7. Lead engine — 900/day capacity, AI-researched, human-approved
  8. Map → Propose → 48hr — then the ask, then silence

Five verbatim lines

Say the line. If he tilts his head or follows up — use the plain English under it.

Price

“Once we map the exact starting scope — custom proposal, forty-eight hours.”

Means: We pick the starting stage in this conversation (or a short Map call). I write a proposal with deliverables, timeline, and one fixed price — within two days. I won’t invent a number live.
If he pushes for a number now: “I can give you a guess, but it’ll be wrong. Same reason Vital Wires doesn’t quote an SAP implementation before discovery. Agree the stage with me — the proposal makes it concrete.”

ROI

“I won’t invent a two-million-dollar chart for you. In consulting you can’t usually prove one campaign caused one deal — you know that. What I commit to is a scoreboard we both watch.”

“Scoreboard / instrumentation” means in plain words: we track real activity numbers — people who reached out, meetings booked, proposals sent, pipeline that came from the marketing work — and we review them monthly so we double down on what works and kill what doesn’t. Not “trust me, branding is good.”
If he asks “so what are we actually measuring?”: “Before we start Sell, we lock three or four indicators with you — for example inbound inquiries, meetings from campaign or LinkedIn, proposal rate, pipeline tagged to presence work. Those go on a simple dashboard. You’re judging me on those numbers, not on how pretty the deck looks.”

Control

“You know how consulting decks get made — cut-paste from three old decks at eleven pm before the client meeting. Control is the system that catches that.”

Means: Your team still produces proposals, decks, posts. Before anything goes to a client or LinkedIn, it passes a quick on-brand check — so late-night Frankenstein decks don’t ship.
If he asks “so you police every slide?”: “We set a review path that fits how your team already works — not bureaucracy. Produce → check → approve → ship. Fast enough for real deadlines, strict enough that Vital Wires always looks like Vital Wires.”

Difference

“One senior brain, no handoffs — and the tools become yours.”

Means: You talk to me, I do the work (with a lean bench for production). No account manager translating you to a junior. Software and brand files we build — Vital Wires owns them.
If he asks “tools become ours how?”: “Files, brand system, and any app we stand up transfer to you. You’re not renting your operating system from me. If we part ways, you keep running.”

The ask → silence

“Brand foundation, or presence-plus-pipeline — which feels like the right first ninety days?”

“Brand foundation” = Create (positioning, identity, site, proof) — fix the surfaces first.
“Presence-plus-pipeline” = Launch + Sell lean — get visible and start generating conversations if the foundation is already strong enough.
Then: stop talking. Count to five in your head. If he stalls: “If it’s easier, we can book fifteen minutes just to Map — then I’ll write the proposal to that.”

Plain English · phrases that sound smart but confuse

If you wouldn’t say it to your dad, don’t say it to Vivek. Use the right column.

“Instrumentation”

Don’t say that word. Say: “a scoreboard we both look at” or “we track the numbers every month.”

“Attribution is murky”

Say: “In consulting you usually can’t prove one LinkedIn post closed one SAP deal — too many people touch the deal. So I won’t fake a ROI chart. I’ll track the leading numbers we can see.”

“Presence”

Say: “How Vital Wires shows up before anyone meets your team — website, LinkedIn, decks, emails, events.”

“Market signal”

Say: “What buyers think you are from your surfaces — right now that understates how good the delivery is.”

“One-time vs ongoing”

Create + Launch = projects with an end date. Control + Sell = monthly work that keeps the brand clean and pipeline moving. He chooses where to start.

“Map → Propose → 48hr”

Map = short conversation on priorities. Propose = I send scoped deliverables + timeline + fixed price. 48hr = you have it within two days. Nothing builds until he approves.

Objections

Full bank is not duplicated here — go read it once.

Open VW Objections ↗

Steal from NEPQ · Nick · Alex

Moves that sharpen the room — not full scripts. Full Alt answers live in VW Objections.

NEPQ · always open objections with

“Yeah, that’s not a problem.” — then handle. Never defend first.

NEPQ · smokescreen piercer

Book next step → “Before I go — what were you wanting to go over in your mind?” → real objection.

NEPQ · self-persuasion

After he agrees something would work: “Why do you feel like it would?” — he sells himself.

Alex · damaging admission first

Agree with the true part of the objection before the reframe. “You’re right — most ROI charts in B2B are theater.”

Nick · system is its own proof

On lead engine / Creative Hub: “This is production work, not a pitch mock — same class of system I’d stand up for you.”

Nick · blame scope, not evasion

Price early: don’t invent a number — Map the stage, proposal in 48 hours. Scope is why the number isn’t live.

Alex · sell the vacation, not the flight

Don’t narrate your process. Sell the end state: buyers feel Vital Wires’ caliber before the call; pipeline you can scoreboard.

Brain · don’t take the bio — take the surface

Trust objection → point at Blenz / Hub / TD work on screen. If it doesn’t match the call, he shouldn’t sign.

If he interrupts / hijacks

Interruption = engagement. Stop the deck. Answer. Re-enter at the nearest chapter.

He jumps to price early

“Fair — I’ll get you a number. Fastest path: pick brand foundation or presence-plus-pipeline as the first ninety days, and I’ll have a fixed proposal within forty-eight hours. Want to finish the two-minute gap so the proposal isn’t generic?”

He goes deep on software / AI

Show Creative Hub for 60–90 seconds. Then: “For Vital Wires I’d still start on brand and presence — the tools support that, they don’t replace it.”

He says “we’re fine / not a priority”

“Got it — then I won’t force it. One useful next step even if we never work together: I can do a short presence sweep — what’s working vs what’s underselling — and send you the notes. No build. Worth thirty minutes?”

He compares you to a big agency

“Big agencies sell coverage. You need coherence — one senior across brand, marketing, and the system underneath, and assets that transfer. For Vital Wires’ stage, coherence beats headcount.”

Lost the thread after a tangent

“Good — let me put that on the board. Nearest chapter for Vital Wires is still: opposite problem of Blenz, then the four stages, then where you’d want the first ninety days.”

Vital Wires cheat sheet · LoopSuit AI · #tab-vwcheat

Read once · Vivek / Vital Wires · primary + NEPQ / Nick / Alex alts

VW objections

Eight answers, once. Primary = Shree-coached / your room script. Alt = second variation from Jeremy Miner NEPQ, Nick Saraev, or Alex Hormozi — try which feels like your mouth.

8 objections Alt NEPQ · Nick · Alex +1 CMO bonus

Jeremy’s NEPQ is already in Playbook → Sales. Full ladder + word-tracks live there.

Open NEPQ in Playbook ↗

How to use Alt

Default to Primary in the room. Use Alt when Primary feels stiff, or when he pushes a second time. NEPQ = agree + questions. Nick = scope / proof / system. Alex = damaging admission first, then reframe.

Objection bank

Short → expansion → Alt. No price numbers. No “MVP.”

1. What does this cost?

Short: “Once we map the exact starting scope, I’ll put together a custom proposal and send it within forty-eight hours. Fixed scope, fixed price.”

Expansion: “Same way Vital Wires would never quote an implementation before discovery — I don’t price before scoping. What I can do right now is agree the starting stage with you, and the proposal makes it concrete: deliverables, timeline, investment.”

Shree-endorsed dodge — keep verbatim as Primary.

Alt · NEPQ (Miner) + Nick

“Yeah, that’s not a problem. I won’t invent a number in the room — same reason you don’t quote SAP before discovery.”

“If the funds weren’t the issue — which feels more useful as a first ninety days: brand foundation, or presence-plus-pipeline?”

Then: “I’ll write that as a fixed-scope proposal within forty-eight hours. You approve before anything builds.”

Mechanism: NEPQ agrees first (deflates tension), isolates value from money, then Nick’s “blame scope / pull to Map.” Still no dollar figure.

2. I already have a good website — why do I need you?

Short: “You do — and a website redesign isn’t what I’m proposing. I’m proposing your brand presence: every surface a buyer crosses before they ever meet your team.”

Expansion: “Here’s what I’d actually do first: a full sweep of your current presence — website, LinkedIn, decks, collateral — what’s working, what’s underselling the delivery. Positive and negative, shown side by side with what it should communicate. If the website turns out to be fine, it stays; the gap is usually everywhere around it — the cadence, the proof, the consistency.”

Shree coaching: analysis, positive and negative, show the impact.

Alt · NEPQ dissatisfaction-finder + Alex damaging admission

“You’re right to protect a site that works — most of what I’m talking about isn’t the homepage.”

“Quick question — is there anything you’d change about how a serious buyer experiences Vital Wires before the first call, if you could? Website, LinkedIn, capability deck, the PDF sales sends?”

Let him talk. Then: “That’s the sweep I’d do — show what’s working and what’s quietly underselling the delivery. If the site’s fine, it stays.”

3. How are you different from any other agency?

Short: “One senior brain across brand, marketing, and the software underneath — nothing gets lost in handoffs, because there are none.”

Expansion: “An agency gives you an account manager between you and the work. I design the brand, I ship the marketing, and I build the tools your team runs on — you saw Creative Hub. Seven years of product design including TD Bank’s mobile app means the digital work is production-grade, not agency-decorative. And whatever we build transfers to you — I’m the only option in the room where the tools become yours.”

“Tools become yours” means: Creative Hub–class software, brand files, guidelines — Vital Wires owns them. You’re not locked into my platform forever.
Alt · NEPQ master disarm + Nick “don’t take the bio”

“Honestly — I’m not sure we’d even be useful yet. It depends whether you need another agency layer, or one senior who designs, ships, and builds the operating system underneath.”

“Don’t take the bio. Take the surface — Creative Hub is live with a Canadian agency’s leadership every day. That’s the difference: proof you can poke, and assets that transfer.”

4. What’s the ROI? Show me results.

Short: “I’ll be straight — I won’t invent a revenue chart that says I made someone two million dollars. In B2B consulting, you usually can’t prove one campaign caused one deal — and you already know that.”

Expansion: “What I will commit to is tracking the numbers that actually move: inbound conversations, meetings booked, proposals out, pipeline sourced from this work. We look at those together every month, keep what works, drop what doesn’t. Sell exists so you can judge me on pipeline — not vibes. Create and Launch have hard outcomes too: brand shipped, site live, proof assets sales can send into every deal.”

If he follows up (“what do you mean / how do we measure?”): “Same way you’d track an SAP rollout — we pick a few leading indicators before we start, put them on a simple scoreboard, and review them on a cadence. I’m not asking you to trust a story. I’m asking you to watch the numbers with me.”
If he says “so you’re not guaranteeing ROI?”: “Correct — I won’t guarantee a dollar number in a first meeting. Anyone who does is selling theater. I guarantee the system: work that ships, presence you can see in market, and a scoreboard we both look at. If the numbers don’t move after a fair run, we don’t expand — we stop or change course.”
Alt · Alex damaging admission + NEPQ self-persuasion + Nick “system is its own proof”

“Here’s what sucks about most marketing pitches — they invent attribution. I won’t.”

“If we put a scoreboard on presence work — conversations, meetings, proposals, pipeline tagged — do you feel that’s a fair way to judge whether this is working?”

If yes: “Why do you feel like that would work for Vital Wires?” (He argues for the measurement.)

“And on pipeline ops — the lead engine you’re looking at is the same class of system I run for my own studio. Proof isn’t a case-study PDF. It’s the system.”

5. Who actually does the work? How big is your team?

Short: “It’s senior-led — I personally lead design and build on every engagement. That’s the point of hiring me.”

Expansion: “Behind me is a lean bench of specialists I bring in per engagement — content production, motion, development — depending on what the work needs. What you never get is the agency pattern: pitched by a senior, delivered by a junior. The person in this room is the person on the work.”

Alt · Alex damaging admission + brain objection-map (trust)

“Fair question — and you’re right to ask. Most shops pitch with a senior and deliver with a junior. That’s the pattern I’m not selling.”

“Don’t take my word. Take the surface — Blenz, Creative Hub, TD-grade product work. If the work on screen doesn’t match the conversation, don’t sign.”

6. Our business comes from referrals — why do we need marketing?

Short: “Referrals are proof your delivery is excellent — that’s the asset. The problem is you can’t turn a dial: every new deal still needs a warm intro, so growth stays capped by who happens to know you.”

Expansion: “And even referred buyers check you out first — they open the website and the capability deck before the call. Those surfaces don’t close deals, but they can quietly kill them, and you never hear which ones died. Marketing isn’t replacing referrals — it’s making every referral land harder, and adding a second path so you’re not only waiting for intros.”

“Nothing compounds” / “starts from zero” means: last month’s intro doesn’t automatically create next month’s pipeline. Referrals don’t stack into a machine you can turn up.
Alt · NEPQ consequence + Alex “objection is the argument for”

“Yeah, that’s not a problem — referrals are the best signal you’ve got. Delivery is clearly strong.”

“Help me understand — when you want a new vertical or a new geography, how do you turn that dial up without waiting for another intro?”

“And even warm intros due-diligence you. So the surfaces that look weak don’t replace referrals — they tax them. Fixing that is how referrals land harder.”

7. After launch, do I keep paying? What are the ongoing costs?

Short: “The tools we build are meant for your team to run without me on every click — that’s how I design them.”

Expansion: “Ongoing costs are just the tool subscriptions, listed in the scope — no surprises. If you want us on maintenance, or on Control and Sell month to month, that’s your call and priced separately. You’re never locked in — files, brand system, and any software we stand up transfer to Vital Wires.”

“Everything transfers” means: you keep the assets even if we stop working together. No hostage retainer — you’re not renting your own brand system from me.
Alt · Nick deliverable pricing / offer stack

“Think of it like a scoped build first — Create and Launch are projects with an end date and a fixed price. That’s the default.”

“Control and Sell are optional rungs after — only if the foundation is earning its keep. Separate scope, separate decision. No open-ended fog, no hostage retainer.”

8. Our team can handle this internally.

Short: “They can keep it running — that’s exactly what the Control stage sets them up to do. What they can’t do alongside delivery is the rebuild itself.”

Expansion: “A brand foundation is a project with an end date, not a task on someone’s side desk. I do the concentrated build; your team inherits a system — guidelines, templates, the review flow — that makes them faster afterward, not dependent on me.”

Alt · NEPQ + brain “hire vs ship this quarter”

“I’m not sure we’d even be needed for the ongoing — that’s the point of Control. Your team should own the run.”

“The rebuild is different. Hire or assign internally when you need a permanent seat. Right now you need a concentrated project shipped this quarter — without pulling delivery people off client work. I do the build; they inherit the system.”

Bonus · if HE names the CMO shape

“Functionally yes — the accountability of a marketing head without the org overhead. Some engagements run two or three days a week, some start with Create as a defined project — the proposal lays out the options and you pick the cadence.”

Only if he names it. Never lead with vCMO / fractional CMO.

Alt · NEPQ “feel” close

“If that’s the shape you want — does it feel more useful as a defined Create project first, or a couple of days a week on presence and pipeline? I’ll write the proposal to whichever you pick.”

Smokescreen · “send me something / I’ll think about it”

Not one of the eight — but it will happen. NEPQ loop.

Primary: “Absolutely — and so it’s useful, not generic: brand foundation or presence-plus-pipeline as the start? I’ll write to that within forty-eight hours.”

Alt · NEPQ objection loop (Miner’s best move)

“Yeah, that’s not a problem. Let’s put fifteen minutes on the calendar so you’re not chasing me and I’m not chasing you.”

Book it. Then: “Before I go — what specifically were you wanting to think through? Just so I know what questions you’ll have.”

Mechanism: Pressure drops → real objection surfaces (price, trust, partner, timing) → handle THAT one now, not in email hell.

If the room goes technical

Show Creative Hub or Franchisee Shift for 60–90 seconds. Then: “For Vital Wires, I’d still start on brand and presence — the systems support that, they don’t replace it.”

Vital Wires objections · once only · #tab-vwobj · sources: Shree room notes · Miner NEPQ (Playbook) · LoopsuitBrain Nick/Alex wiki

Copied as Markdown