For scaling startups

Build-Operate-Transfer for startups: your team, owned later

We hire and run your engineering team, then transfer the people, processes and IP to your entity at a fee agreed on day 1. Horizons usually run 12–⁠36 months.

No lock-in. The transfer fee is written into the first contract.

Fig. 01Build-Operate-Transfer

  • 72hfree hold
  • 4working days to start
  • 48hshortlist
  • 9practices
In short

We hire, run and govern your team in Cairo or at your premises in Saudi Arabia or the UAE, then transfer it at a fee fixed on day 1.

Build-Operate-Transfer for startups is a Remote Pro Ai engagement in which we hire and run your engineering team, then transfer the people, processes and IP to your own entity at a fee agreed on day 1. BOT horizons usually run 12 to 36 months, and the first squad starts within 4 working days.

3 BOT phases with a fixed transfer path

  • Build · months 0–⁠6

    We agree the hiring plan, roles and KPIs, install our delivery framework and start your first squad within 4 working days from bench. We then hire to your plan, with your leaders on the final interview for every Senior and Lead seat.

  • Operate · month 6 until transfer

    We run the team to your KPIs: velocity, quality gates, attrition and cost per seat, reported every Friday and reviewed quarterly. Your product leaders set priorities; we handle hiring, payroll, equipment, performance and replacement.

  • Transfer · an agreed date between months 12 and 36

    People, runbooks, tooling and knowledge move to your entity on the agreed date, with each engineer’s consent. We support the transfer with offer letters, handover plans and a hypercare window. You may keep Remote Pro Ai as a specialist edge for skills you do not want in-house.

  • Who it is for

    • Series A+ startups planning 15+ engineers over the next 3 years.
    • Founders who want an Egypt or Saudi engineering centre without setup risk.
    • Companies with Saudization or local-content targets to meet over time.

Entity and employer-of-record options

OptionHow it worksBest when
Transfer to your existing entityEngineers move to your company in Egypt, Saudi Arabia or the UAE at transferYou already have a local entity
Employer of record firstEngineers move to an EOR, such as Deel or Remote.com, before you open an entityYou want ownership before incorporation
Entity set-up supportWe coordinate licensing partners, such as a MISA licence in Saudi Arabia or ITIDA registration in EgyptYou will open a centre in that country

In Saudi Arabia, your workforce plan can set a Saudi hiring schedule for your own Nitaqat planning, written into the SOW; its effect on your band and on any LCGPA local-content score is verified with HRSD and LCGPA.

Entity set-up runs through Remote Pro Ai’s partners in Saudi Arabia and the UAE, named on request.

A transfer fee you agree before you start

A BOT quotation has 3 lines. A one-off setup fee covers team design, hiring and operations set-up. A monthly operate fee per seat covers salaries, equipment, security tooling, governance and replacement cover. The transfer fee is set in the first SOW, so you can model it from day 1, and it is never renegotiated at the point you depend on the team.

Transfer in months 1–⁠12 of operation
A transfer fee per specialist (in your quote).
Transfer in months 13–⁠24
A reduced transfer fee (schedule in your proposal).
Transfer after 24 months
No fee.

Individual engineers you hire before a full transfer follow the conversion fee schedule in your proposal (declining with tenure, none after 12 months). Your itemised proposal prices each seat by level, practice and engagement model, and we email it within 2 minutes of your request.

What shapes your quotation

  • Target headcount and the hiring curve across 36 months.
  • Country of the centre and the share of on-site roles.
  • Seniority mix and the practice of each seat (prices are per practice and level).
  • Saudization targets and the transfer date.

A typical BOT timeline

WhenMilestone
Week 0MSA, BOT SOW, KPIs and target transfer date signed
Within 4 working daysFirst squad live from bench
Months 1–⁠6Hiring to target headcount; team playbook approved
Month 6 onwardOperation against KPIs, quarterly reviews, your leaders hired into the team
90 days before transferTransfer plan, employee consent, contracts and benefits review
Transfer day (months 12–⁠36)People, tools, accounts and documents move to your entity
After transferHypercare window set in the contract; option to keep specialist seats

Guarantee

  • Every placed engineer is covered: a replacement starts within 4 working days; the full handover completes in under 14 days.
  • 1 free day for every late day on the first squad’s start, capped at 10.
  • IP assigned to you on payment throughout the engagement, not only at transfer.
  • Non-solicitation released for transferring engineers at transfer.

Build-Operate-Transfer for startups: the legal structure

  • An MSA plus a BOT SOW setting phases, KPIs and transfer terms.
  • During operation, engineers are employed by a Remote Pro Ai entity or an EOR.
  • Engineers transfer with their consent; end-of-service entitlements are settled under the applicable labour law and the contract.
  • Data processing agreement under PDPL, UAE PDPL or GDPR; data location is your decision, recorded in writing.
  • Governing law in your jurisdiction, with SCCA arbitration seated in Riyadh for Saudi contracts and DIAC arbitration (seated in the DIFC) for the UAE.
  • Exit and transition plan attached from day 1.

Our offices in Cairo (HQ) and Al-Khobar host BOT teams, and we meet clients in Riyadh and Dubai by appointment. See our offices. A hybrid example: Case P-01, a citizen-services super-app for a national authority in Riyadh, ran 3 seats on-site and 6 from Cairo.

Frequently asked questions

Book a scoping call

20 minutes with an Account Director. No sales script.

Build-Operate-Transfer is an engagement model in which a partner builds a team for you, operates it for an agreed period and then transfers it to your company. With Remote Pro Ai, the first squad starts within 4 working days, operation runs to your KPIs, and the transfer fee and date are fixed in the first contract.

Choose BOT when you expect 15 or more engineers over several years and want to own the team eventually. A Dedicated Pod suits 2 to 5 engineers with no plan to employ them. Many startups start with a team and move into BOT once headcount and funding justify a centre of their own.

No. Remote Pro Ai employs the team during the build and operate phases. Before transfer you can open an entity, use an employer of record such as Deel or Remote.com, or transfer to an entity you already own. Your choice is recorded in the SOW with the transfer date.

You do. Work product is assigned to your company on payment from the very first invoice, not only at transfer. Code lives in your repositories, documents in your workspace, and access is controlled by your administrators. The transfer moves people and processes; the IP is already yours.

Yes. For a Saudi centre, the workforce plan can set a Saudi hiring schedule that you define, with Saudi hires trained alongside experienced engineers; the schedule sits in the SOW and progress is reported quarterly against it. The effect on your Nitaqat band and on any LCGPA local-content score is verified with HRSD and LCGPA, not promised by us.

The exit and transition plan is attached from day 1. You can trigger an early transfer at the agreed fee schedule, or end the engagement with the notice set in your SOW. Either way, documentation, runbooks and repositories stay with you, and we support the handover.

All questions, by topic

Start today

4 working days

Your team can be working within 4 working days of signature.