wurqurBook a scoping call
  • Checks & evidence

Compliance & quality automation

Four Wurqurs find the records across every system, carry out what a person decides, and produce the proof it happened.

handling a request · 60-person HR software company

30 min2–3 minRead the engagement
  • Evidence Clerk

    Collects the proof that things happened and assembles it into a pack an auditor would accept.

    by hand$1,333/mo

    with your Wurqur$100/mo

  • Rights Handler

    Runs a data subject request end to end — finds the person everywhere, routes the decisions, produces the evidence.

    by hand$4,375/mo

    with your Wurqur$303/mo

  • Pre-flight Check

    Checks the thing against the standard before it goes out, and produces evidence for each check.

    by hand$675/mo

    with your Wurqur$56/mo

  • Access Reviewer

    Works out who can reach what, compares it with who should, and drives the removals.

    by hand$1,387/mo

    with your Wurqur$99/mo

Two is a normal build. Your volumes and your rates, in the calculator.

What it costs you now.

Checks live in people's memory, and memory holds until the week gets busy. The cost lands months later, when somebody has to prove the check happened.

  • The sixth system

    A deletion runs clean across five systems and misses the sixth, because the list of systems lives in one person's head.

  • A leaver, still live

    Someone left in March. Their account still opens the billing system in September, because the quarterly review looked at the directory alone.

  • Proof, assembled backwards

    An auditor asks for evidence of a check from March, and three people spend a day rebuilding it out of Slack threads and calendar invites.

They work inside what you already run.

Entra
Okta
Google Workspace
Workday
ServiceNow
Zendesk
Salesforce
Stripe
PostgreSQL
SharePoint
GitHub
Contentful

Not listed? Tell us what you run.

Questions.

What does a build cost?

$2,500 to $5,000 for a Wurqur built on the systems you already run, paid once.

Who decides what may lawfully be erased?

A person on your side, every time. The Rights Handler finds the records, assembles what it found, and puts the decision in front of somebody with the authority to make it, then carries out what is agreed and records what was done. In the HR software company above, one request meant finding a single person across the application database, Salesforce, Stripe, support records and Google Workspace.

What happens to the things it cannot decide?

They go to a person, by a rule you agree before anything is built. A Rights Handler escalates every decision about what may lawfully be erased. A Pre-flight Check escalates every failed check, with the reason. An Access Reviewer escalates leavers with live access and unjustifiable privilege, and an Evidence Clerk escalates a gap in the trail.

Can our compliance platform already do this?

No, and where your platform already does the work, keep it. OneTrust and Osano run a privacy programme properly, your directory's own review covers your directory, and your CI covers your code. These four exist for what none of them covers: the obligation is identical at 40 people and at 4,000, access lives in a dozen systems, and the checks on content, brand and accessibility are still somebody's memory. A release gate for a 40-person B2B SaaS company took clearing a release from a remembered checklist to under 10 minutes.

How long before it is doing real work?

Two Wurqurs took four weeks of work: two weeks building, half a week deploying, a week of testing on your real cases with the old way still running, and the fixes that came out of it.

Tell us what is eating the week.

Scoping is free and it ends with one number.