Arjun Mehta Arjun Mehta
Let's talk

Taking on two new projects from January

I build product software that earns its keep.

Eleven years turning rough ideas into things people use every day — for founders in Colombo, product teams in Singapore and two banks in London. You get working software, a demo every week, and a straight answer on what it costs.

  • 11 yrsShipping products
  • 60+Products delivered
  • 4Countries
Arjun Mehta at his desk in the studio, looking towards the camera.
Arjun Mehta Product engineer · Colombo
React · Node · Go Shipped in six weeks 4.9 average rating

The story

A one-person product team, with the receipts.

No agency layer, no account manager, and no quiet handover to a junior once you have signed.

A developer working at a wide monitor with code and a live site open side by side.
Colombo 05 · Working hours overlap GMT+0 through GMT+8

I started out repairing other people's half-finished projects. It taught me the thing I still build around: most software fails on decisions made in the first fortnight, not on the code written in the last one.

So every engagement opens with a paid two-hour scoping call. We agree what the thing is, what it is not, and what it costs. If the answer is that you do not need me, I will tell you that too — it has happened four times this year.

Since 2014 that has added up to sixty products for founders, operators and product teams across four countries, and a short list of clients who have now hired me three times each.

  • Scope you can readA one-page plan with dates and a price, before any code is written.
  • A demo every FridayYou see the real thing weekly, not a status email about it.
  • You own everythingRepositories, accounts and documentation are yours from day one.
  • Fixed pricesQuoted up front. If I estimate badly, that is mine to absorb.
  • 60+ Products delivered since 2014
  • 98% Delivered on the date we agreed
  • 4.9 Average client rating, out of five
  • 11 yrs Building for founders, operators and product teams

What I do

Take the piece you need, or the whole build.

Everything starts with a paid two-hour scoping call. If we turn out not to be a fit, you keep the notes and owe me nothing further.

Product build, end to end

From the first sketch to the release that ships — interface, server, database, deployment, and the documentation your next hire will need on their first morning.

  • Interface and server designed together, not bolted on
  • Automated tests running on every release
  • Analytics and error reporting wired in before launch
  • Thirty days of support once you are live

From LKR 180,000

Audit and rescue

An inherited codebase nobody wants to open. I read it, write you an honest report on what is salvageable, and quote the repair separately.

From LKR 45,000

APIs and integrations

Payments, messaging, accounting, logistics — joined up and monitored.

From LKR 60,000

Dashboards and internal tools

The screens your team lives in all day, built to stay fast as the data grows.

From LKR 95,000

Mobile apps

One codebase, both stores, shipped with the release pipeline attached.

From LKR 150,000

Fractional engineering lead

A day a week: architecture, code review, and help hiring your first two engineers.

Not on the list?

Most of my work starts with a question that does not fit a menu. Send yours over and I will tell you honestly whether I am the right person.

Ask me on WhatsApp

Selected work

Things that shipped, and what they changed.

Eight frames from the last two years, then three builds in detail.

Two engineers reviewing a release together at a shared desk.
Release review · Ledgerly
A hand holding a phone showing a revenue dashboard, a laptop open behind it.
Revenue dashboard · Mereva
A team working together in an open studio with a whiteboard behind them.
Discovery week · Northwind
A developer at a two-monitor desk with code open on both screens.
Build sprint · Talentpool
A wide monitor on a dark desk showing an interface design file.
Design handoff · Cadence
Pencil wireframes of app screens sketched across a sheet of paper.
First sketches · stackroot
A hand drawing a system diagram on a whiteboard.
Architecture session · Mereva
A phone resting on a wooden desk showing an app home screen.
Storefront build · Ledgerly

Case studies

  1. 01
    Two engineers reviewing a release together at a shared desk.

    Ledgerly — Invoicing that small studios actually finish

    Six screens cut to two, and the whole flow rebuilt around the twenty seconds a designer has between calls.

    • Node
    • Postgres
    • Stripe

    -70%time to raise an invoice

  2. 02
    A team working together in an open studio with a whiteboard behind them.

    Northwind — Field operations, finally off paper

    An offline-first app for crews with no signal, syncing the moment a van comes back into range.

    • React Native
    • SQLite
    • Go

    +180%jobs logged per day

  3. 03
    A developer at a two-monitor desk with code open on both screens.

    Talentpool — A hiring dashboard built in one month

    Scoped on a Monday, launched four weeks later, and still running unchanged eighteen months on.

    • TypeScript
    • Supabase
    • Vercel

    4 wksfrom idea to launch

Trusted by teams at

References

What it is like to work with me.

Four clients, all reachable — ask me for an introduction and I will make it.

Arjun rewrote an invoicing flow we had failed to fix twice. He spent the first week reading and asking questions, which was infuriating until the estimate landed and turned out to be right to the day.
Imran Haniffa
Imran HaniffaHead of Product, Ledgerly
We had four weeks and no engineering team. He scoped it on the Monday, demoed something real on the Friday, and we launched on time. Eighteen months later nothing has needed touching.
Shanika Weerasinghe
Shanika WeerasingheFounder, Talentpool
Our crews work in places with no signal, which every other quote treated as a footnote. Arjun treated it as the whole problem. Job logging is up by more than half and the paper forms are gone.
Piyal Gunawardena
Piyal GunawardenaOperations Director, Northwind
He told us we did not need the rebuild we had asked him to quote for, and sold us two weeks of repairs instead. That is why we have hired him three times since.
Hasini de Silva
Hasini de SilvaChief Technology Officer, Mereva

Contact

Tell me what you are building.

A paragraph is plenty. I reply to everything within one working day, usually sooner.

Nothing is stored on this page. Sending opens WhatsApp with your message already written, so it lands in one place and gets answered there.

  • arjun@mehta.studioEmail, replied within a day
  • Colombo, Sri LankaMehta Studio