Implementation methodology
How we deliver, phase by phase
How Tessovia delivers Streamvane: qualification, KPI discovery, integration level, pilot and managed operations — with clear deliverables and acceptance criteria.
The delivery path
Six phases, sized to your program
Not every client needs every phase at full depth. Jump to any stage to see what it involves, what it produces and how it's priced.
Qualification
A focused contact call
A short, no-obligation call to understand what you actually need before anyone is billed. We map your current Genesys footprint and — just as important — the downstream systems and connectors your KPIs will eventually have to reach.
- Duration
- 30–45 min
- Commercials
- Complimentary
- Exit criteria
- Go / no-go for a paid discovery workshop, with a sponsor and a confirmed downstream consumer identified.
What happens
- Current Genesys Cloud footprint — agents, regions, routing complexity
- Downstream systems already in play — WFM, BI, data platforms, CRM, buses
- Which connectors the program is likely to need
- Cloud and deployment preference — managed by us or embedded in your stack
- Alternatives already evaluated (A3S, AppFoundry, in-house)
KPI discovery workshop
Find the metrics that run your floor
We profile how your operation actually runs and which KPIs drive decisions, then map them against our catalogue of 1,200+ structural Genesys KPIs. Where you need metrics we don't already model, we start designing the client-specific KPIs — the part that usually carries additional cost.
- Duration
- 1–2 weeks
- Commercials
- Paid · sometimes credited toward the pilot
- Exit criteria
- Signed pilot SOW, or a documented stop with an honest alternative recommendation.
What happens
- Profile your activity type, channels and operating rhythm
- Capture the KPIs each team actually acts on, not just reports
- Match needs against the 1,200+ structural KPI catalogue
- Identify gaps and scope the custom KPIs worth building
- Draft connector selection and a target architecture
- Risk register — PII, latency, reconciliation, organizational change
Deliverables
Integration level
Decide how deeply Streamvane lives in your world
Before the pilot we agree how deeply Streamvane integrates with you. The right depth depends on your client type, your governance, and how large the agent and activity ecosystem you want to integrate really is. There are three common levels.
- Duration
- Agreed in discovery
- Commercials
- Scoped per level
- Exit criteria
- An agreed integration level and a deployment topology both sides sign off before build starts.
Run on our architecture
Streamvane runs as a managed PaaS bridge that we operate. Fastest to value and lightest footprint on your side — you consume KPIs through connectors and the REST API.
Embed in your cloud
We deploy the platform into your own Azure, AWS or GCP tenant as software you own and operate — shaped as PaaS or SaaS to fit your governance, keys and networking.
Into your SDLC
When the applications that visualise KPIs must live inside your delivery pipeline, we integrate into your code-production and software-development lifecycle — repositories, CI/CD, environments and release process.
Pilot
Prove one KPI family, end to end
One KPI family and one primary connector, delivered as running software you can accept or reject against explicit criteria. Scope discipline is the point — we prove the pattern before we scale it, so the production decision rests on evidence rather than a slide.
- Duration
- 4–6 weeks
- Commercials
- Fixed project fee
- Exit criteria
- UAT sign-off — a documented, demonstrable acceptance of the pilot scope.
What happens
- Stand up the foundation — bus, Reactive Engine, metrics store, secrets
- Enable engine processors for the agreed Genesys topics
- Implement the primary connector (e.g. Power BI or an HTTP feed)
- Observability dashboards and alerting on lag and failures
- UAT with operations sign-off against written acceptance tests
Deliverables
Production rollout
Scale at the pace and shape you choose
Additional KPI families and connectors roll out at the pace and shape the client wants — phased by KPI family, by region or by business unit — with the operational artifacts enterprise teams require to run it for years.
- Duration
- 8–16 weeks
- Commercials
- Phased, milestone-based
- Exit criteria
- Production acceptance and architecture sign-off.
What happens
- Additional KPI families and connectors, phased deliberately
- High-availability and disaster-recovery considerations as required
- Runbooks and on-call playbooks
- Security review artifacts for enterprise InfoSec
- Knowledge transfer to your platform and operations teams
Deliverables
Operations & roles
Watch the numbers, evolve the definitions
Once live, KPIs need watching and evolving. Managed operations cover platform health and activity monitoring, while evolutionary maintenance keeps definitions, connectors and custom KPIs current as your operation — and your Genesys configuration — keeps changing.
- Duration
- Ongoing
- Commercials
- Optional · SLA-tiered
- Exit criteria
- A clear RACI and SLA tiers defined in contract — never marketed as 24/7 unless staffed.
What happens
- Platform health monitoring — lag, throughput and error budgets
- Activity monitoring — are the numbers flowing and trustworthy
- Incident response within agreed SLA tiers
- Evolutionary maintenance — new KPIs, connectors and definition changes
- Monthly KPI and service report with a clear RACI
Roles & responsibilities
Who owns what, written down
Every engagement runs on an explicit RACI so accountability is never ambiguous — especially once the platform is live and evolving.
| Activity | Client | Streamvane |
|---|---|---|
| Genesys admin access | R/A | C |
| Cloud subscription / tenant | R/A | C |
| KPI definition sign-off | R | C |
| Build and deploy | I | R/A |
| Downstream consumer changes | R/A | I |
| Monitoring & evolutionary maintenance | C | R/A |
| Production acceptance | R/A | C |
R = Responsible · A = Accountable · C = Consulted · I = Informed
What we don't deliver in standard scope
Honesty about boundaries keeps budgets clean. These sit outside the standard engagement and are quoted separately if you need them.
- Genesys routing design or IVR rebuild
- WFM vendor implementation
- Unlimited custom report writing outside the agreed feed / API contracts
- 24/7 operations without an explicit SLA purchase
Start with a qualification call
Tell us your Genesys footprint and the systems your KPIs need to reach, and we'll recommend the right phases and integration level for your program.
Streamvane by Tessovia · Azure · AWS · GCP · Your data, your keys