Our hourly rate is a function of one thing: how many hours a month you commit to per seat. Every number on this page comes out of the same engine that prices every package and every role.
16
roles with a published monthly price
5
levels, from Associate to Principal
160 hours
full capacity on a seat, per month
JOD
the currency of every number on this page
The method
Every role and level has one published number at 160 hours a month. There is no global level multiplier, because a QA seat and a cloud seat share no economics.
The monthly price divided by 160 hours. That is the cheapest hourly rate for the seat, and there is nothing below it.
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.
A fixed-scope contract, where the engineer sits, the term, the timezone, and a managed team. All of them are published multipliers below, not hidden numbers.
These are prototype prices in Jordanian dinar: an internal anchor times multipliers that have not yet had commercial sign-off. They look authoritative because they sit in a table, and they are not. The final price is written after one call, but it starts from these numbers, not from a blank page.
The price book
Jordanian dinar per month for 160 hours, remote from Amman, on a six month term, on European hours. Open the role page for the full commitment curve.
| Role | Min hours | Associate | Mid-Level | Senior | Lead | Principal |
|---|---|---|---|---|---|---|
| Backend engineerNode · Java/Kotlin · PHP · Python | 80h | - | 1,750 JOD | 2,150 JOD | 2,700 JOD | 3,300 JOD |
| Frontend engineerReact · Next.js · Vue | 80h | 1,150 JOD | 1,600 JOD | 2,000 JOD | 2,550 JOD | - |
| Full-stack engineerFront and back in one seat | 80h | - | 1,850 JOD | 2,250 JOD | 2,800 JOD | - |
| Android engineerKotlin · Jetpack Compose | 80h | - | 1,700 JOD | 2,080 JOD | 2,650 JOD | - |
| iOS engineerSwift · SwiftUI | 80h | - | 1,750 JOD | 2,150 JOD | 2,700 JOD | - |
| Flutter engineerOne app, both platforms | 80h | - | 1,650 JOD | 2,000 JOD | 2,550 JOD | - |
| QA engineerManual testing and scenarios | 40h | 850 JOD | 1,250 JOD | 1,600 JOD | - | - |
| Automation QA engineerPlaywright · Cypress · Appium | 80h | - | 1,550 JOD | 1,900 JOD | 2,400 JOD | - |
| DevOps engineerCI/CD · infrastructure as code | 40h | - | 1,900 JOD | 2,350 JOD | 2,900 JOD | - |
| Cloud engineer / SREAWS · GCP · Azure | 40h | - | - | 2,450 JOD | 3,000 JOD | 3,600 JOD |
| Data engineerPipelines and warehouses | 80h | - | 1,850 JOD | 2,300 JOD | 2,850 JOD | - |
| AI engineerLLM · RAG · evaluation | 80h | - | 2,000 JOD | 2,500 JOD | 3,100 JOD | - |
| Product managerDiscovery and roadmap | 40h | - | 1,800 JOD | 2,250 JOD | 2,800 JOD | - |
| Business analystRequirements and specs | 40h | - | 1,450 JOD | 1,800 JOD | - | - |
| UI/UX designerFlows, screens, design system | 40h | - | 1,500 JOD | 1,850 JOD | 2,300 JOD | - |
| Tech leadOwns architecture and the quality bar | 40h | - | - | - | 2,900 JOD | 3,500 JOD |
A dash means we do not sell that level for that role. Associate: never placed into a client staff-aug seat.
What moves the number
| Remote from AmmanThe 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. | x 1.00 |
| Hybrid with visitsRemote by default with a trip to your site roughly each quarter, usually the tech lead or the product manager. The uplift covers travel, visa and accommodation. A visit needs a visa, and a visa can be refused. | x 1.09 |
| On-site with youThe engineer relocates to your country and works from your office. Much more expensive because it is a real move: work visa, residency, cost-of-living difference and sometimes a family. It needs 8 to 14 weeks before day one and depends on a visa we do not control. And not every engineer will relocate, whatever the offer. | x 1.85 |
| 3 months | x 1.08 |
| 6 months | x 1.00 |
| 12 months | x 0.95 |
| Ongoing | x 0.92 |
| Gulf · UTC+3/+4 | x 1.00 |
| Central Europe · UTC+1/+2 | x 1.00 |
| UK · UTC+0/+1 | x 1.00 |
| US East · UTC-5/-4 | x 1.08 |
| US Central · UTC-6/-5 | x 1.10 |
| US West · UTC-8/-7 | x 1.16 |
| Flexible · Not fixed | x 1.00 |
| Monthly seats | x 1.00 |
| Fixed-scope project contractWe absorb the overrun; that premium is the price of the risk moving sides | x 1.22 |
| Managed teamProduct management, technical leadership and delivery accountability | x 1.18 |
FAQ
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.
A fixed monthly price per seat for the hours you committed to, from the same published price book. Invoiced at the start of the month on 15 day terms. The price includes salary, employer costs, equipment and operational support. Annual leave, Jordanian public holidays and sick leave are inside the price: nothing is deducted and nothing is added. Capacity changes on one month's notice; sustained overtime is not included, and we usually refuse it because it burns the engineer out within two months.
That is exactly what the commitment curve is for: pick fewer hours on the role page and you will see the hourly rate rise, because recruiting, social security and leave costs do not shrink with the hours. Every role shows its published minimum on its own page, higher for engineering roles and lower for roles like QA and design. Below the minimum you probably need a short consulting engagement rather than a standing seat, and the Folowise Expert Network is a better fit; we will point you there.
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.
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
