Ask anyone who runs a business in the Kingdom how a single commercial registration renewal actually gets done, and the answer is rarely simple. One task can reach across the Ministry of Commerce, Qiwa, Muqeem and GOSI. Each has its own login, its own fees, and its own idea of what counts as finished. Somewhere in between sits a person holding it all together with a spreadsheet and a phone.
This is the reality for the providers who deliver business services, the accounting, HR, legal and PRO firms, and for the companies that depend on them. The work matters. The way it is run is what breaks.
The hidden cost of fifteen platforms
The Saudi business stack is genuinely impressive. Qiwa, GOSI, Muqeem, ZATCA, Balady, Mudad, Nitaqat, HRSD and more have moved core government processes online. But each platform was built for its own purpose, not to talk to the others. So the burden of stitching them together lands on the people doing the work.
That burden shows up in four predictable ways.
Scattered credentials
Logins, fees and rules across 15+ portals.
Silent expiry clocks
Every Iqama, permit and license ticking.
Manual hand-offs
Chasing a signature, a doc, a fee.
No shared record
Nobody can say who did what, or when.
None of this is a failure of effort. It is a failure of system. The information exists, but it lives in too many places, in too many heads, with no single source of truth.
Services are workflows, and the work is two-sided
The insight that changes everything is simple. A business service is not a document or a request. It is a workflow: an ordered set of steps, each with prerequisites, fees, deadlines, and an owner. Renewing an Iqama, registering a trademark, confirming an annual CR. Every one of them has a shape.
And almost every workflow is two-sided. The provider does the expert work. The company has to approve, pay, sign or upload at the right moments. When those two sides live in separate inboxes, the workflow stalls in the gaps between them. The fix is not more messages. It is one shared, live record that both sides can see.
When a service is a workflow instead of an inbox, nothing stalls silently, because every step knows what it is waiting for and who it is waiting on.
What an operating system looks like
This is the gap Shrkity was built to close. Instead of asking people to coordinate across fifteen platforms by hand, it gives the work a single home.
Providers use a desktop workspace with a visual workflow builder. They compose steps, set dependencies and per-step SLAs, attach pricing and government fees, and publish a versioned service the whole team runs the same way. Government bindings carry the rules and fees of Qiwa, GOSI, ZATCA and the rest, so eligibility is checked before a step starts rather than discovered after it fails.
The companies they serve use a mobile app. They connect to their provider by invite link or QR, then see only what needs them: sign this letter, pay this fee, upload this document. The same request is one record on both sides, so progress is always live, never reconstructed from memory. A documents view tracks CR, Iqama and license expiries before they bite, and a compliance score keeps the whole picture in one glance.
Underneath all of it runs an audit trail. Every step, payment and approval is logged inside the same transaction as the change itself, so an action can never quietly happen without a record. That is what turns a pile of activity into trust: when a client asks what happened, the answer is a record, not an argument.
Built for the Kingdom
An operating system for Saudi business services has to speak the local language: CR numbers, Iqama clocks, Nitaqat zones, SAR fees, ZATCA Phase-2 invoicing, and an Arabic-first, RTL-ready interface. As the Kingdom's services continue to go digital under Vision 2030, the value is not another portal. It is the layer that ties the existing ones together, so providers can scale and companies can stay compliant without living inside fifteen browser tabs.
That is the bet behind Shrkity. The platforms are already here. The work is already being done. What was missing was a system to run it on.