The platform, module by module

One map of your obligations.
Six instruments on top.

Everything below is pictured on the Northwind Pay demo account — a fictional payments company operating across France, the UK, the EU and Singapore. Ask for the demo and we'll drive.

MODULE 01

Review

The applicability inbox

Everything the engine believes applies to your products arrives in one queue, ranked by business impact and confidence. Each suggestion carries its reasoning and its source, so the decision in front of you is 'confirm or dismiss' — not 'go research this'.

Confirmations materialise downstream automatically: obligations join your compliance map, deadlines join the roadmap. Dismissals teach the engine about your edges.

  • Ranked by business impact
  • Reasoning and citation attached
  • Every decision audited
THE APPLICABILITY INBOX, FILTERED LIVELIVE CAPTURE

MODULE 02

Horizon Scan

Tomorrow's obligations, today

A forward-looking feed of what's changing across your regulators — new regulations, amendments, consultations, guidance and enforcement — filtered to your actual footprint, with effective dates.

Nothing sneaks onto your roadmap: an item earns its slot when you acknowledge it. The feed is the early-warning system; the roadmap stays the plan.

  • Monitored across your regulators, not a generic feed
  • Consultations tracked before they bind
  • Acknowledge → graduates to roadmap
Pericls Horizon Scan feed items — new regulation, consultation, enforcement and amendment entries with effective dates and roadmap status
SIX HORIZON ITEMS, MATCHED TO THE FOOTPRINT

MODULE 03

Gap Analysis

Expansion, priced in obligations

Considering a new market, product or service? Compose the scenario and run it. Pericls compares the candidate against your current obligations and returns the factual delta — new obligations, covered ones, and likely-covered equivalents.

Counts and facts, never an 'easiest market' score. Click any cell for the per-obligation breakdown, save the scenario, or make it official and let the map extend itself.

  • New market · service scenarios
  • Delta vs. what you already satisfy
  • One click from scenario to plan
A GAP ANALYSIS, COMPOSED AND RUN — UNCUTLIVE CAPTURE

MODULE 04

Licenses

Authorisations with a lifecycle

Licenses aren't just another obligation — they gate your roadmap. Pericls flags the authorisations your activity likely requires (EMI, PI, CASP, VASP…), explains the trigger, and tracks each application's checklist and evidence.

A granted license doesn't just sit in a drawer: it satisfies the obligations it covers, and your posture updates accordingly.

  • AI-flagged with reasoning
  • Application checklists per regulator
  • Granted → posture updates automatically
Pericls license card — MiCA CASP authorisation flagged with AI reasoning and confirm/dismiss actions
AN AI-FLAGGED LICENSE, REASONING INCLUDED

MODULE 05

Vendors

Delegated is not done

Every regulated firm runs on third parties, and every outsourcing regime asks what you have handed over. Pericls analyses your vendors the way it analyses you: what they sell, what they are authorised to do, and who they depend on in turn.

That last part is the fourth party nobody can see. And because we know a vendor's products individually, you record the ones you actually use — a firm using one product of a vendor does not inherit the obligations of the products it never touched.

  • Their licences, with register references
  • Scoped to the products you actually use
  • Delegated posture, oversight still owed
Pericls vendor detail - the authorisations ClearBank itself holds, each with its register reference and the group entity that holds it, above the sub-vendors it depends on
APP.PERICLS.COM · NORTHWIND PAY

MODULE 06

Evidence

A position you can defend

Knowing an obligation applies is half the job. Against every one you attach the proof — the policy, the procedure, the screenshot, the signed attestation — with a reviewer and a review date. Posture is then computed from what is actually documented: nothing, partial, or met.

That is the difference between a dashboard and a defence. When a regulator, an auditor or a prospective partner asks how you meet an obligation, the answer is already assembled, cited to the regulation that created it, with the full history of who decided what and when.

  • Proof attached per obligation
  • Posture computed, never asserted
  • Reviewer and review date on every item
APP.PERICLS.COM · NORTHWIND PAY
Pericls Compliance Evidence - an obligation with its verified policies attached, a named reviewer and review date, above the vendors that could take the control on

MODULE 07

Overview & Roadmap

The operating rhythm

The overview is the morning check-in: what needs a decision, what's due, what changed overnight, what's assigned to you. The regulatory roadmap behind it is the time-based plan — every item with an owner, a deadline and the regulation that created it.

Filter it by market, by product, by owner or by date range, and the plan reshapes around the question you're actually asking.

  • Deadlines with owners
  • Filter by market, product or owner
  • Jurisdiction & regulator drill-downs
APP.PERICLS.COM · NORTHWIND PAY (DEMO)
Pericls Overview — footprint health, decisions needed, upcoming deadlines
PLUS: JURISDICTIONS & REGULATORS · PRODUCTS & SERVICES · TEAM · AUDIT TRAIL
The demonstration

See your own obligations,
not a canned tour.

Tell us what you build and where. We'll walk you through the platform against a footprint like yours — which regulations bind it, what's on the horizon, and what your roadmap would look like on day one.

30 minutes, straight to substance

Handled by the founding team, not an SDR queue

No data required beyond what's public

REPLIES WITHIN ONE BUSINESS DAY
Full name *
Work email *
Company
Company URL
Your role
Company size
What are you wrestling with? (optional)

No newsletter, no drip sequence. We use this to prepare your demo and nothing else.