The delivery month is the unit of purchase and operate plans are annual. The terms below are the same for every client, and pricing follows a scoping session.
A delivery month means two working days a week dedicated to your project inside one calendar month, against a written scope approved at the start of it. Scope is ordered to fit the month; the month is not stretched to fit the scope.
A new system usually starts at three delivery months, which includes setting up environments and standards once at the beginning. After that it is a delivery month at a price you know before it starts, not an argument halfway through.
| Standard | Extended | |
|---|---|---|
| Scope | One system, one production environment | One system, production and staging |
| Security patching | Monthly | Monthly |
| Backup verification | Monthly | Monthly |
| Real restore test with report | Twice a year | Four times a year |
| Monitoring and alerting | Yes | Yes |
| Operations report | Annual | Quarterly, with a review |
| Response time | Within one working day (Sunday to Thursday) | Within one working day (Sunday to Thursday) |
| Included incident hours | Bought as a change block | 16 hours a year |
We price defined units of work, not hours. Pricing follows a scoping session, and we send a written proposal before any commitment. The company is not registered for VAT, and prices in our proposals are not subject to it. On reaching the mandatory registration threshold, VAT will be added to invoices issued after the registration date, in line with ZATCA rules. Agreed prices are exclusive of VAT, and adding it later is not a price change.