Customer-facing products
Storefronts, marketing sites and mobile apps that carry a brand and take money — fast on a mid-range phone, and still fast a year later.
- Next.js · React
- React Native · Expo
- Shopify headless
- Cloudflare Workers · R2
Software Labs · Bengaluru
We build the systems a company runs on — the storefront that takes the order, the console that tracks it to commissioning, the app people open every morning. Bengaluru, working with founders and operators across India.
What we build
Storefronts, marketing sites and mobile apps that carry a brand and take money — fast on a mid-range phone, and still fast a year later.
Enquiry to commissioning to renewal on one record every department shares, replacing the spreadsheets and the WhatsApp threads between them.
Infrastructure declared in the repository, a staging environment that matches production, and a pipeline that refuses a bad release before anyone sees it.
Selected work
One curated product — the Origin Box, five single-origin coffees from Coorg estates. A static site that behaves like a shop: stock, cart and checkout are real, and nothing waits on a server we have to keep awake.
Internal system
2026
A company that sells capital equipment and then services it for years. Enquiry, order, commissioning and AMC now sit on a single record that sales, back office, finance and the service floor all share.
Mobile product
2026
A runner posts a run — a date, a place, a distance, a pace — and the people who match it ask to come along. Everyone on a run shares one thread, the run is recorded as it happens, and a year of those recordings becomes a runner's own history.
How we work
Push to dev is staging, a release to main is production, and both wait on lint, types, the unit suite, the browser suite and a real build. A deploy is a consequence of a green pipeline, never a person at a terminal on a Friday.
Table types are generated from the live database. When a column changes under the code, the typecheck fails on the branch instead of a page failing in front of a customer.
What someone may see is applied where the data is fetched, not filtered on the way out. A record out of reach is missing rather than refused — a refusal confirms it exists.
Infrastructure, content and permissions are declared in the repository and reviewed as changes. A year later the answer to why something behaves that way is in the history, not in anyone's head.