Run overseas deployment
without losing the thread
SimbaFlow is the operating system for labour export agencies — candidate intake, embassy and Tasheer processing, government clearances, travel logistics and commission settlement, all on one pipeline your whole team can see.
Isolated database schema per agency · MFA on every account
Candidate pipeline
50 active · updated just now
EP52••••1
EP41••••8
Riyadh · KSA
Doha · QAT
- One board
- every candidate, every stage
- Schema-per-tenant
- hard data isolation
- Real-time
- status the moment it changes
- Full audit trail
- who did what, when
Built for the corridors you deploy into
- Saudi Arabia
- United Arab Emirates
- Qatar
- Kuwait
- Jordan
- Bahrain
- Oman
- Lebanon
The platform
Everything the deployment desk touches
Agencies run this work across spreadsheets, WhatsApp threads and a filing cabinet. SimbaFlow puts the whole lifecycle in one system without flattening how your agency actually operates.
Configurable workflow engine
Define your own stages, statuses and transition rules. Action buttons appear only when the field conditions are met, and parallel tracks like Medical and Tasheer run side by side.
- Event-sourced history
- Per-agency stage rules
- Parallel tracks
Candidates and documents
Register a candidate once and carry passport details, labour ID, medicals and contracts through every stage — with a generated CV and a full status timeline attached.
- Passport & labour ID
- Document vault
- Auto-generated CV
Agency ERP
Staff, offices, branches and partner agencies in one directory, with custom roles and permissions each agency defines for itself.
- Staff & offices
- Partner directory
- Custom roles
Real-time everywhere
A WebSocket connection pushes stage transitions to every open screen, so the visa desk and the travel desk are never working from a stale list.
- Live status changes
- Instant notifications
- No refresh needed
Commission and finance
Track what each deployment earns with double-entry accounting, from partner splits through to settlement — tied back to the candidate that generated it.
- Double-entry ledger
- Partner splits
- Settlement tracking
Reporting and audit
Every operation is written to an audit trail, and the numbers your regulators and partners ask for export to Excel or PDF without a spreadsheet detour.
- Immutable audit log
- Excel & PDF export
- Operational analytics
Workflow
Your pipeline, not a template
SimbaFlow ships with the default deployment pipeline below. Every agency then bends it to the way they actually work — stages, statuses, transition rules and the conditions that decide which action buttons appear.
Stage 1
Intake
Register the candidate, collect documents, verify the passport.
Stage 2
Embassy
Visa file, Tasheer appointment, stamping and collection.
Stage 3
LMIS
Government labour registration and clearance.
Stage 4
Ticket
Booking, fare confirmation and itinerary issue.
Stage 5
Departure
Countdown, briefing and airport handover.
Stage 6
Arrival
Employer confirmation and probation follow-up.
Stage 7
Commission
Invoice, partner split and settlement.
Stages you control
Rename them, reorder them, add your own. Nothing here is hard-coded into the product.
Parallel tracks
Medical and Tasheer can run at the same time without one blocking the other.
Event-sourced
Every transition is an event, so the timeline reconstructs exactly what happened.
Security
Multi-tenant, and it means it
You are holding passports, medical records and contracts for people who cannot afford a data leak. Isolation is structural here, not a filter someone might forget to apply.
Schema-per-tenant isolation
Each agency gets its own PostgreSQL schema. Not a tenant column you have to trust — a separate namespace, so one agency's query cannot reach another's rows.
JWT with refresh tokens
Short-lived access tokens, rotating refresh tokens and server-side revocation on logout.
MFA and granular roles
Multi-factor authentication on any account, with permissions your agency defines down to the individual action.
Audit trail on every write
Who changed what, when, and from where — retained for the whole life of the candidate record.
simbaflow · postgres 16
isolatedCross-tenant reads are impossible by construction — the connection is scoped to a single schema for the life of the request.
Pricing
Priced per agency, not per candidate
Your busy season shouldn't cost more to run. Every plan includes the isolated schema, the audit trail and unlimited candidate records.
Starter
For a single office getting off spreadsheets.
$249/month
Start a trial- Up to 10 staff accounts
- Default deployment pipeline
- Candidate & document management
- Real-time status updates
- Email support
Agency
For agencies running multiple branches and destinations.
$690/month
Book a demo- Unlimited staff accounts
- Configurable stages & transition rules
- Parallel tracks and custom actions
- Commission & double-entry finance
- Partner agency directory
- Reporting with Excel & PDF export
- Priority support
Enterprise
For groups, franchises and platform operators.
Custom
Talk to us- Multiple agencies under one platform admin
- SSO and custom retention policies
- Telegram / WhatsApp bot integration
- API access and data residency options
- Onboarding and migration support
All prices in USD, billed monthly. Annual billing saves two months.
FAQ
Questions agencies ask first
Can we keep our own stage names and process?
Yes — that is the point of the workflow engine. You configure stages, statuses, transition rules and the field conditions that decide which actions appear. The default pipeline is a starting point, not a constraint.
How is our data separated from other agencies?
Every agency is provisioned its own PostgreSQL schema, and each request is scoped to that schema for its whole lifetime. There is no shared candidate table to filter, so a missed condition cannot expose another agency's data.
What happens to the candidates we already have on file?
Bring them in during onboarding. Candidate records, passport and labour ID details, and the documents attached to them can be imported, and each one lands at whichever stage it is currently sitting in.
Do our branch offices and partner agencies get access?
Offices, branches and staff are modelled directly in the system, and you define the roles and permissions that govern what each of them can see or change. Partner agencies live in their own directory with their commission terms attached.
Does the team have to refresh to see updates?
No. A WebSocket connection pushes stage transitions to every open screen as they happen, with a notification on the change.
Can we get the numbers out for regulators and partners?
Reporting covers the operational and financial side, and anything you can see on screen exports to Excel or PDF. Every write is also recorded in an audit trail you can hand to an auditor.
See it on your own pipeline
Walk us through how your agency deploys today. We will map it onto SimbaFlow live — stages, roles and all — in about thirty minutes.
Or write to hello@simbaflow.com