Built by Raptors · designed for SuccessFactors
The nábd suite.
Three modules — Pay, Ops, Care — purpose-built for SuccessFactors customers in MENA. All three sit on nábd Core, a shared data foundation that syncs from SuccessFactors, S/4HANA Public Cloud, and the government portals your operations rely on. Each module extends your stack. None of them ask you to leave it.
The principle
Built for what the region actually needs.
SuccessFactors gives MENA enterprises a strong global core. But every region has functions that global products handle generically and local operations handle uniquely — payroll modelled to local labour law, workforce operations for project-based services businesses, employee care extended to MENA realities, and a localisation layer that makes the whole tenant feel native.
nábd is the layer that fills those gaps — without ever asking you to leave SuccessFactors.
How it's structured
A shared foundation, with the apps it carries.
Pay, Ops, and Care are the products you contract for. Each one runs on top of nábd Core — a shared data layer that syncs in real time from SuccessFactors, S/4HANA Public Cloud, and the government portals your operations rely on. Core is included with every module purchase and is never sold standalone.
Payroll engine
nábd Pay
Egyptian and Saudi labour law modelled at the core. WPS-compliant, Saudisation-aware, deployed in weeks.
See Pay
Workforce operations
nábd Ops
For services businesses whose people are the product — engagements, time, skills, utilisation, billing.
See Ops
Employee services
nábd Care
HR case management, asset lifecycle, onboarding and offboarding orchestrated across HR, IT, and facilities.
See Care
Architecture
One data layer. Three modules read from it.
Three sources hold the authoritative picture of your enterprise. nábd Core syncs continuously from those sources. Pay, Ops, and Care read from Core in real time. Core never writes back — it pulls. Module write-backs go directly to the source where applicable.
Sources — authoritative systems
SuccessFactors
Authoritative HR source
EC · ECP · ONB · LMS
S/4HANA Public Cloud
Authoritative finance source
Cost · GL · Vendor
Government portals
Statutory and residency
Muqeem · GOSI · MOL
Foundation
nábd Core
Persistent data layer. Read-only sync from the sources above. Real-time read by the modules below. Built on SAP BTP. Included with every module purchase.
Modules — what you contract for
nábd Pay
Payroll engine
EG · KSA · WPS-ready
nábd Ops
Workforce operations
Engagements · time · billing
nábd Care
Employee services
Cases · assets · joiners
Pattern: sources → Core (read-only sync) → modules (real-time read). One integration surface Raptors maintains end-to-end on each side.
Architectural commitments
Built the way the rest of your SAP estate is built.
Built on SAP BTP
Standard SAP cloud architecture — same security posture, same compliance framework as the rest of your SAP estate.
Continuous sync from sources
SuccessFactors, S/4HANA, and government portals refreshed at frequency tuned to source-system limits — most master data current within minutes.
Real-time read by modules
Pay, Ops, and Care all read from one shared Core instance — no module-to-module reconciliation gap.
Multi-tenant SaaS
Your data isolated in a tenant addressable to your organisation. No shared schemas.
Single sign-on with SuccessFactors
Your users sign in once — no second identity to manage.
MENA data residency
Core runs in SAP BTP regions that satisfy Egyptian PDPL and Saudi PDPL data-residency requirements.
Buyer context
For two situations.
If you are an existing SuccessFactors customer in MENA
nábd extends your tenant with the modules you need — without a global change initiative. Same identity, same UX, same governance.
If you are a new SuccessFactors deployment shipped by Raptors
nábd modules ship alongside your implementation — same delivery team, same go-live, same post-go-live AMS book.
Pilot reference
Raptors runs nábd on itself.
We are the pilot tenant for nábd Pay and nábd Ops — our payroll runs on Pay, our engagement and time tracking run on Ops, both reading from a Core instance synced from our SuccessFactors and S/4HANA Public Cloud systems. Additional reference customers slot here as they go live.
[VERIFY: confirm pilot customer naming and any published outcome metrics before publish.]
Next step
Extend your SuccessFactors tenant. Don't replace it.
We map your gaps against the four modules, then show you what a deployment looks like on your timeline.