SB StartupBasket
All ideas
76 /100 GO Low complexity

PayRunway — WPS escalation runway for UAE employers

Tells a cash-tight UAE employer exactly which staff to pay today to stay above 85% and dodge a permit freeze.

HRTech SaaS Global MENASMBCompliance-drivenAI-agentSolo-builderCashflow
— views
Evaluation Scores
76/100

GO

Overall Score

17
Problem
12
Demand
13
Build
11
Distrib.
12
Revenue
7
Time
4
Defense

PayRunway — WPS escalation runway for UAE employers

1. One-liner

Tells a cash-tight UAE employer exactly which staff to pay today to stay above 85% and dodge a permit freeze.

2. Trend signal — why now?

On 1 June 2026, UAE Ministerial Resolution No. 340 of 2026 took effect and quietly rewired the Wage Protection System from a filing duty into a live, daily-ticking meter.

Three things changed at once:

  1. The 15-day grace period is gone. Wages for a month must land by the first day of the next Gregorian month. Any payment after that is deemed delayed and non-compliant — no buffer, no discretion.
  2. A day-by-day escalation ladder replaced discretionary enforcement. Day 2: electronic monitoring and MOHRE notifications until payment is proven. Day 5: new work-permit issuance suspended across the establishment file, plus a written warning to the owner. Day 11: administrative fines (for repeat violations within six months). Day 16: labour disputes auto-registered for establishments with 25+ workers. Day 21: precautionary attachment of assets, travel ban on the person in charge, and referral to Public Prosecution.
  3. The compliance floor rose from 80% to 85% — at both the establishment level (85% of total wages due, on time) and the individual-worker level (each worker must receive ≥85% of entitled wage).

That third change created a trap almost nobody has priced. Federal Decree-Law No. 33 of 2021 (the Labour Law) permits salary deductions up to 20%, and up to 50% where multiple grounds apply. But under Resolution 340, any deduction taking a worker below 85% of entitled wage makes that individual transfer non-compliant — so lawful deductions are now effectively capped at 15% per pay cycle for WPS purposes. An employer can follow the Labour Law to the letter and still register a worker as unpaid on the system.

The new-hire grace period was also eliminated: every new hire is in WPS scope from their first pay cycle, and must be on the WPS register and the very next SIF immediately on hire.

Meanwhile the population is large and growing. Over 5.1 million private-sector workers fall under MOHRE jurisdiction, and MOHRE reports 99% of workers in registered establishments are WPS-covered. Registered establishments grew 7.8% in the twelve months to Q3 2025. The rule applies to every mainland private-sector employer regardless of size — down to a sole establishment with one employee.

And the pain is a timing problem, not a solvency problem. As one UAE advisory put it: “For many SMEs, delayed payroll is rarely about unwillingness to pay salaries. More often, it is the result of operational delays, cash-flow timing issues, or fragmented back-office processes.” The same source notes that businesses “relied on the informal flexibility of the 15-day grace period to manage short-term cash flow” — flexibility that is now gone.

Critically, outsourcing payroll does not move the liability. Under Article 5 the establishment remains fully liable even where a PRO or payroll bureau runs the process. The person who gets the travel ban is not the person pressing submit.

Provenance:

3. The opportunity

Every UAE payroll vendor — Bayzat, Yomly, Zoho Payroll, plus the long tail of PRO shops — sells the same thing: generate a valid SIF and submit it. They are execution tools. They assume you have the money on the 28th and the only question is file correctness.

Resolution 340 created a different question that none of them answer: what do I do when I don’t have all of it?

That question now has a precise, computable answer, because MOHRE wrote the maths down. 85% at establishment level. 85% at each worker level. A fixed due date. A known escalation ladder. Which means for any given cash position, there is an optimal set of workers to pay that keeps you compliant — and a set of choices that look reasonable but tip you into a permit freeze.

Concretely, the gaps an execution tool structurally cannot fill:

  • The threshold is non-linear and dual. Paying 85% of your total wage bill is not enough if any individual worker drops below 85% of their own entitled wage. An employer paying “most people most of their salary” can fail both tests while believing they passed. Nobody computes this before submission.
  • The deduction conflict is invisible. A payroll clerk applying a Labour-Law-legal 20% loan deduction has just made that worker non-compliant. The payroll software will happily generate the SIF — it validates format, not the 15% WPS ceiling.
  • The escalation clock has no owner. From the moment the 1st passes, the employer is on a ladder toward a travel ban on a named individual. No tool tells them which rung they are on, what happens next, or how many days remain before work-permit issuance freezes for the whole company.
  • Outsourcing creates a blind spot, not safety. The PRO runs payroll; the owner carries the Article 5 liability and the travel ban. The liable party currently has no independent visibility into whether the delegate actually paid on time.

This is the classic split: the party that files is not the party that is punished. The punished party has no instrument.

4. Target market

  • Primary customer: Owner or finance manager of a mainland UAE private-sector establishment with 5–150 employees — construction subcontractors, facilities-management and cleaning firms, F&B groups, logistics and delivery operators, salons and clinics, small contracting outfits. The signature is lumpy receivables (client pays on 45–60 days) against a hard payroll date on the 1st. Typically Dubai, Sharjah and Ajman mainland; typically already using a bank WPS channel and either a cheap payroll tool or a PRO retainer.
  • Why they buy: Because the penalty is now personal and fast. A Day 5 permit freeze stops them hiring or renewing visas across the entire establishment file — which for a labour-supply or contracting business means they cannot staff the job they just won. A Day 21 travel ban lands on the owner personally. As the advisory literature states plainly, the cause is usually “cash-flow timing issues,” not refusal to pay. They need to know which levers keep them legal this month, and they need it before the 1st, not after.
  • Rough TAM reasoning: 5.1M private-sector workers under MOHRE with 99% WPS coverage. Establishments grew 7.8% YoY to Q3 2025. Even if only the 5–150 employee mainland band is addressable and that band is a few tens of thousands of establishments, capturing 500–1,500 of them at AED 400–1,200/month is a $2M–$5M ARR business. I do not need a large share.
  • Why now for them: Before 1 June 2026, a late payroll was absorbed by the grace period and was a non-event. After 1 June 2026, the same behaviour starts an escalation on Day 2. The behaviour didn’t change; the consequence did. Every one of these employers has now either been through one uncomfortable month-end or watched a peer get frozen.

5. Product sketch (MVP)

  • Runway meter — one number on open: days until the next WPS due date, and days remaining before each escalation rung (permit freeze, fines, dispute registration, travel ban) if the current shortfall persists.
  • 85% dual-threshold simulator — enter available cash, and it computes whether you clear both the establishment-level and per-worker-level 85% tests, flagging every individual who would register as unpaid.
  • Pay-triage recommendation — given a cash shortfall, the specific set of workers and amounts to transfer that keeps both thresholds satisfied, with the workers who must be paid in full ranked ahead of those with headroom.
  • Deduction ceiling guard — flags any deduction that is lawful under Federal Decree-Law 33/2021 but breaches the effective 15% WPS ceiling, with the reason written in plain language.
  • New-hire sweep — checks that everyone hired since the last cycle is on the WPS register and in the next SIF, since the new-hire grace period was eliminated.
  • Delegate watch — for owners who outsource to a PRO or bureau, an independent confirmation that the transfer actually cleared by the due date, given Article 5 leaves liability with the establishment.
  • Escalation dossier — if a deadline is missed anyway, a dated file recording the shortfall reason, the partial payments made, the workers kept above 85%, and the remediation date, in a form usable in a MOHRE conversation.

6. AI angle — what’s load-bearing

Deliberately narrow, and honest about it: the core is arithmetic, not AI. The 85% dual-threshold test, the runway countdown, and the triage optimisation are deterministic calculations over a payroll file and a calendar. That is a feature, not a weakness — a compliance decision that determines whether an owner gets a travel ban must be reproducible and explainable, not sampled from a model. Anyone claiming an LLM is deciding who gets paid is selling risk.

AI does three jobs where it genuinely earns its place:

  1. Deduction classification. Employers arrive with messy, free-text deduction lines — “advance”, “loan recovery”, “damage to vehicle”, “absence adjustment”, “salik”. Mapping those to Labour Law categories, determining which are lawful grounds at all, and then testing them against the 15% WPS ceiling is a language task over unstructured input that no rules engine handles cleanly.
  2. Payroll file ingestion. These employers keep payroll in spreadsheets with inconsistent column names, merged cells, mixed Arabic and English headers, and per-company conventions. Getting a reliable employee/wage/deduction table out of that variety is exactly what a model does well and a parser does badly.
  3. Drafting the MOHRE-facing narrative. Turning a shortfall into a dated, defensible explanation of what was paid, to whom, why, and when the balance follows.

Strip the AI out and you still have a product — a worse one, with hours of manual data entry and no deduction reasoning. Strip the arithmetic out and you have nothing. I’d rather be clear about that than dress it up.

7. Localization angle

This is a UAE-first play by construction — the entire product encodes one jurisdiction’s rules: Resolution 340’s ladder, the 85% dual threshold, the SIF schema, MOHRE’s establishment-file mechanics, and the Federal Decree-Law 33/2021 deduction grounds.

Localization specifics that matter:

  • Language: Arabic and English throughout; the workforce and the owners frequently differ in first language. Hindi/Urdu/Malayalam worker-facing payslip messaging is a cheap, high-goodwill addition given the labour demographics.
  • Calendar: the due date is explicitly the first day of the Gregorian month — worth handling precisely, alongside UAE weekend and public-holiday banking cut-offs, which determine when a transfer must actually be initiated to land in time.
  • Channel: WhatsApp is the default business channel in the Gulf. The runway alert belongs in WhatsApp, not email.
  • Pricing: AED-denominated monthly billing at a level a 20-person contractor approves without a procurement conversation.

The natural second market is Saudi Arabia, which runs its own WPS with an analogous mudad/GOSI filing structure and comparable establishment-level enforcement — same product shape, different rule table. That’s the expansion, not the launch.

8. Business model — path to $1M–$5M ARR

  • Pricing: tiered by headcount, flat monthly, AED-billed.
    • Up to 25 employees — AED 399/month (~$109)
    • 26–75 employees — AED 799/month (~$218)
    • 76–150 employees — AED 1,499/month (~$408)
    • PRO/bureau partner plan — AED 2,500–6,000/month for a multi-establishment console covering 10–40 client files
  • Why this clears: benchmarked directly against what these buyers already pay. Zoho Payroll UAE runs from AED 15/employee/month — a 40-person firm is already paying ~AED 600/month for payroll execution alone. PRO service retainers run AED 1,000–5,000/month. AED 799 to avoid a permit freeze that stops all hiring is not a difficult conversation for a contractor who just won a staffing job.
  • ACV: blended AED 9,600/year ($2,600) for direct SMB accounts; AED 45,000/year (~$12,300) for bureau accounts.
  • Rough math to $1M ARR: ~380 direct accounts at the AED 799 tier ≈ AED 3.64M ≈ $992K. Or a mix: 250 direct + 12 bureau partners.
  • Rough math to $5M ARR: ~1,400 direct accounts plus ~60 bureau/PRO partners, with Saudi launched as a second rule table. Requires the bureau channel to work — one PRO firm carrying 30 client establishments is worth 30 direct sales at a fraction of the CAC.
  • Expansion path: headcount tier creep as clients grow (their establishments grew 7.8% YoY as a population); add-on for the escalation dossier and MOHRE correspondence; the Saudi rule table as a second seat; eventually the delegate-watch product sold to the PRO firms as a liability-shield they can resell to their own clients.

9. Go-to-market wedge — first 100 customers

  • PRO and payroll-bureau partnerships (primary channel). There are hundreds of PRO service firms in Dubai and Sharjah, each carrying 10–50 mainland establishment files, and every one of them just inherited a problem: under Article 5 their client stays liable, so when a client gets frozen the PRO gets blamed but has no instrument to prevent it. Approach 60 PRO firms with a white-labelled multi-establishment console. Land 12 and you have 150–400 establishments in the funnel with one relationship each. This is the fastest path and I’d start here on day one.
  • Month-end trigger outreach. The pain has a calendar. Run outbound in the 25th–31st window each month, when the finance manager is actively staring at a shortfall. Scrape mainland establishments in labour-heavy sectors (contracting, FM, cleaning, F&B, logistics) from Dubai Chamber and free directory listings, filter to the 5–150 employee band, and send an Arabic/English WhatsApp with a single hook: a free one-off 85% check on this month’s numbers. Expect low single-digit reply rates on cold, but the ones who reply are in acute pain that week.
  • The free 85% calculator as the top of funnel. Publish a public tool: paste your wage bill and available cash, get back whether you clear both thresholds and who falls below. This is genuinely useful, ranks for the queries these employers are typing right now (“WPS 85 percent”, “salary late UAE penalty”, “Resolution 340”), and captures the establishment name and headcount for follow-up. Note the risk honestly — a free calculator can cannibalise the paid product, so the free version answers “are you compliant?” and the paid one answers “what do I do about it, every month, automatically, with the paper trail.”
  • The advisory and law-firm slipstream. Morgan Lewis, DLA Piper, and a long tail of UAE advisories published Resolution 340 explainers between May and August 2026. That’s an audience already assembled and already alarmed. Offer the tool as the practical companion to their alert — co-branded, no fee — to the mid-tier accounting and PRO advisories who lack an in-house product.
  • Sector associations and labour-supply clusters. Contracting and FM firms cluster in industrial zones (Al Quoz, Sharjah Industrial, DIP). Physical and WhatsApp-group presence in those clusters reaches the exact profile — lumpy receivables, large hourly workforce, hard payroll date.

10. Build complexity — justification

Low. The rule set is small, public, fully specified, and arithmetic: a fixed due date, two percentage thresholds, a five-rung escalation ladder, a documented SIF schema, and a finite list of lawful deduction grounds. No custom models, no novel infrastructure, no regulatory approval to operate — this is an advisory tool sitting alongside the employer’s existing bank WPS channel, not a payment institution.

The real work is unglamorous: spreadsheet ingestion across messy real-world payroll files, a rules table that must be exactly right and kept current, WhatsApp Business API delivery, and Arabic/English UI. A technical founder with a UAE payroll advisor on call ships a credible v1 in 8–10 weeks. The MVP does not need bank integration — the employer tells it the cash position, which sidesteps the hardest integration entirely and is how I’d launch.

11. Gating checklist

GatePass?Note
Legal in target market✅Advisory/calculation tool. Does not move money, does not file on the employer’s behalf, does not require a payment or financial-services licence. Must avoid presenting output as legal advice.
Ethical — no harm / dark patterns⚠️ ✅Passes, but with a real edge. The product optimises partial payment of wages, which reads uncomfortably. It is defensible because it operates strictly inside a threshold the regulator itself defined, and its effect is to keep workers above the 85% floor rather than below it — a cash-short employer left to guess pays people arbitrarily and pushes some to zero. The design must never recommend deferring wages an employer can actually afford, and must always show the full-payment path first.
Market exists (evidence above)✅5.1M workers under MOHRE, 99% WPS-covered, establishments +7.8% YoY; paid incumbents (Zoho AED 15/employee/mo, Bayzat 4,000+ companies) prove budget exists.
1–5 person team can build this✅Deterministic rules engine + file ingestion + messaging. 8–10 weeks for 1–2 people.
Launchable with <$50K / ₹40L✅Well under. Main costs are a UAE payroll/legal advisor on retainer and WhatsApp API volume.

All five gates pass.

12. Feasibility score

AxisWeightScoreNotes
Problem intensity2017/20Monthly, dated, and personal — the ladder ends in a travel ban on a named individual and a permit freeze across the whole establishment file. Not a paperwork irritation. Held below 18 because the acute pain lands only in months where cash is actually short; a well-funded employer feels nothing.
Demand evidence1512/15Strong structural evidence: enacted resolution with a verified commencement date, four independent legal/advisory sources, large covered population, existing paid payroll market. Marked down because I could not find UAE employers complaining about this specific triage problem in their own words — advisory firms describe the pain, employers haven’t said it publicly. That is the weakest link in the case.
Build feasibility1513/15Public arithmetic rule set, no bank integration required for v1, no licence. Deducted for messy spreadsheet ingestion and Arabic/English handling.
Distribution clarity1511/15The PRO/bureau channel is specific, enumerable, and structurally motivated by Article 5 liability. Deducted because it is unproven and PRO firms are relationship-driven and slow to adopt software; the direct month-end outbound is cheap but cold.
Revenue mechanics1512/15Pricing benchmarked against real UAE spend (Zoho per-employee, PRO retainers). ~380 accounts to $1M is achievable within the population. Deducted because the bureau tier — which the $5M path depends on — is an assumption.
Time to first revenue107/10Monthly pain cycle means a natural close every month-end, and the free 85% check converts warm. But this is a considered B2B purchase by an owner, not a card-on-file impulse; realistically 6–10 weeks from launch.
Defensibility104/10Honest score. The rules are public and the maths is simple — Bayzat or Yomly could ship the 85% simulator as a feature in a quarter if they decided to. The only durable moats are the accumulated per-establishment history (which becomes the MOHRE-facing paper trail) and the PRO channel relationships. Execution and speed, not a moat.
Total10076/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · domain-expertise-required

You need someone who can build a rules engine and ingest ugly spreadsheets, paired with genuine UAE payroll/labour-law knowledge. Getting the 85% dual test or the deduction ceiling wrong doesn’t produce a bad recommendation — it produces a client with a travel ban. This is not a domain to learn on the job. A UAE-resident co-founder or a paid advisor on retainer is mandatory, not optional.

Key assumptions to validate (3–5)

  1. Assumption: Cash-short UAE SMEs genuinely don’t know how to triage against the 85% dual threshold, and are currently guessing. How to test: 20 structured interviews with finance managers at 5–150 employee mainland firms in contracting/FM/F&B. Ask them to compute, on the spot, whether a specific shortfall scenario clears both tests. Count how many get it right. If most do, the product is a convenience, not a necessity, and the score drops 10 points.
  2. Assumption: PRO and payroll-bureau firms will resell or white-label rather than treat this as a threat to their advisory value. How to test: pitch 15 PRO firms with the multi-establishment console. Look for 3+ signing a paid pilot within 6 weeks. If they all want to build it themselves or see it as commoditising their advice, the primary channel collapses.
  3. Assumption: Employers will disclose their cash position to a third-party tool. How to test: in the free 85% calculator, measure what fraction of visitors who start actually enter a real available-cash figure versus abandoning. This is a genuine adoption risk — the input is the most sensitive number in the business.
  4. Assumption: Incumbents (Bayzat, Yomly, Zoho) don’t ship an 85% threshold simulator within 6 months. How to test: monitor their release notes and UAE marketing monthly. This is the clearest kill signal on the whole idea.
  5. Assumption: The willingness-to-pay is AED 400–800/month, not AED 100. How to test: price-test three tiers with the first 30 inbound leads from the free calculator.

Risk flags

  1. Ethical/positioning risk: The product optimises partial wage payment. Framed carelessly, it reads as “how to underpay your workers legally” — which would be reputationally fatal in a market with a real history of wage-abuse scrutiny, and would rightly attract MOHRE’s attention. The framing must be uncompromising: this exists to keep workers above the regulator’s floor when cash is short, and it always presents the full-payment path first. If the founder can’t hold that line, don’t build it.
  2. Regulatory risk: Resolution 340 is three months old. Thresholds, the ladder, and the deduction interpretation can all be amended or clarified — and UAE labour rules have moved repeatedly. The entire product is a bet on one rule table staying roughly stable. Worse, MOHRE could publish its own free compliance calculator and vaporise the wedge overnight.
  3. Defensibility risk: Public rules, simple maths, incumbents with the distribution and the payroll data already in hand. The 6-month head start is the whole advantage. If Bayzat ships this as a checkbox, the direct business is gone and only the PRO channel survives.
  4. Demand-evidence gap: I am inferring the triage pain from advisory commentary and the structure of the rule, not from employers stating it. That inference is reasonable but unconfirmed, and it is the single thing most likely to be wrong.
  5. Concentration risk: One jurisdiction, one regulator, one rule. Saudi is the hedge but it’s a second build, not a copy-paste.

14. Structured verdict

Score:                  76/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder based in or close to the UAE, paired with a
                        payroll/labour-law advisor on retainer. Must be comfortable
                        selling to owner-operators and PRO firms, not to HR departments.
Time to revenue:        8-12 weeks (8-10 week build, close inside one month-end cycle)
Capital to launch:      $10-15K (AED 37K-55K) - advisor retainer, WhatsApp API, hosting
Top 3 assumptions to validate first:
  1. Cash-short SMEs cannot correctly compute the 85% dual threshold today -
     20 structured interviews with a live scenario test; look for majority failure
  2. PRO/bureau firms will resell rather than compete -
     pitch 15 firms, look for 3+ paid pilots within 6 weeks
  3. Employers will actually input their cash position -
     measure completion rate on the free calculator's cash field
Kill criteria:
  - Abandon if fewer than 3 of 15 PRO firms sign a paid pilot within 6 weeks
  - Abandon if Bayzat, Yomly or Zoho ships an 85% threshold simulator before v1 launch
  - Abandon if fewer than 25% of free-calculator users enter a real cash figure
  - Abandon if MOHRE publishes an official compliance/triage calculator

15. Next step — 1-week validation sprint

  • Day 1–2: Build the free 85% dual-threshold calculator only — no accounts, no billing. Establishment wage bill in, available cash in, verdict out plus the list of workers who fall below their individual 85%. Ship it in Arabic and English. Simultaneously, pull a list of 60 Dubai and Sharjah PRO firms from public directories.
  • Day 3–4: Push the calculator into three channels at once: WhatsApp outbound to 200 mainland establishments in contracting/FM/F&B filtered to 5–150 employees; direct outreach to the 60 PRO firms offering the multi-establishment console; and comments on the UAE advisory posts about Resolution 340 that are already ranking. Run 10 of the 20 structured interviews in parallel, using the live scenario test.
  • Day 5: Decide on three falsifiable numbers, not vibes:
    1. Threshold ignorance: of the 10 interviewed finance managers given a live shortfall scenario, do 6 or more compute the 85% dual test incorrectly? If most get it right, kill or reshape — the product is a convenience.
    2. Channel signal: did 3 or more of 60 PRO firms agree to a paid pilot conversation? Below that, the primary channel is unproven and the $5M path is fiction.
    3. Disclosure willingness: did 25% or more of calculator users who started actually enter a cash figure? Below that, the core interaction is broken regardless of how good the maths is.

Two of three must clear to proceed to build. All three failing is a clean kill, and I’d rather find that out in a week than after a 10-week build.

Interested in a detailed proposal?

Get a deep-dive with market research, competitive analysis, and implementation roadmap.

Contact us

info@startupbasket.ai