Work
Client platforms we've shipped, and products we build for ourselves. Two so far — both still in active use, both still maintained by us.
BatteryCompany
Needed an e-commerce storefront that could handle a deep, brand-specific battery catalogue without forcing customers through a generic template.
The catalogue is organised across roughly 28 device brands rather than a flat product list, with a separate admin application for day-to-day catalogue and order management, and WhatsApp built in as a real ordering channel alongside standard checkout. Customer accounts, order tracking, and INR pricing were built in from the start rather than added later.
Blazor Server, ASP.NET Core, SQL Server
Read case study
SamToolkit
Wanted a set of everyday developer utilities that didn't require an account or send pasted data to a server.
Built entirely on Blazor WebAssembly so the tools run inside the browser after the initial download — no API calls, no logging, and it keeps working even if you disconnect from the internet mid-task. It currently ships 29 utilities across 7 categories, all free, with no account required.
Blazor WebAssembly
Read case studyOne stack, two very different builds
Both of these run on the .NET/Blazor stack we use for most client work, and both ended up on opposite hosting models for reasons specific to what they needed — BatteryCompany on Blazor Server for a catalogue-heavy storefront that benefits from server-rendered pages, SamToolkit on Blazor WebAssembly because its entire premise depends on nothing being sent to a server. Same tools, different tradeoffs, chosen deliberately rather than by default — more on how that reasoning plays out on the services page.
Why only two
We don't publish every project we've touched — a lot of client work is internal tooling or maintenance on systems we didn't design from scratch, which doesn't make for much of a case study. What's here is work we built end to end and can talk about honestly: what the actual problem was, what we chose to build, and why.
That's also why one is client work and the other is our own product: between the two, they cover most of what we actually do — a real e-commerce build under real operational constraints, and a product shipped with no client at all, built purely because we wanted it to exist. As that list grows, so will this page.