Recommended starting offer

Know what to automate before committing to an implementation.

Map one repeated workflow, define its baseline and constraints, decide what should be automated or left manual, and leave with a fixed-scope pilot decision.

Request this scopeReview evidence status

Good fit

  • Operations leaders with several possible AI use cases
  • Teams that need feasibility, risk, and scope before a build
  • Agency partners preparing a bounded client implementation
  • Buyers comparing standard automation, AI assistance, and manual control

Problems this can address

  • The team has ideas but no ranked use case or measurable baseline
  • Data, access, provider, and integration constraints are not documented
  • A vendor proposal jumps to tools before defining the operating workflow
  • Leadership needs a clear pilot decision and boundary

Deliverables

What the scope includes

  • Current-state workflow and bottleneck map
  • Baseline definition and input/system inventory
  • Data, integration, privacy, and failure-risk review
  • Use-case scorecard and target architecture
  • Pilot acceptance criteria, timeline, and fixed-price proposal

How this engagement works

Each stage has a decision and a documented output.

  1. 1

    Collect a non-confidential workflow brief

  2. 2

    Review the process, inputs, systems, users, and risks

  3. 3

    Compare assist, automate, and do-not-automate options

  4. 4

    Deliver the decision pack and walk through the recommended next step

Qualification

  • A named owner can explain the current workflow
  • Representative examples and approximate volume exist
  • A reviewer is available for one or two working sessions
  • There is a plausible budget and owner for a successful pilot

Evidence required to publish results

  • A sanitized sample assessment artifact
  • A versioned scoring and risk template
  • A documented decision and pilot scope
  • Permission before any assessment result becomes public proof

Common questions

Can the assessment conclude that we should not use AI?

Yes. A useful result may be standard automation, process cleanup, better source data, a smaller assistive tool, or no build. The assessment is a decision product, not a pretext for implementation.

Is the assessment fee credited toward a build?

Not automatically. Any commercial credit must be written into the proposal so scope and incentives remain clear.

Related guidance

Workflow readiness worksheetAI agents vs workflow automation

Bring one workflow

Do not send confidential files. Start with the process, approximate volume, current systems, review owner, and desired output.

Request this scope