Case studies

What we have built, and the problems it solved

Eight platforms across legal and compliance, logistics, healthcare and AI — each written up the same way, so you can compare them.

How to read these

Every case study here follows the same four parts: the problem in the client’s own operational terms, what we built, the product as it shipped, and who we built it with. They are written from the work rather than from a brief, so the detail is about decisions and trade-offs, not adjectives.

Where a performance figure is not shown, it is because the client has not published one. We would rather leave a gap than estimate.

These eight are the projects with the most depth. The full list of everything we have shipped is on the portfolio page.

Legal

Contract review, document processing and access to the right professional.

Logistics

Allocation, dispatch and tracking that stop depending on one planner’s memory.

Finance and compliance

Verified professionals and the statutory workflows that sit behind them.

Healthcare

Joining up providers and programmes that were keeping separate records.

AI

Speech, language and assistance where the interface is the conversation.

All eight at a glance

Every TechOTD case study, its sector and what was built
ProjectSectorWhat we built
LexMate Legal AI drafting and first-pass contract review working from the firm’s own templates and precedent, with clause extraction and compliance checking built into the review step.
Legal Drishti Legal Document processing and research over uploaded paperwork, plus a directory of legal professionals to take the matter on — one flow from document to the right person.
Nexa Move Logistics AI-assisted route planning, automated dispatch with the reasoning recorded against each allocation, real-time tracking and performance analytics.
WeParcel Logistics Real-time parcel tracking visible to both seller and customer, order management shaped around e-commerce dispatch, and automatic delivery status updates.
CAONWEB Finance and compliance A directory of verified chartered accountants and company secretaries, with service workflows for company formation, GST registration, income tax filing and trademarks.
Dr. Khokha Healthcare Appointment booking across doctors, labs and hospitals, teleconsultations, medical records that follow the patient, and diagnostic lab integrations.
Health Boat Foundation Healthcare One portal covering outreach programmes, emergency response, digital health access and community education, with records of what was delivered where.
VoxaAI AI An Android voice assistant with recognition tuned for accents and noise, context carried across multi-turn exchanges, and responses generated over LLM models.

Patterns that repeat across this work

Different sectors, but the same handful of problems keep turning up. These are the ones we have solved more than once.

Verified marketplaces

CAONWEB and Legal Drishti arrived with the same complaint: a client could not tell who was actually qualified before engaging them. Both answer it with credential verification and routed enquiries rather than a list of names.

Documents that become searchable

LexMate and Legal Drishti both turn a stack of PDFs into extracted terms you can query. The work that used to mean opening files one at a time becomes a question you can ask.

Dispatch that is not in one person’s head

Nexa Move and WeParcel both replaced an allocation list held by a planner. The system records why each decision was made, so the operation keeps running when that person is away.

Coordination across providers

Dr. Khokha and Health Boat Foundation both join up parties that were keeping separate records, so the history follows the patient or the programme instead of the paperwork following the person.

The problem each one started with

None of these began as a request for software. They began as something that was not working, described by the people it was not working for. This is the short version of each.

LexMate

First-pass contract review is mechanical work being done by expensive people. The queue builds, the business chases, and the real risk is that something gets waved through because nobody had time to read it properly.

Read the case study →

Legal Drishti

Two slow steps start every matter: working out what the paperwork actually says, and finding a professional who genuinely handles that kind of case. Both were being done by asking around.

Read the case study →

Nexa Move

Allocation depended on the planners who knew which driver suited which lane. None of that was written down, so allocation stalled when those people were away and nobody could explain afterwards why a load went the way it did.

Read the case study →

WeParcel

The seller could not say where a parcel was, so the customer rang to ask, and dispatch was working from a list that had already gone out of date. Every one of those calls was time that should have moved the next consignment.

Read the case study →

CAONWEB

Finding a qualified compliance professional came down to local contacts. Clients could not confirm credentials before engaging, and professionals outside the major metros had no way to reach anyone beyond their own city.

Read the case study →

Dr. Khokha

A patient journey touches several providers that do not share records. Booking happens in one place and diagnostics in another, so the patient carries the paperwork between them and clinicians work without the full picture.

Read the case study →

Health Boat Foundation

Outreach programmes, emergency response and education initiatives were run and recorded separately. Without one system the organisation could not see what had reached which community, and coordinating a response meant working the phones.

Read the case study →

VoxaAI

Voice assistants break where people actually use them. An accent or a noisy room defeats the recognition, every request is treated as if the last one never happened, and a pause long enough to notice turns a conversation into a form read out loud.

Read the case study →

What you will find in each write-up

  • The problemStated in the client’s operational terms — what was slow, who was blocked, what it cost them in time — rather than in ours.
  • What we builtThe actual list of what shipped, not a capability statement.
  • The productA short walkthrough of the working software. Present on LexMate, Legal Drishti, Nexa Move and WeParcel; the other three are documented in writing.
  • Client, sector and who built itRecorded at the top of every page, so there is no ambiguity about whose work it was.

These eight are the ones with that depth. The shorter entries for everything else — twenty-nine web applications and eight mobile apps — are in the portfolio.

Questions we get about this page

Why are there no performance figures here?

Because the clients have not published any. Every number on this site has to come from the people who own the data, and where that has not happened we leave the space empty rather than estimate. If a particular figure would change your decision, ask on a call and we will tell you what we are able to say.

Can I see any of these actually working?

Four of the eight carry a product walkthrough on their own page — LexMate, Legal Drishti, Nexa Move and WeParcel. For the other three, CAONWEB, Dr. Khokha and Health Boat Foundation, the write-up is text only.

Do you only build in these five sectors?

No. These five are simply where the write-ups go deepest. The industries page lists eighteen sectors we have shipped in, and the portfolio has the shorter entry for every project, mobile apps included.

We are in a different sector. Is any of this relevant?

The four patterns above travel further than the sector labels do. Verified marketplaces, documents made searchable, dispatch that does not live in one person’s head, and coordination across providers turn up in businesses that look nothing like each other. Tell us the problem rather than the industry and we will say whether we have solved its shape before.

How these projects run

Each of these started as a scoping conversation and ended as something in production. If you want the detail of how we get from one to the other — discovery, build, deploy and support — that is written up on how we work.

For the shorter write-ups of everything else we have shipped, including the mobile apps, see the portfolio.

Building something similar?

Thirty minutes with the people who would actually build it. You leave with a scope and a timeline.

Let's discuss your project!

Hear from the teams we've built products for

Tell us what you need, and we'll get back with a cost and timeline estimate