Skip to content
SKSuraj Kumar

Development

Business software built to survive its second year

Operational systems where the difficult parts are the ones nobody demos: tenant isolation, approval chains that hold under delegation, stock that cannot be double-promised, and a ledger that still reconciles after a partial payment.

Case studies
9 platforms
Domains
Sales, HR, finance, operations
Stack
Next.js, TypeScript, PostgreSQL
Technical preview
Behind a shared keyword

The platforms

9 case studies · project type stated on every card

Read the Eluno case study
Reconstruction
01MSME operationsSoftware

Eluno

Business software for small enterprises

Business software for a small enterprise that had outgrown notebooks and WhatsApp but was never going to buy an ERP.

MSMEBusiness softwareClient project
Private client project

Foundations

Four decisions made before the first screen

They are unglamorous, and they are the reason a system can absorb a new requirement in month eight without a rewrite.

01

The schema is the product

Entities, states and the transitions between them are designed before any screen exists. Most business software that becomes unmaintainable got the data model wrong in week one and spent the next year working around it.

02

Rules live on the server

Permissions, approval thresholds and period locks are enforced on the write path. Anything enforced only in the interface is a suggestion.

03

History is append-only

Ledgers, movements and audit entries are added, never edited. A balance you cannot reconstruct is a balance you cannot defend in a dispute.

04

Money is integers

Amounts are held in minor units. Proration, percentage escalations and tax all produce repeating decimals, and floating-point drift in a finance system becomes a customer-facing error.

Stack

What these platforms are built with

Deliberately boring choices. A business system is a long-lived asset, and novelty is a cost its owner pays for years.

Product and application engineering
  • Next.js App Router
  • React with Server Components
  • TypeScript (strict)
  • Tailwind CSS design systems
  • Data tables, filtering and saved views
  • Accessible components and keyboard flows
Backend and APIs
  • Django and Django REST Framework
  • FastAPI
  • Node.js
  • REST API design and versioning
  • Authentication, sessions and JWT
  • Role and permission models
Data modelling and storage
  • PostgreSQL schema design
  • Multi-tenant isolation patterns
  • Append-only ledgers and derived balances
  • State machines and status invariants
  • Audit trails and effective-dated records
  • Query performance and indexing
Delivery and infrastructure
  • Docker and container builds
  • Google Cloud Run, Cloud Storage
  • Vercel deployment and edge caching
  • CI pipelines (GitHub Actions, Jenkins)
  • Environment and secret management
  • Logging, tracing and error reporting

Software engagement

Replacing a spreadsheet with something that scales?

Describe the process, who touches it and where it currently breaks. You will get a data model sketch, a technical approach and a timeline before any commitment.

Email
surajk86808@gmail.com
Based in
Bengaluru, India
Working hours
IST (UTC+5:30)
Availability
Taking new engagements