How QStory Pricing Works

QStory is priced on a per-licence-per-month basis, scoped to each customer’s operation rather than sold from a public price list. What you pay reflects three things: the size of the teams you’re scheduling, the parts of the platform you use, and the complexity of your deployment. This page explains how that works, so you can gauge whether QStory fits your budget before you ever speak to us – and the fastest route to an exact figure is a short scoping conversation, which starts with a demo.

How is QStory priced?

QStory is an intraday-native, full-suite workforce management platform, and it’s modular: Workforce Management (forecasting, scheduling and schedule optimisation), Real-Time and Intraday Management, Employee Engagement through the Agent App, Back-Office Workforce Management, and coverage for branch and field teams. Your subscription is scoped to the modules you use and the teams you bring into them. There’s no public per-seat rate card — the section below explains why.

What determines the cost?

Three drivers shape every QStory proposal:

Because those three vary so much between operations, two customers rarely pay the same amount – and neither is subsidising the other.

Why doesn’t QStory publish a price list?

Because a single number would mislead almost everyone who read it. A 150-seat, single-site contact centre and a multi-thousand-seat operation spanning frontline, back office and branches are not buying the same thing, and a one-size price would misprice both. Scoped pricing means the figure you’re quoted reflects the coverage you’ll actually use – nothing padded in, nothing hidden to be discovered later. Generic per-seat figures for enterprise WFM rarely survive contact with a real deployment; a proposal built from a proper scoping conversation does.

What does a licence fee include?

Your licence fee covers the platform modules you’ve scoped, for the teams you’ve brought into them, including the Agent App for the people working those schedules where Employee Engagement is in scope. Implementation, onboarding and support arrangements are agreed as part of your plan and set out clearly in your proposal, so you know exactly what’s covered before you commit.

How do I get an accurate price?

Three steps, no homework:

  1. Book a demo. You’ll see the platform working the way your operation would use it.
  2. Scoping. We work through team sizes, channels, the modules that fit, and the systems we’d sit alongside.
  3. Your proposal. A tailored figure built from that scoping so the price reflects your operation, not an average of everyone else’s.

Book a demo →

What kind of return do QStory customers see?

Pricing conversations at QStory tend to become payback conversations, because the returns are measured in repurposed hours and retained people. NatWest repurposes 400,000 hours a year of previously idle time and cut agent attrition from 65% to 22%. Nationwide reduced lateness by 1,000 hours a month. eBay cut attrition by 25% with the Agent App. Jet2 increased coaching time by 87%. Those are the numbers to hold a subscription price against — and the case studies behind them tell the full story.

Book a demo →

Frequently asked questions

Does QStory publish prices?

No. Every subscription is scoped to the operation buying it – team size, modules and deployment complexity – so a public rate card would misprice most buyers. This page explains the model so you can gauge fit before talking to us.

What are the main factors that affect QStory’s price?

The number of people you’re scheduling and managing, which platform modules you deploy, and the complexity of the deployment – channels, sites, and the systems QStory works alongside.

Can we start with one part of the platform?

The platform is modular and every subscription is scoped to the modules you use. The scoping conversation establishes the right starting footprint for your operation and how it can grow from there.

Does pricing cover back office, branch and field teams as well as the contact centre?

Yes – QStory covers frontline, back-office, branch and field teams in one platform, and your subscription is scoped to whichever of those teams you include.

How do we see the product before committing?

Book a demo. It’s shaped around your operation rather than a generic walkthrough, and it’s the first step of the scoping that produces your proposal.

Is support included?

Implementation, onboarding and support arrangements are agreed as part of your plan and set out in your proposal, so there are no ambiguities about what’s covered.

What happens after the demo?

Scoping, then a tailored proposal built directly from it. You’ll know what drives your figure because you’ll have walked through the drivers with us.

Thinking about switching platforms? See how migrating WFM platforms works.