Test one AI-assisted business workflow.
Connect a selected source of information to one useful result. EAC builds the pilot in an agreed test environment and documents how it behaves before you consider a wider rollout.
EAC will confirm the scope, price, payment terms and availability directly.
Who it is for
A team with a repeatable task, a process owner and suitable examples to test.
- 01One approved source collection supports one tested business workflow that a named owner can maintain.
What is included
A workflow map, working test-environment pilot, editable source or export, operating instructions and a record of the agreed checks.
- 01Current-state and proposed workflow map
- 02Working pilot in an agreed test environment
- 03Editable code or workflow export, configuration guide and operating instructions
- 04Test report with assumptions and known limitations
- 0520 representative-input checks plus four control/failure cases
- 06One 30-minute scope session and one 30-minute handoff
- 07Input validation, limited retries, failure reporting and duplicate-action protection where applicable
Scope and limits
One trigger, up to five processing or action steps, one conditional branch and one structured output. The pilot can use up to two existing business systems and one AI provider, with one human-review checkpoint.
- One trigger, up to five processing/action steps and one conditional branch
- Up to two existing business systems plus one AI provider using supported connectors or documented APIs
- One structured output and one human-review checkpoint
What to prepare
Share the process, trigger, inputs, expected output and owner. Provide supported connection details, a test environment and 20 approved examples with expected results.
- Selected process, trigger, inputs, output and process owner
- API/connector documentation and an available test environment
- Twenty redacted or non-sensitive examples with expected outcomes
- Human-review rule and exception owner
- Client-owned approved accounts, software budget and project-scoped access
How we review the work
We check routing, required fields, representative outputs and the agreed failure cases. The existing acceptance criteria specify the output rubric and the four control or failure cases.
- 01Agreed input reaches reviewed output in the test environment
- 02Deterministic routing, validation and required fields pass
- 03Agreed representative-output rubric and control/failure cases are recorded
- 04Client can run the pilot from delivered instructions
- 05At least 18 of 20 representative outputs meet the agreed content rubric; all four specified control/failure cases behave as agreed
Outside the scope
Production rollout, autonomous external communications, payments, major data migration and a complete business platform require a separate scope.
- Complete business platform or new dashboard/authentication
- Undocumented APIs, scraping, data migration or custom model training
- Payments, autonomous external communications, consequential decisions or production rollout
Follow one input through a reviewable workflow.
Try three synthetic inputs. This local example uses fixed rules to illustrate validation, boundaries and human review.
- Request
- Please send details about a workflow pilot.
- Contact
- example@example.com
Waiting for a sample
Choose an input and run it to see the decision and the reason behind it.
Illustrative demo • Synthetic data • No AI call, saved inquiry or live integration. Project behavior is tested against an agreed scope.
Delivery steps
Define the task
Select one workflow and agree the review rules
Build the pilot
Build the pilot with supported connections
Run the agreed checks
Test representative inputs and failure paths
Hand over the source and instructions
Hand over source, test evidence and run instructions
Terms and support
EAC confirms scope, price and payment terms in writing after inquiry. Billing is handled directly through EAC.
EAC confirms availability, timing and required inputs in writing before work begins.
One consolidated in-scope revision and one clarification round requested within seven calendar days. Ongoing support and production rollout are separate.
Client-owned accounts, hosting, subscriptions and software usage are separately funded.
Questions
How do I get started?
Send the project goal, current tools and the relevant details through the inquiry form. We’ll assess fit and confirm scope, price and availability before work begins. An inquiry does not purchase a service or reserve a session.
How are costs and payment handled?
EAC confirms the project price and payment terms in writing. Software subscriptions, hosting and usage charges are separate unless expressly included in the proposal.
Does this include a production rollout?
This engagement delivers a pilot in the agreed test environment. Production activation, wider rollout and continuing monitoring need a separate written scope.
Share the task, current tools and the result you want. We’ll review the request and discuss the scope.
A clear scope and practical review
EAC confirms the task, required access and review criteria before work begins. Public demonstrations use EAC-owned or synthetic examples. Each engagement sets out its deliverables, limits and handoff.
