PRICING

Three arrangements. One product.

The same AI employees, the same approvals, the same audit trail, whichever way you run it. Managed SaaS for small teams. Two custom arrangements for enterprises. Prices live in the agreement, not on this page. One call gets you a real number.

Pick the arrangement. We price the work.

You pay for employees and the work they complete, never for seats. Work only counts when a named person on your team approves it.

Monthly, per employee

Managed SaaS

For small teams that want to start now.

One shared multi-tenant deployment, run by us. Sign up and go. Each AI employee carries a monthly fee with a usage limit included; work beyond the limit bills per approved unit. Your data is never mixed with another customer's, never trained on, and exportable.

Custom grade · in the contract

On your infrastructure

For enterprises whose data cannot leave.

Single-tenant, on your own cloud or data center: your database, your storage, your domain. Documents never leave your perimeter. Winsen operates the runtime. Delivered through the engagement below.

Custom grade · in the contract

Dedicated isolated unit

For enterprises that want isolation without operating anything.

A single-tenant deployment we host exclusively for you: your own domain, your own database and storage, in your region. You get the isolation. We do the operating. Delivered through the engagement below.

The custom arrangements are single-tenant: your own database, your own storage, your own domain. On managed SaaS, your data is still never mixed with another customer's.

How a custom engagement runs.

For the two custom arrangements. It mirrors the Winsen Labs engagement model: 3 to 4 months, a forward-deployed team working alongside your people, and a small number of engagements at a time. Managed SaaS skips all of this. Sign up and go.

Understand · week 1

A working session with your team. Nothing to sell in it. We map the queue, the approval rules, and the work your team has already checked.

Deploy narrow · weeks 2-4

One team, one workflow, on your stack, inside your approval rules. The first runs are a paid pilot on historical work your team already knows the truth about, so the result is measured against ground truth.

Measure · weeks 4-12

Approved-work volume, time returned, error rates. On shared dashboards both sides read. What your process caught, what it missed, cost and turnaround per item.

Expand · when proven

Only when the measurements make the case. More teams, more workflows, same approval rules. Never before the numbers.

FAQ

What procurement will ask.

No dodging, no contact-sales-to-find-out.

Which arrangement should we pick?+

Managed SaaS if you are a small team and want to start now. Your infrastructure if your mandate says data cannot leave the building. A dedicated isolated unit if you want single-tenant isolation without operating anything. The product is identical in all three.

Why is there no price list?+

Because the honest number depends on the deployment: which employees, what volumes, where it runs. You will have a concrete figure after one conversation, and it will not change shape later.

Who pays for the AI model usage?+

It is part of the deployment. Model access is provisioned and governed by us, so there is no separate token bill to manage, and your data is never used to train models.

What counts as billable work?+

A completed unit of work that a named person on your team approved: a reviewed file, a closed exception, an audited invoice. Rejected work costs nothing.

Is there a pilot?+

Yes, inside the custom engagement. Deploy narrow is the pilot: one team, one workflow, first runs on historical work your team has already checked. It is paid, modestly, and it credits against the first year. Paid pilots get staffed, scoped and finished. Free ones drift.