About OnePointDelta
I build software systems around how businesses actually work.
I’m Sachin, a software systems builder and the person behind OnePointDelta.
My work sits at the intersection of software engineering, product development, business operations, and AI. I’m interested in a simple problem:
How do we build software that reflects the reality of an organisation rather than forcing the organisation to adapt to the software?
Most businesses accumulate tools over time—CRMs, spreadsheets, messaging platforms, payment systems, internal dashboards, databases, and countless conversations between people. These tools capture fragments of the business, but rarely the system as a whole.
I build systems that connect those fragments.
One of those systems is running a practice today. NutriDesk is the system behind Mind Your Food, Khadija’s nutrition practice: a client books, follow-ups schedule against them, and the assessment and plan are built at the desk and publish straight to the client’s app. Before it, running the practice by hand sat alongside the clinical work — bookings, follow-ups, assessments and plan delivery all with her. That time now goes to her clients. The practitioner’s desk is on this site, and you can open it and use it.
What I build
I work on software products and internal business systems from the underlying architecture through to the interface and deployment.
That can include:
- Business operating systems
- SaaS products
- Internal operational platforms
- AI-assisted workflows
- Communication and knowledge systems
- Customer and sales systems
- Data and decision infrastructure
- Custom software for specialised businesses
The objective is not to add technology for its own sake.
It is to make the underlying operation more observable, coherent, and capable of improvement.
How I think about software
I don’t see software as a collection of screens.
I see it as a representation of a system.
A useful software system should understand:
what happens → why it happens → what depends on it → what should happen next.
That changes how I approach product development.
Before deciding what to build, I try to understand the operating model underneath it—the people, decisions, information flows, constraints, communication, and outcomes that make the organisation work.
Then the software can be designed around that reality.
Building in the AI era
AI changes the economics of software development, but I don’t think the most important change is simply that models are becoming more capable.
The more important question is:
What does an intelligent system actually have access to?
Business reality exists across conversations, decisions, documents, transactions, customer interactions, operational events, and human judgment.
When those signals can be connected into a coherent representation of the business, AI becomes substantially more useful.
This is why I’m particularly interested in the intersection of:
communication → context → business memory → intelligence → action.
I believe the next generation of business software will increasingly be built around this relationship.
Work
I have built and shipped software across different layers of the stack—from low-level systems and programming languages to complete production SaaS platforms.
This work reflects the way I like to work:
understand the system → design the architecture → build the machinery → ship the product.
OnePointDelta
OnePointDelta is the name I do this work under.
It focuses on building software systems for businesses whose operational reality cannot be adequately represented by generic software.
The name comes from an idea I keep returning to:
one point of change can produce a much larger delta in the system.
Good software should identify those points of leverage.
Not every problem requires more software.
Sometimes the right answer is to remove a system, simplify a workflow, reconnect information, or change the underlying model.
The goal is always the same:
build the smallest coherent system that creates the largest useful change.
What I’m working toward
I’m interested in a future where software is less about navigating applications and more about interacting with systems that understand the environment they operate in.
Where businesses don’t have to translate their reality into dozens of disconnected tools.
Where communication becomes structured organisational memory.
Where AI is not simply an assistant sitting on top of existing software, but an active layer capable of understanding, reasoning about, and operating within the systems underneath it.
That is the direction I’m exploring through OnePointDelta.
Build the system first. Make intelligence useful because the system already understands what it is operating on.
— Sachin
Founder, OnePointDelta