§ Pricing

Priced like a credit platform, not a SaaS dashboard.

CORE pricing should match how a program-credit shop operates: modules in use, active deal volume, implementation scope, and the amount of controlled AI work running through the platform.

Pricing shape

One platform, scoped around the work.

Most buyers should expect an annual platform license, implementation/configuration, and optional expansion by module or volume. We do not lead with per-seat gimmicks.

Final numbers handled in sales process

§ What Matters

What the buyer needs to believe.

01

Platform license

Access to the CORE workspace, configured modules, audit trail, and user roles.

02

Implementation

Program configuration, workflow mapping, data/file setup, training, and launch support.

03

Usage and expansion

Additional modules, volume, automation, or intelligence workflows can expand after the first launch.

§ Fit

What affects pricing

This page should reduce demo friction without publishing numbers too early.

01

Program and module scope

02

Number of active deal files

03

Document, extraction, and AI generation volume

04

Implementation complexity

05

Security, integration, and support requirements

§ Path

Buying path

01

Workflow review

We look at the real work before quoting the platform.

02

Scope proposal

You get a launch scope, modules, timeline, and commercial shape.

03

Pilot or launch

Start narrow enough to prove value and broad enough to matter.

§ Next Step

Ask for pricing when the workflow is visible.

A ten-minute form cannot price a program-credit operation. A real file can.