Custom software makes sense when off-the-shelf tools cannot support a critical workflow or staff repeatedly copy data between systems. We compare configuring a ready-made product, integrating existing tools and building a dedicated system before choosing the scope.
What is included
- A workflow map with roles, statuses, exceptions and acceptance criteria.
- Staff and customer interfaces, a database and agreed access controls.
- Website, CRM or accounting integrations after checking API documentation and access.
- Agreed source code, deployment instructions and an access handover plan.
How we work
- Review a real process from incoming request to completion and define what needs improving.
- Agree roles, fields, a prototype and the first release; separate later features.
- Build and demonstrate workflows; check permissions, calculations and integration failures.
- Migrate agreed data, reconcile it with the responsible team member and launch. Agree maintenance separately.
How we estimate cost
Cost depends on business rules, user roles, integrations and source data quality. A customer status portal is a different scope from a multi-branch order and stock system. Discovery, development, migration and support are estimated separately; timing follows the agreed first release.
What to bring to the conversation
Share a process description, anonymised spreadsheet or report, user roles and current tools. Do not send passwords or customer personal data in the brief. A finished technical specification is not required to start.