Build or buy scheduling software in Hyderabad?
Before the decision
Dispatchers handle site exceptions in spreadsheets beside a basic ticketing tool. An engineer can often recover from an impossible schedule by calling several technicians. Procurement needs to compare software against that actual workflow, including its hidden manual effort.
The problem
Should the team choose Build scheduler or Buy software for the next 12 months?
Decision owner: The business unit lead.
A purchased product may standardise work but constrain exception handling.
Option economics
Scroll the table to see all figures.
| Option | Volume (completed jobs) | ₹ per unit | Fixed cost | Net contribution |
|---|---|---|---|---|
| Build scheduler | 4,40,000 | 14 | ₹47 lakh | ₹14.6 lakh |
| Buy software | 4,15,000 | 12 | ₹32 lakh | ₹17.8 lakh |
Make the call
- Calculate net contribution for Build scheduler and Buy software. Which assumption makes the comparison most fragile?
- If the leading option delivers 10% fewer completed jobs, does your recommendation change?
- What evidence would you ask for before the team makes an irreversible commitment?
Reveal the worked solution
Start by validating Buy software. It contributes ₹17.8 lakh after fixed costs and leads by ₹3.2 lakh. Treat that gap as the amount of unmodelled cost or lost contribution the option can absorb before the ranking reverses.
- Frame the decision
Compare the cost of delivering a successful outcome, including exceptions and manual work. Check whether the operating team can run the new process.
- Calculate both options
Build scheduler: 4,40,000 completed jobs × ₹14 less ₹47 lakh in fixed costs gives ₹14.6 lakh. Buy software: 4,15,000 completed jobs × ₹12 less ₹32 lakh in fixed costs gives ₹17.8 lakh.
- Stress-test the forecast
Buy software leads by ₹3.2 lakh in the base case. If Buy software delivers 10% fewer completed jobs (3,73,500) at the same margin and fixed cost, it contributes ₹12.82 lakh. Holding the other option constant, the stressed result falls behind. This isolates volume risk. Check whether both options would respond to the same change in demand.
- Set a decision threshold
Holding the other option’s result fixed, Buy software needs at least 3,88,334 completed jobs to match or beat it under the model. Run the same failure scenarios in both workflows and log manual handoffs.
A purchased product may standardise work but constrain exception handling. Compare the cost of a limited test with the loss the business would face if the full commitment failed. Ask the team to agree the decision criterion before collecting more evidence.
What if the whole market moves?
The worked solution tests a change to one option at a time. Here, both options gain or lose the same percentage of volume. Unit contribution and fixed costs stay constant.
| Volume scenario | Build scheduler | Buy software | Higher contribution |
|---|---|---|---|
| Both lose 10% of volume | ₹8.44 lakh | ₹12.82 lakh | Buy software |
| Base assumptions | ₹14.6 lakh | ₹17.8 lakh | Buy software |
| Both gain 10% of volume | ₹20.76 lakh | ₹22.78 lakh | Buy software |
Explain which option you would take forward. Check whether capacity, price or customer mix would also change as the market moves.
Practise this case as an interview