Build your own platform

Start with a working CRA foundation. Make it unmistakably yours.

Building differentiated screening technology should not mean teaching a generalist how orders, searches, providers, holds, reports and client commitments fit together. deverus brings the screening operating view to a configurable foundation, then builds around how your company works.

Book a platform fit session See the foundation in action

Configure the common work. Integrate the ecosystem. Build what makes your CRA different.

A foundationNot a blank sheet, not a box

The fastest path to your own platform is not starting from zero.

A blank-sheet build spends its time rediscovering what every CRA does. A fixed platform makes you fit someone else's model. We start between the two: a working foundation for the common operation, built to be configured and extended around you.

Start with the CRA foundation

Working patterns for orders, search fulfillment, review queues, researchers, clients, pricing, invoices, documents, permissions and activity history.

Configure the operation

Shape search setup, provider assignments, client rules, helper instructions, compliance materials, pricing, branding, roles and controls around your business.

Build your advantage

Create the workflows, client experiences, integrations, data products and service model that set your CRA apart.

You do not pay to rediscover the industry's table stakes. You put the investment into the operation and experience that should belong to you.

What the foundation covers

One operating system for the work behind a screening business.

Operate screening work

One place for orders, searches, documents, prices, status and activity, including adverse-action controls.

Direct workflow

Queues and exceptions become clear, governed next actions, with helper instructions and client-level overrides.

Govern compliance processes

Approved templates, assignments, disclosures and consent documents sit inside the operation, with order-level history.

Run the commercial side

Client administration, pricing, invoices, agreements, onboarding and communication settings.

Configure the fulfillment network

Model how searches move through internal teams, integrated providers and researchers.

See the operation

Volume, status, turnaround, clients and bottlenecks in one view.

See the operating modelThree short walkthroughs

Three processes. Plainly demonstrated.

Synthetic demonstration data shown in an authenticated platform environment. Available scope is confirmed during platform blueprinting.

Compliance · 0:18

From policy to proof

Approved materials, assignments, review and evidence stay connected to the work.

What to notice

The responsibility: Apply an approved compliance process consistently without turning the system into an autonomous legal decision-maker.
Where people decide: The system prepares and enforces the workflow. Your authorized team keeps policy judgment and approval.
What can be yours: Your rules, review points and evidence record.

Workflow manager · 0:24

Resolve the queue, preserve the decision

One exception, from configured guidance through review, action and a recorded result.

What to notice

The responsibility: An order is held. The team needs context and an approved next action instead of tribal knowledge.
Where people decide: Automation assembles context and directs the process. The authorized operator owns the decision when review is required.
What can be yours: Client overrides, helper instructions, permitted actions and what counts as resolved.

Insights · 0:18

See the bottleneck, open the work

From an operating metric to the orders and searches that need attention.

What to notice

The responsibility: A leader sees a turnaround or status signal and needs to get from the number to the underlying work.
Where people decide: The platform shows patterns and records. Leaders decide the response.
What can be yours: The metrics, segments, reports and decisions your leaders need.

From fit to operation

A staged build, decisions in the right order.

01Fit

Confirm the business case, goals, constraints and whether this is the right deverus path.

02Blueprint

Map the current operation, target experience, boundaries, data, integrations, compliance responsibilities and success measures.

03Configure

Set up the shared foundation: searches, resources, clients, roles, instructions, materials, pricing, branding and rules.

04Build

Develop the workflows, integrations, interfaces and client experiences in the blueprint, to agreed acceptance criteria.

05Prove and migrate

Test security, workflow, data, integration and acceptance. Rehearse cutover with rollback criteria.

06Operate and improve

Monitor, measure, manage change and keep automating where the evidence supports it.

Define control before the build

"Your platform" should be written rights, not a slogan.

What is right depends on scope, architecture and the commercial structure. Before implementation, we agree in writing how each of these is handled, so nothing is ambiguous at launch or later.

Application and custom source access
Ownership or licensing of existing and new components
Data ownership, access, portability, retention and deletion
Hosting account, infrastructure control, monitoring and incident responsibilities
Third-party services, licenses, credentials and pass-through costs
Security, privacy, compliance and audit responsibilities
Documentation, releases, maintenance and support
Transition help, export formats and termination rights

Questions worth answering early

A clear view before a serious platform decision.

Is this a platform we buy or a custom software project?

Both, in a sense: a configurable CRA platform foundation plus a scoped product and implementation program. The common capabilities are the starting point. Differentiated workflows, integrations and experiences are defined in the blueprint and built to agreed acceptance criteria.

What already exists in the foundation?

The demonstrated environment covers orders and searches, queues and holds, search setup, researchers and assignments, compliance materials, clients, pricing and invoices, agreements, users, branding, activity and operational insights. Exact production scope is confirmed during fit and blueprinting.

What can be unique to our company?

Client and user experiences, workflows, integrations, data products, reports, service rules and decision support. Scope, dependencies and acceptance criteria are documented before the build.

Who owns the platform and data?

It depends on the commercial and technical structure you approve. Data rights, source access, component ownership or licensing, hosting control, third-party dependencies, support and transition terms are written down before implementation.

How do you manage migration risk?

Migration is a workstream, not a final import. The blueprint covers data, integrations, parallel operation, validation, security, training, cutover and rollback. Launch happens only when agreed readiness criteria are met.

Does AI make compliance decisions?

The platform can organize information, apply configured rules, route work and prepare actions. Policy-sensitive or judgment-based decisions keep defined human review and accountability. Controls are set for each workflow.

Can this work with our current providers and systems?

We assess integration needs during blueprinting. Providers, client systems, data exchanges, credentials, service limits and fallback behavior are validated before any integration is called available.

How long will it take?

That depends on scope, integrations, migration, security needs and how much differentiated development you want. We give a phased estimate after the fit and blueprint work has established those facts.

The next step

Bring us the process your current platform cannot become.

In a platform fit session we look at the operating model, constraint or market advantage driving the change, and decide whether the answer is configuration, automation, a differentiated build, or another deverus path.

Book a platform fit session Watch the platform demos

Not sure which path? Verocity 2.0 and Workflow AS may fit better.