Approach Audit Work Expertise About Work with me Blog Book an audit →

Work with me

Start with the workflow, then decide what AI should actually do.

Most useful agent projects begin with a bottleneck that already costs time: inbox triage, lead follow-up, document review, reporting, or internal search.

Talk through the workflow

Packaged start

The AI Workflow Audit.

A focused first step for teams that know something is wasting time, but do not yet know whether the answer is AI, rules, a small product, or a simpler automation.

01 / Output

Workflow map

Current steps, owners, tools, handoffs, and failure points — written in plain language, not diagrams nobody reads.

02 / Output

Automation slice

The first useful version to build, chosen so the project can prove itself before it gets expensive.

03 / Output

Guardrail plan

Review points, logs, permissions, fallbacks, and the success metrics we will actually check against.

How the work is shaped

Three phases, and you can stop after any of them.

Nothing here is a retainer trap. Each phase produces something you own and can hand to someone else.

01

Workflow audit

We map the current process, find where time leaks, and decide whether AI, rules, or a simpler automation belongs there.

Own the output
02

Agent build

I build a first useful version around real inputs, review points, logs, and the tools your team already uses.

Own the output
03

Automation product

When the workflow needs a proper interface, I design and build the product layer around the agent, not just the prompt.

Own the output

How projects usually start

Small enough to test. Serious enough to ship.

  1. Step 01

    Map the workflow and name the decision points.

  2. Step 02

    Choose the first useful slice instead of trying to automate everything.

  3. Step 03

    Prototype with realistic data and known failure cases.

  4. Step 04

    Add human review, logs, fallbacks, and permissions before rollout.

  5. Step 05

    Hand over the system with the prompts, rules, and operating notes documented.

Good fit

Bring the messy version. We can scope from there.

A useful first conversation usually needs the workflow, the tools involved, the risk of getting it wrong, and what success would look like.

Typical audit One to two weeks
Working style Direct, async-first
Time zone IST · overlaps EU & US AM
Response time Within 24 hours
Request a workflow audit