The Staffmint Playbooks Staffmint · staffmint.ai
Staffmint FIELD GUIDE

The Staffmint Playbooks

12 operating sequences that chain your specialists together. Who to call, what to brief, what they hand back, and what to carry to the next desk.

01Launch
02Content
03Onboard
04Leads
05Pricing
06Funnel
07Brand
08Sales
09Email
10Churn
11YouTube
12Reset
Your specialists are hired. These are their marching orders. staffmint.ai

Read this first

How to run a playbook

A playbook is a complete operating sequence: it chains multiple specialists together, in the right order, with the right handoffs, toward one business outcome. You stop prompting one assistant at a time and start running a team the way an operator does. Each playbook tells you who to call, what to brief them, what they hand back, and what to carry to the next desk.

Run /mint first if you have not.Every playbook leans on your Business Profile so specialists never re-ask what you have already answered.
Open the playbook and follow the sequence.Each step names the specialist command, gives a delegation brief in quotes, and tells you what to carry forward. Adapt the brief to your business; the structure does the heavy lifting.
Paste the carry-forward.When a step says "carry into the next step," paste that output (or its key points) into the next specialist's brief. Handoffs are where teams win or lose.
Never skip a Vera gate.When the playbook calls /chief-of-staff, that is your manager reviewing the work before it ships. Vera catches fabricated claims, weak hooks, and drift from your offer. The gate is the difference between output and finished work.
Check "Done when."A playbook is complete when every box is checked, not when you run out of steam.

You can run playbooks back to back. A common first quarter: brand-sprint, then launch-week, then content-month, then lead-gen-sprint.

One rule above all The brief in quotes is a starting point; your specifics make it sharp. Swap in your offer, your audience, your real numbers. Specialists do excellent work with a clear brief and mediocre work with a vague one. That part of the job stays yours.

Index

The 12 playbooks

01Launch WeekAn offer launched and selling in 7 days7 days
02Content Month30 days of content from one pillar piece2 days build, 30 days run
03Client OnboardingA new client impressed by end of week 17 days
04Lead-Gen SprintA full outbound pipeline with follow-up wired5 days
05Price RaiseHigher prices, base intact2 weeks
06Funnel FixAn underperforming funnel diagnosed and repaired3 to 5 days
07Brand SprintA position you can defend in one sentence5 days
08Sales Call SystemA repeatable path from booked call to closed deal3 days build
09Newsletter EngineA weekly newsletter that sells, on rails2 days build, weekly run
10Churn RescueSlipping customers caught and won back1 week build
11YouTube EngineA channel with a system behind it1 week build, weekly run
12Quarterly ResetA 90-day plan you actually believe2 days
01Playbook 01 · 7 days

Launch Week

Outcome: An offer live and selling in 7 days: offer doc, landing page, 5-email launch sequence, and 3 ads, all reviewed before anything ships.

When to run it: You have a product, service, or idea and no launch date. Or your last launch was a soft mumble and you want this one structured.

The sequence

Day 1/offerDean, your offer specialist
The brief

"Build the offer for [product/service] at [price]. The buyer is [who] and the result it delivers is [outcome]. Give me the core promise, deliverables tied to problems, a risk reversal I can actually honor, and a real reason to act now."

Hands back

A complete offer stack plus a one-sentence version.

Carry forward

The full offer stack. Every step below builds on it.

Day 1, after Dean/customer-avatarMaya, your avatar specialist
The brief

"Here is the offer: [paste stack]. Build the avatar for the person most likely to buy this in the next 30 days. I need their exact pains in their own words, the objections they will raise, and what they have already tried."

Hands back

A buying avatar with language you can lift into copy.

Carry forward

Pains, objections, and their phrasing.

Day 2 to 3/landing-pageTessa, your landing page specialist
The brief

"Write the landing page for this offer: [paste stack]. The reader: [paste avatar pains and objections]. One CTA. Handle the top 3 objections on the page. Proof points marked [your real result] where I need to supply them."

Hands back

Full page copy, headline to CTA.

Carry forward

The headline and core promise wording, so emails and ads match the page.

Day 3VERA GATE 1/chief-of-staff
The brief

"Review this offer and landing page together. Flag any claim I cannot prove, any mismatch between promise and deliverables, and the single weakest section."

Fix what she flags before writing a word of email.

Day 4 to 5/email-marketingHana, your email specialist
The brief

"Write a 5-email launch sequence for this offer: [paste offer + page headline]. Sequence: announce, problem story, objection-crusher using [paste avatar objections], proof and urgency, last call. The 'why now' is [real reason]. No fake countdowns."

Hands back

5 emails with subject lines.

Carry forward

The strongest hook lines. Drew will want them.

Day 5 to 6/ad-copyDrew, your ad copy specialist
The brief

"Write 3 ad variations driving to this landing page: [paste headline + promise]. Audience is [cold/warm]. Use these proven hook angles from the email sequence: [paste]. Real numbers only, placeholders where I must supply proof."

Hands back

3 complete ads with a test note.

Day 6VERA GATE 2/chief-of-staff
The brief

"Final pre-launch review: landing page, 5 emails, 3 ads. Check claim integrity, voice consistency, and that every piece points at the same single promise."

Ship only what passes.

Day 7LaunchYou run this step

Page live, email 1 sent, ads submitted. Calendar the remaining 4 emails.

Done when
  • Offer stack exists with a guarantee you can honor
  • Landing page is live with one CTA and zero unproven claims
  • All 5 emails are written and scheduled
  • 3 ads are submitted with the test note saved
  • Both Vera gates passed with flags resolved

The Staffmint Playbooks01 · Launch Week

02Playbook 02 · 2 days build, 30 days run

Content Month

Outcome: 30 days of platform-ready content built from one pillar piece: a full calendar, posts adapted per platform, and captions written, in about two working days.

When to run it: You post inconsistently, or you create from scratch every day and it is eating your week. Run it once a month, first week of the month.

The sequence

Day 1, morning/social-managerHeidi, your social manager
The brief

"Build my 30-day content calendar for [month]. My business: [offer + audience, or point to Business Profile]. Platforms: [your 2-3 platforms]. One pillar theme for the month: [theme]. Mix of educate, story, proof, and ask posts. Mark which days are pillar-derived and which are native."

Hands back

A 30-day calendar with post types, themes, and platform per slot.

Carry forward

The calendar and the pillar theme.

Day 1, middayCreate or pick the pillarYou run this step

The pillar is one substantial piece: a blog post, a video script, a newsletter issue, or a talk you already gave. If you need one written, brief /blog (Beth): "Write the pillar piece for this month's theme: [theme]. Audience: [who]. 1,200-1,800 words, structured so sections can stand alone." If you have one, skip to Pia.

Day 1, afternoon/repurposingPia, your repurposing specialist
The brief

"Here is my pillar piece: [paste]. Atomize it against this calendar: [paste calendar]. For every pillar-derived slot, give me the core idea, the angle, and the format. Do not write final platform copy yet, give me the atomized briefs."

Hands back

A brief per slot, each traceable to the pillar.

Carry forward

The atomized briefs, sorted by platform.

Day 2, morningPlatform specialists

Send each platform's briefs to its specialist, one conversation each:

/linkedin (Brett)

"Turn these briefs into LinkedIn posts: [paste LinkedIn briefs]. My voice: [2-3 lines or Business Profile]. Hooks first, no hashtag walls."

/instagram (Nina)

"Turn these into Instagram content: [paste IG briefs]. Mark which should be carousels vs single posts vs Reels concepts."

/twitter (Gabe) or /short-form-video (Kai), same pattern for your remaining platform.

Hands back

Drafted posts per platform.

Carry forward

Every draft into one document, ordered by calendar date.

Day 2, afternoon/social-captionsDemi, your captions specialist
The brief

"Write captions for these video and visual posts: [paste the slots that need captions]. Front-load the keyword [your keyword], keep my voice, CTA on the proof and ask posts only."

Hands back

Finished captions.

Day 2, endVERA GATE/chief-of-staff
The brief

"Review this month of content: [paste all]. Flag any invented stat or result, any post that drifts off the pillar theme, and the 3 weakest hooks. Suggest rewrites for those 3."

Fix, then schedule everything.

Done when
  • 30-day calendar exists with every slot filled
  • Every pillar-derived post traces back to the pillar piece
  • Each platform's posts written in that platform's native format
  • Vera flagged and you fixed the 3 weakest hooks
  • Everything is scheduled, not sitting in a doc

The Staffmint Playbooks02 · Content Month

03Playbook 03 · 7 days

Client Onboarding

Outcome: A new client moved from signed contract to genuinely impressed inside week 1: welcome sequence sent, kickoff run, first visible win delivered, and the relationship on rails.

When to run it: Every time a client signs. The first 7 days set the tone for the whole engagement; winging them is how churn starts on day 1.

The sequence

Day 1/retentionPriya, your retention specialist
The brief

"A new client just signed for [service] at [price]. Design my week-1 onboarding arc: what they should receive, see, and feel on each of the first 7 days so they are confident they chose right. Include the first quick win I should aim to deliver by day 5."

Hands back

A day-by-day onboarding arc plus the quick-win target.

Carry forward

The arc. It is the spine of everything below.

Day 1/email-marketingHana, your email specialist
The brief

"Write a 3-email client welcome sequence following this arc: [paste arc]. Email 1 today: warm welcome, what happens next, what I need from them. Email 2 day 2: how we work, response times, who to contact. Email 3 day 4: progress note teeing up the first win. My voice: [Business Profile or 2 lines]."

Hands back

3 emails ready to send.

Carry forward

The "what I need from them" list into the kickoff prep.

Day 2/productivityDana, your productivity specialist
The brief

"Turn this onboarding arc into a reusable SOP and checklist: [paste arc]. Include the kickoff call agenda, the intake items I collect, internal setup steps, and the day-5 quick-win delivery step. I want to run this same checklist for every future client."

Hands back

An onboarding SOP plus kickoff agenda.

Carry forward

The kickoff agenda to the call. Save the SOP; it is the permanent asset this playbook leaves behind.

Day 2 to 3Run the kickoff callYou run this step

Use Dana's agenda. Confirm scope, success metric, communication rhythm, and the date they will see the first win. Send a same-day recap email (Hana's email 2 structure works as the base).

Day 4 to 5Deliver the quick winYou run this step

Ship the small, visible result Priya targeted: an audit, a first draft, a fixed page, a setup completed. Small and done beats big and pending.

Day 5VERA GATE/chief-of-staff
The brief

"Review my quick-win deliverable and the note announcing it: [paste]. Is the result framed honestly, is the value obvious to a non-expert, and does it set up the next milestone?"

Fix flags, then deliver with Hana's email 3.

Day 7Close the loopYou run this step

Short check-in: one question, "On a scale of 1-10, how is the start? What would make it a 10?" Log the answer in Dana's SOP for the next client.

Done when
  • All 3 welcome emails sent on schedule
  • Kickoff call run from the agenda, recap sent same day
  • Quick win delivered by day 5 and acknowledged by the client
  • Onboarding SOP saved and ready to reuse on the next signing
  • Day-7 check-in answered and logged

The Staffmint Playbooks03 · Client Onboarding

04Playbook 04 · 5 days

Lead-Gen Sprint

Outcome: A working outbound pipeline in 5 days: a sharp target list definition, a cold email sequence, a LinkedIn touch plan, and follow-up wired so no reply dies in your inbox.

When to run it: The pipeline is thin and you have been "meaning to do outreach" for weeks. Also run it before any slow season you can see coming.

The sequence

Day 1/customer-avatarMaya, your avatar specialist
The brief

"Build the outbound avatar for [offer] at [price]. I need: the exact title or business type to target, the trigger events that make them buyable this month (hiring, launching, complaining publicly), the pain they would say out loud, and 3 disqualifiers so I stop emailing people who will never buy."

Hands back

A targeting spec with triggers and disqualifiers.

Carry forward

The pain language and triggers. They are the raw material for every message.

Day 1, afternoonBuild the listYou run this step

Using Maya's spec, pull [your target number, 50-200] prospects from wherever your market lives. Every record needs name, company, and one line of evidence they match a trigger. No evidence, no list spot.

Day 2/cold-emailJoel, your cold email specialist
The brief

"Write a 4-touch cold email sequence for this avatar: [paste spec]. Touch 1 leads with their trigger, not my offer. Touch 2 adds a proof point [your real result] or a useful observation. Touch 3 is a short angle change. Touch 4 is a polite close-the-file. Under 100 words each, one clear ask: [your CTA, e.g. a 15-minute call]."

Hands back

4 emails with subject lines and send spacing.

Carry forward

The touch-1 angle. Brett mirrors it on LinkedIn.

Day 3/linkedinBrett, your LinkedIn specialist
The brief

"Design a LinkedIn touch plan that runs parallel to this cold email sequence: [paste touch 1]. Connection note under 200 characters, a no-pitch first message, and one comment strategy on the prospect's content. The email and LinkedIn touches must feel like one coherent person, not two campaigns."

Hands back

Connection note, message scripts, comment guidance.

Day 3VERA GATE/chief-of-staff
The brief

"Review this outbound system: [paste emails + LinkedIn scripts]. Flag anything that sounds like a mass blast, any claim without proof behind it, and any touch that asks too much too early."

Fix before a single send.

Day 4/crm-followupTom, your follow-up specialist
The brief

"Wire the follow-up logic for this outbound campaign: [paste sequence summary]. Give me the pipeline stages, what happens on positive reply, neutral reply, objection, and silence, and the reply templates for each. Include the rule for when a lead goes to nurture instead of dead."

Hands back

Stage definitions and reply playbook.

Day 4 to 5LaunchYou run this step

Start sends in daily batches of [your batch size]. Log every reply against Tom's stages from day one, not "later."

Done when
  • List built with trigger evidence on every record
  • 4-touch email sequence and LinkedIn plan live and coherent
  • Vera gate passed, mass-blast smell removed
  • Every reply type has a scripted next move
  • First batches sent and logged in the pipeline

The Staffmint Playbooks04 · Lead-Gen Sprint

05Playbook 05 · 2 weeks

Price Raise

Outcome: New, higher prices in force, existing customers handled with respect, and a script for every pushback. Run over 2 weeks so nobody feels ambushed.

When to run it: You have not raised prices in a year or more, you are at capacity, or every prospect says yes too fast. All three mean you are underpriced.

The sequence

Day 1 to 2/pricingWalt, your pricing specialist
The brief

"I charge [current price] for [offer]. Costs: [your numbers]. Close rate: [your number, or 'roughly X of Y proposals']. Capacity: [hours or client slots]. Build the case for a raise: the new price you recommend, the math behind it, how to handle existing customers (grandfather, delayed raise, or migrate), and the revenue impact if I lose [10/20/30] percent of the base."

Hands back

A recommended price with scenarios and an existing-customer policy.

Carry forward

The new price, the policy, and the value justification.

Day 3/objection-handlingLara, your objections specialist
The brief

"I am raising [offer] from [old] to [new] on [date]. Existing customers get [policy]. Script my responses to: 'why the increase,' 'I can't afford this,' 'competitor X is cheaper,' 'can I lock in the old rate,' and 'I'm leaving.' Calm and firm. I want to keep the relationship without negotiating against myself."

Hands back

A response script per objection, plus the one concession you are allowed to make and the line you never cross.

Carry forward

The scripts. Keep them open during every conversation for the next month.

Day 4 to 5/email-marketingHana, your email specialist
The brief

"Write the price-change announcement for existing customers. New price [new] effective [date, at least 30 days out]. Their treatment: [policy]. Lead with the value they have received and what is coming, state the change plainly in one sentence, no apologizing, no over-explaining. Then a second short email for day [date minus 7] as a reminder with the same calm tone."

Hands back

Announcement plus reminder email.

Day 5VERA GATE/chief-of-staff
The brief

"Review this price raise package: announcement, reminder, objection scripts: [paste]. Flag anywhere I sound apologetic, anywhere the value claim is unproven, and any objection response that gives away the raise."

This gate matters more than usual: one weak sentence in a price email costs real money.

Day 6Update everything that shows a priceYou run this step

Website, proposals, checkout, contracts. The announcement and your assets must never disagree.

Week 2Send and holdYou run this step

Send the announcement. Respond to every reply within a day using Lara's scripts. Track who pushes back and on what; if the same objection appears [3+] times, take it back to Lara for a sharpened response, not back to Walt for a discount.

Done when
  • New price set with the math documented
  • Existing-customer policy decided and stated in writing
  • Announcement and reminder sent on schedule
  • Every pushback answered from a script, not improvised
  • All public prices updated, nothing contradicts the announcement

The Staffmint Playbooks05 · Price Raise

06Playbook 06 · 3 to 5 days

Funnel Fix

Outcome: An underperforming funnel diagnosed, the real leak named, and the broken stage rebuilt, in 3 to 5 days.

When to run it: Traffic arrives but money does not. Before you buy more ads, run this. More traffic into a leaking funnel just buys you a faster leak.

The sequence

Day 1Gather the numbersYou run this step

Before any specialist, collect what you have for the last 30-90 days: visitors, opt-ins or leads, sales calls or checkouts started, purchases. Rough is fine; "I don't track that" is itself a finding. No specialist can diagnose a funnel from adjectives.

Day 1 to 2/funnel-strategyDiane, your funnel specialist
The brief

"Diagnose this funnel. Offer: [offer + price]. Traffic source: [where visitors come from and how warm]. Numbers: [paste what you gathered]. Walk the stages, tell me where the biggest drop is, whether the problem is traffic-to-page mismatch, page, offer, or follow-up, and which ONE stage to fix first. I want a diagnosis, not a redesign."

Hands back

A stage-by-stage read with the primary leak named and a fix priority.

Carry forward

The named leak. The rest of the playbook attacks that one stage. Resist fixing everything.

Day 2 to 3Rebuild the broken stage

Route by Diane's diagnosis:

Leak at the page (people land, nobody acts): /landing-page (Tessa)

"This page is converting at [rate or 'poorly']. Diane's diagnosis: [paste]. Rewrite it for [audience temperature]. One CTA, objections handled on-page, proof marked [your real result] where I must supply it."

Leak at attention (they do not even read): /headlines (Roy)

"The headline and opening of this page are losing [cold/warm] traffic from [source]. Diagnosis: [paste]. Give me 5 headline and lead options matched to that awareness level, different angles, not rewordings."

Leak at the offer itself (they read everything and still leave):

That is not a copy problem. Take it to /offer (Dean) before touching another word of copy.

Leak after opt-in (leads go cold): /email-marketing (Hana) for the follow-up sequence, same diagnosis-first brief.

Hands back

The rebuilt stage.

Carry forward

Old version plus new version, side by side, into the gate.

Day 4VERA GATE/chief-of-staff
The brief

"Here is the funnel diagnosis: [paste Diane]. Here is the old stage and the rebuild: [paste both]. Does the rebuild actually address the diagnosed leak, or does it just sound better? Flag claims without proof and any new mismatch with the traffic source."

Ship only if the fix matches the diagnosis.

Day 4 to 5Ship and instrumentYou run this step

Publish the rebuilt stage. Write down the one number that should move and where it stands today, so in 2 weeks the verdict is data, not vibes. If you can split-test, test against the old version rather than replacing it blind.

Done when
  • Funnel numbers gathered, gaps in tracking noted
  • One primary leak named in writing
  • Only that stage rebuilt, by the right specialist
  • Vera confirmed the fix matches the diagnosis
  • Baseline number recorded with a 2-week review date set

The Staffmint Playbooks06 · Funnel Fix

07Playbook 07 · 5 days

Brand Sprint

Outcome: A position you can state in one sentence, defend against competitors, and apply to every asset: positioning statement, name and tagline decisions, and a messaging hierarchy, in 5 days.

When to run it: You hesitate when someone asks "so what do you do?" Or your marketing says five different things in five places. Or you are entering a new market or repositioning an old offer.

The sequence

Day 1/competitor-analysisReid, your competitive intel specialist
The brief

"Map the competitive field for [your category] serving [your market]. My top [3-5] competitors: [names, or 'find them']. For each: their core promise, who they target, their price posture, and the angle they own. Then tell me the gaps: which positions are crowded and which are unclaimed."

Hands back

A competitive map with claimed and unclaimed territory.

Carry forward

The unclaimed positions. You are choosing from these, not inventing in a vacuum.

Day 2/customer-avatarMaya, your avatar specialist
The brief

"Here is the competitive territory available: [paste gaps]. Build the avatar for [your market] and tell me which of these unclaimed positions they actually care about. What do they believe about the existing options, what disappointed them, and what would make them switch?"

Hands back

An avatar with a verdict on which gap has buyer pull.

Carry forward

The gap with real demand behind it, plus the avatar's language.

Day 3/brand-strategyEsme, your brand strategist
The brief

"Build my positioning. The territory: [paste the chosen gap]. The buyer: [paste avatar verdict]. My genuine strengths: [your honest list, with evidence]. Give me: a one-sentence positioning statement (for WHO, we are the WHAT that WHY-US), the 3 messages that support it, the 3 things we deliberately do not claim, and how this changes my current materials."

Hands back

Positioning statement, messaging hierarchy, and a do-not-claim list.

Carry forward

The positioning statement, word for word.

Day 4/namingWynn, your naming specialist
The brief

"Position: [paste statement]. Pressure-test my current name and tagline against it: [current name/tagline]. If they hold, say so and give me 5 tagline options sharpened to the new position. If they fight the position, tell me plainly and propose alternatives."

Hands back

Keep-or-change verdict plus tagline options.

Day 5VERA GATE/chief-of-staff
The brief

"Review this brand sprint output: competitive map, avatar verdict, positioning, naming: [paste]. Three checks: is the position actually different from the competitors Reid mapped, can I defend every claim in it with evidence, and would Maya's avatar recognize themselves in it? Flag anything aspirational that I cannot back today."

Day 5, after the gateWrite the one-pagerYou run this step

Condense to a single page: positioning statement, 3 support messages, do-not-claim list, tagline. This page now rules every future brief you give any specialist. Add it to your Business Profile so the whole roster inherits it.

Done when
  • Competitive map shows where you do and do not fit
  • Position chosen from a gap with confirmed buyer pull
  • One-sentence positioning statement passed the Vera gate
  • Name and tagline verdict made, not deferred
  • One-pager saved and added to the Business Profile

The Staffmint Playbooks07 · Brand Sprint

08Playbook 08 · 3 days build

Sales Call System

Outcome: A repeatable path from booked call to closed deal: call structure, objection scripts, a same-day proposal template, and follow-up rules. Build it in 3 days, then run it on every call.

When to run it: Calls happen but deals do not, every call is improvised, or proposals go out days late and die in silence.

The sequence

Day 1/sales-closerMarcus, your sales specialist
The brief

"Build my sales call structure for [offer] at [price] sold to [who]. Calls run [length]. Give me: the opening that sets the frame, the discovery questions that surface pain and budget without interrogating, the transition from discovery to pitch, how to present the price, and the close that asks for a decision on the call. My style leans [consultative/direct]."

Hands back

A call script with the key questions and exact transition lines.

Carry forward

The discovery questions and the close. Lara scripts what happens when the close meets resistance.

Day 1, afternoon/objection-handlingLara, your objections specialist
The brief

"Here is my call structure and close: [paste]. Script my live responses to the objections I actually hear: [your real top 3, e.g. 'too expensive,' 'need to think about it,' 'need to ask my partner'], plus 'send me a proposal' used as a dodge. For each: acknowledge, reframe, question that re-opens the conversation. Also give me the walk-away criteria so I stop chasing dead deals."

Hands back

Objection scripts plus disqualification rules.

Carry forward

The "send me a proposal" handling into Erin's brief.

Day 2/proposalsErin, your proposals specialist
The brief

"Build my proposal template for [offer]. It must be sendable within [4 hours/same day] of a call. Structure: their situation in their words, the outcome we agreed matters, the plan, the investment stated plainly, one expiry date with a real reason, and a single next step. Short enough to read in 5 minutes. Mark the sections I personalize per deal."

Hands back

A fill-in proposal template.

Carry forward

The template and its expiry logic into Tom's follow-up rules.

Day 2VERA GATE/chief-of-staff
The brief

"Review my sales system: call script, objection scripts, proposal template: [paste]. Flag anything that sounds like pressure instead of confidence, any promise the delivery cannot keep, and any gap between what the call sells and what the proposal says."

Fix before the next booked call.

Day 3/crm-followupTom, your follow-up specialist
The brief

"Wire follow-up for this sales process: [paste summary + proposal expiry logic]. Define stages from booked call to closed. Give me the follow-up cadence after a proposal goes out (day 1, 3, expiry-minus-1), the template for each touch, and the rule for moving a deal to closed-lost and into nurture instead of letting it rot in 'pending'."

Hands back

Stages, cadence, and templates.

OngoingRun and refineYou run this step

After every [5] calls, take notes back to Marcus: "Here is where calls stalled: [notes]. Tighten the script." The system improves on cadence, not on memory.

Done when
  • Call script exists and you have run at least one call on it
  • Your top 3 real objections have scripted responses
  • Proposal template fires same-day after a call
  • Follow-up cadence runs without you remembering it
  • Vera gate passed: no pressure tactics, no undeliverable promises

The Staffmint Playbooks08 · Sales Call System

09Playbook 09 · 2 days build, weekly run

Newsletter Engine

Outcome: A weekly newsletter that people open and that quietly sells: format locked, first issue written, subject-line system in place, and a repurposing loop so each issue feeds your social channels. 2 days to build, then a weekly rhythm.

When to run it: You have an email list doing nothing, or you keep "meaning to start a newsletter" and stall on format. This playbook removes the blank page permanently.

The sequence

Day 1/newsletterMargot, your newsletter specialist
The brief

"Design my weekly newsletter. Audience: [who, or Business Profile]. My business: [offer]. Goal: stay top of mind and generate [replies/calls/sales] without being a weekly pitch. Give me: the format (named sections I repeat every issue), ideal length, the sell-to-value ratio, and the standing CTA approach. Then write issue 1 in full on this topic: [your first topic]."

Hands back

A locked format plus a complete first issue.

Carry forward

The format doc. Every future issue is briefed against it, which is why issue 30 takes an hour instead of a day.

Day 1, afternoon/headlinesRoy, your headlines specialist
The brief

"Here is issue 1 of my newsletter: [paste]. Give me 7 subject line options across different patterns: curiosity, specific benefit, contrarian, story-open. Then give me a reusable subject-line checklist for future issues: what my list responds to is [open] until I have data, so include what to test first."

Hands back

Subject options plus a testing checklist.

Carry forward

The checklist into your weekly routine.

Day 2VERA GATE/chief-of-staff
The brief

"Review my newsletter format and issue 1: [paste]. Three checks: would [my audience] genuinely forward this, is the selling light enough to sustain weekly trust, and are all claims and examples real or clearly marked for my proof? Flag the weakest section of the format itself, not just this issue."

Fix, then send issue 1 to the list.

Day 2, afternoon/repurposingPia, your repurposing specialist
The brief

"Here is my newsletter format and issue 1: [paste]. Design the standing repurposing loop: each week, which sections become a LinkedIn post, a thread, or a short-form script, and in what form. Make it a checklist I run every week after sending, then demonstrate it on issue 1."

Hands back

A weekly repurposing checklist plus issue 1 atomized.

Weekly rhythmAbout 90 minutesYou run this step
  1. Brief Margot: "Issue [n], format as locked. Topic: [topic]. This week's example or story: [yours]." She writes against the locked format.
  2. Run Roy's subject checklist, pick one, note the variant you would have tested.
  3. Quick Vera pass on any issue containing claims, numbers, or a harder sell.
  4. Send, then run Pia's repurposing checklist.

Every [8] issues, take open and reply data back to Margot and Roy: "Here is what performed: [your numbers]. Adjust the format and subject patterns."

Done when
  • Format locked with named, repeating sections
  • Issue 1 sent with a deliberately chosen subject line
  • Weekly repurposing checklist exists and ran on issue 1
  • The 90-minute weekly rhythm is on your calendar
  • Review point set after issue [8] with real numbers

The Staffmint Playbooks09 · Newsletter Engine

10Playbook 10 · 1 week build

Churn Rescue

Outcome: A working retention system in one week: early-warning signals defined, a save process for at-risk customers, a win-back sequence for the already-gone, and cancellation handling that keeps the door open.

When to run it: Cancellations are climbing, customers go quiet before they leave, or you only find out someone churned when the payment fails. Keeping a customer is cheaper than replacing one; this playbook is usually worth more than a new lead campaign.

The sequence

Day 1 to 2/retentionPriya, your retention specialist
The brief

"Build my churn early-warning and save system. My product/service: [offer] at [price], billed [cycle]. Customers typically leave because: [your honest top reasons, or 'unknown']. Give me: the 3-5 warning signals I can actually observe (usage drop, slower replies, missed sessions, support tone), the intervention for each signal, and the save offer ladder for someone who says they want to leave: what I offer first, second, and what I never offer."

Hands back

Signal definitions, interventions, and a save ladder.

Carry forward

The signals list and the save ladder. They drive both scripts below.

Day 2 to 3/customer-serviceRosa, your customer service specialist
The brief

"Here are my churn signals and save ladder: [paste]. Script the conversations: the check-in message for each warning signal (caring, not desperate, no discount in the first touch), the response when someone asks to cancel (one genuine attempt to understand and save, then graceful acceptance), and the goodbye message that leaves the door open. My voice: [Business Profile or 2 lines]."

Hands back

A script per signal plus the cancellation conversation flow.

Carry forward

The goodbye framing into the win-back sequence.

Day 3 to 4/email-marketingHana, your email specialist
The brief

"Write a 3-email win-back sequence for customers who left [30-90] days ago. They left because: [paste top reasons]. Email 1: honest check-in, what has improved since they left, no pitch. Email 2: a specific reason to return tied to their original goal, with [your real improvement or change] as the hook. Email 3: a simple return offer [your win-back offer from Priya's ladder] with a clean expiry. Respect their decision throughout; nobody returns to a guilt trip."

Hands back

A 3-email win-back sequence.

Day 4VERA GATE/chief-of-staff
The brief

"Review my full churn system: signals, save scripts, cancellation flow, win-back emails: [paste]. Flag anything that sounds desperate or manipulative, any promised improvement that has not actually shipped, and any save offer that trains customers to threaten cancellation for discounts."

That last failure mode quietly destroys margins; take the flag seriously.

Day 5Wire it and run the backlogYou run this step
  1. Put the signal checks on a recurring slot (weekly for most businesses).
  2. List every customer currently showing a warning signal and send Rosa's check-in to each, personalized.
  3. List everyone who churned in the last [90] days and start Hana's sequence for the ones you would genuinely want back.
Done when
  • Warning signals defined and on a recurring weekly check
  • Every currently at-risk customer has received a check-in
  • Cancellation conversation flow exists, including the graceful goodbye
  • Win-back sequence launched to the recent-churn list
  • Vera confirmed nothing in the system trains discount-threats

The Staffmint Playbooks10 · Churn Rescue

11Playbook 11 · 1 week build, weekly run

YouTube Engine

Outcome: A channel with a system behind it: positioning and content lanes defined, first 4 videos planned with titles and outlines, a Shorts pipeline from every long video, and search-informed topics. One week to build, then a weekly production rhythm.

When to run it: You are starting a channel, or you have one that posts randomly and grows accordingly. Run the build once; the rhythm carries it from there.

The sequence

Day 1 to 2/youtubeTalia, your YouTube strategist
The brief

"Build my YouTube strategy. Business: [offer + who it serves]. Goal: [subscribers as pipeline / authority / direct sales]. I can realistically produce [1] video per week at [length]. Give me: the channel positioning in one sentence, 3 content lanes (the repeatable formats I rotate), who the viewer is at minute zero, and the first 4 videos: working title, hook for the first 30 seconds, and a bullet outline each."

Hands back

Channel strategy plus 4 planned videos.

Carry forward

The 4 titles and outlines. SEO checks them before you record.

Day 2/seoNoor, your SEO specialist
The brief

"Here are my first 4 YouTube videos: [paste titles + outlines]. Check search demand: for each, what are people actually typing around this topic, which title wording matches real queries, and is there a higher-demand angle I am missing? Give me revised titles where the data disagrees with the draft, plus description keywords per video."

Hands back

Search-validated titles and description keywords.

Carry forward

Final titles into production; keywords into upload day.

Day 3VERA GATE/chief-of-staff
The brief

"Review my channel strategy and first 4 videos: [paste]. Three checks: does every video serve the channel's one-sentence positioning, will the first 30 seconds of each actually hold a cold viewer, and is the production load honest for my capacity of [your capacity]? Flag the weakest hook of the four."

Fix the weak hook before recording anything.

Day 4 to 5Record video 1, then/short-form-videoKai, your short-form specialist

Record video 1 from the outline. Then brief Kai:

The brief

"Here is the script/outline of my long video: [paste]. Pull 3 Shorts from it: the strongest standalone moment, the sharpest contrarian or surprising claim, and a how-to fragment. For each: hook line, beat-by-beat script under 45 seconds, and the on-screen text."

Hands back

3 Shorts scripts per long video.

Carry forward

This becomes a standing step: every long video ships with 3 Shorts.

Day 5/repurposingPia, your repurposing specialist
The brief

"Design my weekly YouTube repurposing loop: each long video should also become [LinkedIn post / newsletter section / thread, pick yours]. Give me the checklist I run after every upload, then demonstrate it on video 1."

Hands back

A post-upload checklist.

Weekly rhythmThe production loopYou run this step
  1. Talia: "Next video in lane [n]. Topic: [topic]. Title, hook, outline."
  2. Noor checks the title against search.
  3. Record and upload with Noor's keywords.
  4. Kai cuts 3 Shorts.
  5. Run Pia's checklist.

Every [8] videos, bring Talia your retention and click-through numbers: "Here is what the data says: [your numbers]. Adjust the lanes."

Done when
  • Channel positioning fits in one sentence
  • 4 videos planned with search-validated titles
  • Video 1 published with 3 Shorts cut from it
  • Post-upload repurposing checklist exists and ran once
  • Review point set at video [8] with real channel data

The Staffmint Playbooks11 · YouTube Engine

12Playbook 12 · 2 days

Quarterly Reset

Outcome: A 90-day plan you actually believe: last quarter honestly reviewed, the market re-checked, the one or two real strategic decisions made deliberately, and the quarter translated into a weekly operating rhythm. Two days, four specialists.

When to run it: The last two weeks of every quarter. Also after any shock that invalidates the current plan: a big client lost, a launch that flopped, an opportunity that changes the math.

The sequence

Day 1, morningGather the quarter's truthYou run this step

Thirty minutes, before any specialist: revenue vs plan, what shipped vs what was promised, where your time actually went, and the one thing you kept avoiding. Honest and rough beats polished and flattering.

Day 1, morning/business-strategyVivian, your strategy specialist
The brief

"Quarterly review. The plan was: [last quarter's goals]. What happened: [paste your numbers and notes]. Diagnose: what worked and should get more resources, what failed and why (bad bet vs bad execution, be specific), and what I am avoiding that is quietly the real problem. Then give me the 2-3 candidate priorities for next quarter, with the case for each. Do not pick yet."

Hands back

An honest diagnosis plus candidate priorities with trade-offs.

Carry forward

The candidates. Farah checks them against the outside world before anything is chosen.

Day 1, afternoon/market-researchFarah, your market research specialist
The brief

"Here are my candidate priorities for next quarter: [paste]. Check each against the market: has demand shifted for [your offer category], what are competitors doing that changes the calculus, and is there a trend that makes any candidate more or less urgent? Tell me which candidates the market supports and which it undercuts. Pull live data where you can."

Hands back

A market read per candidate.

Carry forward

Candidates plus market verdicts into the decision.

Day 2, morning/decision-advisorVance, your decision specialist
The brief

"Help me commit. Candidates and market verdicts: [paste]. Constraints: [your real capacity, cash runway, energy]. Pressure-test each: what has to be true for it to work, what I am giving up by choosing it, and which failure would hurt most. Then force the call: ONE primary priority for the quarter, at most one secondary, and the explicit not-doing list. Push back if I try to keep three."

Hands back

The decision, the not-doing list, and the reasoning on record.

Carry forward

The chosen priority into execution planning.

Day 2, afternoon/productivityDana, your productivity specialist
The brief

"Turn this quarter's priority into an operating rhythm: [paste decision]. Break it into [3] monthly milestones, then the weekly actions that compound toward each. Design my weekly review: the 20-minute Friday check of what moved, what stalled, and next week's three actions. Make the plan survive a bad week without collapsing."

Hands back

Milestones, weekly cadence, and the review ritual.

Day 2, endVERA GATE/chief-of-staff
The brief

"Review my quarterly plan: diagnosis, decision, not-doing list, operating rhythm: [paste]. Three checks: does the plan attack what Vivian diagnosed or quietly dodge it, is the load honest for one person, and is the not-doing list real (things I was actually tempted to do)? Flag wishful thinking line by line."

Done when
  • Last quarter reviewed with real numbers, including the avoided thing
  • One primary priority chosen, reasoning written down
  • Not-doing list exists and contains at least [3] tempting items
  • Weekly rhythm and Friday review on the calendar for all 13 weeks
  • Vera gate passed with wishful-thinking flags resolved

The Staffmint Playbooks12 · Quarterly Reset

Staffmint

Run a team, not a chat.

Your specialists are hired. These were their marching orders.

Staffmint · staffmint.ai