One engineer, or a whole team. We recruit, employ and retain them in Jordan; you run them as part of your team. No entity to register, no payroll to run, no recruiting function to build, and a monthly price published before any call.
In numbers
Packages
22, priced in public
Roles
16 roles, 8 in the network today
Numbers we can keep
Every number here is either verifiable or a process commitment we can actually keep. No pool size, no client count.
5 days, then 3 to 6 weeks
Five working days from a clear brief to a first shortlist. Then 3 to 6 weeks until the engineer actually starts
Two numbers, not one. Publishing one hides the other
8 hours
Daily overlap with Central Europe on a standard Jordan day, and a full shared day with Riyadh and Doha
North America needs a shifted day. Real numbers in the timezone section
UTC+3, fixed
Jordan does not run DST, so the schedule does not shift twice a year
The gap only moves when your clock moves
A formal Jordanian contract
The engineer is a Folowise employee, not a loose contractor
Social security, payroll, NDA, and IP assignment
Where you are
Same engineers, same price. What changes is the clock, the working week, the language and the law. Read the part that is about you.
The same clock and the same Sunday to Thursday week as Riyadh and Doha — one hour and a different week with Dubai, which we put in the contract explicitly — and Arabic-native engineers. The closest thing to an in-house team without Riyadh or Dubai cost.
7 to 8 hours of overlap with Berlin and Amsterdam on a standard day, 6 to 7 with London. We contract a Monday to Friday week and write it into the agreement.
US East gets 5 to 6 hours of overlap on a shifted Amman day that we contract and price. For the West Coast we advise against a full shifted day, and we say so before the contract.
Four models
Most companies pick the wrong model because they compare prices instead of comparing responsibility. Read the "do not pick this" box on each card before you decide: that is the useful part.
Engineers who work inside your team
You have an engineering team, a roadmap, and technical leadership. What you lack is capacity. The engineer joins your squad, attends your standup, and has their code reviewed by your engineers.
The staff augmentation pageDo not pick this if: Do not pick this if you have nobody to direct the engineer day to day. We will hand you a good engineer and you will get output you cannot use. Pick a dedicated team instead.
A standing team built around your product
You own the product direction and you know what you want built, but you do not have the bandwidth to manage engineering day to day. We assemble a standing team with a tech lead and run the delivery process for you.
Do not pick this if
Do not pick this if your scope changes weekly. A standing team needs a roadmap that survives a quarter. If you are still exploring, start with one or two engineers on staff augmentation.
A business outcome, not a set of seats
You have a business goal and a budget, and no engineering leadership. You give us the outcome; we own product management, technical leadership, design, build, QA and operations. You make the call: go or stop.
Do not pick this if
Do not pick this if you already have a strong CTO and a working team. You would be paying for leadership you already have. Staff augmentation is cheaper and fits you better.
Your own engineering presence in Jordan, operated by us
You want a permanent engineering presence in Jordan at the scale of dozens of engineers, under your brand and your culture, without registering and running an entity. We build it, we operate it, and we hand it over when you are ready.
Do not pick this if
Be aware: we have not yet run a hub at this scale for a single client. We have the recruiting, operating and leadership capability, but we do not have a track record at 30 or 50 engineers. If that is what you need, talk to us and we will tell you plainly what we can execute today and what we cannot.
How it starts
No slide deck and no "we will be in touch". This is what actually happens, by the day, and what we need from you at each step.
Day 1
A package from the catalogue, a seat from a role page, or a team from the builder. An account manager reads it the same working day and replies in writing: specific questions, or a confirmation that we understood.
Day 2
A short call pins the roles, levels, hours, timezone and engagement model. The brief becomes a record with an id and an owner, not a message in an inbox.
Day 5
Two to four anonymised profiles per seat: level, stack, assessment result and why we picked them. That is for roles we recruit continuously; other roles add two to three weeks.
Week 2
You meet whoever you choose and say no without explaining. Once you approve, the engineer's notice at their current employer starts, typically two weeks to a month.
Weeks 3 to 6
The Jordanian contract, the NDA, the equipment and the access are ready before day one. And if the engineer is not right within the first 30 days, we replace them at no additional fee.
Packages
Twenty-two packages, eight single seats and fourteen teams. Every package says who it is for and who it is not for, and all of them price through one engine.
Android, iOS, backend and QA. Everything needed to launch an app and keep it alive.
Per month at these settings · 720h · 12.50 – 14.50 JOD/h
Frontend, backend and design. A site or dashboard from design through to deploy.
Per month at these settings · 480h · 10.75 – 12.75 JOD/h
Product manager, full-stack, design and half a QA seat. Idea to a real first version.
Per month at these settings · 720h · 14.75 – 17.00 JOD/h
The builder argues with you, it does not just add seats up
Pick the roles, the levels and the hours, and the builder reprices in front of you from the same engine that prices every package. Then it sends the whole brief in one click.
Start buildingWhat it costs
Each role's default level at 160 hours a month, remote from Amman. All sixteen roles at every level are in the price book, and the number moves on each role page with the hours and the level.
Senior · Node · Java/Kotlin · PHP · Python
a month, estimated · 13.25 – 15.50 JOD an hour
Senior · Kotlin · Jetpack Compose
a month, estimated · 13.00 – 15.00 JOD an hour
Mid-Level · Manual testing and scenarios
a month, estimated · 7.75 – 9.00 JOD an hour
Lead · Owns architecture and the quality bar
a month, estimated · 22.50 – 26.25 JOD an hour
Every number here is an estimated range, not a final price. The final price is written after one call, against a real brief, a real timezone and a real term.
Inside every price
What moves the number
The hours you commit to each month first, then the level. Fewer hours mean a higher hourly rate, because recruiting, social security and leave costs do not shrink with the hours. The other multipliers (where the engineer sits, engagement length, timezone, a managed team) are all published in the price book, not in a call.
Prototype prices. The final price is written after one call, but it starts from these numbers, not from a blank page.
Guarantees
Every competitor in this market promises to be reliable, committed and transparent. An adjective binds nobody. A number written into the contract does.
30 days
The mismatch window. If the engineer is not right within the first month, we replace them at no additional fee and with no notice period charged to you.
10 working days
Our commitment to a replacement shortlist if an engineer leaves. The search is at our cost, and we do not bill you for an empty seat.
Zero
Replacement fees, and conversion fees if you decide to hire the engineer into your own company after 12 months. No fees hidden in the terms of use.
The people you interviewed are written into the service agreement by name. Not "a senior backend engineer", their name.
Your engineer is on your team full time. Not shared, not pooled, not "allocated at a percentage". If you need part of a seat, we sell you part of a seat and it says so on the invoice.
Your Slack, your standup, your calendar. There is no account manager between you and the person writing the code. We show up when you need us, not as a permanent gate.
What we do not promise: that every engineer will fit, that a replacement arrives just as fast for a rare role, or that we can guarantee the performance of somebody you have not met. Impossible guarantees are written to be broken, and we would rather write down what we actually do.
Journeys
A staffing firm enters at one point: how many people do you want. Four journeys below, and where each one ends.
A staffing firm asks how many engineers you want. We ask what you are trying to ship, by when, and who is reviewing the code on a Friday. The questions differ because what we are selling differs.
Honesty
These objections will be raised inside your company anyway, so you may as well hear them from us first.
For engineers
Register once and we put you forward when a matching request arrives: a Jordanian contract with Folowise, work for clients in the Gulf, Europe and the US, and a published seniority ladder. Every role, from fresh graduate to principal.
Read more
Ten pages, each answering one question and stopping. No PDF that arrives after the call.
FAQ
Yes, and it is the start we recommend. One engineer on a three month engagement is the cheapest way to test us. If it works, scale. If it does not, your downside was capped and visible from the start.
For roles where we have a standing pipeline: a first shortlist within 5 working days of a clear brief, and your interviews the week after. The actual start depends on the engineer's notice period with their current employer, and Jordanian labour law requires a month on indefinite contracts. Realistic total: 3 to 6 weeks. We publish both numbers deliberately: anyone publishing "48 hours" alone means time to shortlist, not time to start, and is offering you whoever is unoccupied rather than the best people in the market.
Folowise employs them in Jordan on a formal employment contract, and pays salary, social security and applicable taxes. You pay Folowise one monthly invoice. There is no direct contractual relationship between you and the engineer, which is what protects you from worker-classification exposure.
Yes. Every engineer in the network is based in Jordan and Arabic-native, and works in English for documentation and code review as the region does. For a Gulf client that means meetings without a language barrier; for a Western client, a recorded English score that reaches you with the profile.
You do, and the mechanism is worth a minute because it is not what you expect. Jordanian copyright law does not adopt US work-for-hire: commissioned work vests in its author by default, a blanket assignment of future works is of uncertain effect, and moral rights cannot be assigned away. So we transfer ownership through a written assignment per deliverable instead of one broad clause. The practical outcome for you is the same, but the route is different, and we would rather you heard it from your own counsel before signing than after a dispute. The open source policy is agreed in writing before work begins, and we do not put a copyleft-licensed library into your product without your approval.
Yes, fully. Every role and level has a published monthly price at full capacity, and a commitment curve that shows the hourly rate at every hour count. Move the hours on any role page and the number moves in front of you, and every page reads from the same price book, so you will never find two different numbers for the same seat. The final price is written after one call, but it starts from these numbers, not from a blank page.
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
