AI EngineeringAgents & Agentic Workflows
Vertical Agent Launch
One of BigStep's pre-built vertical agents running in the client's production environment, connected to their systems, configured to their rules, with human approval on anything it cannot undo, an evaluation baseline on their own cases, monitoring, and a trained team operating it.
Vertical Agent Launch
$35K–$60K
- Duration: 4–6 weeks
- Tier: Launch
- Format: Fixed scope
You leave withA BigStep vertical accelerator deployed, integrated and customised in production
Book a Free SessionSound familiar?
We've seen the demos and we know an agent could handle this. But we don't want to spend six months building from scratch, and we don't want a black box we can't change. We want something that's already worked for companies like ours, plugged into our systems, live this quarter.
What you leave with
Deployed agent
Format: Client's production environment
How we know it’s acceptableMeets the agreed thresholds on the evaluation baseline
Configuration spec
Format: Document
How we know it’s acceptableSigned by the process owner
Integrations
Format: Code and config in client repo
How we know it’s acceptableTested end to end in staging; smoke tests pass in production
Evaluation set and baseline
Format: In client repo
How we know it’s acceptableClient's team can re-run it without us
Monitoring dashboard
Format: Client's tooling
How we know it’s acceptableShows completion rate, escalation rate and cost per task
Runbook
Format: In client repo
How we know it’s acceptableClient's engineer handles an incident drill unaided
Managed services transition plan
Format: Document
How we know it’s acceptableAgreed with the client and the Managed Services — Essential / Managed Services — Growth owner
Also included
- Human approval on any action that cannot be undone
How it runs
4–6 weeks
Week 1
Fit-gap against the client's process and configuration spec.
OutSigned spec, and a go or re-route decision.
Weeks 2 and 3
Sign off and integrate and configure in staging.
OutAgent running in staging on the client's data.
Week 4
Evaluate on historical cases, tune approvals, security review.
OutEvaluation baseline and security sign-off.
Week 5
Production rollout, shadow mode first, then live for part of the volume.
OutAgent live with monitoring.
Week 6
Hypercare and handover.
OutRunbook, training, managed services transition plan.
For a four-week engagement, weeks 2 and 3 merge and hypercare shortens.
Is this right for you?
This is for you if
- Buyerthe person who owns the business process the agent takes over, such as the head of customer service, operations or the relevant back-office function.
- Also has to say yesthe owner of each system the agent connects to; whoever signs off security, because the agent writes to real systems; compliance or legal in regulated sectors; Finance above the buyer's limit.
This is the wrong answer if
- Their process is not our accelerator's process. If more than roughly a third of the workflow needs custom logic, this becomes a custom build. Sell the Agent Scale Launch or the Agent Prototype Sprint instead.
- There is no way in. If the core systems have no API and no sandbox, integration is the project and the price band will not hold.
- They want to own the agent outright. If the client needs full source ownership to build on it themselves, a custom build fits better.
- Nobody will own it after launch. If no one on the client side can take the exception queue, the agent will be switched off within months.
What’s included, and what isn’t
In scope
- one accelerator
- one process
- up to two integrations
- configuration
- human approval on irreversible actions
- one production environment
- team training
Out of scope
- new agents or workflows not in the accelerator
- changes to the client's systems
- data cleanup
- more than one language or region
- support after handover, which is Managed Services (Essential or Growth) and priced separately
Before we start
Before day one
- The accelerator for this vertical is production-ready (internal gate).
- Sandbox access to every system in scope.
- A named process owner.
- Historical cases with known outcomes.
- A security review slot already booked for week 4.
What we’ll need from your team
- The process owner: three hours a week.
- An IT or integration engineer: four hours a week in weeks 2 and 3.
- A security reviewer: about four hours in week 4.
- The people who will work alongside the agent: two hours of training in week 6.
- A decision-maker available within 24 hours.
Pricing
What we need to give you a quote
- A walkthrough or map of the process.
- The list of systems with API documentation.
- Monthly volume.
- Hosting constraints.
- 50 or more historical cases with known outcomes, to check fit and build the evaluation set.
After we hand over
Who owns it after we leave
The process owner owns the agent's outcomes and the exception queue. A named engineer owns the runbook. We size the exception queue from the escalation rate measured in week 5 and state what reviewing it takes from someone's week.
What we measure
- Task completion rate
- Escalation rate
- Handling time
- Cost per completed task
Agreed in week 1 and reported at handover. The client measures the before figures in week 1.
What comes next
- A second accelerator for another process.
- For a client with several workflows, the Agent Scale Launch.
Questions buyers ask us
Sometimes that's true, and it's a fair concern. Week 1 is a fit-gap against your real process. If the gap is too big, we tell you, and we recommend a custom build rather than bending the accelerator.
The honest answer depends on licensing terms that aren't decided yet.
Anything it can't undo needs a person's approval. We measure it on your historical cases before launch, and the monitoring shows the escalation rate from day one.
Inside their own product, yes. This works across your systems, on your rules.
The accelerator is the pilot that's already been run. This programme is about getting it into production on your data.