Standalone and combined capabilities
Objective. Explain each application's independent value and the incremental value when applications are combined - what each needs as input, what it optionally enriches - without overselling integration that a customer does not have.
The difference between a trusted advisor and a bundle-pusher is the ability to say what one app does on its own and what genuinely improves when two are combined. This teaches independent value per app, the real incremental value of combinations, and the honest limits that keep you from promising seamless integration you cannot stand behind.
See it in the demo
The customer problem
Customers have two opposite fears and you have to disarm both. One is 'this only works if I buy the whole suite' - the fear of a forced, expensive, all-or-nothing commitment. The other is 'these are just separate tools bolted together' - the fear that the 'platform' is a logo over disconnected products. Oversell either way and you lose: promise that everything is seamlessly integrated and you set up a trust failure at implementation; undersell the connections and you leave the strategic value - the staircase - on the table. The business impact of getting it wrong is deals that collapse on price (because you implied a bundle) or on scope (because you implied integration that needs work to deliver). The skill is precision: name the standalone value, name the real incremental value, and name the input required to get it.
Independent value - each app earns its place alone
Every application answers a customer question on its own, with no other app required:
- Time and Activity alone answers 'how are paid hours used and where do I investigate?'
- Work Output alone answers 'are busy teams producing expected work at quality and cost?'
- Work Understanding alone answers 'why does this work take so long?'
- Capacity Planning alone answers 'how many people and skills, when?'
- Scheduling alone turns a requirement into a feasible schedule.
- Real-Time Adherence alone compares live activity to the schedule.
- Intraday Management alone reforecasts today and evaluates fixes.
- RCM Operations alone prioritises the next revenue-cycle issue.
- Quality and Call QA alone runs evaluation to coaching.
- RCM Insights alone answers business questions with evidence.
- Value Leakage alone finds and tracks recoverable value.
- Employee Monitoring alone provides scoped activity visibility.
This matters for scoping (S03): you can always propose the single app that answers the customer's stated question, which is cheaper, faster to prove and easier to trust.
Incremental value - what genuinely improves combined
The staircase (F01) is where combinations add real value, and you should be able to name the mechanism, not just wave at 'synergy':
- Time and Activity + Work Output - utilisation becomes meaningful only beside output attainment: busy is not the same as productive, and together they answer 'are the paid hours turning into the expected work?' (Work Output's sales task is exactly this contrast.)
- Capacity Planning + Scheduling + RTA + Intraday - a planning chain: forecast required capacity, build a feasible schedule, watch adherence live, reforecast the day. Each needs the previous as a trustworthy input.
- Work Output + Work Understanding - what is produced, plus why it takes as long as it does and which change to try.
- Any operational app + Value Leakage - findings get attributed and tracked to recovery.
- Operational apps + RCM Operations / Insights - floor signals connect to business outcomes and answerable questions.
The honest framing: each combination requires inputs (mappings, standards, a trusted forecast, defined 'done'). Incremental value is real but it is earned with those inputs, not automatic on purchase.
What to say / do
Sales, the application/value map move (S05): for a sample customer, draw each app, its independent value, the inputs it needs, and the incremental value when connected to the next step. Say it as: 'Work Output stands on its own and answers your output question today. If you later add Time and Activity, utilisation becomes meaningful next to output - but that is a next step, not a prerequisite.' This positions expansion without forcing a bundle.
CSM, in expansion qualification (C09): lead with an unmet objective the customer already has, then show which combination answers it and what input it needs. Never pitch an add-on as automatically integrated; confirm the input and the included-feature check first.
Both: when you describe a combination, always name the input it depends on. 'Adherence needs a published schedule from a trusted forecast' is the sentence that keeps you honest and keeps implementation sane.
Objections and honest limits
'So I have to buy everything for it to work?' - No. Lead with the single app that answers their question; combinations are optional incremental value, not prerequisites.
'Is it really integrated, or just bundled?' - The applications share the staircase model and, in the Enterprise Platform demo, a common chrome and shared services. But whether two specific apps are integrated and entitled together for a given customer is a packaging and implementation fact - confirm with product (F10). Do not promise seamless data flow between apps you have not verified for that customer.
Honest limit: the demos show each app's independent value and the Enterprise Platform shows them hosted in one chrome with shared services. That demonstrates the platform intent. It does not prove that any two apps are automatically connected in a customer's instance, or that an incremental benefit arrives without the input (mapping, standard, forecast) it depends on. Separate 'designed to combine' (demo-supported) from 'already combined for you' (confirm with product).
Interpretation check
Each application has genuine standalone value and combinations add real but earned incremental value; 'designed to combine' is not the same as 'already integrated and entitled for this customer.' Never imply automatic integration you have not confirmed.
In the field
KnackGlobal can start on Work Output alone to prove output-per-FTE against the incumbent, then add Time and Activity so utilisation is read beside output and Value Leakage to attribute and track recovery - a sequenced, input-aware expansion rather than a day-one bundle.
Practical task
Draw an application/value map for one sample customer: list the apps relevant to their problem, each app's independent value, the input each needs, and the incremental value of the one or two combinations that matter most - explicitly labelling which connections are 'designed to combine' versus 'confirm with product' for that customer.
Self-check
A customer only has an output problem. Why is proposing the whole platform the wrong move?
Work Output answers their stated question on its own; proposing the whole platform inflates price and risk, implies a forced bundle, and delays a provable result. Lead with the single app and position the rest as optional next steps.
Explain the real mechanism by which Time and Activity plus Work Output beats either alone.
Utilisation (busy time) only becomes meaningful next to output attainment: together they answer whether paid, used hours are actually producing the expected work at quality and cost, which neither answers alone.
What input does Real-Time Adherence depend on, and why must you name it?
A published schedule built on a trusted forecast. Naming it keeps the combined value honest and sets correct implementation expectations - adherence is only as good as the schedule and forecast behind it.
Which combination claim is demo-supported and which needs product confirmation?
Demo-supported: the apps share a staircase model and run in one chrome with shared services (Enterprise Platform). Confirm-with-product: whether two specific apps are integrated and entitled together in a given customer's instance.
Verified vs demo. Each app's standalone value and the platform hosting them in one chrome with shared services are shown in the demos; whether specific apps are integrated and entitled together for a real customer, and the inputs required, need product confirmation.