Five weeks from now,your recurring work runs itself.
The Setup Sprint is a done-for-you implementation of Patricia, the AI teammate in your Slack. We do the mapping, the plumbing, the training, and the tuning, one clear week at a time. You end up AI-native without ever running an AI project.
We connect Patricia to the tools your team already runs on.
Built for small teams doing the job of a big one.
Why a sprint
You have seen the AI demos. You have also seen them die.
Most AI projects in established businesses fail the same way. The demo looks great, then it meets the real company: the client list in a spreadsheet, the process in one person's head, the folder structure that grew by accident. The tool was never the problem, and neither was your team. The implementation was.
The Setup Sprint exists because connecting an AI teammate to a real, messy business is a job. It is the job we do. We map how the work actually flows, fix the plumbing, and stay until your team delegates without thinking about it.
Week by week
The five weeks, exactly as they happen.
No vague phases. Every week has a name, a job, and a deliverable you can hold us to.
Week 1
Map the work
You know exactly what Patricia will take over, and in what order.
What happens
- We sit with your team 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
Included
- 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.
Week 2
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
Included
- 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.
Week 3
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
Included
- 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.
Week 4
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 all week answering questions as they come up
Included
- 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
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.
Week 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
Included
- 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.
After week five
The sprint ends. The routine does not.
You own everything
The configured skills, the playbook, and the credits are yours. Nothing is rented, and the included credits never expire.
Patricia keeps working
The routines built in the sprint keep running on schedule. Your trained owner adjusts them as the business changes.
We stay a message away
Normal support covers you from day one. If you want us to keep managing and expanding the setup, we can talk about that too.
The call is a fit check, not a pitch. Thirty minutes, and you leave with a straight answer.
Pricing
One sprint, one price.
The Setup Sprint
$9,750
- The work audit: your recurring work mapped, ranked, and turned into a handoff plan
- The plumbing: every tool connected, permissions scoped, guardrails live
- The routine build: your reports, briefs, and recaps running in your voice, proven side by side
- Launch week: a live session with your whole team, plus a week of us on call in your Slack
- The handover: a trained internal owner and the full playbook
- $1,000 in Patricia credits, they never expire
- Bought separately, that is $14,000 of work. The sprint is $9,750, one time.
Your time: one point person and about two hours a week. We handle the rest.
Our 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.
The realistic alternative is an internal project that eats a quarter of someone's year; the sprint gets you the outcome in five weeks, with the keys handed back to you.
Security and trust
Built to be trusted with your company's data.
Your data stays yours. Every action is logged, she checks her own work, and she gets sharper every week.
Your data stays yours
Walled off, never used to train anyone else's model, and deleted if you cancel.
Every action logged
A full audit trail of what she did, when, and on whose say-so. Nothing happens off the record.
She checks her own work
Patricia reviews what she produces against your brand and your brief before it reaches you.
Sharper every week
The more feedback you give, the better she gets at your product and your voice, so the work lands closer to right over time.
Secure to connect
The compliance most tools cannot show.
Founders connect Patricia to their company because the paperwork is already done. Verify everything in the Trust Center.
How your data is protected, in plain languageFAQ
Questions, answered.
Who is the Setup Sprint 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.
Our systems are a bit of a mess. Is that a problem?
It is the reason the sprint exists. Week 1 maps how work really flows through your company and week 2 does the plumbing: connecting tools, untangling shared drives, and scoping access properly. You do not need to clean up before we arrive; the cleanup is part of what you are buying.
Why five weeks?
Because connecting tools is the easy part. Mapping the real work, testing output side by side against your team's own, launching with every person hands-on, and tuning against real usage each need their own week. Five weeks is the honest amount of time it takes to make a company AI-native rather than AI-curious.
Can I not just set Patricia up myself?
You can. Connecting Patricia to Slack takes minutes, and plenty of teams start that way. What you cannot shortcut is the implementation: mapping the real work, fixing the plumbing, and getting a whole team to actually delegate. The sprint buys that shortcut and the people who do it every week, so nobody on your team has to become the AI person.
What do you need from us?
One point person, access to the tools you want connected, and one working session with the team most weeks, usually an hour or two. We handle everything else, including the plumbing.
Is Patricia's subscription included?
The sprint is a one-time fee that covers the full five-week implementation and includes $1,000 in Patricia credits. Her plan is billed separately and starts at $45 a month. The included credits never expire, so they keep working long after the sprint ends.
What if we want to stop halfway?
You can 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 process map and handoff plan. We can offer that because the sprint is structured to prove itself week by week.
What happens after week five?
You run it. The routines keep working, your trained owner adjusts them, and the playbook covers the rest. Normal support is always there, and if you want us to keep managing and expanding the setup month to month, we can scope that on the call.
What if Patricia is not a fit for us?
That is what the setup call is for. It is a fit check first: we only take on a sprint when we are confident she will carry real work for your team, and we will tell you straight if she will not.
Five weeks from now, this is just how you work.
The recurring work runs itself, your team delegates without thinking about it, and you own the whole setup. It starts with one call.