Per seat / 3 month minimum / UTC+0
Build a Dedicated
Development Team
in Morocco
A standing team that works on your product and nothing else. You point it. We employ it, manage it, and replace anyone who leaves.
Priced per seat so you can do the arithmetic before you contact us. The whole team sits on your clock rather than relaying across one.
Team shape, monthly number, real start date
01 / Before anything else
Make sure this is the thing you want
Three different products get sold under overlapping names, and picking the wrong one is expensive. Find your row before you read any further.
| Agency project | One engineer | Dedicated team | |
|---|---|---|---|
| You are buying | A finished scope | Capacity | A standing team |
| Roadmap | Frozen at signature | Yours | Yours, and it can move |
| Changing your mind | Change order and a fee | Free | Free |
| Who manages the people | The agency | Mostly you | Us |
| Ends when | The scope is delivered | You give notice | You give notice |
| Right for | A one-off build with hard edges | Filling one gap in a working team | Product work with no end date |
Only need one more pair of hands? Then hiring a single senior engineer in Morocco is cheaper and simpler, and we would rather tell you that than sell you a team.
02 / The operating model
Who decides what
These engagements do not fail on skill. They fail because nobody wrote down who gets to decide, and six weeks in two people both think they own the roadmap.
So here it is in advance. This goes into your contract close to word for word.
What gets built, and in what order
It is your product and your market. We do not get a vote on the roadmap, and a vendor who wants one is selling you an agency project.
Sprint scope and acceptance
Your product owner runs planning. The team attends and estimates. Nothing is accepted by us on your behalf.
Architecture and technical standards
Your standards, your patterns. We will push back hard and in writing when we think something is wrong, then implement your call.
Code review and merge
Every pull request goes through your review process like anyone else on your team. No code arrives as a surprise.
Who is on the team
We propose, you interview. If you do not want someone they do not join, and you never have to explain why.
How the team is managed day to day
One to ones, performance, growth, workload, time off. You should not be managing people who are not your employees.
Employment, payroll, benefits, contracts
Entirely ours. That is the risk you are transferring and the reason this costs more than a freelancer.
Replacing someone who is not working out
You tell us early, we handle the conversation and the replacement. You never have to fire anyone.
Team size, up or down
Per seat, on the notice period in your contract. You are not locked into a headcount for the life of the engagement.
Who owns the code and the IP
Assigned in the contract from the first commit, not on final payment. There is no leverage clause and we would not want one.
6 of 10
Decisions that are yours outright
2 of 10
Shared, with you holding the final call
2 of 10
Ours, and both are about employment
03 / Proof / Federal Government Advisors
Six months, one team, a platform
that replaced an ERP
“Six months in, OpsVoid had built an entirely new platform, and our win rate moved with it.”
Why it had to be a team, not a project
The roadmap moved several times as their business learned what it actually needed. A fixed-scope contract would have turned every one of those discoveries into a change order and an argument. A standing team absorbs them.
How the work was split
Sammy Chafiqui as architect and delivery lead, engineers executing against that architecture. FGA set priorities. We ran the people. Exactly the split in the table above.
The engineering spine
A synchronized HigherGov data feed into the system of record on a thirty minute cycle, running unattended, with the breakdowns their team works from generated straight off it. We replaced the legacy ERP rather than scaling it, on the judgement that the data model was the real bottleneck.
What it did to the day job
Capability statement production went from three days to twenty minutes. Their CEO attributes a measurable move in win rate to the platform.
04 / Shapes and timing
Team shapes, and how long each takes to stand up
Two plus a lead
Two senior engineers, fractional technical lead
One product, one backlog. The most common starting shape and usually the right one.
Fastest to startThree or four plus a lead
Backend, frontend, generalist, fractional lead
A product with a web app, an API and integrations all moving at once.
Often needs one hireFive or more
Multiple workstreams, full time lead
Possible. It means recruiting, and we give you a date we can hold rather than an optimistic one.
Recruiting requiredWe do not have a bench
OpsVoid is a small engineering company. There are no five idle engineers waiting for a contract to land. For a larger team we recruit against your requirements and you interview every candidate. That is slower than a vendor assigning whoever is free this month, and it is the reason the people who start are the people who stay.
The ramp we hold ourselves to
- Week 0
Scoping
A senior engineer goes through your codebase and roadmap. You leave with a team shape, a monthly number and a start date.
- Week 1
You interview everyone
Every proposed engineer. No exceptions, no persuading, no candidate you did not approve.
- Week 2
Access and environment
Contracts and NDAs signed, repo access granted, environments running, the team in your standups reading code.
- Weeks 3–4
First real pull requests
Small and contained deliberately, so you can judge the work before it matters.
- Weeks 5–8
Full velocity
The team owns areas of the product rather than individual tickets. This is the point a dedicated team starts beating contractors, and it is why we will not take a one month engagement.
05 / Money
Do the arithmetic yourself
Per seat, per month, no separate management fee. Multiply and you have your number before you ever speak to us.
$15,600–$23,400
per month / typical team of three with a fractional lead
| Each senior engineer, full time | $4,800–$7,200 |
| Fractional technical lead, about a day a week | $1,200–$1,800 |
| Team of three with a fractional lead | ≈ $15,600–$23,400 |
| Five or more | Capacity and lead time |
| Recruiting for your team | On us, never billed |
The number moves on seniority mix, how much technical leadership you need, contract length, on-call cover and how specialised the skills are. Morocco is why the range sits where it does: senior rates here are the lowest of any region Lemon.io tracks in its 2026 data, and the reason is local cost of living rather than a discount on the engineering.
What the seat price covers
The engineer, their equipment, their manager, their replacement if they leave, and our time keeping delivery on track. If someone is ill, on holiday or resigns, that is our cost and our problem. Transferring that risk is most of what you are buying.
06 / The contract
The clauses people only read once something goes wrong
Read them now instead.
Adding people
A few weeks if we have the right person, longer if we recruit. Tell us a quarter ahead and it is almost always easy.
Removing people
Notice period per seat, agreed in the contract. You are not locked into a headcount.
Someone is not a fit
Tell us early, we replace them, you do not pay for the overlap. At our size that can mean recruiting rather than swapping, so we agree the window before you sign.
Someone leaves
Our problem. We cover the handover and the technical lead carries the context through it. That continuity is a large part of what the seat price buys.
You want to stop entirely
Notice period in the contract, no exit fee, documentation and access handed over before we go.
Minimum commitment
Three months. Below that the team is still ramping and we would be charging you for setup rather than output.
Code, IP and security
- 01IP assigned to you in the contract from the first commit, not on final payment
- 02NDAs signed before anyone opens your repository
- 03Your repo, your cloud accounts, your data. Nothing of yours lives on our infrastructure.
- 04Production access scoped per engagement and revoked the day someone rolls off
- 05Contracting entity and governing law confirmed in writing before any work begins
07 / Accountability
Who runs the team
Founder and CTO
Sammy Chafiqui
Computer Science degree in the United States, then five years building production software as an engineer in California before founding OpsVoid.
Architect and delivery lead on the Federal Government Advisors platform above. On your engagement he is accountable for architecture and technical direction, and he is one message away with no layer to escalate through.
LinkedInEveryone else on your team is introduced to you before they start, and you interview them. That is the veto in the table above, and we mean it literally.
08 / Questions
Straight answers
What does a team of three cost per month?
About $15,600 to $23,400. Three engineers at $4,800 to $7,200 each, plus a fractional technical lead at $1,200 to $1,800. No separate management fee, so any team size is just arithmetic.
How long until the team is productive?
First pull requests in weeks three to four, full velocity around weeks five to eight, if we already have the right people. If we need to recruit, add the hiring time, and we tell you which case you are in on the first call.
Who manages the team day to day?
We do. You direct the work. Look at the decision table above: priorities, architecture and merge are yours, people management and employment are ours.
What if I need to scale up or down?
Up depends on whether we have the person or need to recruit. Down is a notice period per seat. You are never locked into a headcount for the life of the engagement.
What happens if someone leaves?
We replace them and cover the handover. The technical lead carries the context through it, which is why continuity survives a departure instead of restarting with it.
How do I keep control of architecture and code quality?
Your standards, your review process, your merge button. We will argue with you in writing when we disagree, then implement your decision. Nothing lands without your team approving it.
What is the minimum commitment?
Three months. Shorter than that and you are paying for the ramp without getting the part that comes after it.
Can I interview everyone first?
Yes, and you should. We do not place anyone you have not met. You can decline a candidate without giving a reason.
Do we have to use your tools or processes?
No. Your repo, your Jira or Linear, your Slack, your ceremonies, your times. You do not log into anything of ours.
Bring the roadmap you cannot staff
Thirty minutes with a senior engineer. You leave with a team shape, a monthly number and a start date we can actually hold, whether or not you hire us.
Also for you
Python engineers who can read your codebase / AWS engineers who have been on call