I build agents that do the work.
- 14:02:11.004 trigger: request · "Reconcile March invoices"
- 14:02:11.630 plan: 3 steps · 2 tools · 1 check
- 14:02:13.902 act: sheets → ledger · 41 rows matched
- 14:02:19.247 ship: verified · report sent to #finance
- 14:02:19.250 done: 8.2s · 0 errors · next run: yours ↓
I design, build and run AI agents and automations for teams that are done doing the same work twice.
That was one of mine. Now yours.
What should run itself?
This is how I start every project: map the work, decide where a model helps, where code is safer, and where a person stays in the loop.
03 — How I work
Agents that fail loudly. Automations with an off switch. Systems your team actually trusts.
04 — Selected runs
05 — Process
- Trigger01
Trigger
Something happens: an email lands, a form is sent, a schedule fires. I find the moment where the work really starts.
- Model02
Plan
The agent decides what needs doing and which tools it may use. Limits come first, so it never wanders.
- Tool03
Act
It does the work in your real tools (CRM, sheets, inbox) with the same access a person on your team would have.
- Code04
Verify
Every result is checked by code or a second model. When it is unsure, it stops and asks a person instead of guessing.
- Tool05
Ship
The result lands where your team already works, and every run is logged so it can be replayed later.
Ask it about my work. It will show you.
It answers from my case studies, shows every tool call it makes, and can take you straight to what you are looking for.
This is RUN #011, [Invoice extraction pipeline]. I have highlighted it on the page and I am opening the full run report next.
07 — Toolbox
Models
Backend
Data
Ops
Start a run.
Describe the work in your own words. I read every message myself and reply from
Book a call · [booking link]