Skip to content
RSRANJEET SAINI

Software & Product Strategy

Software that fits the way a business actually works

I think about software as a product first: a specific user, a specific job, a workflow it fits into and economics that make sense. AI is a capability inside that — powerful, but never the point.

Areas

What I focus on

SaaS products

Vertical, workflow-deep subscription software with sensible unit economics from day one.

Digital products & platforms

Web and mobile-first products designed around how people actually work — often on a phone, often multilingual.

Business automation

Removing repetitive steps with reliable software, and adding AI exactly where inputs are messy.

AI as a capability

Models as replaceable components inside a product, never as the product itself.

Integrations

Being where users already work: accounting tools, CRMs, messaging, payments, ERPs.

Product strategy

Choosing the wedge, scoping the MVP, sequencing the roadmap and deciding what not to build.

Process

How a product comes together

The same order every time, because skipping a step is how products get built that nobody uses.

  1. 01

    Understand the workflow

    Interviews and observation before any design. The goal is to see where time and money actually go.

  2. 02

    Define the thinnest complete product

    One user, one job, end to end. Metering, logging and correction built in from the start.

  3. 03

    Choose boring architecture

    Standard web stack, relational database, queue for slow work, thin layer around any AI provider.

  4. 04

    Ship to pilots, measure, iterate

    Activation, retention, cost per action and correction rate — the numbers that tell you if it works.

Principles

Beliefs that shape every build

Depth in one workflow beats breadth across many features.
Deterministic code guards money, permissions and compliance; AI handles the messy steps.
Design for correction — users forgive a wrong suggestion, not a wrong action.
Measure cost per action as seriously as revenue per user.
Build to swap: models, providers and vendors will change.
Honest status labels — idea, research, MVP, in development, live — on everything.

Planning a software product?

Let's talk through the wedge, the MVP and the economics before you write a line of code.