
Building Fintech That Reconciles to the Paisa
Ledgers, idempotency and daily reconciliation. The unglamorous engineering that separates fintech products that survive audit from those that do not.
What we have learned shipping AI systems, SaaS platforms and industry software — including the parts that went wrong. Written by Purushottam Kumar Suman.

Big-bang rewrites fail for reasons that are structural, not managerial. How to route traffic away from a legacy system feature by feature, reversibly.

Ledgers, idempotency and daily reconciliation. The unglamorous engineering that separates fintech products that survive audit from those that do not.

Most SaaS churn happens before anyone uses the product properly. How to find the moment people stop, and design the path to first real value.

Not a cheap version of the product and not a prototype. An MVP is an experiment with a hypothesis — and most of the value is in what you agree not to build.

The demo impressed everyone and then the project quietly died. Here is the pattern behind it, and the four things that separate pilots that ship from pilots that do not.

N+1s, missing indexes, unbounded results and the ORM conveniences that quietly stop scaling. Diagnosis and fixes with the reasoning behind them.

Clinical software fails on click count, not features. Designing for short consultations, constant interruption and staff who will route around friction.

Every user sees the empty state before they see the full one. Designing the zero-data, error and loading screens that decide whether people continue.

Teams reach for fine-tuning when they need retrieval, and for retrieval when they need neither. A practical decision framework based on what each technique actually changes.

How to assess technical skill you cannot evaluate directly, what to test for, and the hiring mistakes that are hardest to undo at small scale.

Rolling releases are the easy half. The hard half is database migrations, and that is where most 'zero-downtime' pipelines quietly fail.

Getting data off the plant floor is the easy part. Turning it into decisions about downtime, yield and maintenance is where the value is.

In India the median user is on a mid-range device with variable connectivity. What that means for images, fonts, JavaScript and interaction design.

Without scored evaluation, prompt engineering is superstition. How to build a golden set, choose metrics that mean something, and wire it into CI.

Building what you should buy wastes a quarter. Buying what you should build caps your ceiling. Four questions that settle it.

Beyond the discourse: where the rendering boundary belongs, what it does to bundle size and data fetching, and the mistakes that follow from misplacing it.

Customers do not need a precise arrival time. They need one they can trust. Building ETAs that account for reality, and communicating uncertainty well.

Semantics, focus order, contrast and keyboard paths cost little during the build and a great deal afterwards. A practical WCAG AA working method.

AI features that work but cannot be afforded get switched off. Caching, model tiering, context discipline and per-tenant budgets — with the numbers that matter.

Overruns are usually scoping failures, not engineering ones. What to pin down before a quote, and the questions that surface hidden work.

Additive change, deprecation policies you can enforce, and usage telemetry that tells you when it is genuinely safe to remove an endpoint.

Teachers are the most time-poor users in any system. Why tools that add preparation work fail regardless of quality, and what removing work looks like.

Roadmaps built from the loudest request produce products nobody loves. A method for weighing requests against usage, revenue and cost of delay.

Autonomous agents make compelling demos and unnerving production systems. Where agents genuinely earn their place, and the boundaries that make them safe.

How to keep ownership of your product, code and knowledge while an external team builds it — from a company that takes this work.

Networks retry, users double-click, queues redeliver. The single most valuable defensive pattern for any endpoint that moves money or creates records.

Overselling, dead capital and cancelled orders all trace to the same cause. Building a single authoritative stock position that every channel respects.

Confusion converts worse than a high price. Structuring plans, choosing the value metric, and removing the questions that stall a decision.

Hallucination is not a model defect to wait out. It is a systems problem with known mitigations — retrieval, structure, refusal design and citation.

The question is not which is better but which fits the shape of the work. Duration, specialisation and the cost of a wrong hire.

Alert on symptoms users feel, trace the requests that matter, and log for the question you will ask at 2am — not for completeness.

Straight-through processing for the simple majority, humans for the rest. Drawing the boundary so speed does not become an unmanaged liability.

Most design systems decay into a component library nobody follows. What makes tokens, documentation and governance actually hold as a product grows.

The choice is rarely about raw capability. It is about cost at your volume, data residency, latency and who is responsible when the endpoint is down.

The right architecture at eighteen months of runway is the wrong one at five. Matching technical decisions to the time you actually have.

A flaky suite is worse than no suite, because it teaches the team to ignore red. How to build coverage that earns confidence and keeps it.

Most agritech fails on assumptions about connectivity, literacy and device quality. Building for the conditions farmers actually work in.

Day-one experience predicts day-thirty retention better than functionality does. What to fix first when people try the product once and never return.

Version control, review, tests and staged rollout for prompts. The engineering hygiene that turns prompt tinkering into a repeatable practice.

Equity is the most expensive currency a founder has. When a technical co-founder is right, and when a partner or a hire serves you better.

What to cache, where to put it, and how to invalidate without serving stale data — plus the stampede that takes systems down at exactly the wrong moment.

Site software fails on ergonomics before it fails on features. Designing capture that takes seconds in sunlight, with gloves, offline.

Button labels, field hints, confirmations and error messages. The smallest text in the product does the most work at the moments that matter.

Invoices, statements and forms in every layout imaginable. A practical pipeline for extraction with confidence scoring and a human path for the rest.

Fixed price feels safe and creates incentives that damage the product. When it works, when it does not, and the middle ground that usually does.

Some debt is a rational trade and some is compounding interest. How to tell them apart, and how to argue for repayment in terms a business will fund.

Citizen services cannot choose their users. Designing for old devices, low literacy, multiple languages and people with no other option.

A week of prototyping routinely saves a quarter of building. What to prototype, at what fidelity, and how to test it so the answer is trustworthy.

An AI company arguing against AI. The situations where a rule, a query or a form beats a model — and how to tell before you have spent the budget.

Automating before you understand the workflow builds the wrong thing efficiently. Why doing it by hand first is an engineering strategy, not a stopgap.

If one of these describes a problem you have,
bring it to a call and we will talk it through.