The assessment
One to three weeks to a scoped pod
Every pod starts with an assessment, and the assessment is the only thing we ask you to buy cold. One to three weeks, with the scope and fee agreed before we start. No subscription, no commitment past it.
First we sit in the workflow. We read the queue, pull the export, interview the people who actually do the work, and find where the hours and the errors live. Then we baseline the number, spec the pod, and show a working slice of the agents running on your data, not a slide about them. A single, clean queue takes about a week. A workflow spread across several systems and teams takes closer to three.
You leave with three things in writing: the map of the workflow as it actually runs, the baseline number a pod would be accountable for, and a fixed monthly price. If we don't believe a pod will move your number, we say so, and you keep the map.
Pricing depends on the workflow, the volume, and where you're starting from. That's why we don't publish a rate card: the assessment is where the price gets set, in writing, before you commit to anything.
Pricing
What you get, and how it's priced
| What you get | How it's priced | |
|---|---|---|
| The assessment | 1 to 3 weeks. Workflow map, baseline number, working slice on your data, scoped pod and price. | fixed fee, agreed up front |
| The pod | Agents built and run by SectorFlow on your private instance, named lead, tuning and drift handling, monthly metric report. Billed monthly. | monthly, set at the assessment |
| Growing it | Deeper automation on the same workflow, or a new pod on the next workflow. Priced in the original agreement; an upgrade is a signature, not a sales cycle. | priced at assessment |
Assessment FAQ
Questions we get before the call
What do you need from us?
Read access to the systems in the workflow and a few hours with the people who run it. No integration work in the assessment.
Who runs the pod afterward?
We do. Building, hosting, tuning, drift, updates. Your team handles exceptions we route to them and keeps final authority on business decisions. You never hire for it.
Who picks the number?
You do, and the assessment validates it. If the metric can't be measured cleanly, or a pod can't materially move it, we say so during the assessment and propose the number it can move. We don't run a pod against a number we can't influence.
What does it run on?
Your private instance of SectorFlow One. Private, auditable, every agent action logged with a reasoning trace and a reversal path. Nothing trains on your data.
What if we leave?
After the initial term, 30 days' notice. You take your data, the audit logs, and any documents the pod generated for you. If the number stalls for months despite remediation, the contract gives you an early exit.
Why is the assessment paid?
Because it's work, and because you keep the output either way. Paid also keeps us honest: we'd rather lose an assessment than run a pod that won't move a number.