Skip to content
HHussain C

01Service

AI agents & workflow automation

Agents that read what comes in, decide what to do, and do it, with a person in the loop where it matters.

EmailWhatsAppSend a brief

Agents that do the boring part of the job, reliably.

An agent is just software that reads a situation, picks a tool and uses it. The hard part isn't the model. It's choosing which steps to hand over, giving the agent tools that can't do damage, and knowing when it got something wrong.

I start with one workflow your team repeats every day: support triage, lead research, document intake, follow-ups. We automate that end to end, measure it against how it's done today, then widen the scope once it's earned trust.

A good fit if

What you get

How a project runs

  1. Week 1

    Discovery

    I sit with the people who do the work today. We pick one workflow and agree on what success looks like in numbers.

  2. Weeks 2 to 4

    First version

    A narrow agent that handles the common cases, running alongside your team with every action reviewed.

  3. Weeks 5 to 8

    Hand over the wheel

    Review steps are removed where the logs show it's safe. Edge cases get their own tools or routes to a person.

  4. Ongoing

    Stay on

    Monitoring, model upgrades and new workflows on a monthly retainer, if you want it.

Questions people ask

Which model do you use?

Whichever does the job at the right cost. I've shipped on OpenAI and Claude, and I test Gemini and open-weight models for each task. The code is written so the model can be swapped without a rewrite.

Will it work with our existing tools?

Usually, yes. If a tool has an API, a database or even a reliable inbox, the agent can work with it. I check this in week one before you commit to a build.

We're in a different timezone. Is that a problem?

No. I keep flexible hours and shift my day to overlap with yours, so standups, reviews and launches happen on your clock.

What happens when the agent gets it wrong?

It will, sometimes. That's why every action is logged, risky actions need approval, and we keep a set of past mistakes that every new version has to pass.

Do you work with in-house teams?

Most of the time. I work as a forward deployed engineer: embedded with your team, in your Slack and your repo, and I leave behind code your engineers can maintain.

Contact

Tell me what you're trying to fix.

I read every message myself and usually reply the same day. A rough idea is enough to start.

Or send a short brief

Hours

Your hours work for me.

  • San Francisco

    --:--

  • New York

    --:--

  • London

    --:--

  • Berlin

    --:--

  • Dubai

    --:--

  • Singapore

    --:--

  • Sydney

    --:--

  • Surat

    --:--

    Me

I keep flexible hours and move my day to overlap with yours, whether that's a morning standup in New York or a late release in Sydney.