How we
work together.
Most AI tools impress in a demo, then stall the moment real work hits them. I build the opposite: systems that get more useful with age, because they're grounded in evidence, shaped around how you actually work, and built to keep paying back long after the pilot.
Everything I do runs on the same engines I build in the open, webdevOS and cofounderOS. The four practices below are how I put that discipline to work for you.
New to this? Take the 2 minute diagnostic to see where you are.
Your Claude, Dialled In
I can't get Claude Cowork to work for me.
You've got Claude Cowork, and maybe Claude Code, but it won't click. It forgets what you told it, it doesn't sound like you, and the links to your tools feel brittle.
It starts with a discovery call, the same as Find the Value but more targeted, because you already know you're working with Claude. From there I dial it in on three fronts. Memory, so the context you build up survives between sessions instead of evaporating. Voice, so what it produces reads like you wrote it, not like a generic assistant. Connectivity, so the tools you actually use are wired in cleanly, because not all MCPs are born equal.
You end up with a Claude coworker that remembers, sounds like you, and connects cleanly, so it earns a place in your day instead of being abandoned after the first week. And because we build it together on top of a setup that already works for me, you can run and extend it yourself.
- D.01A proven core setup, based on an adapted PARA structure (after Tiago Forte's method), drawn from the system I use myself and built together so you can run it yourself.
- D.02Memory that holds the context you build, so it survives between sessions.
- D.03Output that reads like you wrote it, not a generic assistant.
- D.04Clean, efficient connections to the tools you actually use.
I have Claude Cowork but I can't get it to work for me. Can you fix that?
Yes, that's the whole point of this offering. "It doesn't work for me" almost always comes down to three things: it forgets context, it doesn't sound like you, and its connections to your tools are brittle. I dial in all three so it earns a place in your day instead of being abandoned after a week.
Why does Claude keep forgetting what I told it?
Because memory has to be implemented deliberately, it isn't automatic. I set up memory so the context you build up persists properly across sessions, which is the single biggest reason a Claude coworker starts to feel genuinely useful rather than amnesiac.
Can you make it sound like me rather than a generic assistant?
Yes. Voice guidelines are paramount in this work. I capture how you actually write and encode it so what Claude produces reads like you wrote it, which is what makes the output usable without a heavy editing pass every time.
I've connected some MCPs but it still feels clunky. What's wrong?
Not all MCPs are born equal. A clumsy or redundant set of connections makes everything feel slow and brittle. I wire in efficient, clean MCP connectivity to the tools you actually use, so the integrations help rather than get in the way.
Does this work for Claude Code as well as Claude Cowork?
It applies to both. The memory, voice, and connectivity work carries across the Claude tools you use day to day, Claude Cowork and Claude Code alike. And it isn't limited to Anthropic: I can work with non-Anthropic architectures too, so you're not locked to a single vendor.
Not sure which fits?
The four practices map to the four stages of adoption. Most people start with Find the Value and grow from there.