An illustrative workflow compares configuration, integration and custom development. Identify the constraint that needs your own software and plan its maintenance.
The spoken explanation, organised by chapter.
This accompanies our article on custom software. First establish which limitation of existing software your organisation needs to solve.
A fictional inspection service uses an existing product for customers and appointments. Its planner-to-inspector handover needs an additional check, currently tracked by employees in separate files.
Follow one assignment from preparation to handover. What information does each user need, who can change it, and when is the assignment ready for the next responsible person?
First investigate product configuration. Then examine a supported integration. Only a remaining relevant constraint establishes which part might justify custom development rather than replacing something that already works.
Perhaps only a review screen beside the existing product is needed. Customer management and scheduling can remain. The first version covers one complete user flow rather than rebuilding everything.
Ask intended users to complete the handover with permitted example records. Test missing information and limited permissions. A working demonstration does not establish support for everyday operational work.
Compare development with maintenance, dependencies and change costs. Agree who controls records, source code and configuration, and who must be able to resolve problems after the initial delivery.
Document the limitation and selected approach. Describe installation, access, data transfer and recovery, so another developer can understand the component and make controlled changes when required.
Custom development starts with a justified choice for your process. Our source article on custom software compares configuration, integration, new development and the responsibilities of long-term maintenance.
2:00An illustrative quotation tool shows how an MVP examines one assumption. Separate a working product, independent task completion and evidence of willingness to pay.
Source articleMVP development: test your product’s key assumption
2:00An illustrative recovery question separates missing evidence from a demonstrated defect. Make scope, impact, follow-up action and verification clear in an audit.
Source articleSoftware audit
2:00Follow customer details, work status and invoice data through three fictional systems. See why each integration field needs an agreed source and direction.
Source articleSoftware integrations for connected business applications