ABOUT
Adesh Lande
Software Developer · Product Builder
I am Adesh Lande. I design and build practical software systems for businesses — from billing screens and inventory flows to multi-tenant architecture, accounting engines and operational platforms.
Most of my work is business software that has to be right rather than impressive: a bill that has to print, stock that has to reconcile, a ledger that has to close. That constraint is what makes it interesting — the design space is real operations, not a design system.
I LIKE SOFTWARE THAT HAS CONSEQUENCES IN THE REAL WORLD.
I am interested in systems where software is not just displaying information — it controls an actual operational process.
Those relationships are the interesting part. Getting them right is most of what building business software actually is.
Six rules that decide how a system gets built.
Not opinions about frameworks. These are the decisions that determine whether business software still works in year three.
- 01
Software starts with the business flow.
Understand what actually happens at the counter, the warehouse, the office or the hotel before designing tables. The schema is a consequence of the operation, not the other way round.
- 02
Accounting should happen automatically.
A business event should generate its accounting consequence at the moment it is recorded. If someone has to re-enter the day into accounts later, the system is only half built.
- 03
Data belongs to the tenant.
Every system is designed with tenant isolation from the first migration. Scope is resolved server-side from credentials, never from something the client sends.
- 04
Offline is not an afterthought.
Operational software has to survive an unstable network. Queued operations with idempotency keys are cheaper to design in than to retrofit after the first lost day of billing.
- 05
The UI should reduce work.
A billing operator using software for eight hours a day does not need decorative animation. They need fewer keystrokes, predictable focus order and a screen that does not move under them.
- 06
Architecture should survive growth.
A system designed for one business should have a visible path to ten and a hundred. Usually that means shared infrastructure — accounting, identity, workflow — instead of a fork per customer.
What I actually work with.
Listed as a matrix because that is what it is — a set of tools applied to a set of problems, not a scoreboard.
FRONTEND
06- Flutter
- Flutter Web
- TypeScript
- React / Next.js
- Responsive UI
- Operator-speed forms
BACKEND
06- Node.js
- REST APIs
- Authentication
- Multi-tenancy
- Background processing
- Idempotent posting
DATA
06- MySQL
- PostgreSQL
- Neo4j
- Redis
- IndexedDB
- Schema & migration design
ARCHITECTURE
06- Multi-tenant SaaS
- RBAC
- Offline-first
- Accounting integration
- Inventory systems
- Real-time workflows
INFRASTRUCTURE
06- Windows Server
- IIS
- Linux
- SSL
- Reverse proxy
- Deployment & rollout
EXPLORING
05- AI agents
- Voice interfaces
- Graph systems
- Vector search
- Business automation
Varad Software builds practical custom business applications and ERP systems for operating companies — hotels, distributors, contractors, agencies and processors. The work is mostly the unglamorous kind: billing that has to be right, stock that has to reconcile, and accounts that have to close.
Most of the systems on this site were designed and built under Varad Software. The company builds them; this page is about how they are put together.
HAVE A SYSTEMTHAT NEEDS BUILDING?
The most useful first message describes the operation, not the technology — what happens at the counter, who has to approve it, and what currently goes wrong.