USMAN / FIELD NOTES
FIELD NOTES · SERVICES · 2026

I build AI automations for ops and sales teams.

Three weeks, working code, fixed price. No retainer.

01The offer

Three ways to work together.

Cheapest first, largest last. Each tier is a complete deliverable — you can stop after any of them. Prices are fixed. No “starting at,” no “contact for a quote.”

01·Free
Free60 min · video

An hour to figure out if there's anything worth automating.

I ask the right questions, you point at the things that hurt. By the end we both know whether this is a fit.

  • Map your 2–3 highest-friction workflows
  • Honest read on which (if any) are worth automating now
  • Short follow-up note: what I'd build first and why
  • Zero obligation. No follow-up sales sequence.
02·Standalone
€1,0002 days · on-site

Two days embedded with your team. A written audit you can act on without me.

I sit with the people doing the work, watch what actually happens, then write up what to automate, in what order, and what each one is worth.

  • Top 3 automation candidates, ranked by impact ÷ effort
  • Recommended sequence + dependencies
  • Expected hours saved and rough build cost per candidate
  • Yours to keep. Take it to anyone — including no one.
Fully credited toward the sprintBook the audit
03·Build
€3,0003 weeks · fixed

Pick one workflow. I build it, integrate it, and hand it over working.

Fixed price, fixed timeline. Working code in your stack at the end. No retainer, no subscription, no vendor lock-in.

  • Week 1: deep dive, design, mid-week review
  • Week 2: build the core, daily commits
  • Week 3: integrate into your tools, test, hand over
  • Code lives on your GitHub. You own it.
02How the sprint works

Three weeks. Nothing surprising.

Day-by-day so you can tell your team what to expect. The mid-week review on Wednesday is where the wrong thing gets caught before it gets built — that's the meeting that earns the fee.

Week 01

Discovery & design

  • Mon–TueDeep dive. Sit with the team doing the work. Watch the actual workflow, not the org-chart version.
  • WedMid-week review. 30-min sync. I show the design + acceptance criteria. We adjust before anything gets built.
  • Thu–FriFinalise. Locked-in design, integration plan, list of what's in and what's explicitly out.

Week 02

Build

  • Mon–WedCore build. Working end-to-end by mid-week. Daily commits so you watch progress, not wait for a reveal.
  • Thu–FriHardening. Edge cases, prompt tuning, retries. The part most demos skip and ship anyway.

Week 03

Integrate & hand over

  • Mon–TueIntegrate. Wired into Slack, email, your CRM, internal docs — whatever your team already uses.
  • Wed–ThuTest in your stack. Real data, sandbox users. Catch the things the design missed; adjust where needed.
  • FriHandover. Repo transfer, documentation, ~15-min Loom walkthrough, basic monitoring. Then I'm done.
03What you actually get

The handover package.

At the end of the sprint, this is in your hands. No follow-up dependency, nothing routed through my infrastructure, no managed-service tail.

// after the 3-week sprint
  • Working code, deployed where you deploy// not a demo, not a notebook
  • Source on your GitHub// transferred at handover. yours.
  • Architecture doc + runbook// for the next engineer, including future-you
  • Loom walkthrough (~15 min)// so the team can operate it without me
  • Basic monitoring + alerts// you find out before the user does
  • No subscription, no retainer, no API tokens routed through me// you keep the keys
04Example workflows

What “one workflow” actually looks like.

A sprint targets exactly one. These are the shapes that fit — concrete enough to scope in three weeks, ambiguous enough that an LLM earns its keep over a regex.

KNOWLEDGE

Internal Q&A bot

Slack-native. Queries your docs, SOPs and Notion. Cites sources.

DOCUMENTS

Supplier invoice processing

Reads PDFs, extracts line items, posts to your accounting system.

SALES

Lead triage & qualification

Scores inbound against your ICP, routes to the right rep with context.

SUPPORT

Ticket routing & draft replies

Classifies tickets, attaches relevant docs, drafts a first response.

REPORTS

Recurring report generation

Pulls from your warehouse, drafts the Monday-morning email by Sunday night.

SALES

Call note structuring

Turns transcripts into CRM-ready notes — owner, next step, blockers.

05Fit check

Who this is for. And isn't.

Most service pages won't tell you who they shouldn't work with. Here you go — saves us both the discovery call.

Good fit
  • 50–300 employees
  • Ops, sales, or support team with repetitive knowledge work
  • A decision-maker who can approve €3k without a six-month procurement loop
  • You already know which workflow hurts. You just need it built.
Not a fit
  • Looking for a strategy deck or AI roadmap — I build, I don't advise
  • Enterprise procurement, MSA negotiations, vendor onboarding portals
  • Ongoing managed services or a long-term retainer relationship
  • No one internal has the time to point me at the right problem
06About

Who's building it.

I'm Usman. Senior engineer at IKEA, founder of PayZap, currently building Grafora on the side. I've been shipping production AI workflows since the API was an autocomplete endpoint with a temperature knob.

If you want to see how I think before you book the call, read Field Notes. It's the most honest version of a CV I have — what's working, what's breaking, and the things I got wrong the first three times.

STILL HERE? GOOD.

Book the 60 minutes.

We'll know inside an hour whether there's anything here worth building. Worst case, you walk away with a written recommendation you can take to anyone.

Book the call