What building it yourself actually costs, once you count year two
Building is a legitimate choice, and we would rather you make it with the real numbers than discover them eighteen months in. The first version is not the expensive part. The expensive part is everything that has to keep working afterwards.
Where each one actually lands
Written to be usable in a meeting where someone has both options open. If a row reads as though we won it too easily, check it — we would rather you did.
| building it in-house | cabsoft.app | |
|---|---|---|
| Fit to your process | Exact, by definition. You build what you actually do. | Configured to your rates, roles, vendors and templates — close, but within a model someone else chose. |
| Time to first useful version | Months, realistically, for booking and dispatch alone. | Weeks, mostly spent agreeing rules rather than writing code. |
| Mobile apps | Two more products, two more release cycles, two app-store relationships. | Included, published under your brand. |
| Indian tax handling | Place of supply, reverse charge and FY numbering are subtle and unforgiving to get wrong. | Already built and already argued over with accountants. |
| The person who built it | Becomes critical infrastructure. Their notice period becomes a business risk. | Support is a contract rather than an individual. |
| Ongoing cost | Salaries, indefinitely. The system never stops needing someone. | A licence, and it stops if you stop. |
| Ownership | Complete. Nobody can raise your price or discontinue it. | You own your data; you licence the software. |
When building it in-house is the right answer
If one of these describes you, we are not the better choice today. Come back when it stops describing you.
Transport genuinely is your differentiator
If how you move people is the thing customers choose you for, and it is unusual enough that no product models it, build. Owning the thing that makes you different is worth paying for.
You already run a capable software team
If you have engineers, product management and a release process, the marginal cost is far lower than it is for an organisation that would be hiring from scratch.
Your requirements really are unusual
Some operations are strange enough that configuration cannot reach them. If you have honestly tested that rather than assumed it, building is the right call.
When we are the better choice
Transport supports your business rather than being it
A hospital, hotel or manufacturer building transport software is spending its scarcest resource — engineering attention — on something that will never be a competitive advantage.
You have not costed the apps
Most in-house estimates cover the web console. The driver and passenger apps are two more products with their own release cycles, and they are where the operational value actually is.
GST is not a feature you want to own
Place of supply, reverse charge and financial-year series are unglamorous, easy to get subtly wrong, and expensive when a client’s finance team rejects the invoice.
You need it before next quarter
Configuration finishes in weeks. A build that has to cover dispatch, tracking, two apps, pricing and invoicing does not.
Common questions
Can we start with you and build later?
Yes, and it is often the sensible sequence. Running on a configured system teaches you what your rules actually are — which is the expensive thing to discover halfway through a build.
Do we own our data?
Yes. Your trips, customers, drivers and documents are yours, and being able to leave with them is a reasonable thing to require of any vendor, including us.
What if we need something the product does not do?
Ask. Some things are configuration, some are genuine development, and some we will tell you we are not going to build. You are better served by a straight answer than by a maybe.
Bring us the case against
Tell us why you think the alternative wins for your operation. If you are right, we will say so.