Run it yourself
Take the files and documentation and carry on with no ongoing tie.
Ownership and handover
The project ends, and you stay in control after handover.
We do not lock you in. We hand over the project with its files and documentation per the contract, and then you choose: continue yourself, hand it to your team, hand it to another developer, or keep us on an annual support plan.
What you actually receive
Handover is not one file. These are the layers that can be part of it, depending on the project and its scope.
- The project The product or system in its final form, after we have tested it with you.
- Files and repository The code and the repository, as the contract sets out.
- Access Administrative accounts and permissions that fall inside the project scope.
- Documentation Operating guide, system map and the list of integrations.
- Deployment Transferable deployment settings and how updates get published.
- Data Data structure and how to export it, according to the project.
- Acceptance A clear list of what was tested and handed over.
- What comes next Suggestions for the stage after this one, with no obligation.
What the handover package contains depends on the type of project and its scope. Ownership and handover details are set in the contract. Third-party technology and licences remain under their owner’s terms.
After handover
Four options, all of them open to you.
Your team continues
We hand your technical team what they need, and sit with them for a handover session if that helps.
Another developer continues
The documentation and repository are organised so any competent developer can take over.
We stay on a support plan
If you would rather we stayed, choose the level that fits the size of the project.
Annual support plans
Support is entirely optional. The scope of each plan is set in the contract according to the project.
Care
For stable sites and systems that need periodic attention.
- Scheduled maintenance review
- Dependency and update review
- Backup responsibility review
- Fault investigation
- Deployment assistance
- Periodic health check
12% of original project value annually, minimum SAR 2,400
Not included: Major new functionality or third-party and cloud charges. Response arrangements and included hours are defined in the support proposal and contract.
Growth
For sites and systems that keep evolving.
- Everything appropriate from Care
- Planned improvement cycles
- Performance review
- Search foundation review for websites
- Small agreed changes
- Integration health review
- Periodic roadmap session
18% of original project value annually, minimum SAR 4,800
Not included: Major new functionality or third-party and cloud charges. Response arrangements and included hours are defined in the support proposal and contract.
Priority
For systems the daily operation depends on.
- Higher support priority
- Scheduled maintenance
- Monitoring where the infrastructure supports it
- Release coordination
- Backup and recovery checks
- Incident coordination
- An agreed change allowance
- Periodic technical review
25% of original project value annually, minimum SAR 9,600
Not included: Major new functionality or third-party and cloud charges. Response arrangements and included hours are defined in the support proposal and contract.
We do not publish response times, included hours or availability figures before they are agreed in writing. What goes in the contract is what binds us.
Ongoing costs
The project itself carries no compulsory monthly fee. There are, however, normal ongoing costs for any digital project, and we set them out at the start rather than letting them surprise you.
- Hosting and the domain, in your name and on your account
- Any third-party service or API carries its own fees
- Licence renewals if the project uses licensed components
- A support plan, if you choose one
- New work outside the scope, quoted separately
Ready to start?
Put your project details together and we get to scope and price in the first conversation.