Client engagements
Work delivered for clients
Most of our engagements are embedded work on someone else's product, and a good number sit under a confidentiality agreement. We take that seriously enough not to trade on it for marketing — so no client names, no screenshots of their software, and no links to their sites.
What we can share is the engineering: the architecture, the constraints, the trade-offs and the reasoning. If you want references, we arrange those directly, with the client's permission.
Full-stack platform
Building a vacation rental platform that cannot double-book
A short-term rental operator was selling the same week twice across Airbnb, Vrbo and its own site. We made that structurally impossible.
Web application
Taking a home services business off the phone and the spreadsheet
Dispatch ran on a phone, a whiteboard and one very load-bearing spreadsheet. We replaced it with software that customers could see into.
Legacy modernisation
Modernising a ColdFusion application without rewriting it
A working ColdFusion application that nobody wanted to touch and nobody wanted to rewrite. We modernised the front of it and left the parts that were still doing their job.
Data pipeline & AI
Scraping 30+ retailers daily, and classifying what comes back
A daily scraping pipeline across 30+ retail brands, an AI classifier for what it collects, and a human in the loop where the classifier is unsure.
Our own products
Software we build for ourselves
These are OffSetup's own products, so there is nothing to anonymise and we can be specific — including about the mistakes. They are the honest answer to “what is your team actually capable of”, because every decision in them was ours to make and ours to live with.
Tax engine
A tax calculator, and the two defects we found in its own source data
We ported slab data from our own payroll engine, then re-checked it against the Finance Acts instead of trusting it. That found two defects — one worth Rs 142,500 at a single salary point.
Multi-tenant SaaS
A payroll SaaS where every tenant gets its own database
Payroll is the worst possible place for a cross-tenant data leak. So the isolation boundary is a separate database per tenant, not a column you can forget to filter on.
Multi-tenant SaaS
Two billing systems in one building management platform
Companies pay us per building; residents pay the company for their units. Conflating those two flows would be the single most expensive bug this product could have.
Marketplace
A job marketplace where a CV is never one URL away from the public
The most sensitive object in a job marketplace is the CV. Ours has no permanent URL at all — access is authorised per request and the link expires.
Recognise your own problem in one of these?
Most of what we do starts with a conversation about a system that works but is getting harder to live with. Tell us where yours hurts.