AI can draft a feature in minutes, but making it right for a regulated business still takes weeks of checking and rework.

Spexd keeps everything your business has agreed in one place, from how you read the regulation to the risks you've chosen to take, so your teams and your agents all start on the same page.

Built for product and engineering teams in gambling, payments, banking, insurance and anywhere else understanding your requirements really matters.

Maya from Product: Too many in-play bets fail when the price moves. Can we accept them at the new price automatically?

Ask Spex: Not for everyone. REQ-112 needs the player's confirmation when a price changes, unless they've opted in to auto-accept. Legal and Product agreed in v2 to offer that for higher prices only, in 6 of your 11 jurisdictions.

Maya from Product: Where is the auto-accept opt-in shown to the user?

Ask Spex: In the betting controls in their account settings, for players in eligible locations (DES-49).

Maya from Product: Can we surface it on the bet slip instead to encourage uptake?

Thinking…

AI sped up the building, but not the checking

  • A few experts review everything.

    Whatever AI produces, someone who knows your regulatory position has to look over it, and you've only got a couple of people like that.

  • Decisions surface too late.

    Work looks done right up until it runs into a requirement that only a few people knew applied to it.

  • AI doesn't support teams.

    Everyone's prompting their own tools with their own context, making it faster to reinvent than align.

AI knows the regulation, but not where you stand on it

Ask AI about a regulation and it'll tell you your product must do something, because it can't see that your business already meets it with a back-office programme. It doesn't know how you've chosen to meet the regulation, so it fills the gap with the safest, most average answer it can find.

The regulation, as AI reads it

“Situations shall be identified where the player has placed a wager for which the associated odds/payouts or prices have changed, and unless the player has opted in to auto-accept changes as permitted by the regulatory body, provide a notification to confirm the wager given the new values.”

Event wagering regulations
Your position, as Spexd keeps it

Offer auto-accept for higher prices only, as an opt-in, in the 6 of 11 jurisdictions that allow it. Everywhere else, the player confirms.

Agreed by Compliance, Legal and Product at v2

What is Spexd?

Spexd is a product definition platform for teams in regulated markets. It keeps your requirements, how you intend to meet the regulation and the decisions behind your product in one place, each with the name of whoever approved it, so your people and your AI agents work from the same context whether they're proposing, building or reviewing a change.

Who it's for: product, engineering, compliance and legal teams who want AI working from what the business actually signed off, not a best guess.

For one feature, that looks like this:

  • RegulationEvent wagering regulations“…unless the player has opted in to auto-accept changes as permitted by the regulatory body, provide a notification to confirm the wager given the new values.”Linked to REQ-112
  • RequirementREQ-112 v2Price changes need the player's confirmationApproved by Compliance
  • DecisionRisk we acceptedAuto-accept for higher prices, as an opt-in, in 6 of 11 jurisdictionsAgreed by Legal and Product at v2
  • DesignDES-49The auto-accept opt-in lives in the betting controls in account settingsBuilds on REQ-112 v2

See what changes when your agent knows your constraints

Pick a request and watch the same coding agent take it twice: once reading only your code, and once reading your code and what your business agreed in Spexd.

Maya from Product asks Claude Code: Can we put the auto-accept opt-in on the bet slip instead of burying it in settings? I want uptake up before the Champions League. Without Spexd, it reads the code and replies: Done. The bet slip now has an "Accept price changes" toggle that writes the same acceptPriceChanges setting as BettingControls, so the two stay in sync. To get uptake moving I've set it to "any change" by default on in-play slips, so fewer bets are rejected when prices move. Want an event on it so you can track uptake? What happened next: The toggle now shows in all 11 jurisdictions, starts switched on and accepts lower prices too. Only 6 jurisdictions permit auto-accept, and the regulation says the player has to opt in. With Spexd, it reads the same code and what the business agreed in Spexd, and replies: Yes, with two guardrails from REQ-112. Auto-accept is cleared for higher prices only, in 6 of your 11 jurisdictions, and the regulation needs the player to opt in themselves, so it can't start switched on. The best moment to ask is when it bites: a bet rejected because the price moved up. A one-tap "Accept higher prices from now on" on that rejection, for eligible players only, would write the setting DES-49 already uses. I've raised that in Spexd as a proposal adding the bet slip to DES-49, for Product and Legal to agree before I build it. What happened next: Product and Legal agreed the proposal that week, the agent built what was agreed, and it shipped first time.

Every decision comes with who made it and why

Each requirement holds the regulation, how you intend to meet it and the criteria every change is checked against, along with everyone who signed it off, so when someone asks for the audit trail, it's already there.

  • WhyWhat's fixed The regulation in its own words, and the date it kicks in.
  • Risk we acceptedHow you'll meet it How your business intends to meet the regulation, and any condition that comes with it.
  • Acceptance criteriaWhat gets checked The criteria every change has to meet before it ships.
  • ApprovedWho agreed it Compliance, Legal and Product each sign it off, and if a change alters what it means, their sign-off no longer counts until they've looked again.

Passing tests don't make a change compliant

Spexd reads every pull request against the requirements behind it, tells you what's missing and suggests the fix, whether a person or an agent wrote it.

↑ Every test passes, but the change misses two things Legal and Product agreed. Once it's fixed, the check clears.

Let your experts get back to their own work

Early access starts with a chat with the founders and a hand getting set up, and your team can be up and running in an afternoon.