Start with the workflow boundary
Scope begins with the trigger, trusted inputs, normal path, output, exception handling, systems touched, and proof of completion. Those details turn a broad goal into a buildable project.
Before work starts, the agreement defines included workflows, operating responsibility, controls, change handling, support expectations, and exit requirements. See Pricing for the available engagement shapes.
The six scope drivers
| Driver | What it means | What expands the work |
|---|---|---|
| Integrations | How many systems the workflow reads from and writes to. | Each connection adds authentication, mapping, testing, monitoring, and failure handling. |
| Data quality | Whether the required inputs are complete, consistent, and tied to a source of truth. | Duplicates, conflicting fields, and unclear statuses add cleanup, validation, and exception work. |
| Risk and authority | Which actions may run under policy and which require authorization. | Money movement, credential changes, deletion, sensitive commitments, and difficult-to-reverse actions require stronger controls. |
| Volume | How many leads, invoices, documents, or messages run through per month. | Higher volume means more runtime, more exceptions in absolute terms, and tighter monitoring. |
| Tool sprawl | How many overlapping tools hold competing versions of the truth. | Three places a customer record can live means three places it can disagree. Sprawl multiplies the seams an operator has to watch. |
| Compliance | Rules the system must respect: licensing, contact consent, retention, and industry requirements. | Each requirement adds controls, evidence, testing, documentation, or deployment constraints. |
Read your own office against them
Map these factors before scoping a build:
- Count the systems one workflow would touch, end to end.
- Gut-check the data. Would you trust the CRM status field with money?
- List the actions that involve money, credentials, deletion, sensitive commitments, or difficult-to-reverse changes.
- Estimate monthly volume for the one workflow that hurts most.
- Count the tools that hold a copy of the same customer record.
- Name your rules — anything a regulator or a contract makes you do.
A workflow with few systems, consistent data, stable rules, and reversible actions is simpler to build and operate. Several interacting constraints may point to a cleanup or planning phase before implementation. The audit makes that sequence explicit.
Compare the project with the current process
Document the repeated work, delays, corrections, missed follow-through, and management attention the current process requires. That creates the baseline for evaluating a proposed project.
Use the ROI calculator to enter your own time, labor cost, and workflow volume. The calculation stays in the browser and helps compare the proposed system with the cost of the current process.
Clear scope makes the project plan usable
Ridgeway documents the workflows, systems, exceptions, controls, maintenance responsibility, and change path. The full method is in how to scope AI workflows for sustainable operations.
Ask any provider to state what is included, what counts as maintenance, and how new work or changed risk is handled.
How Ridgeway defines the project shape
- Map. Identify the workflow, systems, exceptions, controls, and desired result.
- Audit. Verify readiness, dependencies, risks, and the sequence of work.
- Proposal. Document scope, responsibilities, support, acceptance, and terms.
- Controlled start. The workflow runs in shadow or review mode, then routine cases move under policy as the evidence supports.
The pricing page lays out the three engagement shapes, and who owns what covers the seam that matters on the day you leave.
Bring evidence to the scoping conversation
A representative inbox thread, form submission, spreadsheet, report, or exception is more useful than a polished feature wish list. Evidence shows which fields exist, where context is lost, how often the normal path bends, and who currently resolves the disagreement.
Use the workflow-audit method to collect those examples consistently. Better evidence narrows uncertainty; it does not guarantee a smaller project, but it makes the proposal explainable, the acceptance test concrete, and the operating responsibility easier to price, review, and hand to the team doing the work.