The work that eats your week, running on AI.
Inside the tools you already use. Your team corrects it. It stays corrected. Eight weeks.
A founder corrects one line. The next follow-up uses it.
Sounds familiar?
"I spend my mornings on follow-ups nobody answers."
The follow-up goes out itself, with a day and a time.
"Every new customer needs the same five emails."
Onboarding runs in order and reads like you.
"Support is a founder in a Slack channel."
Tickets sort by rules your team wrote.
"The investor update takes my Sunday."
The update assembles from the numbers.
"Our launch copy sounds like the deck."
The launch speaks to the customer's pain.
"Content stops when we get busy."
The week's content keeps moving.
A sample week at Sorrelwood.
Sorrelwood makes software for independent physical therapy clinics. Twenty two people, Series A. The work below is fictional, built from the problems a company like this has every week.

The sequence starts with the clinic owner's problem, not a feature list.
Sample. A fictional company, built to show the work.
The recap leaves the call with a next date, owners, and the buyer's words.

One screen: what moved, why it moved, and what the team is betting on next.

Tillwright's screen follows activation, payouts, and take rate.

Different company, same mechanism. Sample. A fictional company, built to show the work.
Eight weeks, then yours.
For the first two weeks, I sit in your Slack, shadow the work, and draw the map of every recurring workflow. We pick the three that cost you the most.
For the next six weeks, I build inside the tools you already use. Your people correct the output. Each correction becomes a rule with a test.
Week eight is the handover. Your team runs it, the rulebook is yours, and I stay on call for thirty days.

The investor update is a side effect of the weekly screen, not another Sunday job.
Sample. A fictional company, built to show the work.The proof is dated.
6,511
Pull requests in our own company, counted 2026-09-14.
5,471
Merged pull requests, counted the same day.
448
Adversarial review transcripts, counted 2026-09-14.
A salon's posts have published on their own since 2026-07-14.
This is for you if
- You have 10 to 80 people and tools already in place.
- A founder or operator can correct the work for six weeks.
- You want the work done inside the company.
This is not for you if
- You want a deck about AI.
- The pilot has no owner.
- Nobody will correct what the system writes.
Send me the workflow.
One sentence is enough. Tell me the work your team hates and I will tell you where I would start.
Send the workflowSubject: The workflow we hate
A rulebook your team can read, correct, and keep.