The jobs these take over
Anything with the shape on the approach page is buildable. These are the jobs that come up most, sorted by the part of the business they take work off of.
Invoices come in and somebody files them
The PDF lands in the right job folder, the numbers land in the tracker, you get a link.
operationsYears of files nobody can find
Read first, plan the moves, delete nothing, keep a log you can walk backward.
knowledgeThe monthly close, the checking parts
Pull the reports, reconcile against what cleared, flag what doesn’t tie.
operationsSomebody reads the shared inbox every morning
Triage, route, draft the replies. Nothing sends without your eyes on it.
assistantThe report you write every Monday
Pulled from the systems it’s connected to, waiting when you wake up.
recurringA stack of documents, one decision
Deal files, bids, contracts. It reads them, gives the call, shows what it read to get there.
knowledgeThe recurring job that gets forgotten
Runs on a schedule without anyone starting it, and tells you when it can’t.
recurringResearch and prospecting nobody has time for
Companies, properties, people. Tracked somewhere you can actually check.
assistantMeetings and calls that never get written up
Summarized into something the business can use, not a transcript nobody opens.
assistantThe knowledge that only lives in your head
How you price, who you call, what happens when X. Written down where a machine can work in it and a person can still read it.
knowledgeIf one of these is a job somebody at your company does every week, that’s the one to start with. One job, one agent, then we see what else it can carry.
What the case studies don’t show
Three things don’t fit in a case study, so they’re here in plain words and the agent on this site can say them too.
The first is the everyday material, the spreadsheets, documents, email and systems a business already runs on. There’s no case study for Excel because a spreadsheet isn’t a build. It’s where most of this work already lives and I’ve run my own businesses inside spreadsheets and documents for ten years so if the job is in that material, I work in it.
The second is the platforms. I work in the tools companies use to work with AI every day and I don’t keep paid seats on platforms no client of mine runs. If your work needs one, I get it. Every one of them is a model with a place it reads from and a place it writes to, which is a shape I’ve built several times over, so a platform I haven’t used is a few turns of screenshots and questions away from one I have. The 24/7 agent and the coaching platform on this site got built that way and I couldn’t have built either one unaided. Most companies assume running agents means an expensive platform subscription and more often than people expect, it doesn’t. A folder structure with the judgment written into the files, run by the AI you already pay for, does the job at a fraction of the cost, which is what the approach page describes. The platforms earn their place where the work is complex enough to need them and the audit is where I tell you which side of that line you’re on.
The third is scale. There is no headcount where a build stops being mine, and I’m not going to make one up. The audit is where I find out whether a job is something I handle alone or something that needs more hands than mine to hit a date. When it needs more, I work alongside a developer, either yours or one I bring, and I say so before the work starts rather than in month two.
The coaching platform is production software with clients training on it right now. I know what it would take to make it a consumer app, which is a software engineer and a small team to maintain it.