Result
self-reportedClaude saved a fractional CTO 128 hours in 6 weeks, after taking off the time spent prompting it and fixing its work.
David Szabo-Stuban runs the technical side of 4–5 businesses as a fractional CTO. He used to spend the first hour of every client session explaining that client to Claude. Now each client has its own Claude Project with the same five things loaded. Before each call he can see everything that client is still waiting on, and he has rules so Claude can't say a task is done when it isn't, or send or delete anything from a regular chat.
Who did it
Try it now
- Create one Claude Project per client.
- Load the same basics into each: who they are, goals, systems and access, open work, and how they like to communicate.
- Before each call, ask for everything that client is still waiting on from you.
- Add rules: a task is only done when you confirm it, and nothing is sent or deleted from a regular chat.
You're my assistant for client [name]. Project files: [about the client], [goals this quarter], [systems and access], [open work list], [how they like updates]. Before each call, give me: what they're waiting on from me, what I'm waiting on from them, and 3 things to raise. Never mark a task done unless I say so. Never send or delete anything. Draft it for me.
Want this set up on your own site?
Build it with PageWhat to watch out for
Self-reported, and he subtracted his prompting and fixing time, which is the honest way to count. Keep client secrets out of anything you don't control. Build it with Page: a client portal page that shows open work and next steps.
Did it work?
PageMotor keeps this site free.