Workflow orchestration using existing SaaS platforms

We put the SaaS tools the group already licenses to work as governed workflows: order platforms, spreadsheets, messaging tools, forms, CRM, ledger and file storage. Each workflow has a trigger, a set of steps, an approval where money or customers are affected, and an owner.

• A software and workflow register: tools, licences, owners, costs and the data each holds.
• A workflow catalogue with trigger, steps, approver and owner for each.
• Built workflows, tested against real cases.
• An approvals rule for steps that move money, change prices or contact customers.
• A change and access procedure, so workflows survive staff changes.
• A short list of tools to retire, with the saving shown from your own invoices.

• Every active subscription has an owner.
• Documented workflows match the workflows that run, and the two lists are compared.
• Staff spend fewer hours moving information by hand, measured as hours of manual transfer removed per month.
• Licence cost is retired where tools overlap, and the amount retired is shown from your invoices.
• Workflows survive staff changes, and the ones that stopped after a change are counted.

Software sprawl costs twice: once in subscriptions and again in the people paid to carry information between them. Workflows built ad hoc by individual staff break when they leave, and nobody can say what runs on a personal account.

• Staff have built connections between tools on personal accounts.
• You pay for several tools that do overlapping jobs.
• Information leaves one tool only when someone remembers to export it.
• A proposal for a new platform arrives before the old ones are used fully.
• Nobody can list which workflows run automatically today.

Groups that have accumulated many subscriptions across brands and teams, and have staff linking them by hand, and chairmen who want a rule that no new tool is bought until the existing ones are used well.

Qasim Abbas has spent more than 16 years inside Gulf family-based and venture-backed groups, where subscriptions pile up as cost lines nobody owns. We start with the question every board should have answered: what the group pays for and what it uses.

We work on the platforms in your register, including whichever workflow tools the group already pays for. See how fees work.

How do you handle approvals?

Any step that moves money, changes a price or contacts a customer needs a named person's approval inside the workflow, and the approval is logged.

What does the register show?

Every tool, its licence, its owner, its cost and the data it holds, so the group sees what it pays for and what it uses.

How do workflows keep running when staff change?

A change and access procedure keeps each workflow running, and every active subscription has an owner.

Gather the tools your teams log into. We show how much of the register overlaps and which three workflows to govern first.