The cost of custom software depends on what the system must do, who can change which records, what it connects to and what data it has to carry over. A single internal dashboard and a multi-team order system may have equally simple screens, but the order system takes more work to test and roll out.
Four things to put in the brief
- Workflow. Describe a real transaction from start to finish, including one exception such as a cancelled or partially fulfilled order.
- Access. List who can view, approve or export records, and who can change those permissions.
- Integrations and migration. Name the systems involved, who owns each account and which historical records must move.
- Handover. Ask who handles staff training, fixes after launch, hosting and future changes, and how each is priced.
Compare quotes against the same acceptance criteria
Give every provider the same example workflow and ask what users should be able to do by launch. For an inventory project, have them explain how they would demonstrate a partial delivery, a stock correction and the permission settings for both. Ask for separate line items for implementation, migration and recurring services so you can compare the scope behind the price.
Start with the workflow that costs your team the most time
Use a sample transaction to decide what to build first. My published starting price for Odoo implementation is from AED 12,000. The Blocktec case study shows an ERP implementation you can use to see how that kind of work is scoped. Custom software is quoted after reviewing the requirements.
Worked example
Blocktec Philippines: odoo erp case study. I mapped Blocktec’s handoffs and implemented Odoo Enterprise so sales, purchasing, inventory and project teams could work from the same records. The rollout took more than four months, with a phased go-live and handover to Blocktec’s team.
Want this mapped for your business?