For Saudi corporate-services & compliance firms
Compliance OS is the operating system for firms that manage corporate, HR, accounting and regulatory work for many clients. From the first enquiry to renewals, portals, evidence and billing — one connected model instead of spreadsheets, inboxes and shared passwords.
Bring one real client workflow. We'll show how it maps into Compliance OS.
The problem
Excel
Expiry dates, trackers
Documents, instructions
Client answers, OTP requests
Shared drives
Scans, versions, drafts
Calendar reminders
Personal, not shared
Government portals
Status, one login at a time
Accounting
Billed — or not
Staff memory
The real process
Compliance OS: one operating model for all of it.
The product model
Task managers track tasks. Compliance OS knows who the client is, which legal entity a requirement belongs to, which service created it, who owes it, which portal it runs through, what evidence closes it and whether it can be billed.
Win the client
Sales context carries into operations.
Logged with goals and services of interest. A duplicate check warns of existing records.
Answers marked Known, Unknown or To confirm. Proposal fees come from the Fee master.
Converting creates the customer, its legal entities and the onboarding in one step.
Set up the work
Driven by what the client actually is.
One customer, many compliance subjects. Customer and legal entity are separate.
Each service is pinned to a published version, so later changes don't rewrite this client's scope.
Generated by your rules, each with an owner: Client, your firm or the Authority.
Run it
Day-to-day, across every client.
Assigned, due-dated tasks. Portal access is logged, with a reason.
A step that needs evidence can't be completed without it.
Chargeable work shows in Finance. Recurring work and renewals keep the cycle going.
Why it matters: every item in the chain keeps its link to the one before it. That's how a blocker, an expiry or an unbilled job can be traced back to the client, the entity and the rule behind it.
How it works
Control what's due, blocked and expiring. Execute by turning services into requirements and work. Scale by encoding how your firm works so it doesn't depend on one person.
Control · Home
Not another dashboard. Home answers one question: what needs me today? Blockers come first, then your work, what's waiting on the client and what needs your approval.
Control · Customer 360
Open a customer and see the relationship, its legal entities, requirements, work, documents, billing, history, portals and conversation — with blockers and exceptions pinned to the top.
Control · Work queue
Managers switch to Team and see everyone. Specialists switch to Mine. Click a status tile to filter.
Control · People & calendar
Expired IDs are called out at the top of People. Every ID shows its expiry date and status — Valid, Renewal due or Expired — next to the open renewal work for that person.
Execute · Onboarding
Enquiry, qualification, proposal, customer, guided onboarding, documents, activation. What you enter changes what's required — so the client isn't pushed through the same checklist as everyone else.
Control · Portal vault
Each legal entity has its own portal logins. They're write-only: once saved, nobody can read them back. To use one, your team opens the portal, picks a reason and sees the credentials for 60 seconds.
Before
After
To be precise: Compliance OS doesn't sign in to portals for you. It controls and records who gets the credentials, and why.
Control · Finance
Completed chargeable work shows up as Unbilled — with the client, fee item, fee type and amount — next to invoices and subscriptions.
Scale · Setup Studio
The system isn't built around one frozen checklist. Your compliance team defines how each service works — and the rest of the product follows it.
A service is composed from reusable masters. It references them; it never copies them.
Services, requirements, rules, documents, portals, authorities and fees are separate masters. Fee amounts live only in the Fee master, with effective dates — never in a service or template.
Build rules as WHEN… AND… THEN add requirement. Values come from your masters, not free text, and every branch is shown as a plain sentence a reviewer can check.
Document types carry validity rules, review checklists and legalisation routes by country group — set once, applied wherever the rule fires.
Rules & simulator
Describe a client scenario — legal form, shareholder, parent country, activities, hiring, premises — and see the requirements it generates, who owns each, and the rule and version behind it.
WHEN Parent country is <country from master>
AND Shareholder type is Corporate
THEN add requirement <document from master>
Illustrative structure of a rule, not a real configured rule. Conditions and outcomes are picked from your own masters.
Versioning
Publishing creates a new version and never edits the old one. Engagements stay pinned to the version they started on, and nothing changes for them without a deliberate migration.
Built for Saudi operations
Switch language from the top bar. Navigation, layout and dates mirror for right-to-left reading.
Turn on Show Hijri in the calendar to see Umm al-Qura dates beside Gregorian on every day.
Legal entities, Iqamas and permits, and portals such as Qiwa, Muqeem, GOSI, Mudad and MISA appear throughout the sample workspace. Document masters carry legalisation routes (apostille, notarisation, translation) by country group.
Document-request emails are available in English and Arabic.
Who it's for
The strongest fit is a firm managing many clients, many legal entities, many employees and many portals — where memory, Excel and inboxes stop being dependable infrastructure.
From enquiry to an activated entity: qualify, propose, convert, onboard, collect documents, activate.
Enquiry → Onboarding → Activation
Ongoing requirements, renewals, portals and filings for each legal entity, with owners and due dates.
Requirements → Work → Evidence
People, Iqamas, visas and permits, with renewal tasks next to every ID.
People → ID expiry → Renewal task
Recurring filings and uploads on a schedule, with chargeable work and subscriptions visible in Finance.
Recurring work → Finance
Run the whole client relationship in one system — one customer, many entities, many services.
Customer 360
Before & after
Tracks tasks. Compliance OS also understands clients, entities, services, requirements, expiries, portals and evidence.
Records dates. Compliance OS turns them into assigned work, blockers and a calendar.
Stops around customer acquisition. Compliance OS carries the relationship through onboarding and into ongoing work.
Describes today's process. Compliance OS keeps it as versioned, testable configuration.
Security & control
Compliance firms hold the keys to their clients' government accounts. These are the controls the product enforces.
Per legal entity and portal. Saving needs the Portal Vault Manager role. Values are never shown again after saving.
Opening a portal requires a reason. A permanent log records who opened which portal, when and why.
Sensitive actions — opening a portal, saving credentials, approving Studio changes — can ask users to confirm it's them without losing their place.
Authenticator-app codes, optional or required at first sign-in. Admins can see who hasn't set it up and reset a device without seeing secrets.
Seven roles with read, write, create, delete, submit and export permissions per record type, managed in Admin.
Nobody approves their own change. Activity is append-only — entries can't be edited or deleted.
Isolated by workspace. Each workspace runs on its own site, and its data doesn't mix with other companies'. For hosting, data-residency and security questions specific to your rollout, ask us in the demo.
Book a demo
Bring a real client workflow to the demo. We'll show how it maps into Compliance OS — enquiry, onboarding, Customer 360, work, expiries, portals, billing and Setup Studio.
Prefer email? inquiry@dvnks.com
A few details so we can prepare something relevant. No pricing pressure, no obligation.
Screens show a fictional sample workspace. Names, IDs and amounts are not real clients.
