Every sprint includes a fixed set of deliverables regardless of tier. The scope of what's automated varies by tier, but the delivery process and inclusions are the same.
Included in every sprint
Discovery and design (Week 1) A series of workshops with your team to map the workflow in detail, understand edge cases, and sign off on the assistant's behaviour before we build anything.
Build and integration Full development of the AI assistant, including all system integrations required within the sprint scope. We connect to your email, policy admin system, CRM, or portal as needed.
Testing on your real data We test the assistant against your actual documents and submissions — not synthetic data. You review and approve before go-live.
Deployment We deploy to your live environment and monitor the first days of operation.
Team training A training session with your team covering how to use the dashboard, review flagged items, and adjust confidence thresholds.
30 days post-launch support If anything behaves unexpectedly after go-live, we fix it. Included at no additional cost.
What varies by tier
- Proof of Concept — one specific sub-process, 2-week delivery
- Process Transformation — one complete workflow end-to-end, 30-day delivery
- Multi-Process Rollout — 2–3 processes in parallel, 45-day delivery
See the pricing page for full tier details and costs.
What is not included
- Ongoing platform hosting (this is covered by your monthly platform subscription after the sprint)
- Changes to the assistant scope after sign-off — any scope changes are treated as a new sprint
- Custom infrastructure or dedicated cloud environments (available on request at additional cost)
Sprint timelines depend on the tier you choose.
Sprint timelines
| Tier | Timeline |
|---|---|
| Proof of Concept | 2 weeks |
| Process Transformation | 30 days |
| Multi-Process Rollout | 45 days |
What affects delivery time
Most sprints run to schedule. The things that can slow a sprint down are:
- Integration access delays — if it takes time to get API credentials or system access from your IT team, this can add days. We flag what we need at the start of Week 1.
- Document sample availability — we need real document samples to train and test the assistant. Having these ready at the start of Week 2 keeps things on track.
- Stakeholder availability — the Week 1 discovery workshops require 3–4 hours of your team's time. If key people are unavailable, we may need to delay the build phase.
What we do if something slips
If an integration takes longer than expected or a discovery finding changes the scope, we will tell you immediately with a revised plan. We do not silently extend the timeline.
After the sprint
The 30-day post-launch support period begins from go-live, not from the end of the sprint timeline. If deployment runs to the end of Day 30, your support period still runs for 30 days from that date.
Most customers start with the Process Transformation tier (Tier 2). It delivers a complete end-to-end workflow in 30 days at a scope that is meaningful enough to demonstrate clear ROI.
When to choose Proof of Concept (Tier 1)
Choose the Proof of Concept if:
- You are not yet sure whether AI will work in your specific environment
- You need internal buy-in before committing to a larger deployment
- You have a very specific, narrow sub-process that would be an ideal first test
- Your budget for the initial engagement is limited
The 2-week proof is specifically designed to produce a visible result quickly. Many customers complete a Proof of Concept, see the result, and book a Process Transformation sprint 6–8 weeks later.
When to choose Process Transformation (Tier 2)
Choose Process Transformation if:
- You have already identified the workflow you want to automate
- You want an end-to-end result, not just a narrow test
- You are ready to commit to a 30-day engagement
This is the most popular starting point.
When to choose Multi-Process Rollout (Tier 3)
Choose Multi-Process Rollout if:
- You have already seen AI work in your operation (e.g. after a Tier 1 or Tier 2 sprint)
- You want to automate multiple workflows simultaneously
- You have executive sponsorship and internal resource available across teams
Not sure? Book the workshop first
If you are genuinely unsure, book the free discovery workshop. After 90 minutes with your team we will give you a clear recommendation — and it is always the honest one, not the most expensive option.
After your sprint, your AI assistant goes live and runs on the Evari platform. Your relationship with Evari shifts from a project engagement to an ongoing platform subscription.
The Evari platform
Your assistant is hosted on the Evari platform — a managed AI operations environment that handles uptime, security, model access, and performance monitoring. You do not need to manage any infrastructure.
Platform subscription
Once the sprint is complete, you move onto a monthly platform subscription. The tier depends on your transaction volume:
- Small — up to 100 daily transactions
- Growth — up to 500 daily transactions
- Scale — 1,000+ daily transactions
See the pricing page for current subscription costs. You can also save 20% by paying 12 months upfront.
Ongoing support
Your platform subscription includes an account manager and standard support. If something is not behaving as expected, contact us and we will investigate.
What about the 30-day post-launch support?
The 30-day post-launch support period is included in the sprint. This covers issues that arise directly from the sprint delivery — unexpected behaviour, edge cases that were not caught in testing, integration problems. It is separate from and in addition to your ongoing platform support.
Adding more assistants
Once you are seeing ROI from your first sprint, many customers book a second sprint to automate a second workflow. Each sprint is scoped independently. There is no requirement to do another sprint — you can stay on a single assistant as long as you like.
Yes. Many customers run multiple sprints over time, automating a new workflow every few months as they see ROI from the previous one.
How multiple sprints work
Each sprint is scoped and priced independently. There is no bundled commitment. After your first sprint, you can:
- Book a second sprint immediately if you already know what you want to automate next
- Wait 3–6 months to measure ROI from the first sprint before committing to a second
- Skip additional sprints entirely if your first sprint meets your needs
There is no pressure and no expectation of a follow-on engagement.
Do I get a discount for multiple sprints?
We do not apply automatic multi-sprint discounts, but if you are planning several sprints in a short timeframe we are happy to discuss pricing. Contact us to talk through your roadmap.
Can I run two sprints at the same time?
In most cases we recommend running sprints sequentially rather than in parallel. Running them in parallel requires significant team availability for two simultaneous discovery processes, which is difficult for most brokers and MGAs with lean operations teams.
The exception is the Multi-Process Rollout (Tier 3), which is specifically designed to automate 2–3 workflows in a single coordinated sprint. If you know you want to move fast on multiple workflows, Tier 3 is more efficient than two separate engagements.
Platform costs with multiple assistants
All your assistants run on the same platform subscription. You do not pay per assistant — you pay for the transaction volume across your whole operation. Multiple assistants are included in every platform tier.