INTUDLY

How it works

From a regulator's update to audit-ready proof.

Every step has an input, an output and a named owner. Rules do the predictable work, AI drafts with citations, and people sign off.

End-to-end example

One thread from regulatory change to verifiable proof.

A worked example: a market tightens loss limits for young adults. Regulation → obligation → gap → task → evidence; an auditor can follow it in either direction.

  1. 1 · Detect

    Radar picks it up

    The regulator's update is captured, summarised and scored High because you hold that licence and offer slots.

    RAD-NL-2026-0917

  2. 2 · Map

    Obligations update

    Two existing obligations change and one is added, each linked to the exact provision and the brands it binds.

    OBL-NL-RG-017

  3. 3 · Assess

    Gaps found

    The RG policy, the limit configuration and an active CRM campaign are flagged, with suggested redlines.

    GAP-0412 · 0413 · 0414

  4. 4 · Fix

    Owned tasks

    Gaps become tasks for Compliance, Product and CRM, synced to Jira, each with acceptance criteria and a due date.

    COMP-171 · 172 · 175

  5. 5 · Prove

    Evidence sealed

    Approved policy, configuration screenshot and the campaign's sealed record are linked to the original update.

    EV-2291 · sealed

Rules first, AI second

Structured data and fixed rules do the predictable work. AI reads, summarises and drafts, and every output cites its source.

People sign off

Nothing changes in your policies or systems without a named approver. Intudly suggests; your team decides.

No citation, no finding

A finding without a traceable source is not shown.

Identifiers are sample data. Most of this thread uses Phase 2 and 3 modules; Phase 1 covers the campaign part.

Launch · MVP · Q1 2027

Campaign Shield · the launch module

Start with the first campaign. A low score never cancels a mandatory restriction.

  1. 01

    Submit

    CRM uploads copy, bonus terms, channel, markets and a pseudonymised audience via CSV/SFTP, API or Slack/Teams.

  2. 02

    Check

    Hard gates run first. Then cited findings and an explainable risk score that sets review priority.

  3. 03

    Fix

    Automatic exclusions apply; missing terms such as an expiry date need a person — nothing commercial is invented.

  4. 04

    Approve

    A separate Compliance checker approves the exact version. Blocked campaigns can't be sent for approval.

  5. 05

    Prove

    A sealed decision record is kept and reconciled against the actual send log.

Try the interactive campaign example

See what your last three campaigns would have flagged.

Free backtest of three recent campaigns, or a 30-minute walkthrough on a sample operator configured for your markets. We reply to agree scope and a secure way to share files.

Get a free 3-campaign backtest Book a 30-minute walkthrough