A defined process from enquiry to handover
Our delivery process is intended to make the required outcome, responsibilities, cost and approval points clear before and during a project.
1. Initial enquiry
The client provides a summary of the requirement, intended users, existing systems, desired timeframe and known constraints. We review whether the request fits our services and current capacity.
An initial discussion is exploratory and does not create a commitment to provide services.
A defined path from first enquiry to handover
Outcomes, responsibilities, costs and approval points are made clear before and during the project.
2. Discovery and assessment
For a straightforward request, we may be able to proceed directly to a proposal. More complex or uncertain work may require a paid discovery stage to examine workflows, technical dependencies, data requirements, risks and priorities.
3. Proposal and scope
We prepare appropriate project documentation describing:
- the agreed objectives;
- deliverables and exclusions;
- delivery stages and assumptions;
- client and supplier responsibilities;
- fees and payment schedule;
- change-control arrangements;
- testing and acceptance approach; and
- support or handover provisions.
4. Project commencement
Chargeable work begins after the required documents have been accepted and any initial payment or onboarding requirements have been completed.
Where relevant, access to systems, code, documentation, test environments and third-party accounts must be authorised by the client.
5. Design and development
We complete the work in agreed stages. The client provides timely information, decisions and feedback. Progress reviews may include demonstrations, written updates or review access to a development version.
6. Testing and acceptance
The software is tested against the agreed scope. The client may also complete user acceptance testing and confirm whether the stated acceptance criteria have been met.
Issues are assessed to distinguish defects within scope from new or changed requirements.
7. Release and handover
Deployment assistance, documentation, access transfer and knowledge handover are provided as stated in the agreement. The party responsible for the live environment and ongoing operation is identified before release.
8. Ongoing support
Continuing support is optional unless included in the original contract. If required, it is provided under a defined maintenance plan, retained allocation or separately approved work order.
Change control
Software requirements can change during delivery. When a requested change affects the scope, cost, timing or technical approach, we record the change and provide its likely impact. Work on the change begins only after approval under the agreed change-control process.
Invoicing and payment
Invoices are issued according to the applicable proposal or agreement. Depending on the project, payment may be required in advance, at agreed milestones, monthly for time-based work or on another documented schedule.
We do not request payment to an account that has not been formally identified through our business communications. Clients should verify any unexpected request to change payment details by contacting us through info@dmacapitalsuk.com.
Intellectual property
Ownership and licensing of project materials, software, pre-existing tools, third-party components and client-provided content are stated in the relevant contract. No transfer of intellectual property should be assumed outside those written terms.
Start a Project Enquiry