Professional services
AI Document Processing Platform
From 40 hours to 4 minutes per contract review
99.8%
Processing Time
97.3%
Accuracy
openailangchainpineconenextjs+2
Taking on 2 new projects this quarter
Java engineer who shipsAI products fast
I'm Sri. I build AI-powered products and modern web platforms for startups and growing teams. Independent, hands-on, and focused on shipping work that lasts.
Senior software engineerJava, Spring, AWS, AISolo, by design
Scroll for the substance
How I work
Independent, hands-on, accountable
No agency layers, no junior handoffs. The person you brief is the person who builds.
Solo
One engineer, end to end
No agency layer, no offshore handoff. You talk to the person doing the work.
Honest
Scope before contract
If your problem isn’t a fit, I’ll say so on the first call.
Modern
AI, Java, and the modern web
Next.js, React, Spring Boot, AWS, and LLM integration done carefully.
Fast
Replies within 24 hours
I read every enquiry myself. No CRM funnel, no autoresponder rabbit hole.
What I do
Six things I do well, and a few I don’t
I keep my service list short on purpose. These are the engagements where I’ve put in the reps. If your problem doesn’t fit cleanly, tell me anyway, I’ll point you to someone who’s a better fit.
Selected work
Three projects I’m happy to talk about
14 case studies in total. Names and exact numbers are anonymised because most of these clients sign NDAs, but the architecture decisions, trade-offs and metrics are real. If you want, I’ll walk you through the production code on a call.
How I work
Four phases, no surprises
I borrowed this from the way regulated banks structure delivery, then stripped the parts that don’t belong in a startup. You get the rigour, not the bureaucracy.
1
Discovery
One paid week. I read your code, talk to your team, and write a brief that says what we’re building, what we’re not, and why.
2
Architecture
Diagrams, ADRs, schema, infra plan. You get a doc that survives me leaving the project. No black boxes.
3
Build
Weekly demos on Fridays. Production deploys from week 2 onwards. You see the thing running, not slides about the thing.
4
Handover
Runbooks, dashboards, a recorded walkthrough, 30 days of bug-fix support. Your team owns it the day I leave.
Industries
Where I do my best work
I’ve shipped in all of these. Fintech and SaaS are where I’m fastest because I’ve seen the failure modes. Healthcare and marketplaces are where I move slower on purpose. The full breakdown lives on the industries page.
Stack
What I reach for, and why
I keep my stack narrow on purpose. Java, Spring Boot, Postgres and TypeScript handle 90% of what teams actually need. I add Python when there’s real ML, Go when latency matters, and the AI layer that fits the problem. The years number is how long I’ve shipped it in production, not how long I’ve read about it.
Recent thinking
Things I’ve written lately
I publish what I learn while building. No SEO listicles, no thought-leadership-by-LinkedIn. If a post helps you avoid a bad architectural call, it’s done its job.
FAQ
Things people ask before they hit reply
If your question isn’t here, just email me. I’d rather answer it directly than have you guess.
If you’ve read this far, we should probably talk
The fastest path is a 30-minute call. I’ll ask you four questions, you’ll know within ten minutes whether I’m the right fit. If I’m not, I’ll tell you who is.
I reply within 24 hours, usually same day in UK hours.