Development
Applications, platforms and internal tools for processes that need a purpose-built solution.
What’s included
- Process analysis, requirements and architecture before development.
- Interface, application logic, data and integrations within the agreed scope.
- Testing, documentation and launch against defined acceptance criteria.
Outside the scope
Scope, source-code handover and support are agreed in writing. Applicable taxes, infrastructure, licences and API usage are separate.
Planning
Schedule and quotation after reviewing requirements, dependencies and technical feasibility.
Define a software project that can be accepted and handed over
Start by describing the users, the task they need to complete and the systems that already hold your data. A purpose-built application can bring these steps together when the agreed requirements call for custom development. Technical feasibility and dependencies are reviewed before a delivery schedule or quotation is agreed.
What to prepare
Bring a description of the current process, sample inputs without confidential information, the systems involved and the outcome you need to verify. Identify who can approve requirements and who will use the software. This makes scope, dependencies and exclusions explicit.
What to agree before delivery
Agree observable acceptance criteria for important user journeys, data handling and integrations. Testing, documentation, launch, source-code handover and support follow the written agreement. Infrastructure, licences, taxes and API usage are separate costs.
Prepare software requirements and acceptance criteria