Skip to content
About Oadbox

The alternative to a stack nobody designed.

We pick industries where the existing software is old, expensive or absent — then build the system that industry should have had all along, and run it ourselves.

1,000+
businesses running on it
12
products in market
8
industries served
100%
designed and built in-house

Most Indian businesses run on a stack that nobody designed: a decade-old desktop package for accounts, spreadsheets for everything it cannot do, WhatsApp for approvals, and one person who understands how the pieces connect.

We build the alternative one industry at a time. Today that is 12 products across eight industries — schools and colleges, hospitals, real estate developers, lenders and chitfunds, multi-branch retailers, fleet operators and process manufacturers — plus the monitoring, SEO and AI tools the rest of them depend on.

Every one of them was designed, built, shipped and is supported by the same in-house team. No outsourcing, no white-labelling, no reselling someone else's platform under a new logo.

We do occasionally put money behind a company we did not build. Those are investments, not products — someone else's team, someone else's roadmap — and they are kept where they cannot be mistaken for the portfolio, on ventures.

It works because the products are not really separate systems. They share one core — tenancy, permissions, statutory tax, mobile sync, audit logging, reporting — so the effort goes into the part that is genuinely different about running a hospital versus running a fleet.

House rules

Five things we do not put to a vote.

EntryIn-house · India
01

We run what we build

The people who wrote it are the ones on the line when it misbehaves at 11pm. That shows up in what we are willing to release.

02

Compliance nerds

GST, TDS, PF, ESI, RERA. The parts most software pushes into an export for finance to fix by hand, we treat as product surface.

03

Built for bad wifi

Shared devices, networks that drop for an hour, staff who did not ask for a new system. It works there or it does not work.

04

Month-end people

We design for the week when payroll, filing and closing all land together — not for a demo on a quiet Tuesday.

05

We answer the phone

Support reaches someone who can read the code and ship the fix. There is no tier one standing in the way.

Entries 01–05 · unchanged since day one
Principles

What we believe

Four positions that decide what gets built, what gets refused, and what we are willing to keep running afterwards.

Verticals beat horizontals

A hospital does not want a database with a healthcare template. It wants a system that already knows what an IPD transfer is, what a package tariff does to a bill, and why the pharmacy counter cannot wait four seconds for a page.

Compliance is a feature, not a footnote

GST, TDS, PF, ESI, RERA and ABDM are where Indian software usually breaks — pushed to an export that finance fixes by hand every month. We treat them as first-class product surface.

Software has to survive the field

Bad networks, shared devices, and staff who did not ask for a new system. If it only works in the demo, on good wifi, with the person who championed it standing there, it does not work.

Owning it beats shipping it

We run what we build. That changes what you are willing to put in — nobody ships a fragile feature when they are the one who gets the call at month end.

Eleven products, already running. One of them probably fits how you work.

See it on your own data rather than in a slide deck — thirty minutes with someone from the product team.