Spring 2026.

Not every business needs custom software. Here's an honest framework for figuring out if yours does.

I turn down projects regularly.

Not because we're too busy, but because bad-fit software projects waste everyone's time and money. The client ends up with something they don't use. We end up with a case study we can't be proud of.

So here's the framework I use before taking on any project:

You don't need custom software if:

• → Your process is simple and an off-the-shelf tool already covers it
• → You're pre-revenue and still figuring out your model — build the business first, then systematize it
• → The problem you're solving changes every few weeks — software needs stable problems to be worth building

You do need custom software if:

• → You're managing a process that touches multiple people and has several handoff points
• → You're running critical business data through Excel or WhatsApp, and it's costing you accuracy or speed
• → You've outgrown a generic tool and you're hacking it to do things it wasn't built for
• → You have a competitive advantage you want to protect, and your current vendor owns your data

The sweet spot:
A process you run repeatedly. That costs you real money or time when it breaks. That won't change fundamentally for the next 1 to 2 years.

That's the project worth building. Everything else, wait.

I'm sharing this because most agencies won't tell you when you don't need them. I'd rather have an honest 20-minute conversation that saves you ₹50,000 than take a project that shouldn't exist.

If you have a process you're not sure about, DM me. I'll tell you straight whether it's worth building or not.

No pitch. Just an honest answer.

Day 8 of my 30-day build-in-public series; sharing what I'm building at ViberNet and OpenLoop every day.