Skip to content
Back to the Setup Sprint

Curriculum

The Patricia Setup Sprint

At the end of week 5 your recurring work runs on schedule in your voice, your whole team delegates to Patricia daily, and a trained owner on your side holds the keys.

5 weeks, done for you. $9,750 one time, includes $1,000 in Patricia credits that never expire.

  1. Week 1 of 5

    Map the work

    You know exactly what Patricia will take over, and in what order.

    What happens

    • We sit with your team over video and map the work that repeats: the reports, the briefs, the follow-ups, the busywork
    • We trace where the knowledge actually lives, in tools, spreadsheets, inboxes, and people's heads
    • We pick the first handoffs together: highest payoff, lowest risk, visible within a week
    • Access and security review with your point person, so week 2 starts with no surprises

    What you get

    • A process map of your recurring work
    • A prioritized handoff plan
    • An access and permissions checklist

    What this week is really about: Most businesses we implement in did not grow up AI-native, and that is fine. The client list is a spreadsheet, the reporting steps live in one person's head, and three tools do overlapping jobs. Week 1 is not a workshop about AI, it is an audit of how work really flows through your company today. We interview the people who do the work, write down the steps nobody ever wrote down, and rank every recurring task by payoff and risk. You end the week with a plan you would keep even if you never bought anything else from us.

  2. Week 2 of 5

    Connect and plumb

    Every tool Patricia needs is connected, scoped, and capped.

    What happens

    • We connect your stack, GA4, Meta, Google Ads, HubSpot, Notion, your drive, one tool at a time
    • We do the unglamorous plumbing: untangling shared drives, naming things, retiring the logins nobody remembers
    • We scope what Patricia can see and do, per tool, with your point person approving each scope
    • Spend caps and approval flows go live before she touches anything real

    What you get

    • Your full stack connected and tested
    • A permission matrix you can audit any time
    • Spend caps and approval flows, on by default

    What this week is really about: This is the week that separates a demo from an implementation. In an established business the data is never sitting in one clean place: the folder structure grew by accident, the CRM has three fields that mean the same thing, and half the reporting starts from an export someone runs manually. We fix enough of that plumbing for Patricia to work reliably, and we document what we fixed. Guardrails come first, not last: before she runs anything real, every send and spend already needs a yes from your team.

  3. Week 3 of 5

    Build the routines

    Your recurring work runs on schedule, in your voice, to your standard.

    What happens

    • We configure the skills from your week 1 plan: reports, briefs, recaps, follow-ups
    • Everything runs side by side with how your team does it today, so you can compare outputs directly
    • We tune tone and format to your house style until the output reads like your team wrote it
    • Your point person approves each routine before it graduates from the test channel

    What you get

    • Your first skills running on schedule
    • Side-by-side samples approved by you
    • Output in your voice and format, not a template

    What this week is really about: We never ask a team to trust output they have not compared against their own. Every routine runs in a test channel first, next to the version your team produced by hand, until the difference is that Patricia's arrived on time without anyone asking. Tone matters as much as accuracy in an established business: a weekly client report that reads like a robot wrote it undoes years of relationship. So we tune until your account lead shrugs and says they would have sent it as is. That shrug is the exit criterion for week 3.

  4. Week 4 of 5

    Launch with your team

    Your whole team delegates to Patricia like she has been there for years.

    What happens

    • Patricia moves from the test channel into the channels where work actually happens
    • A live working session: every person hands her a real task from their own plate, not a demo task
    • We set the etiquette together: what to delegate, how approvals work, when to escalate to a human
    • We stay in your Slack or Teams all week answering questions as they come up

    What you get

    • A live launch session with your whole team
    • A one-page delegation cheat sheet per role
    • A week of us on call inside your Slack or Teams

    What this week is really about: Adoption is where AI projects in established companies quietly die, so we treat it as a phase, not an afterthought. The launch session is deliberately hands-on: each person brings one task they dread, hands it to Patricia live, and reviews the result with us in the room. People trust what they have seen work on their own job. By Friday the question inside your team changes from whether to use her to what to hand her next, and that is the only adoption metric that matters.

  5. Week 5 of 5

    Tune and hand over

    The routine runs itself, and your team owns it.

    What happens

    • We watch a full week of real usage and fix every rough edge we find
    • Routines that earned trust get expanded; anything shaky gets tightened or cut
    • We train an internal owner to adjust skills, budgets, and permissions without us
    • You get the playbook: everything she runs, how it works, and how to change it

    What you get

    • A tuned setup based on real usage, not assumptions
    • A trained internal owner on your team
    • The full handover playbook

    What this week is really about: The goal of week 5 is to make ourselves unnecessary. We do not want you dependent on an agency to change a report format, so we train someone on your team to own the setup: adding a skill, adjusting a cap, changing who approves what. The playbook we hand over is written for that person, not for us. You end the sprint with a working AI teammate, a team that uses her daily, and the keys in your own pocket.

The per-week guarantee

Stop at the end of any week and we refund every week we have not started. You keep everything built up to that point, including the week 1 map and plan.

Who it is for

Established businesses and agencies that want the outcome without running the project: teams where the tools grew organically, part of the process lives in spreadsheets and inboxes, and nobody has five spare weeks to become an AI expert. If that sounds like your company, the sprint was designed for you.

The whole sprint runs fully remote, inside your Slack or Microsoft Teams and over video. If you want the kickoff in the room, the offline kick-off add-on brings us to you for the week 1 discovery workshop.