Skip to content
Sharan Shyamsundar
← Sharan Shyamsundar

Build log · 1 of 2

qado · Procurement · 2026 – now

Agents that stop procurement savings from leaking away

Companies negotiate good contracts, then lose the savings in day-to-day buying: missed discounts, prices that drift from what was agreed, deadlines that pass unnoticed. At qado we build agents that catch that gap.

Role
Founding AI Engineer
Domain
Enterprise procurement
Stack
TypeScript · Azure · LLM agents · built with Claude Code

My part

I work across the product: from the agents that read contracts and turn what's in them into something a buyer can act on, to the platform they run on and the AI tooling that makes our own team faster.

How it works, live

A simplified view. As you scroll, a sample supplier moves through it and the active step lights up, with a one-line trace of what the agent is doing.

  1. 01 · Input · activeContracts + invoiceswhat was agreed, what was paid
  2. 02 · Read · activeContract termsthe clauses that move money
  3. 03 · Check · activeInvoices vs. termswhere reality drifts from the contract
  4. 04 · Flag · activeAction for the buyerwhat to do, with the evidence
  1. 01load · sample supplier · contract + invoices
  2. 02read · prices · conditions · deadlines
  3. 03check · invoiced price above the agreed one (sample)
  4. 04flag · action for the buyer · linked to the clause
Illustrative, synthetic data. Simplified; real components are not shown.

What makes it hard

An early-stage startup never hands you one thing at a time. In the same week I can be deep in contract logic, fixing an edge case and picking up a customer request. Early customers are demanding, and they should be: every request has to be weighed for what it does to the product, not just shipped.

A lot of the ground isn't there yet, either. You wear many hats, and you have to stay alert to all of them.

What I learned

Keep up, then share. Models and coding agents change every few weeks, so I try new tools as they land, keep what genuinely helps, drop what doesn't, and pass the good ones on to the team.

And be proactive. In a small team, helping each other move faster matters as much as your own tickets. It's demanding, and it's the fastest I've ever grown.

Outcome

  • In production

    My work runs with qado's customers today.

  • Team awards

    Won together by the whole qado team.

Next build logQuid: from LLM demo to agents that do the books