← All case studies

Case study 05 · Pintu

Internal tools built with agentic AI

Moving Pintu’s budgeting and procurement off spreadsheets and email, with internal tools I built alone with Claude Code and MCP in 3–4 months, now used by every department that works with a budget.

Role
Built the tools alone, fully with AI
Used by
Finance, Procurement, Engineering, Marketing, Product
Timeline
Started Jun 2026 · 3–4 months to launch
Stack
Claude Code · MCP
Simplified flow of the budgeting and procurement tool.

The challenge

Budgets and purchases ran on spreadsheets and email

Company budgeting at Pintu, and procurement from purchase to payment, ran manually on spreadsheets and email. Every department spends money, so every department was part of that process: Finance, Procurement, Engineering, Marketing and Product.

Internal tools rarely make it to the top of a product roadmap, yet the work they replace is manual and repeats all year. The question was whether agentic AI could close that gap without creating new risks.

Small tools, built quickly, that people outside engineering actually use.

My role

Building it alone, with AI

I built the tools myself, fully with AI, using Claude Code and MCP. It took 3–4 months from the start in June 2026 to launch, including testing.

Approach

How I built it

1. Start from the manual process

The tools replaced the spreadsheets and email behind two processes: company budgeting, and procurement from purchase to payment.

2. Detailed requirements first

Claude Code writes code very fast, but sometimes it hallucinates. Writing the requirements in real detail kept it on track.

3. Human approval and an audit log

Every money movement needs a person’s approval before it goes ahead, and every step is recorded in an audit log.

4. Test by hand

Every flow was tested manually before release. Testing was part of the 3–4 months, not an afterthought.

Outcome

What changed

5
Departments using the tools
3–4 mo
From start to launch, including testing
1
Engineer, building fully with AI

Finance, Procurement, Engineering, Marketing and Product now work in the same tools, and every money movement is approved by a person and recorded. Some teams still use spreadsheets this year while the transition finishes.

What I learned

What I’d keep, and what I’d change

AI makes coding very fast, but its output sometimes hallucinates. What made it work was writing requirements in real detail and testing everything by hand. The engineer is still the architect; the AI is only the executor.