Success Section 01
Purpose and scope
This Customer Success Policy describes how Kool&Tech approaches post-sale alignment, onboarding, adoption, value realization, service reviews, risk management, recommendations, renewals, and long-term customer development for eligible services.
Success Section 02
Policy, not outcome guarantee
Customer Success is a collaborative operating model and does not guarantee revenue, savings, adoption, renewal, compliance, project success, or another business result. Customer-specific commitments exist only when stated in a signed agreement.
Success Section 03
Eligibility
Customer Success activities apply according to the purchased subscription, managed-services plan, retainer, SOW, Order Form, account tier, and available service resources. Not every Customer receives the same cadence or deliverables.
Success Section 04
Customer Success principles
Kool&Tech seeks to align services with Customer goals, make responsibilities visible, support adoption, identify risk early, document decisions, recommend practical next steps, and maintain transparent boundaries between success, support, projects, and commercial services.
Success Section 05
Success lifecycle
01AlignConfirm objectives, stakeholders, scope, responsibilities, constraints, and intended outcomes.
02OnboardEstablish access, governance, training, readiness, and first-value milestones.
03AdoptEncourage effective use of agreed workflows, capabilities, documentation, and controls.
04Realize valueReview progress against Customer-defined goals and available evidence.
05EvolvePrioritize improvements, risks, integrations, governance, and roadmap opportunities.
06Renew or transitionPlan continuation, expansion, reduction, nonrenewal, or orderly handoff.
Success Section 06
Sales-to-service handoff
Where applicable, handoff may include Customer objectives, contracted scope, stakeholders, commercial assumptions, technical context, success criteria, risks, exclusions, timelines, and outstanding decisions. The signed Agreement remains the authoritative source.
Success Section 07
Customer onboarding
Onboarding may include kickoff, stakeholder alignment, access validation, environment review, communications, documentation, training plan, milestone confirmation, support channels, escalation contacts, and transition to recurring operations.
Success Section 08
First-value milestone
The parties may identify an initial operational milestone that demonstrates usable progress. The milestone, evidence, dependencies, timing, and acceptance must be appropriate to the service and documented when contractually relevant.
Success Section 09
Joint success plan
An eligible engagement may use a success plan describing goals, milestones, measures, risks, owners, dependencies, decisions, and next actions. A success plan supports coordination but does not expand contracted scope or replace a Change Order.
Success Section 10
Customer goals
Customer owns its business goals and must communicate changes, priorities, constraints, and success criteria. Kool&Tech may help translate goals into service objectives, recommendations, workflows, or measurable indicators.
Success Section 11
Roles and stakeholders
Customer should identify an executive sponsor, operational owner, technical contact, approvers, process owners, and other relevant stakeholders. Kool&Tech may identify success, delivery, support, technical, and commercial contacts according to the engagement.
Success Section 12
Governance cadence
Governance may include operational check-ins, project reviews, service reviews, executive business reviews, roadmap sessions, renewal planning, and incident escalation. Cadence and participants depend on the selected service model.
Success Section 13
Adoption
Adoption may be reviewed using available evidence such as enabled users, active workflows, completed training, documented processes, feature use, system records, or Customer feedback. Usage alone does not prove business value or correct process execution.
Success Section 14
Enablement and training
Enablement may include walkthroughs, administrator coaching, role-based training, written guides, recordings, office hours, knowledge transfer, and recommended learning resources when included in scope.
Success Section 15
Customer change management
Customer is responsible for internal communication, leadership alignment, policy updates, role clarity, incentives, adoption expectations, staffing, and organizational change unless specific change-management services are included.
Success Section 16
Value realization
Value discussions should connect use and delivery to Customer-defined outcomes, while recognizing that results may depend on Customer data, behavior, staffing, decisions, market conditions, third parties, and other factors outside Kool&Tech control.
Success Section 17
Metrics and evidence
Metrics should have a defined source, owner, calculation, period, interpretation, and limitation. Kool&Tech will not present estimated, incomplete, or Customer-supplied data as independently verified unless the service expressly includes validation.
Success Section 18
Customer health framework
Where offered, a health view may consider adoption, engagement, support patterns, unresolved risks, stakeholder alignment, contractual consumption, technical conditions, and progress against goals. Health indicators are operational tools, not guarantees or judgments about individuals.
Success Section 19
Service reviews
A service review may cover objectives, usage, incidents, support themes, consumption, open risks, dependencies, upcoming changes, recommendations, decisions, and action items. The agenda should be adapted to the Customer and contracted service.
Success Section 20
Business and executive reviews
Quarterly or executive reviews, when included, are intended to realign goals, summarize available evidence of value, surface risks, evaluate adoption, discuss recommendations, and agree forward-looking actions rather than merely list completed activities.
Success Section 21
Review preparation
Kool&Tech may prepare an agenda or pre-read using available service records and Customer-provided information. Customer should review material, identify changed priorities, invite appropriate decision-makers, and correct inaccurate assumptions.
Success Section 22
Action plans
Review outcomes should identify clear actions, owners, dependencies, target dates or sequences where appropriate, and the evidence needed for closure. Action items do not authorize out-of-scope work or override contractual change control.
Success Section 23
Risks and blockers
Kool&Tech may document risks such as missing access, delayed decisions, unsupported systems, data quality, low adoption, capacity, licensing, vendor changes, security concerns, resource constraints, and unresolved scope decisions.
Success Section 24
Escalation
Customer Success escalation is used for strategic alignment, cross-functional blockers, repeated risk, unresolved service concerns, or executive attention. Technical incidents and support requests must continue through authorized support and SLA channels.
Success Section 25
Relationship to support
Support handles incidents, requests, troubleshooting, and service operations under the Support Policy. Customer Success synthesizes themes, alignment, adoption, risks, and forward plans. It does not replace ticket submission or create new response targets.
Success Section 26
Relationship to Professional Services
Implementation, configuration, development, migration, integration, assessment, training programs, and process redesign require Professional Services scope when not already included. Customer Success recommendations are not automatic authorization to perform project work.
Success Section 27
Product feedback
Kool&Tech may collect feedback about features, workflows, documentation, integrations, support, and future needs. Feedback may inform product or service planning but does not create a commitment to deliver a feature or roadmap date.
Success Section 28
Roadmap discussions
Roadmap sessions may address Customer priorities, lifecycle changes, technical debt, platform evolution, integrations, governance, risks, and recommended phases. Roadmaps are planning tools and remain subject to scope, feasibility, pricing, and authorization.
Success Section 29
Recommendations
Recommendations reflect the information available when made and may require discovery, validation, testing, Customer approval, third-party review, or a separate SOW. Customer remains responsible for business decisions and implementation authorization.
Success Section 30
Renewal planning
Where applicable, renewal planning may review continuing needs, service performance, consumption, plan fit, upcoming changes, risks, commercial timing, and transition requirements. Renewal terms are governed by the relevant Order Form or agreement.
Success Section 31
Expansion and additional services
Kool&Tech may identify optional services, licenses, modules, integrations, training, managed services, or subscription changes where relevant to Customer goals. Any purchase requires separate commercial authorization.
Success Section 32
References and advocacy
Participation in references, testimonials, case studies, events, reviews, or referrals is voluntary and subject to appropriate Customer approval, confidentiality, privacy, and branding requirements.
Success Section 33
Customer feedback and concerns
Customers should provide timely, specific feedback through the appropriate channel. Kool&Tech may use feedback to improve services, identify risk, clarify expectations, and route issues to responsible teams.
Success Section 34
Success records
Kool&Tech may maintain success plans, meeting notes, goals, action items, risks, decisions, usage summaries, recommendations, feedback, renewal records, and stakeholder information for service management and contractual purposes.
Success Section 35
Privacy and confidentiality
Customer Success information is handled subject to the Privacy Policy, DPA, confidentiality terms, access controls, and applicable law. Customers should avoid sending unnecessary sensitive data in routine success communications.
Success Section 36
Customer responsibilities
Customer must provide accurate information, appropriate stakeholders, timely decisions, access, data, internal coordination, testing, adoption leadership, and feedback. Customer delay or nonparticipation may affect milestones and value realization.
Success Section 37
Service boundaries
Customer Success does not include unlimited consulting, project management, custom reporting, data analysis, development, training, onsite work, compliance certification, legal advice, or around-the-clock support unless expressly purchased.
Success Section 38
Changes to engagement model
Kool&Tech may adjust contacts, tools, meeting format, reporting, or engagement method while preserving contractual commitments. Material changes to purchased deliverables or cadence follow the governing agreement.
Success Section 39
Transition and offboarding
At renewal change, nonrenewal, or termination, the parties may review open actions, service dependencies, exports, documentation, credentials, access, provider contacts, and separately scoped transition assistance.
Success Section 40
Relationship to other terms
Signed Order Forms, SOWs, Managed Services Schedules, SLA Schedules, and DPAs control their subjects. The Master Services Agreement, Subscription Agreement, Support Policy, Professional Services Agreement, and this policy provide the broader framework.
Success Section 41
Policy updates
Kool&Tech may update this policy as products, services, engagement models, tools, and operating practices evolve. Updates do not amend a signed Customer commitment unless permitted by the governing agreement.
Success Section 42
Customer Success contact
Questions about onboarding, success planning, service reviews, adoption, roadmap discussions, risks, renewals, or engagement eligibility may be sent to info@koolandtech.com. Active incidents should use the authorized support channel.