FIELD GUIDE
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.
Read this first
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.
/mint first.Your specialists read your Business Profile, so they already know your business, your audience, and your voice. They never re-ask what it already answers./mint and all your playbooks in one Cowork Project folder. That folder is where your team keeps its memory of you, so every specialist already knows your business, even in a brand new chat. You never paste work between steps./chief-of-staff, that is Vera reviewing several pieces together before they ship. Never skip it.You can run playbooks back to back. A common first quarter: brand-sprint, then launch-week, then content-month, then lead-gen-sprint.
Index
Outcome: An offer live and selling in 7 days: offer, 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.
Run this playbook inside your one Staffmint Project folder, so every specialist already knows your business. A new chat is fine; just stay in the folder. If a specialist needs a specific input, it asks.
"Maya, build the avatar for my launch: the person most likely to buy what I am launching in the next 30 days."
The buyer's real pains, the objections they will raise, and what they have already tried, in their own words. Maya reads your profile; if you run more than one offer, she asks which one this launch is for.
"Dean, build the offer for my launch, for the buyer Maya just mapped."
A complete offer stack plus a one-sentence version, with a core promise and risk reversal shaped by the avatar's real pains and objections. If Dean needs your price or date, he asks.
"Tessa, write the landing page for the offer we just built and the avatar Maya just mapped."
Full page copy, one CTA, the avatar's top objections handled. She uses your real proof where you have it, and sells on the mechanism and your guarantee where you do not.
"Vera, review the offer and landing page together: any claim I cannot prove, any gap between the promise and what is delivered, and the single weakest section."
Your specialists already proof their own work. This gate is the bigger cross-check. Fix what she flags before any email.
"Hana, write the 5-email launch sequence for this offer and page: announce, problem story, objection-crusher, proof and urgency, last call."
5 emails with subject lines. She uses Maya's objections and your real why-now; tell her your date if you have one. No fake countdowns.
"Drew, write 3 ads driving to this page." Tell him cold or warm audience.
3 ads with a test note. He pulls the strongest hooks from Hana's emails. Real numbers only; with no proof yet he leads on the mechanism and the promise.
"Vera, final review: landing page, 5 emails, and 3 ads together. Claim integrity, one consistent voice, and every piece pointing at the same promise."
Ship only what passes.
Page live, email 1 sent, ads submitted. Calendar the remaining 4 emails.
The Staffmint Playbooks01 · Launch Week
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.
Run this playbook inside your one Staffmint Project folder, so every specialist already knows your business. A new chat is fine; just stay in the folder. If a specialist needs a specific input, it asks.
"Heidi, build my 30-day content calendar for this month. Mix of educate, story, proof, and ask posts. Mark which days are pillar-derived and which are native."
A 30-day calendar with post types, themes, and platform per slot. Heidi reads your profile for your business and platforms. If she needs this month's pillar theme or which platforms to focus on, she asks, and you answer in a line.
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, say to /blog (Beth): "Beth, write the pillar piece for this month's theme, structured so sections can stand alone, 1,200 to 1,800 words." She reads your profile for theme and audience and asks if either is unclear. If you already have a pillar, drop it in the folder and skip to Pia.
"Pia, atomize the pillar piece against the calendar Heidi just built. For every pillar-derived slot, give me the core idea, the angle, and the format. Atomized briefs only, not final platform copy yet."
A brief per slot, each traceable to the pillar, sorted by platform.
Hand each platform's briefs to its specialist, one conversation each. They pull your voice from the profile:
/linkedin (Brett)
"Brett, turn Pia's LinkedIn briefs into posts. Hooks first, no hashtag walls."
/instagram (Nina)
"Nina, turn Pia's Instagram briefs into content. Mark which should be carousels vs single posts vs Reels concepts."
/twitter (Gabe) or /short-form-video (Kai), same pattern for your remaining platform.
Drafted posts per platform, in your voice. Each leans on your real proof where you have it, and sells on the specifics where you do not, never an invented result.
"Demi, write captions for the video and visual posts. Front-load my keyword, keep my voice, and put a CTA on the proof and ask posts only."
Finished captions. If she needs the keyword to front-load, she asks, and you answer in a line.
"Vera, review this month of content together: any invented stat or result, any post that drifts off the pillar theme, and the 3 weakest hooks. Suggest rewrites for those 3."
Your specialists already proof their own posts. This gate is the bigger cross-check across the whole month. Fix what she flags, then schedule everything.
The Staffmint Playbooks02 · Content Month
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.
Run this playbook inside your one Staffmint Project folder, so every specialist already knows your business. A new chat is fine; just stay in the folder. If a specialist needs a specific input, it asks.
"Priya, a client just signed. 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, and the first quick win I should aim to deliver by day 5."
A day-by-day onboarding arc plus the quick-win target. Priya reads your profile and builds it. If she needs which service they bought or the price, she asks, and you answer in a line.
"Hana, write the 3-email client welcome sequence following the arc Priya just built. 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."
3 emails in your voice, ready to send, with the "what I need from them" list ready for the kickoff. She writes from your real way of working, not invented promises.
"Dana, turn Priya's onboarding arc into a reusable SOP and checklist: 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."
An onboarding SOP plus kickoff agenda. Save the SOP; it is the permanent asset this playbook leaves behind, and the kickoff agenda feeds the call below.
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).
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.
"Vera, review my quick-win deliverable and the note announcing it: is the result framed honestly, is the value obvious to a non-expert, and does it set up the next milestone?"
Your specialists already proof their own work. This gate is the deliberate cross-check before the client sees it: she confirms the win is framed honestly, with no result overstated. Fix flags, then deliver with Hana's email 3.
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.
The Staffmint Playbooks03 · Client Onboarding
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.
Run this playbook inside your one Staffmint Project folder, so every specialist already knows your business. A new chat is fine; just stay in the folder. If a specialist needs a specific input, it asks.
"Maya, build the outbound avatar for my offer: the exact title or business type to target, the trigger events that make them buyable this month like hiring, launching, or complaining publicly, the pain they would say out loud, and 3 disqualifiers so I stop emailing people who will never buy."
A targeting spec with triggers and disqualifiers, in the buyer's own words, ready to feed every message. Maya reads your profile and builds it. Run more than one offer, or she needs your price? She asks, and you answer in a line.
Using Maya's spec, pull 50 to 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.
"Joel, write a 4-touch cold email sequence for the avatar Maya just mapped. Touch 1 leads with their trigger, not my offer. Touch 2 adds a proof point 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."
4 emails with subject lines and send spacing, the touch-1 angle ready for Brett to mirror on LinkedIn. Joel uses your real proof where you have it, and leads on the trigger, the mechanism, and your specifics where you do not. If he needs your one ask, like a 15-minute call, he asks.
"Brett, design a LinkedIn touch plan that runs parallel to the cold email sequence Joel just wrote, mirroring his touch-1 angle. 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."
Connection note, message scripts, comment guidance, all in one voice with Joel's emails.
"Vera, review the outbound system together: the cold emails and the 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."
Your specialists already proof their own work. This gate is the bigger cross-check across email and LinkedIn. Fix what she flags before a single send.
"Tom, wire the follow-up logic for this outbound campaign. 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."
Stage definitions and a reply playbook keyed to Joel's sequence.
Start sends in daily batches you can keep up with. Log every reply against Tom's stages from day one, not "later."
The Staffmint Playbooks04 · Lead-Gen Sprint
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.
Run this playbook inside your one Staffmint Project folder, so every specialist already knows your business. A new chat is fine; just stay in the folder. If a specialist needs a specific input, it asks.
"Walt, build the case for raising my prices: the new price you recommend, the math behind it, how to handle existing customers, and the revenue impact if I lose part of the base."
A recommended price with scenarios and an existing-customer policy. Walt reads your profile and builds it. If he needs your current price, costs, close rate, or capacity, he asks, and you answer in a line.
"Lara, script my responses for the raise Walt just laid out: '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."
A response script per objection, plus the one concession you are allowed to make and the line you never cross. Keep these open during every pricing conversation for the next month.
"Hana, write the price-change announcement for existing customers using Walt's new price and 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 short reminder email for a week before it takes effect, same calm tone."
Announcement plus reminder email. She leans on the value your customers have actually received; tell her your effective date, at least 30 days out, if she does not have it. No invented results.
"Vera, review the price raise package together: announcement, reminder, and objection scripts. Flag anywhere I sound apologetic, anywhere the value claim is unproven, and any objection response that gives away the raise."
Your specialists already proof their own work. This gate is the deeper cross-asset check, and it matters more than usual: one weak sentence in a price email costs real money.
Website, proposals, checkout, contracts. The announcement and your assets must never disagree.
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 keeps appearing, take it back to Lara for a sharpened response, not back to Walt for a discount.
The Staffmint Playbooks05 · Price Raise
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.
Run this playbook inside your one Staffmint Project folder, so every specialist already knows your business. A new chat is fine; just stay in the folder. If a specialist needs a specific input, it asks.
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.
"Diane, diagnose my funnel. Here are the numbers I 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."
A stage-by-stage read with the primary leak named and a fix priority. Diane reads your offer and traffic source from your profile; she only asks where a number is missing. The rest of the playbook attacks that one named leak, so resist fixing everything.
Route by Diane's diagnosis:
Leak at the page (people land, nobody acts): /landing-page (Tessa)
"Tessa, rewrite this page for the leak Diane just diagnosed. One CTA, the avatar's objections handled on-page. Use my real proof where I have it, sell on the mechanism and my guarantee where I do not."
Leak at attention (they do not even read): /headlines (Roy)
"Roy, the headline and opening of this page are losing the traffic Diane flagged. 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 ask.
The rebuilt stage, with the old version still in the folder beside it for the gate.
"Vera, review the rebuild against Diane's diagnosis and the old stage beside it. Does the rebuild actually address the diagnosed leak, or does it just sound better? Flag any claim I cannot prove and any new mismatch with the traffic source."
Your specialists already proof their own work. This gate is the deliberate cross-check that the fix matches the diagnosis, not just the copy. Ship only if it does.
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.
The Staffmint Playbooks06 · Funnel Fix
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.
Run this playbook inside your one Staffmint Project folder, so every specialist already knows your business. A new chat is fine; just stay in the folder. If a specialist needs a specific input, it asks.
"Reid, map the competitive field for my category and market, then show me the gaps: which positions are crowded and which are unclaimed."
A competitive map with claimed and unclaimed territory, so you choose from real openings instead of inventing in a vacuum. Reid reads your category and market from your profile and finds your competitors. If he has names you want included, he asks for them.
"Maya, build the avatar for my market and tell me which of the unclaimed positions Reid just mapped they actually care about: what they believe about the existing options, what disappointed them, and what would make them switch."
An avatar with a verdict on which gap has real buyer pull behind it, plus the avatar's own language.
"Esme, build my positioning on the gap Maya confirmed: a one-sentence 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."
Positioning statement, messaging hierarchy, and a do-not-claim list. She builds the WHY-US from your real strengths in your profile and the evidence behind them; where a strength is not yet proven, she frames it on the mechanism and what you guarantee, never on a claim you cannot back. If she needs a strength clarified, she asks.
"Wynn, pressure-test my current name and tagline against the position Esme just built. If they hold, say so and give me 5 taglines sharpened to it. If they fight the position, tell me plainly and propose alternatives."
A keep-or-change verdict plus tagline options. Wynn reads your current name and tagline from your profile; if either is missing, he asks for it.
"Vera, review the brand sprint together: competitive map, avatar verdict, positioning, and naming. 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 I cannot back today."
Your specialists already proof their own work. This gate is the deliberate cross-asset check that the position holds together and stays honest. Fix what she flags before the one-pager.
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.
The Staffmint Playbooks07 · Brand Sprint
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.
Run this playbook inside your one Staffmint Project folder, so every specialist already knows your business. A new chat is fine; just stay in the folder. If a specialist needs a specific input, it asks.
"Marcus, build my sales call structure for my offer: 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."
A call script with the key questions and exact transition lines. Marcus reads your offer, audience, and selling style from your profile. If he needs your price, call length, or which offer this is for, he asks, and you answer in a line.
"Lara, script my live responses to the objections this call will hit, plus 'send me a proposal' used as a dodge. For each: acknowledge, reframe, a question that re-opens the conversation. And give me the walk-away criteria so I stop chasing dead deals."
Objection scripts plus disqualification rules, built off Marcus's close. She works from the objections in your profile; tell her the real top three you hear if she asks. She handles objections with honest reframes, never pressure or invented proof.
"Erin, build my proposal template for this offer, sendable same day after 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, and mark the sections I personalize per deal."
A proposal template that folds in Lara's "send me a proposal" handling. She uses your real results where you have them and sells on the plan, the specifics, and your guarantee where you do not. If she needs your turnaround window, she asks.
"Vera, review my sales system together: call script, objection scripts, proposal template. 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."
Your specialists already proof their own work. This gate is the deliberate cross-asset check across all three. Fix what she flags before the next booked call.
"Tom, wire follow-up for this sales process. Define the stages from booked call to closed, the cadence after a proposal goes out (day 1, day 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.'"
Stages, cadence, and templates, timed to Erin's proposal expiry logic.
After every 5 calls, take your notes back to Marcus: tell him where calls stalled and have him tighten the script. The system improves on cadence, not on memory.
The Staffmint Playbooks08 · Sales Call System
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.
Run this playbook inside your one Staffmint Project folder, so every specialist already knows your business. A new chat is fine; just stay in the folder. If a specialist needs a specific input, it asks.
"Margot, design my weekly newsletter and write issue 1. Lock the format with named sections I repeat every issue, set the length, the sell-to-value ratio, and a standing CTA, so I stay top of mind without it being a weekly pitch."
A locked format plus a complete first issue. Margot reads your profile for your audience, your offer, and your voice. If she needs your first topic or what a single issue should drive toward, replies, calls, or sales, she asks, and you answer in a line. The format doc is why issue 30 takes an hour, not a day.
"Roy, give me 7 subject lines for the issue Margot just wrote, across curiosity, specific benefit, contrarian, and story-open. Then a reusable checklist for future issues, with what to test first since I have no open data yet."
Subject options plus a testing checklist you fold into your weekly routine. Roy works from the issue in the folder; until your list shows you what it responds to, the checklist tells you what to test first.
"Vera, review my newsletter format and issue 1 together. Three checks: would my audience genuinely forward this, is the selling light enough to sustain weekly trust, and is every claim and example real. Flag the weakest section of the format itself, not just this issue."
Margot and Roy already proof their own work. This gate is the deliberate cross-asset read of the format you will run for months, so she checks that claims trace to your real proof and that nothing is invented. Fix, then send issue 1 to the list.
"Pia, design the standing repurposing loop for my newsletter: 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."
A weekly repurposing checklist plus issue 1 atomized. Pia works from the format and issue 1 in the folder, and reuses only the real examples already in your newsletter.
Every 8 issues, take your open and reply data back to Margot and Roy and ask them to adjust the format and subject patterns to what actually performed.
The Staffmint Playbooks09 · Newsletter Engine
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.
Run this playbook inside your one Staffmint Project folder, so every specialist already knows your business. A new chat is fine; just stay in the folder. If a specialist needs a specific input, it asks.
"Priya, build my churn early-warning and save system: the 3 to 5 warning signals I can actually observe, the intervention for each, and the save ladder for someone who wants to leave: what I offer first, second, and what I never offer."
Signal definitions, interventions, and a save ladder. Priya reads your profile for the offer, price, and billing cycle. If she does not know why customers leave, she asks for your honest top reasons, and you answer in a line.
"Rosa, script the conversations for the signals and save ladder Priya just built: a check-in per warning signal that cares without sounding desperate and holds back any discount on the first touch, the cancel response that makes one genuine attempt to understand and save before a graceful yes, and a goodbye that leaves the door open."
A script per signal plus the cancellation flow, written in your voice from the profile. The goodbye framing carries into Hana's win-back sequence.
"Hana, write a 3-email win-back sequence for customers who left a month or so ago, using Priya's reasons and Rosa's goodbye framing. 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. Email 3: a simple return offer from Priya's ladder with a clean expiry. Respect their decision throughout; nobody returns to a guilt trip."
A 3-email win-back sequence. She leads on real improvements you have actually shipped; where there is none yet, she sells on the mechanism and the specifics and never invents one. If she needs the exact window since they churned, she asks.
"Vera, review my full churn system together: signals, save scripts, cancellation flow, and win-back emails. Flag anything desperate or manipulative, any promised improvement that has not actually shipped, and any save offer that trains customers to threaten cancellation for discounts."
Your specialists already proof their own work. This gate is the deliberate cross-asset review. That last failure mode quietly destroys margins; take the flag seriously.
The Staffmint Playbooks10 · Churn Rescue
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.
Run this playbook inside your one Staffmint Project folder, so every specialist already knows your business. A new chat is fine; just stay in the folder. If a specialist needs a specific input, it asks.
"Talia, build my YouTube strategy: channel positioning in one sentence, 3 content lanes I can rotate, who the viewer is at minute zero, and the first 4 videos with a working title, a 30-second hook, and a bullet outline each."
Channel strategy plus 4 planned videos. Talia reads your profile for the offer, the audience, and the goal. If she needs your realistic cadence or video length, she asks, and you answer in a line.
"Noor, check search demand on the 4 videos Talia just planned: what people actually type around each topic, which title wording matches real queries, and any higher-demand angle I am missing. Revise the titles where the data disagrees, and give me description keywords per video."
Search-validated titles and description keywords. The final titles carry into production and the keywords into upload day.
"Vera, review the channel strategy and first 4 videos together: does every video serve the one-sentence positioning, will the first 30 seconds of each hold a cold viewer, and is the production load honest for my capacity? Flag the weakest hook of the four."
Your specialists already proof their own work. This gate is the bigger cross-check across the whole plan. Fix the weak hook before you record anything.
Record video 1 from the outline. Then say:
"Kai, pull 3 Shorts from the long video I just recorded: the strongest standalone moment, the sharpest contrarian or surprising claim, and a how-to fragment. For each, give me a hook line, a beat-by-beat script under 45 seconds, and the on-screen text."
3 Shorts scripts per long video. This becomes a standing step: every long video ships with 3 Shorts.
"Pia, design my weekly YouTube repurposing loop so each long video also becomes the channels I care about, then give me the post-upload checklist and demonstrate it on video 1."
A post-upload checklist. Pia reads your profile for which channels you run; if she is unsure which to include, she asks.
Every 8 videos, bring Talia your real retention and click-through numbers and ask her to adjust the lanes. She works from your actual channel data, never invented numbers.
The Staffmint Playbooks11 · YouTube Engine
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.
Run this playbook inside your one Staffmint Project folder, so every specialist already knows your business. A new chat is fine; just stay in the folder. If a specialist needs a specific input, it asks.
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.
"Vivian, run my quarterly review. Here is what I gathered this morning. 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 to 3 candidate priorities for next quarter, with the case for each. Do not pick yet."
An honest diagnosis plus candidate priorities with trade-offs. Vivian reads your profile and your morning notes; if she needs last quarter's goals or numbers spelled out, she asks, and you answer in a line. The candidates carry into Farah's market check before anything is chosen.
"Farah, check the candidate priorities Vivian just surfaced against the market. For each: has demand shifted in my 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 the market supports and which it undercuts. Pull live data where you can."
A market read per candidate, with the candidates and verdicts ready for the decision. She works from real, current signals; where data is thin she says so rather than guessing.
"Vance, help me commit. Take the candidates and Farah's market verdicts and pressure-test each: what has to be true for it to work, what I give 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."
The decision, the not-doing list, and the reasoning on record, ready for execution planning. If he needs your real capacity, cash runway, or energy to weigh the call, he asks, and you answer in a line.
"Dana, turn the priority Vance just locked into an operating rhythm. Break it into 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."
Milestones, weekly cadence, and the review ritual. If she needs the number of milestones you want or a fixed start date, she asks, and you answer in a line.
"Vera, review my full quarterly plan: diagnosis, decision, not-doing list, operating rhythm. 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."
Each specialist already proofs their own work. This gate is the deliberate cross-asset check across the whole plan. Fix what she flags before you commit the quarter.
The Staffmint Playbooks12 · Quarterly Reset
Your specialists are hired. These were their marching orders.
Staffmint · staffmint.ai