Pricing and engagement

From working session to proposal.

Step 1. A working session, 45 minutes

You describe one process where errors cost money. We ask about the documents, rules, volume, systems, exceptions, and owner. We confirm whether Manuel fits during the meeting.

Step 2. Paid discovery, ten working days

We run representative files through the control. You receive documented exception categories, a measured baseline, a fixed first scope, acceptance criteria based on your data, and a firm price. The fixed discovery fee is credited against implementation if you proceed within 60 days.

Discovery is paid because it produces the scope, baseline, acceptance criteria, and price used for the implementation decision.

Step 3. Build, on a frozen scope

The scope includes numeric limits, acceptance criteria, owners on both sides, and an engineering-confirmed schedule.

Step 4. Go live, then the next control

Most first deployments run read-only. We compare the control with your existing process before enabling write-back. Later controls reuse connectors, business records, master data mappings, and approval settings from the first.

Choose an implementation model.

Build and maintain.

A one-time implementation priced on man-days, then an annual maintenance and support fee.

Deploy and subscribe.

A fixed implementation from a proven template, then a platform subscription priced per control in production, falling as you add controls.

Pricing is set per control. OCR pages, record counts, and API calls do not determine the fee.

Implementation and subscription are scoped to each control. We set the price after paid discovery because the documents, systems, and checks vary by process.