This week we kept landing on the same thing: a service business hiding inside what almost everyone treats as a personal-productivity tool. Here's what we found.
| 01 the find |
A service that sells AI operating system setups to founders who want one but won't build one themselves.
The setup is a single Claude window wired into the founder's email, calendar, pipeline and numbers. They open it in the morning and see one live dashboard instead of eight tabs.
The move: you build one for yourself first, and that is your demo. Then you sell the same setup, on a 3–5 day turnaround.
The build is the proof. The setup is the product.
We've watched a couple of people run it quietly off warm intros, with no agency, no team, and nothing posted publicly. The pieces only became usable in the last six months, and most founders don't know they exist yet. That gap is the opportunity.
| 02 the numbers |
| time to build | ~8–10 hours · one focused weekend The setup, the 90-sec demo, the offer page, your first outreach run. Closer to a long weekend if you've never opened Claude's desktop app. |
| time to first paying client | 2–6 weeks, if you do the outreach Nothing pays until the messages go out. |
| price per setup | $300–$1,500 The low end is a starter: one connector, one dashboard, one walkthrough Loom. The high end is a full multi-panel build with two revisions and a thirty-day check-in. |
| what this is not | A six-figure consulting business One or two setups a month is realistic, which is what makes it interesting for someone with a day job. |
| Honest note. The build is the easy part. The single reason most people who try this earn nothing isn't the tech: they set up a good-looking dashboard, post the screenshot, and never send a single outreach message. A service with no outreach is a hobby. Plan the outreach before you plan the build. |
| 03 the toolkit |
Everything you'd actually need on Monday:
| Claude Pro — Cowork mode, connectors, and the custom-artifact builder all live behind Pro | $20/mo |
| App connectors — Gmail, Google Calendar, Drive, the obvious ones. Hard cap at about five | free |
| Firecrawl — the scraper for any data that doesn't have a connector. Optional but earns its keep | free–$20/mo |
| Zapier MCP — bridges the 9,000+ apps Claude doesn't natively speak to | free tier |
| Loom — the 90-second demo and the client walkthrough | free tier |
| Carrd — your one-page offer site | free–$19/yr |
| Stripe — for the half-up-front payment when a client says yes | free to start |
total stack cost: $20–$40/mo — the bulk of it is Claude
| 04 the steps |
The whole build, in order: what each step means and what you have at the end of it. The full version walks the how.
| 01 | → | Map the founder's surfaces You write down where one founder's working life actually lives: inbox, calendar, pipeline, numbers. That list becomes the spec for everything the dashboard shows. |
| 02 | → | Wire the connectors Claude gets read access to the first two surfaces, usually email and calendar. From here it sees the real data instead of being told about it. Start with two, not five. |
| 03 | → | Build the morning-brief dashboard The centrepiece: one live panel that opens with today's meetings, open threads and the numbers that matter. This is the thing the demo sells. |
| 04 | → | Add the on-demand skills A handful of repeatable jobs the founder can trigger: draft the replies, summarise the pipeline, prep the next meeting. |
| 05 | → | Record the 90-second demo A short screen recording of your own dashboard doing its morning routine. It becomes the only sales asset you need. |
| 06 | → | Put up the one-page offer A single page naming the service, the price and the turnaround. Somewhere to send people; nothing fancier. |
| 07 | → | Run the first outreach pass Ten short messages to founders you already know, each with the demo attached. This is the step that actually produces a client. |
| 08 | → | Deliver setup no. 1 The first paid build, on the client's accounts, with a walkthrough at the end, on a 3–5 day turnaround. Finish it and you have a reference customer and a repeatable service. |
| 05 the first move |
Don't open Claude yet. Open a blank doc.
Write down, in plain English, every place a single non-technical founder you actually know currently lives: the inbox, the calendar, the spreadsheet they reopen every Monday, the dashboard they bookmark, the Slack channel they check, the notes app they keep falling back to. Five to ten lines, max.
That list is the spec for your own AI operating system. Everything Claude is about to do gets pointed at one of those surfaces.
The single biggest reason this build fails is that people skip this step, fire up Claude, and try to design the dashboard before they've named the inputs.
Thirty minutes, one column, tonight.
That's it.
If you want the whole build laid out, that's the next Kit out: AI Operating System Setup Service.
It has the twelve numbered steps, the copy-paste prompts, the 90-second demo script, the one-page offer template, the outreach message shape, and what to do at week three if nobody's replied.
Otherwise, see you next Friday.
Dan and Adam