The playbook

Shane Jacobs.
Monday morning.

Mon 31 Aug · 9am to 1pm 14 Ascot Road, Ballina

Where you are

The build went on hold on 24 August and never came off it. Everything green below is genuinely ready. Everything amber happens live, with him in the room.

DateLocked Monday 31 Aug, 9am to 1pm, on site. Not the Wednesday first discussed.
MoneyPaid in full $1,200, invoice W9Z5VDGI-0001, bank transfer 27 Aug. Nothing to chase.
The kitBuilt and live 10 skills, a GymMaster CLI and 9 routine recipes, public on GitHub.
Teaching materialWritten Scripted notes plus three decks to pick from.
His business loaded in23 blanks The profile was never filled. This is the 9:45 slot, and it is the one that gets cut when you run late.
The routinesNot built yet Prompts are written and paste ready. Building them together IS the day.
ConnectorsNever tested First contact is tomorrow morning. Hard 30 minute timebox at 10:10.
RehearsalNone Install has not been run end to end. Do that tonight, it takes 5 minutes.
Do not reopen this The invoice said "including GST" and you are not registered. You decided on 27 August to leave it alone. Do not raise GST with Shane tomorrow.

Tonight

Twenty minutes, and it removes most of what can go wrong tomorrow. Ticks save on this device.

Ticks stay on this device. Nothing is sent anywhere.

The day

The first forty minutes are teaching, not clicking. That is what he is paying for. If he can only work the buttons, he stops using it in three weeks.

9:00

Get him set up, and the three tabs

Do: Claude on his laptop and his phone. Sign in, sort the plan. Run one real task in the first five minutes so he sees it work before any theory.

SayChat is for asking. Cowork is for doing. Code is for building software, if you ever want to go there.
The trick that pays for itself Make him type /vgc-posts into the Chat tab on purpose and watch nothing happen. Then move to Cowork and watch it work. Thirty seconds, and he never hits that alone in a fortnight and decides it is broken.
9:20

How the whole thing is built. ARMS.

Do: draw four layers on paper. Do not open a screen for this.

LayerWhat it meansHis version
A ApplicationsThe software it can reachXero, Stripe, Mailchimp, Gym Master, socials
R RoutinesRuns without being askedWeekly posts, Monday brief, monthly report
M MemoryWhat it knows about the businessHis prices, hours, packages, how he talks
S SkillsThe jobs it can doThe ten commands below
Say it as a chain, this is the ahaMemory first, it cannot write about your business until it knows your business. Then Applications, it cannot pull your numbers until it can reach your systems. Then Skills, now it can do a real job. Then Routines, put it on a timer and stop thinking about it.
The line that lands Most people start at Skills with an empty Memory, then wonder why it sounds like a robot.

Do NOT teach prompting, the skills carry it. Do NOT explain tokens, models or MCP. That is showing off and it makes a capable bloke feel stupid.

9:45

Layer one, Memory. Load his business in.

Do: install the plugin, then fill in the profile together. Prices, memberships, hours, packages, current offers, how he talks.

This is the one that gets cut. Do not cut it. Every skill refuses to invent a price, so an unfilled profile means every output comes back full of [CHECK] markers a week later, and he will not ring to tell you.

Need from him: the price list. A photo of the board on the wall is fine.

10:10

Layer two, Applications. Connect his systems.

Hard thirty minute timebox. This is where these days die. See the connector table below for which route each system takes.

The ruleAnything not connected by 10:40 goes on the quoted separately list. The proposal already allows for it: "Anything that has to be built rather than linked up on the day gets quoted on its own, before I start it."
10:40

Break

Ten minutes. He owns the place, he will want to look at the floor.

10:50

Layer three, Routines. The moment that matters.

Do: build ONE scheduled task together. Set it. Shut the laptop. Watch it run anyway.

Protect this slot This is the reason for the whole day and the bit he tells his mates about. If you are running late, cut anything else before this. Start with the Monday brief or the weekly posts, both prompts are paste ready.
11:25

Layer four, Skills. Real output.

Do: run /vgc-posts for a real week, and /vgc-report for the monthly owner report with the profit and loss commentary already written. He drives, you sit beside him.

The report is the single biggest time saver he named in the walk-through. He writes that commentary by hand every month right now.

12:00

Outreach

Do: first emails for schools and for corporate Christmas functions.

Say why nowCompanies plan their Christmas functions across September and October. That window is open this week. It is the reason the proposal said now rather than later.
12:25

He builds one on his own

Do nothing. Hands off the keyboard. Two routines are deliberately left for him, because he holds knowledge you do not.

The real testAsk him which layer he is working in, and why it needs the other three. If he can answer that, the day worked, regardless of how many connectors came good.
12:45

Playbook and questions

What got set up, how to change it, what to do when something new turns up.

The ten skills

These install into his Cowork as slash commands. He types the command, it does the job in his voice. Every one is draft only, nothing sends or publishes by itself.

/vgc-brand

The voice

His colours, fonts, audiences and hard rules. Every other skill reads this first. It is what stops the output sounding like a robot.

Reference
/vgc-posts

A week of posts

Seven posts and a carousel, in his voice. Checks the Ballina forecast and leads with the wet weather angle when rain is coming.

Sonnet
/vgc-carousel

One swipe post

The multi image posts he hand makes now. Tells him to make it a single post instead if the idea does not need a carousel.

Sonnet
/vgc-report

The monthly owner report

Pulls Xero, Stripe and Gym Master, then writes the profit and loss commentary. He edits, he never drafts. Flags anything that looks like a data error rather than reporting it straight.

Opus
/vgc-winback

Bring back the quiet ones

Finds anyone missing 30 to 180 days. Checks Stripe for failed cards FIRST, because those people did not leave, their payment broke. Easiest money in the list.

Sonnet
/vgc-schools

School and NDIS outreach

Turns the wet weather walk ins into a worked pipeline. Refuses to invent supervision ratios or insurance cover, those are duty of care questions.

Sonnet
/vgc-functions

Christmas functions

Corporate outreach for the September to October window. Checks the date and refuses to run out of season, because that burns the list for next year.

Sonnet
/vgc-reply

Answer an enquiry

Sorts the type first, then drafts in his voice. Never confirms a booking or a refund, it cannot see the diary. Complaints go straight to him untouched.

Haiku
/vgc-learn

Record a correction

He says "stop writing it like that" and it becomes a permanent rule. Facts go to the profile, preferences go to the learned file.

Haiku
/vgc-tune

The weekly tune

Diffs what Claude drafted against what he approved and learns from the difference. One change is noise, three is a rule. This is what makes the kit get better on its own.

Opus
Why the model tiers matter The daily job runs about 30 times a month, more than everything else combined, so it is Haiku. Only two things touch Opus and both are infrequent. That is what keeps him on Claude Pro at about $35 a month instead of needing Max.

The nine routines

Scheduled tasks that call the skills on a timer. Prompts are written and paste ready in the kit. None of them exist yet. Building them is the day.

Daily 07:00

Enquiry triage

Drafts replies to overnight enquiries. Function enquiries get flagged urgent.

We buildHaiku
Mon 06:00

Weekly posts

The week's posts and a carousel, waiting for his approval when he opens up.

We buildSonnet
Mon 07:00

Monday brief

Bookings, takings and cash position boiled to three things that matter this week.

We buildHaiku
Fri 09:00

Win backs

Quiet members found, billing failures separated out, emails drafted.

We buildSonnet
Fri 16:00

The tune

The self improvement loop. If he ever turns one off, make sure it is not this one.

We buildOpus
Tue + Thu, Sep to Oct

Function outreach

Christmas function emails while the window is open. Retires itself on 31 October.

We buildSonnet
1st of month 06:00

Owner report

The monthly report with commentary already written.

We buildOpus
Before each school holiday

Holiday campaign

Families and kids around the racing sims. He builds this one. He knows the holiday rhythm and you do not, so it is real input rather than a demo.

He builds, live
Weekly

Review watch

New Google reviews, drafted responses. He builds this one. He knows how he wants to sound when someone complains.

He builds, live

Connectors, and the CLI

Which route each of his systems takes. Almost all of these are his OAuth click, which is why the timebox is tight.

SystemRouteWatch for
StripeOfficial Claude connectorRead and write. Straightforward.
XeroOfficial Claude connectorThe login often lives with the accountant.
MailchimpOfficial connectorVerify it exists. Sources disagreed. Zapier is the fallback.
Instagram, Facebook, Google Business ProfileBuffer MCP, https://mcp.buffer.com/mcpOne connector covers all three. Costs money on top of Claude. Price it live and tell him the real total.
Gym MasterOur own CLINothing in the directory covers gym software. Key is self serve from his admin, Settings then Integrations, five minutes.
GmailNative connectorDrafts only, never sends. That is by design and it is fine for tomorrow.
The GymMaster CLI, in one line GymMaster publishes no spec and offers no test environment, so it is the one thing we hand built. It is read only and it asks his account what reports exist rather than guessing: gymmaster doctor, then gymmaster categories, then gymmaster report. It will never send anything other than a read.

The gaps, and the move for each

None of these are fatal. The day always included the connector work and the profile work. What is missing is the rehearsal, so work the timeboxes harder than planned.

GapWhat it meansThe move
Profile has 23 blanksSkills output [CHECK] markers until filledThe 9:45 slot. Do not skip it.
No routine exists yetNothing runs on a timerBuild one at 10:50, two more with him after
Connectors never testedFirst contact is live, in front of himHard timebox. Overflow gets quoted.
Buffer never pricedYou cannot quote his monthly total yetPrice it live, give him the real number
Gmail send never testedNative Gmail drafts onlyDraft only is fine tomorrow. Real sending is a follow up.
Install never rehearsedCould fail at his counterTest tonight. USB as backstop.
If it goes wrong Plugin will not install, upload from the USB and wire the marketplace before you leave. A connector will not authorise, park it, name it, quote it, and do not burn the 10:50 slot. Running behind at noon, cut the outreach block, never the 10:50 one and never the 12:25 one.
Money, settled Paid in full. After the day it is $0 a month, you recommended he runs it himself, hold that line. $300 a month stays available if he asks, revisit a month later. His own cost is Claude Pro at about $35, plus Buffer if he wants hands off posting. Anything that needs building rather than connecting gets quoted before you start it.
Not in this The balustrading business. He raised it, the proposal deliberately parked it as its own conversation. Mention it warmly at the end if there is time. Do not sell it.