Implementation-led, scoped to your Genesys program
Streamvane is enterprise software plus delivery — not a per-agent SaaS SKU. We publish our approach and packages openly, because Genesys KPI scope varies far more than agent count alone.
Packages
Six ways to start, one shared engine
Each package layers connectors onto the same Reactive Engine. You can begin narrow and expand without re-architecting.
Core Platform
Ingress, Reactive Engine, metrics store and the REST API — the base every other package builds on.
- For platform teams building internal consumers
- Entered after paid discovery
Microsoft & Power BI
Core plus the Power BI connector and Azure-native patterns for Microsoft-standardized estates.
- Azure + Power BI standardization
- Streaming datasets for live views
Operational Feeds
Core plus scheduled operational HTTP feeds for WFM, legacy schedulers and contractual exports.
- WFM intraday actuals
- Schema-controlled contracts
Enterprise Multi-sink
All implemented connectors plus optional managed operations — for multi-destination architectures.
- Telco, BPO, multi-sink programs
- Optional managed ops add-on
Partner / SI
Reference architecture, modules and a co-delivery kit for Genesys system integrators.
- Repeatable client delivery
- Partner margin on shared IP
Managed Operations
Layer onto any package: we run, monitor and evolve the platform — health, alerting, minor changes and a monthly KPI report.
- SLA-tiered monitoring
- Evolutionary maintenance
Pricing drivers
What actually moves the price
Streamvane is priced by scope and operational responsibility — not by agent headcount. Dashboard connectors meter per seat; we don't. The drivers below are what genuinely move a quote up or down, and they're exactly what we size with you during discovery, so the eventual number is explainable line by line instead of arriving as a surprise.
| Driver | What we look at | Why it moves the price |
|---|---|---|
| KPI families in scope | Agent vs agent + skill + routing + outbound | More families mean more processors, definitions and reconciliation |
| Connectors enabled | Power BI, feeds, brokers, warehouses, CRM | Each egress is a packaged module to configure, test and support |
| Environments | Dev / test / prod and DR | More environments multiply deployment and validation effort |
| Latency & SLA | Sub-second streaming vs contracted feed cadence | Tighter targets need more capacity, alerting and on-call cover |
| Operating model | Managed PaaS vs embedded in your own cloud | Embedded adds SDLC integration; managed adds ongoing run cost |
| Integration depth | Our architecture, into yours, or full SDLC | Deeper integration into your pipelines adds engineering days |
| Reconciliation complexity | WFM / Genesys baseline alignment | Definition alignment is analysis work, not just code |
Every driver is discussed openly in discovery — nothing is hidden behind a per-agent multiplier.
Engagement phases
Phase pricing — planning ranges, not quotes
Indicative ranges to help you budget before discovery. They are deliberately wide because Genesys KPI scope varies far more than agent count — a scoped, fixed quote comes out of the discovery workshop.
| Phase | Duration | Planning range (EUR) | Notes |
|---|---|---|---|
| Intro call | 30–45 min | Complimentary | Qualification, no obligation |
| KPI discovery | 1–2 weeks | 7.5k – 20k | Partly credited toward pilot in some deals |
| Pilot | 4–6 weeks | 30k – 75k | One KPI family + one connector |
| Production rollout | 8–16 weeks | 100k – 300k | Multi-connector, phased by family |
| Managed operations | Ongoing | 5k – 25k / mo | SLA-dependent add-on |
Ranges are for planning only and are replaced by an approved rate card before any contract.
What increases scope — and where the ROI comes from
We flag change requests early so budgets stay honest. The value levers below are why the platform pays back versus bespoke builds.
- Scope change: a new KPI family not in discovery
- Scope change: a new connector or additional Genesys org
- ROI: reusable reactive processing IP cuts SI days
- ROI: one KPI definition removes reconciliation labor
- ROI: pilots ship in weeks, not greenfield quarters
- ROI: a multi-connector fabric avoids duplicate ingestion
Request a scoped quote
Tell us your KPI families, connectors and environments, and we'll come back with a phase plan and range for your program.
Streamvane by Tessovia · Azure · AWS · GCP · Your data, your keys