Custom Support Packages

Introduction

Off-the-shelf support contracts rarely fit. You're forced into rigid tiers with included hours you don't need, SLA response times that don't match your actual risk profile, or coverage windows that don't align with your operating hours. You pay for features you won't use or compromise on critical requirements because they're not included in standard packages.

Custom support packages solve this by building agreements around your specific needs: your application's criticality profile, your team's internal capabilities, your operating hours and user distribution, your budget and risk tolerance, and your compliance or regulatory requirements.

According to HDI's 2025 Support Center Practices report, organizations with tailored support agreements experience 34% better SLA compliance and 41% higher customer satisfaction compared to standard tiered packages, because the SLA terms actually reflect real-world requirements rather than arbitrary vendor defaults.

We design custom support packages that align precisely with your business needs — whether that's a lightweight 10-hour monthly retainer for low-volume maintenance, 24/7 white-glove support with 15-minute response SLAs, hybrid arrangements combining managed hosting with application support, or fractional team models providing specific expertise (security, database, infrastructure).

Why standard support packages don't fit

1. Unused hours create inefficient budgets

The scenario: A professional services firm purchases a 40-hour monthly support package for their client portal because it's the only tier with weekend coverage. In reality, they average 12-15 support hours per month. After 8 months, they've paid for 320 hours but used 104 hours — leaving 216 unused hours (£20,520 at £95/hour) that don't roll over. They continue paying because they need the weekend SLA, even though 60% of their spend delivers no value.

The cost: £20,520 spent on unused hours annually. A custom package with weekend coverage and 15-hour monthly allocation (with overflow at hourly rates) would have cost £14,400 annually plus £4,000 in overflow = £18,400 total. Inflexible packaging cost £2,120 in wasted budget.

2. Missing coverage creates business-critical gaps

The scenario: An e-learning platform operates globally with heavy usage from 6 AM to midnight UK time. They purchase "24/7 support" but discover the SLA only covers P1 incidents outside business hours — routine P2 issues (bugs affecting specific user segments, performance degradation, integration failures) aren't addressed until next business day. A P2 bug affecting mobile users hits at 8 PM Thursday, isn't addressed until 9 AM Friday, and impacts 2,400 users over 13 hours.

The cost: 13-hour degraded experience for 24% of user base during peak study period before exams. Customer complaints, support ticket volume spike, and dissatisfaction measurable in post-incident NPS drop from 68 to 54. Issue would have been P1 under appropriate coverage definition but vendor's standard package doesn't classify mobile-specific bugs as critical.

3. Wrong SLA priority definitions cause misalignment

The scenario: A logistics company's standard support contract defines P1 as "complete system unavailability." When their automated dispatch system fails but manual dispatch remains possible, the vendor classifies it as P2 (next business day) even though this forces 40 staff onto manual process costing £180/hour in reduced efficiency. The business considers this P1 (dispatch system is operationally critical) but the vendor's rigid definitions don't account for customer's operational reality.

The cost: 16-hour delay in fixing automated dispatch while £2,880 in efficiency loss accumulates. Custom SLA definitions aligned to business impact would have classified this as P1, triggering 2-hour response instead of next-day queue.

4. No flexibility for seasonal demand

The scenario: A retail analytics platform has highly seasonal usage — 80% of annual support needs occur September-January (retail planning and holiday seasons), with minimal support required February-August. Their annual fixed-capacity support contract allocates 30 hours monthly regardless of actual need. They routinely exceed allocations in Q4 (paying overflow rates) while leaving hours unused in Q2-Q3.

The cost: Over 12 months, they paid for 360 hours but used 280 hours (80 unused) plus 48 overflow hours at 1.5x rate. Outcome: paid for 408 hour-equivalents while consuming 328 hours. A custom package with variable allocation (15 hours baseline, 50 hours Q4 surge) would have aligned spend with actual usage pattern.

5. Bundled services include unnecessary components

The scenario: A fintech company needs application support but their chosen vendor only offers packages bundling application support with infrastructure management. They already have internal DevOps team managing infrastructure, making 40% of the bundled package redundant. They pay £9,500/month for bundled services when they only need £5,800/month in application support.

The cost: £3,700 monthly (£44,400 annually) spent on infrastructure management they don't use, because vendor doesn't offer unbundled application-only support. Custom package unbundling services would eliminate this waste.

Custom support package components

1. Tailored SLA definitions and response times

We define incident priorities based on your business impact definitions, not arbitrary vendor standards. If your dispatch system failing is P1 for your operations (even if manual backup exists), we classify it P1 with corresponding response times.

Custom priority definitions: Work with you to define P1/P2/P3/P4 based on business impact (revenue, operational disruption, customer experience, compliance risk), set response and resolution targets aligned to actual consequences, and agree coverage windows matching your operational hours and user distribution.

2. Flexible hour allocations and rollover policies

Monthly hour allocations matching your actual usage patterns, with options for unused hour rollover, banked hours for future use, or variable allocations across the year. If you need 50 hours in December and 10 hours in July, we structure the package accordingly.

Allocation models: Fixed monthly hours with overflow at agreed rates, variable monthly allocations (higher during known busy periods), annual hour banks with monthly draw (e.g., 300 hours annually, allocated flexibly), or retainer models with capacity guarantees (we keep capacity available whether you use it or not).

3. Customized coverage windows and escalation paths

Coverage aligned to your operational needs — not arbitrary business hours. If you need 7 AM-10 PM coverage Mon-Sat because those are your customer-facing hours, that's what we provide. Emergency escalation paths defined based on your risk tolerance.

Coverage options: Business hours (9-6), extended hours (7-10), weekend coverage, 24/7 full coverage, follow-the-sun models (peak hours across multiple timezones), or hybrid (business hours standard, 24/7 emergency escalation).

4. Modular service components

Pick exactly the services you need rather than forced bundles. Need application support but not infrastructure management? Need security patching but not feature development? Need incident response but not proactive monitoring? We unbundle services to match your requirements.

Available components: Application bug fixes and maintenance, security patching and dependency updates, infrastructure monitoring and management, incident response and root cause analysis, change requests and feature enhancements, performance optimization, database administration, integration support (third-party API/system issues), compliance and audit support (SOC 2, ISO 27001, GDPR).

5. Scalability and adjustment provisions

Business needs change. Custom packages include clear terms for scaling up or down, adding/removing service components, adjusting hour allocations, or changing coverage windows. Typically quarterly adjustment windows with 30-day notice.

Flexibility terms: Quarterly reviews with adjustment options, scale-up provisions for growth or seasonal demand, scale-down options if requirements decrease, team member changes if expertise needs shift, and month-to-month terms after initial minimum period (typically 3-6 months for onboarding efficiency).

Custom package design process

Phase 1: Requirements discovery (Week 1)

We conduct structured interviews with stakeholders to understand your application portfolio, current support arrangements, historical incident patterns, internal team capabilities and gaps, operational hours and user distribution, and budget and risk tolerance.

Deliverables: Requirements summary document, current-state support assessment, and identified gaps and risks.

Phase 2: Package design and proposal (Week 1-2)

Based on requirements, we design a custom support package including SLA definitions (priority levels, response times, resolution targets), hour allocations and rollover policies, coverage windows and escalation paths, included service components, team composition and named contacts, and pricing with transparent breakdown.

Proposal components: Service Level Agreement (SLA) document, Statement of Work (SOW) defining scope, pricing schedule (monthly or annual), team profiles and expertise areas, and implementation/onboarding plan.

Phase 3: Negotiation and refinement (Week 2-3)

We review the proposal together, adjust terms based on feedback, clarify any ambiguous definitions, and agree final SLA and commercial terms.

Typical adjustments: Hour allocation tuning based on historical data, priority definition refinement to match business impact, coverage window adjustments for cost optimization, modular component additions/removals, and escalation procedure clarification.

Phase 4: Onboarding and steady-state operations (Week 3+)

Once terms are agreed, the support team undergoes onboarding on your systems (typically 2-4 weeks depending on complexity), we establish monitoring and alerting, set up communication channels (ticketing, Slack/Teams, phone), document procedures and runbooks, and begin steady-state support delivery.

Onboarding deliverables: Team introduction and contact details, support procedures documentation, access provisioning completed, initial system health assessment, and transition complete confirmation.

Case studies: Custom package outcomes

Case study 1: Retail seasonal support optimization

Client: Online furniture retailer with £18M annual revenue

Challenge: Using standard 40-hour monthly support package year-round. Actual usage: 12-18 hours monthly Feb-Aug, 55-80 hours monthly Sep-Dec. They paid for 480 hours annually but used 520 hours (40 hours overflow at 1.5x rate). Effective cost per hour: £108 due to misaligned fixed allocation. Annual support spend: £54,720 (480 base hours at £95/hour plus 40 overflow at £142.50/hour).

Solution: Designed custom package with variable monthly allocations: 15 hours monthly baseline (Feb-Aug: 105 hours), 70 hours monthly peak season (Sep-Dec: 280 hours), annual allocation 385 hours at £92/hour flat rate, overflow hours at standard £115/hour (not 1.5x premium), and quarterly true-up allows reallocation if patterns shift.

Results:

• Annual base allocation: 385 hours at £92/hour = £35,420
• Typical overflow: 20-30 hours at £115/hour = £2,300-£3,450
• Total annual spend: £37,720-£38,870 vs previous £54,720
• Annual savings: £15,850-£17,000 (29-31% reduction)
• Better alignment: hours available when actually needed instead of wasted in off-season

ROI: Immediate 29-31% cost reduction with same service quality. Custom packaging eliminated ~£16,000 annual waste.

Case study 2: Fintech unbundled infrastructure support

Client: Payment processing platform, £45M annual transaction volume

Challenge: Vendor offered only bundled packages combining application support with infrastructure management. Client had strong internal DevOps team managing infrastructure, making the bundled infrastructure component redundant. Package cost £11,200/month. Client estimated only £6,500/month value derived from application support component.

Solution: Designed custom unbundled package focused exclusively on application-level support including application bug fixes and feature enhancements, API integration troubleshooting and maintenance, payment gateway integration support (Stripe, Adyen, checkout.com), security vulnerability patching, compliance support (PCI-DSS, PSD2), and 24/7 incident response for application-layer issues (infrastructure remained client responsibility).

Results:

• Custom package cost: £7,200/month
• Previous bundled cost: £11,200/month
• Monthly savings: £4,000 (£48,000 annually)
• Service quality maintained: all needed support components retained
• Eliminated redundancy: infrastructure management component removed

ROI: 35% cost reduction through unbundling. £48,000 annual savings with no service degradation.

Pricing framework for custom packages

Custom packages are priced based on component selection, hour allocations, coverage windows, and SLA response times. Below are indicative ranges — actual pricing tailored to specific requirements.

Component pricing (indicative)

Application support (bug fixes, maintenance):

• Business hours coverage: £3,500-£6,000/month (15-30 hour allocation)
• Extended hours (7-10 PM): +£1,200-£2,000/month
• 24/7 coverage: +£2,500-£4,000/month

Infrastructure monitoring and management:

• Basic monitoring (CloudWatch, alerting): £1,800-£3,200/month
• Full managed hosting (patching, backups, optimization): £4,500-£8,500/month

Security patching and compliance:

• Regular patching (monthly cycle): £800-£1,500/month
• Compliance support (SOC 2, ISO 27001, HIPAA): +£1,200-£3,000/month

Incident response SLA tiers:

• 4-hour P1 response (business hours): baseline included
• 2-hour P1 response (business hours): +£500-£1,000/month
• 30-minute P1 response (24/7): +£1,800-£3,500/month
• 15-minute P1 response (white-glove): +£3,000-£5,000/month

Change request allocations:

• 20 hours monthly: £1,900-£2,400/month
• 40 hours monthly: £3,600-£4,400/month
• 80 hours monthly: £6,800-£8,500/month

Database administration:

• Performance tuning and optimization: £1,200-£2,500/month
• Full DBA services (backups, replication, query optimization): £3,000-£6,000/month

Hour allocation models

Fixed monthly retainer: 10 hours: £1,200-£1,500/month 20 hours: £2,000-£2,600/month 40 hours: £3,600-£4,800/month 80 hours: £6,400-£8,500/month

Annual hour bank: 150 hours annually: £13,500-£16,500 (£90-£110/hour effective rate) 300 hours annually: £25,500-£31,500 (£85-£105/hour) 500 hours annually: £40,000-£50,000 (£80-£100/hour)

Variable allocation (seasonal): Baseline + surge pricing: e.g., 15 hours/month baseline 8 months (£1,800/month) + 60 hours/month peak 4 months (£6,000/month)

When you need a custom support package

Custom packages are ideal if:

1. Usage patterns are seasonal or variable — Predictable high/low periods that don't fit fixed monthly allocations
2. Standard SLA definitions don't match your risk profile — Your definition of "critical" doesn't align with vendor defaults
3. You need specific expertise not in standard packages — Database specialists, security expertise, specific framework/technology knowledge
4. Your application has unique operational hours — Global users, weekend-heavy usage, or non-traditional business hours
5. You want modular services without bundling — Need application support but not infrastructure, or vice versa
6. You have internal capabilities covering some areas — Want to supplement existing team, not replace them
7. Standard packages waste budget on unused features — Paying for services or hours you consistently don't use

Why iCentric for custom support packages

No forced bundling: We design packages around your actual needs. If you only need application support, you don't pay for infrastructure management you'll never use.

Transparent pricing: Component-based pricing with clear breakdown. You'll understand exactly what you're paying for and can make informed tradeoff decisions.

Flexible terms: Month-to-month contracts after initial onboarding period (typically 3-6 months). Quarterly adjustment provisions as your needs evolve. No multi-year lock-in to terms that become obsolete.

Business-aligned SLAs: We define incident priorities based on your operational impact, not generic severity matrices. If a "P2" incident by standard definitions causes major business disruption for you, we classify and respond according to your reality.

UK-based team: Engineers based in the UK with native English fluency and understanding of UK business culture, compliance requirements, and working hours.

Track record across sectors: Experience designing custom packages for healthcare (HIPAA, CQC compliance), finance (FCA, PCI-DSS requirements), e-commerce (seasonal peaks), professional services (variable workload), and SaaS platforms (continuous deployment support).

Next steps: Custom package consultation

Start with a complimentary requirements discovery session to understand your specific needs, operational patterns, and budget parameters.

Discovery session includes:

• Application portfolio and criticality assessment
• Historical support usage and incident pattern analysis
• Internal team capability evaluation
• SLA requirement definition workshop
• Custom package design and proposal
• Transparent pricing breakdown

Get started: Contact us to schedule a requirements discovery session or request an initial custom package proposal.