Two backend engineers and DevOps. For APIs, services and deploy pipelines.
At a glance
From
6,650 JOD a month
At full capacity
Remote from Amman
The price
How you engage
You choose each seat's monthly hours and the commitment curve prices it: more hours, better hourly rate. Capacity changes monthly on one month's notice.
Capacity per seat
Lower capacity is not a proportional discount: recruiting cost, social security and leave accrual do not shrink with the hours, so the hourly rate rises as the commitment falls. The full price curve is on each role's page.
Where the engineer sits
The engineer sits in our Amman office with their team and works in your tools and channels. This is the default and the fastest to start.
Engagement length
Where your team sits
Seniority
Optional add-ons
The price
6,650 JOD
per month · 480h · 3 FTE · 13.85 JOD/h
Prototype prices. The final price is written after one call.
Price by seniority
| As composedSenior across every seat | 6,650 JOD |
| Mid-LevelDelivers a whole feature without close supervision | 5,400 JOD |
| SeniorOwns a subsystem and reviews others | 6,650 JOD |
| LeadOwns architecture and the quality bar | 8,300 JOD |
| PrincipalDecides what does not get built | 9,500 JOD |
Who this is for
You have a working frontend or app, and the whole bottleneck is behind it.
The delivery playbook
Not marketing promises; this is how we actually run this kind of package. If we drift from it, this text is what you hold us to.
Before day one
Access, docs, a map of the services, and what your own team is afraid of in the current system. Understanding first; it is the cheapest fix there is.
Week one
One small change through tests, review and automated deploy. If there is no automated pipeline, building it is task one, not feature one.
Weeks 2 to 4
APIs and services land in the order that lowers production risk, with load tests on whatever will actually take load.
Month two
Dashboards, alerts and written service objectives. A system whose sickness you cannot see is one whose death you will.
Month three
Architecture decisions written down, runbooks in place, and your team able to operate what we built without us. That is a success criterion, not an option.
The subscription
What landed, what got stuck, what is next, readable in two minutes. No extra meeting unless you ask for one.
Thirty minutes with you: priorities, levels, team size. Cancelled when there is nothing worth it; your time beats our rituals.
Team leave and Jordanian holidays in a calendar you see weeks ahead, not in an apology on delivery morning.
Not only the first thirty days. An engineer who stops being right gets replaced in any month, and a vacant seat is never invoiced.
One monthly invoice, one line per seat, no surprises and no hidden fees. The number we agreed is the number that arrives.
Is the level you pay for still the right one? Sometimes we advise down and lose invoice value, because the renewal matters more to us than the margin.
In every package
FAQ
It depends on the model. On staff augmentation and a dedicated team you run it as part of your company. On a managed team we run it and you receive the outcome. The package suggests the best fit; the call is yours.
Yes, monthly. Add a seat, remove one, or change its level on one month's notice. The package is a starting point, not a contractual cage.
On one month's notice you can shrink or end the package. We do not sell a "pause" that holds seats free of charge, because the engineers are employees on real salaries, and anyone promising that is paying for it out of engineer quality.
Always. We send anonymised profiles, you pick who to meet, and the final interview is yours with the right to say no without explaining. Nobody starts on your team whom you did not approve.
Similar packages
Android, iOS, backend and QA. Everything needed to launch an app and keep it alive.
Per month at these settings · 720h · 13 JOD/h
Two Android engineers and QA. For a large Android app or fast growth.
Per month at these settings · 480h · 12 JOD/h
Two iOS engineers and QA. Swift, SwiftUI and a regular release cycle.
Per month at these settings · 480h · 12 JOD/h
Next step
Not the headcount. Tell us the product, the date, and what team you have today, and we will propose the shape. If we think what you need is not more engineers, we will say so on the first call.
Typical response within one business day · everything you share is treated as confidential
