Custom software development for the process nobody sells software for

Soham Dang builds custom software for businesses whose process does not fit an off-the-shelf product — internal platforms, workflow systems and admin tools, built on React, Node.js and MongoDB.

Most companies do not need custom software. Off-the-shelf tools are cheaper, better tested and someone else maintains them. That is the honest starting position.

Custom becomes the right answer at a specific point: when the process is the competitive advantage, when the licence cost across many seats exceeds the build, or when the work of gluing five products together has quietly become someone's full-time job.

When custom is genuinely cheaper

  • Per-seat licences across a large team

    Ten tools at a few dollars per user per month is a permanent cost that scales with headcount. A built system is a one-off cost that does not.

  • Manual work between systems

    If someone exports from one product and imports into another every week, that salary cost is the real price of the current setup.

  • A process no product models

    Bending your operations to fit a tool's assumptions has a cost too. It is just harder to see on an invoice.

  • Data you cannot get out

    Reporting that spans products you do not control is a permanent tax on every question anyone asks.

When it is not

Accounting, payroll compliance, CRM at small scale, email — these are solved problems with well-tested products and regulatory requirements you do not want to own. Building them yourself is expensive and worse.

The rule of thumb: build the part that is specific to how you work, buy the part that everyone does the same way, and integrate them properly.

What a build actually involves

  1. Map the current process

    Including the spreadsheets and the WhatsApp threads. The unofficial parts are usually where the real requirements are.

  2. Model the data

    Entities, states and permissions written down before any code, because these are the decisions that are expensive to change later.

  3. Build the foundation

    Authentication, roles, deployment and monitoring first. Every module after is cheaper once these exist.

  4. Ship module by module

    One complete, usable module at a time, so people are using the system while the rest is built rather than after.

  5. Hand over properly

    Documentation, admin access and a system a different developer can pick up.

Evidence

Avani Business OS is the largest example: a 25+ module platform covering tasks, projects, meetings, leads, expenses, assets, billing, KPIs, finance, email CRM and a full HR suite, which replaced more than ten separate internal tools and is used daily by 10,000+ people.

The HR portion alone digitised onboarding, leaves, payroll and salary slips, removing more than 20 hours of manual work per week. Payroll generates salary slips directly from attendance and leave data rather than from a spreadsheet someone maintains by hand.

Common questions

What is custom software development?

Building software specifically for one organisation's processes, rather than buying a general product. It makes sense when the process is unusual, when per-seat licence costs across a large team exceed a build, or when staff are manually moving data between disconnected tools.

Is custom software cheaper than off-the-shelf?

Sometimes. A build is a larger up-front cost and a smaller recurring one, so it wins over time at scale — particularly where a system replaces several subscriptions at once. For a small team using a well-fitting product, off-the-shelf is almost always cheaper.

How long does custom software take to build?

It depends on scope, but the sequence is consistent: map the process, model the data, build the foundation, then ship one usable module at a time. That means people are using the first module while later ones are still being built, rather than waiting for everything.

What happens if the developer leaves?

That risk is managed by documentation, conventional architecture and admin access being handed over — not by hoping. A system built on standard React, Node.js and MongoDB with written decisions can be picked up by another developer.