How we
work together.
I've found that agentic systems can plateau at the demo. I aim to design systems that get more useful with age: memory-first architecture, context engineering, embedded delivery, and operational discipline for regulated environments.
I've built my practice around webdevOS and cofounderOS, my in-house multi-agent orchestration engines. The four practices below are how I deliver it.
Find the Value
Where do I start? Which tools actually pay back?
You've tried some tools and it hasn't been as impactful as you'd hoped. The question underneath is harder than which tool: it's where, in your actual business, intelligence earns its keep.
I start with evidence, not enthusiasm. I audit how work flows today, benchmark what you're already running against what good looks like, and pull in the best practices that actually transfer to your context. Then I pair that diagnosis with practical enablement, so the people doing the work understand what changed and why.
The outcome is an evidence-based starting point: a clear view of where the value is, and a team equipped to go get real impact rather than another pilot that plateaus at the demo.
- D.01Current-state audit of how work flows today
- D.02Benchmarking against best-practice reference points
- D.03Prioritised opportunity map (where the value is)
- D.04Practical enablement for the team doing the work
I've already tried some AI tools and they didn't help much. Is this different?
That's exactly the situation this is for. Tools that underdeliver are usually pointed at the wrong problem, not the wrong vendor. I start by auditing how your work actually flows and benchmarking what you're running, so the next step is grounded in evidence about where value lives in your business rather than in tool enthusiasm.
Where do I start? I don't know which tools actually pay back.
You start with a diagnosis, not a tool purchase. I look at how work flows today, compare it against best-practice reference points, and surface the small set of places where intelligence earns its keep. The output is a prioritised opportunity map, so you can see where to invest before you commit to any particular tool.
Will my team be able to act on this, or is it just a report?
It comes with practical enablement, not just a document. The people doing the work need to understand what changed and why, so I pair the diagnosis with hands-on enablement aimed at the team, leaving them equipped to go get real impact themselves.