Key terms at a glance
Framework
Each SOW sits under the MSA, whose terms apply unless the SOW overrides a named clause.
Controlled fields
Self-serve SOWs change only validated fields; any other edit moves the booking to the enterprise lane.
Price
Taken from the quotation, valid 30 days, in SAR, AED, USD or EUR, with VAT shown separately.
Start date
No earlier than 4 working days after signature, for every bench, off-bench or on-site engineer.
Trial
1 no-bill trial per company: 5 working days in the self-serve and reservation lanes, 10 in the enterprise lane.
Replacement
Any reason, under the MSA guarantee: a replacement starts within 4 working days; the full handover completes in under 14 days.
Term
A minimum of 1 month for a single specialist and 3 months for squads, pods and managed delivery, then automatic monthly renewal; 30 days’ notice to end or reduce seats; reminders 45, 30 and 7 days before the minimum term ends.
Residency
Data pattern (A, B or C) and region fixed in the SOW.
Acceptance
Milestone deliverables reviewed within 5 working days, then accepted or returned with written reasons; with no response, deemed accepted after 10 working days.
Invoicing
Monthly per seat; milestone projects invoiced on acceptance.
Changes
Raised in Client OS; no changed work starts before a signed amendment.
Warranty
Defects fixed free of charge for 60 days after go-live on every fixed-scope delivery (Managed Delivery milestones, Project Engagement, Prototype → Production and launch builds).
IP
Work product assigned on payment, as set in the MSA.
Signature
E-signature through Zoho Sign with emdha (Nafath-backed in KSA), UAE Pass or an EU qualified electronic signature.
The fields the booking flow fills in
Each field accepts validated values only, which is why a standard SOW needs no legal review.
| Field | Accepted values | Helper text |
|---|---|---|
| Engagement model | Team Extension · Ready Squad · Managed Delivery · Project | Sets which schedules attach |
| Roles and levels | Any of 122 role profiles · Mid · Senior · Lead | Levels map to years of experience |
| Headcount | 1–12 per squad; more in the enterprise lane | Squad sizes 4, 7 and 12 are pre-priced |
| Named engineers | From your shortlist | Changeable during the trial |
| Start date | 4 working days after signature or later | 4 working days for on-site roles too |
| Working hours | Hours per week · time zone · overlap window | Overlap shown in your time zone |
| Location | Remote · hybrid · on-site city | On-site adds travel and permits |
| Data pattern and region | A, B or C · KSA, UAE, EU, UK or US | Must match your DPA annex |
| Security requirements | Managed device · VDI · clearance level | Affects start date for cleared roles |
| Price per seat | From quote | Valid 30 days from issue |
| Currency | SAR · AED · USD · EUR | VAT added at invoice |
| Trial length | 5 or 10 working days | 1 trial per company |
| Term | 1 month (single specialist) or 3 months (squads) minimum, then monthly | 30 days’ notice to end |
| Billing | Contact · PO number · invoice frequency | PO number printed on every invoice |
| Acceptance criteria | Required for milestones | Measurable, testable statements |
Template outline
Every SOW follows this structure. The PDF template shows the full wording in English and Arabic.
- Parties, MSA reference and SOW number
- Engagement model and objectives
- Roles, levels, headcount and named engineers
- Start date, working hours and overlap
- Location and on-site arrangements
- Data-residency pattern, region and security requirements
- Deliverables, milestones and acceptance criteria (where applicable)
- Governance: Squad Lead, Governance Officer, reporting and steering cadence
- Service levels and guarantee references
- Trial terms
- Fees, currency, taxes and invoicing
- Term, renewal and seat changes
- Change-request procedure
- Client dependencies and access
- Hand-over and exit specifics
- Signatures
3 worked examples
Representative SOWs showing how the controlled fields combine. Prices appear only in your proposal, never on this page.
Example 1 · Team Extension
- Pattern A: work inside the client’s cloud tenancy and managed devices
- Seat price: [seat price as in the proposal], per month, VAT shown separately
- 2 Senior backend engineers (Java, Kafka), remote from Cairo
- 40 hours a week, full overlap with Central European Time
Example 2 · Ready Squad (Squad-in-4)
- 7-person product squad: 1 Lead, 2 backend, 1 frontend, 1 mobile, 1 QA automation, 1 DevSecOps
- Pattern B: client’s in-Kingdom cloud region, zero-trust access with logging
- Start 4 working days after signature; weekly executive report every Friday
- Priced as the sum of its 7 seats less the 3+ specialist discount (rate in your quote) · minimum term 3 months · 5-working-day trial in the reservation lane
Example 3 · Milestone project (Managed Delivery)
- 4 milestones: discovery, MVP build, hardening, go-live
- Each milestone has written acceptance criteria and a demo
- Invoiced on acceptance only; 60-day defect warranty after go-live
- Source-code escrow at Remote Pro Ai’s cost
How scope changes without surprises
Either party can propose a change. Nothing changes until both sign the amendment.
Either party raises a change request in Client OS, describing what should change and why.
Remote Pro Ai returns a written impact assessment covering scope, price, timeline and staffing.
The client approves or declines; approval generates an amendment from controlled fields.
Both parties sign by e-signature, and the amendment attaches to the SOW.
Added seats follow the 4-working-day start; seat reductions take effect after 30 days’ notice.
- Plain-language rule
- No changed work starts, and no changed fee is invoiced, before the amendment is signed.