Connect applications without overselling
Objective. Explain each application's independent value, its required inputs, its optional enrichment from other applications, and the incremental value of combining - without implying everything is mandatory.
Teaches you to sell the platform's compounding value honestly: each application stands alone, some inputs are required for it to work, others are optional enrichment, and combinations add incremental value. You will draw an application/value map for a sample customer that a champion can take to a budget holder without feeling trapped into an all-or-nothing purchase.
See it in the demo
The customer problem
Buyers fear platform lock-in: 'if I buy one piece, do I have to buy all of it for any of it to work?' When an AE blurs independent value with combined value, the buyer assumes the worst - that the standalone application is crippled without the rest - and either over-buys (slow, risky) or walks. Business impact: inflated deals that stall in procurement, or lost deals where a single-application entry would have won. The skill is to be precise about three different things that AEs routinely merge: what an application does on its own, what it must have to function (required inputs), and what it does better when fed by or feeding another application (optional enrichment and incremental value). Precision here is what lets a champion fund a small start and expand on results.
Independent value vs required inputs vs optional enrichment
INDEPENDENT VALUE - what the application delivers alone. Time and Activity alone answers which paid hours are available and where to investigate. Work Output alone answers whether completed work meets standard at acceptable cost. Capacity Planning alone produces a requirement-vs-available plan with assumptions. Quality and Call QA alone runs evaluation-to-coaching. REQUIRED INPUTS - what it must have. Work Output requires a completed-work definition and a source for counting it; Scheduling requires a forecast/requirement and the rules, skills and time zone; Real-Time Adherence requires an activity mapping and an imported/published schedule. If a required input is missing, the application cannot deliver - name this honestly, do not hand-wave. OPTIONAL ENRICHMENT - what another application adds. Work Output is richer when Work Understanding explains WHY output is low (friction, rework); Scheduling is stronger on a Capacity Planning forecast than on a hand number; RCM Operations and Value Leakage sit on top of the operational applications to connect to outcomes and recoverable value. Enrichment is upside, not a prerequisite.
What to say / do - drawing the application/value map
For a sample customer, draw three columns per application in scope: Independent value (the standalone business answer), Required inputs (what they must provide for it to work - be specific: definitions, sources, rules), Incremental value from combining (which neighbouring application adds what, and roughly how much more decision power - not a fabricated percentage). Then a START box (the smallest useful application, from S03) and arrows to the expansion applications labelled with the incremental value. Talk track: 'Here is what this one application does on its own and what it needs from you to work. These others are optional - each adds specific value when you are ready, and you can see on the map exactly what you would gain, so nothing here is all-or-nothing.' Ground the arrows in real adjacencies: Time and Activity -> Work Output (from hours used to work produced), Work Output -> Work Understanding (from what to why), Capacity Planning -> Scheduling -> Real-Time Adherence -> Intraday Management (the WFM plan-execute-adhere-correct chain), all -> Value Leakage / RCM Operations (operational to financial/outcome).
The WFM chain and the outcome layer as honest combinations
The Workforce Management chain is the clearest honest combination story: Capacity Planning answers how many and which skills (https://capacityplanner.demo.timechamp.io/#/overview); Scheduling turns that requirement into feasible schedules (https://schedules.demo.timechamp.io/#/planner); Real-Time Adherence compares planned vs actual vs output live (https://rta.demo.timechamp.io/#/control); Intraday Management reforecasts and evaluates corrective action (https://idm.demo.timechamp.io/#/tower). Each is independently useful, but the incremental value of the chain is a closed loop from plan to execution to correction. Say explicitly where a required input links them: Scheduling needs the forecast version; a stale forecast is exactly why a schedule can look valid while failing current coverage. The outcome layer (RCM Operations, Value Leakage, RCM Insights) is enrichment that turns operational signals into revenue-cycle decisions and recoverable value - powerful, optional, and dependent on the operational applications beneath having trustworthy data.
Objections and honest limits
'So I need the whole suite for this to be worth it.' - No, and say it flatly: name the independent value of the one application, confirm it stands alone, and show the map where combinations are labelled 'optional, adds X'. 'If I only buy one, am I getting a crippled version?' - Distinguish required inputs (things THEY provide for it to work) from other applications (optional enrichment). A standalone application with its required inputs is fully functional. Honest limits: do not quantify incremental combined value with invented numbers - describe the decision power gained ('you go from what to why', 'you close the loop from plan to correction') and let the pilot measure magnitude; and where a combination depends on an integration or packaging detail, flag it to a specialist rather than promising seamlessness. Overselling the combination is the fastest way to lose the single-application entry that would have won the account.
Interpretation check
Three things are different and must not be merged: independent value (what one application does alone), required inputs (what the customer must provide for it to function), and optional enrichment (what other applications add). Blurring them either over-sells the suite or makes a strong standalone look crippled.
In the field
KnackGlobal map: START = Work Output on one claim team (independent value: cost per clean unit and output per FTE; required input: an agreed clean-unit definition and source). Arrows: -> Work Understanding ('why output lags'), -> Value Leakage ('turn the capacity opportunity into a tracked, owner-assigned recovery, capacity kept separate from cash'), -> RCM Operations ('connect to denial/AR outcomes') - each labelled optional so the displacement can start small and expand on proof.
Practical task
Draw an application/value map for a sample customer: for each application in scope list independent value, required inputs and incremental value from combining; mark the smallest-useful START application and draw labelled arrows to the expansion applications. Nothing on the map should imply an all-or-nothing purchase.
Self-check
A buyer asks whether Work Output is useless without the rest of the platform. Answer honestly.
No - it has independent value (does completed work meet standard at acceptable cost). It does have a required input: a completed-work definition and a source to count it. Other applications (e.g. Work Understanding) are optional enrichment, not prerequisites.
Distinguish a 'required input' from 'optional enrichment' with one example each.
Required input: Scheduling needs a forecast version, rules, skills and time zone to function. Optional enrichment: Work Understanding adding the 'why' behind a Work Output number - valuable but not required.
Why should you not put a percentage on the incremental value of combining applications?
You would be inventing a metric. Describe the decision power gained (what to why, closed-loop plan-to-correction) and let the customer's pilot measure the actual magnitude.
Describe the WFM chain and the required input that links two of its steps.
Capacity Planning -> Scheduling -> Real-Time Adherence -> Intraday Management. Scheduling requires the forecast version from Capacity Planning; a stale forecast makes a schedule look valid while failing current coverage.
Why is overselling the combination risky even when the platform is genuinely strong?
It makes the purchase feel all-or-nothing, inflating price and risk, and can cost you the single-application entry that would have won the account and set up expansion.
Verified vs demo. Application independence, the required inputs and the real adjacencies between applications are demo-grounded; the magnitude of incremental combined value and any integration/packaging dependency are NOT - describe them qualitatively and route specifics to a specialist.