Customer story

ScreenlyyID ships its roadmap with VocxAI

A risk decisioning platform where every request touches fraud, identity and compliance logic. Customer feedback now moves from support ticket to reviewed pull request without leaving the team's existing GitHub workflow.

Join private beta Read the next story

At a glance

Company ScreenlyyID — identity verification, fraud and AML risk decisioning

Where Global, API-first platform

Used for Shipping the product roadmap from customer and support signals

Features Talk to your Data, AI-generated PRDs, GitHub PR automation

Stack GitHub · .NET Core · Angular · XUnit

Roadmap items shipped through the pipeline

1 day

Time from request to open pull request

93%

Share of PRs merged without rework

Engineering hours returned per month

The challenge

A roadmap gated by review capacity

Signals arrive from every direction

Feature requests come through support, sales calls, integration partners and developer questions about the API. The pattern behind them was never in one place.

A small team against a wide surface

The platform spans document checks, biometrics, eIDV, AML screening, device and payment signals. Every request competes with the next layer of the roadmap.

Compliance work can't be rushed

Changes near verification and audit paths need a written rationale and a review, not a fast merge.

What shipped

Roadmap items delivered through the pipeline

OriginChangeWhat it didOutcome

Slack + CRM Single Risk API entrypoint Unified multiple risk products into a single, unified endpoint. Delivered in 1 day

Email + CRM Risk rule evaluation Evaluate endpoint returns risk score and escalation recommendation for the unified endpoint. Delivered in 1 day

Slack Dashboard view for API rule results Viewable results of API rule evaluations in the dashboard. Delivered in 1 day

CRM Weighted scoring Weighted scoring rules for more deterministic outcomes. Delivered in 2 days

Competitor Analysis Decision Workflows Configurable workflows based on decision results. Delivered in 2 days

How it runs

Their loop, week to week

Step 01

Signals cluster

Support tickets, calls and developer questions group into themes automatically.

Automatic

Step 02

The team picks

Themes are scored by revenue at stake; a person approves what becomes a spec.

Their decision

Step 03

Agent builds and tests

A PRD is generated, then an agent writes the change and runs the suite in a sandbox.

Cost tracked live

Step 04

Engineer reviews the PR

The change opens as a normal pull request with the originating tickets cited.

Their decision

A completed build run with linked evidence, revenue impact and a comment thread, plus a View PR link

Only the repos you choose

Scoped to the repos ScreenlyyID selects, with write limited to branches and pull requests.

Every PR cites its source

The tickets or calls behind a change are linked in the description for reviewers.

Cost tracked in real time

Every job's spend is visible as it runs — no black box.

Nothing self-merges

A ScreenlyyID engineer approves every pull request.

With a small engineering team, our backlog used to be a queue that would shift based on the most recent customer call. Small fixes would wait weeks behind big features. Now it moves on evidence and clarity on what's holding us back. By documenting everything, and generating architectural decisions that can be reviewed by a senior engineer before implementing, the amount of work we can run in parallel is incredible.

Brett Wise, CEO ScreenlyyID