SAP Implementation Cost: UK Pricing, Timelines and Factors

Estimating the cost of an SAP implementation is rarely straightforward. Unlike standard SaaS products with fixed subscription plans, SAP projects vary significantly depending on business requirements, deployment model, and implementation scope.

For example, implementing SAP S/4HANA Cloud Public Edition for a growing UK manufacturer typically requires a very different investment than migrating a global enterprise from a heavily customized SAP ECC landscape to SAP S/4HANA Private Edition.

While software licensing is an important part of the budget, it is only one component of the overall investment. Project costs are primarily influenced by implementation complexity, including business process scope, deployment approach, data migration, system integrations, customization requirements, testing, user adoption, and long-term support.

This guide explains the main factors that influence SAP implementation costs in the UK, compares typical deployment scenarios, highlights common hidden expenses, and outlines practical ways to optimize project budgets while reducing delivery risk.

How Much Does SAP Implementation Cost? (Enterprise Benchmarks)

While exact pricing depends on tailored scope discovery, executive decision-makers need realistic budget categories to plan capital and operational expenditure. In the UK market, SAP implementation projects generally fall into three primary enterprise complexity tiers based on software scope, user counts, and delivery timelines:

SAP Implementation Cost and Complexity Benchmarks

Implementation budgets increase with project complexity - not simply with the number of users. Data migration, system integrations, process redesign, testing, and organizational change management typically have a greater impact on overall costs than software licensing itself.

For most SAP projects, software licenses or cloud subscriptions account for approximately 20%–30% of the total five-year investment. The remaining 70%–80% is typically allocated to implementation services, system integration, data migration, testing, training, and change management. As a result, controlling project complexity is often the most effective way to reduce both costs and delivery timelines.

Executive Summary: SAP Implementation Budget Allocation

To evaluate enterprise budgeting, implementation partners assess costs relative to overall project effort and allocation across key lifecycle phases. The matrix below outlines how a typical enterprise SAP implementation budget is distributed across core workstreams:

Typical SAP Implementation Budget Allocation Matrix

Budget allocation should reflect the full implementation lifecycle rather than focusing on a single phase. Projects that invest consistently in planning, data quality, integration, testing, and user adoption are typically better positioned to achieve a predictable go-live and faster business value.

Implementation Timeline vs. Cost Relationship

Project duration is one of the most direct multipliers of SAP implementation consulting costs. Extending a project timeline by just two months significantly increases resource burn rates across both external consulting teams and internal business staff.

Delivery Duration vs. Financial Impact

Although every SAP implementation includes the same core workstreams, budget allocation varies depending on project complexity. The largest differences typically arise in data migration, integrations, custom development, and testing - areas that expand as business scope and technical requirements increase.

Cost by Project Complexity Tier

Evaluating your SAP ERP implementation budget requires matching your functional scope requirements against established technical complexity tiers:

Each successive complexity tier expands not only functional scope but also implementation effort. Additional modules introduce new integrations, master data domains, testing requirements, and business owners that increase project coordination across the organization.

Rather than maximizing scope from day one, many organizations achieve better outcomes by delivering a stable core ERP foundation first and introducing advanced capabilities through phased rollouts. This approach reduces delivery risk while accelerating time-to-value.

Cost of SAP Implementation by Deployment and Migration Scenario

The technical migration pathway and cloud hosting model selected directly shape both initial implementation pricing and long-term operating expenses:

Deployment and Technical Migration Comparison Matrix

The migration approach has a direct impact on both implementation investment and the future operating model of the SAP landscape. The lowest-cost pathway is not always the one with the lowest long-term risk. For example, a Brownfield conversion may reduce initial migration effort by preserving existing structures and historical data, but organizations often inherit years of technical debt, unused custom code, and inefficient business processes that increase future maintenance costs.

SAP S/4HANA Cloud Public Edition Greenfield implementations typically require a stronger commitment to process standardization. By adopting SAP Best Practices and limiting in-core customization, organizations can achieve faster deployment cycles, simpler upgrades, and lower long-term system complexity. However, this approach requires business teams to actively redesign legacy processes rather than replicate existing ways of working.

Private Edition and Selective Data Transition approaches provide additional flexibility for organizations with complex operational requirements, extensive integrations, or regulatory obligations around historical data retention. This flexibility comes with additional implementation effort, as teams must manage more complex migration activities, custom development decisions, and broader testing requirements.

Ultimately, the right migration strategy should be determined by the organization’s transformation objectives. Companies seeking rapid modernization and process simplification often benefit from a Greenfield approach, while organizations with highly complex SAP landscapes may require a more controlled transition model to balance operational continuity with long-term modernization goals.

Internal vs. External Implementation Costs

Many organizations estimate SAP implementation budgets by focusing primarily on external consulting fees. However, the total investment required for an ERP transformation extends far beyond the implementation partner contract.

A successful SAP program requires significant internal involvement from finance teams, procurement specialists, manufacturing experts, IT departments, and business process owners. These resources participate in process design, data preparation, testing, training, and change management activities while continuing to support daily operations.

As a result, the true cost of implementation consists of two major components: external delivery costs and internal business transformation costs.

Internal vs. External Cost Distribution

Detailed Budget Breakdown

A successful SAP implementation depends not only on selecting the right technology partner but also on preparing the organization to support the transformation. Companies that allocate insufficient internal resources often experience slower decision-making, delayed testing cycles, and increased pressure on project timelines.

The most predictable SAP programs treat internal participation as a planned investment rather than an operational burden. Clear ownership, dedicated business resources, and early preparation of data and processes help reduce implementation risk and improve the long-term return on the ERP investment.

Primary Factors That Drive SAP Implementation Pricing

An implementation budget is heavily influenced by three core operational vectors:

• Scope and Business Processes: The total number of sites, configured SAP modules, and variations in business workflows.
• Technical Deployment Model: Choosing between Public Cloud, Private Cloud, and the volume of legacy custom ABAP code to remediate.
• Data and Integrations: The baseline cleanliness of legacy data, requirement for multi-currency ledgers, and the volume of third-party APIs (MES, CRM, WMS).

1. Business Scale and Organizational Complexity

2. SAP Product Ecosystem and Solution Scope

The SAP product landscape extends far beyond the core ERP platform. While SAP S/4HANA provides the central digital foundation for finance, procurement, manufacturing, and operations, many enterprises expand their architecture with specialized cloud solutions to address specific business capabilities.

Each additional SAP product increases the overall implementation scope through new data models, integration requirements, security configurations, testing cycles, and user adoption activities. As a result, the final implementation budget is influenced not only by the number of SAP solutions selected, but also by how deeply they are connected to core business processes.

Enterprise SAP Product Scope Impact

Adding specialized SAP solutions can significantly increase business value, but each component introduces additional implementation dependencies. For example, SAP IBP requires accurate planning data and mature supply chain processes, while SAP Ariba depends on supplier readiness and external network adoption.

The most successful SAP programs therefore define the target solution landscape early and prioritize capabilities based on measurable business outcomes rather than adding applications without a clear operational purpose.

3. Data Migration, Cleansing and Governance

Data migration is consistently ranked by enterprise project leaders as one of the most underestimated cost drivers in ERP transformations. The challenge is not only transferring data into SAP S/4HANA, but ensuring that the new digital core starts with accurate, standardized, and business-ready information.

The migration process typically follows three controlled execution phases:

1. Legacy Extraction: Extracting legacy master and transactional data, profiling source-system quality issues, identifying duplicates, and defining the migration scope.
2. Cleansing and Conversion: Removing obsolete Redundant, Obsolete, and Trivial (ROT) data, standardizing master records, converting legacy structures, and preparing information for SAP S/4HANA-compatible formats.
3. Target Loading and Validation: Loading approved datasets through SAP Migration Cockpit or automated migration tools, executing transformation rules, and completing reconciliation checks before production cutover.

Key cost and complexity drivers include:

• Master Data Cleansing: Decades of ERP operation typically create duplicate vendor records, outdated materials, inconsistent descriptions, incorrect units of measure, and inaccurate Bills of Materials (BOMs). Cleaning and validating this information requires dedicated involvement from business teams before technical migration cycles begin.

• Data Model Transformation: SAP S/4HANA introduces structural changes such as the unified SAP Business Partner (BP) model, replacing separate customer and vendor master records. Converting legacy data requires detailed mapping, validation rules, and business approval.

• Data Governance and Ownership: Successful migration requires clear ownership of critical master data domains. Organizations must define responsible data owners, establish validation rules, and implement governance processes to prevent data quality issues from reappearing after go-live.

• Historical Transaction Migration: Migrating open purchase orders, open sales orders, inventory balances, and unreconciled financial transactions requires multiple mock migration cycles. Each iteration improves transformation logic, loading performance, and financial reconciliation accuracy before final production deployment.

Poor data preparation creates additional project costs through failed migration runs, extended testing cycles, and operational disruption after go-live. Investing in data cleansing and governance early reduces migration risk and creates a stronger foundation for long-term SAP S/4HANA performance.

4. Third-Party System Integrations

Enterprise ERP platforms rarely operate as standalone systems. Modern organizations depend on a connected technology ecosystem that links SAP S/4HANA with manufacturing platforms, logistics networks, customer systems, financial institutions, and regulatory services.

Integration complexity is one of the major SAP implementation cost drivers because each external connection requires architecture design, interface development, security configuration, testing, monitoring, and long-term support.

Key integration areas include:

• Shop-Floor MES and Automation: Connecting manufacturing execution software, SCADA systems, and conveyor lines.
• Logistics and Warehouse Management: Interfacing with third-party logistics (3PL) providers, carrier portals, and automated WMS hardware.
• Front-Office and E-Commerce: Interfacing with Salesforce, Shopify, or custom B2B web portals.
• Financial and Regulatory Gateways: Connecting corporate banking platforms, payroll engines, and tax authority portals.

A modern SAP architecture typically uses SAP BTP Integration Suite with standard REST and OData APIs rather than fragile point-to-point connections. While this approach increases initial architecture and development effort, it improves scalability, simplifies future upgrades, and supports a cleaner long-term operating model.

The biggest cost impact usually comes not from the number of integrations alone, but from the complexity of legacy interfaces, poor documentation, custom middleware dependencies, and the level of real-time data exchange required.

5. Customization vs. Clean Core Extensibility

Hidden Costs Companies Often Forget

UK-Specific Cost Considerations

Implementation Cost vs. Business ROI

While controlling implementation costs remains a key executive priority, leading organizations evaluate SAP investments based on the long-term business value generated after go-live.

The highest returns typically come from using SAP S/4HANA as an integrated digital core - connecting finance, procurement, supply chain, and manufacturing processes rather than simply replacing legacy software. A well-designed transformation can reduce operational friction, improve decision-making speed, and create measurable financial benefits.

Financial and Operational Value Realization

SAP implementation value is not created by the ERP platform alone. The strongest ROI comes from simplifying processes, improving data quality, and connecting business functions into a single operating model. Organizations that treat SAP transformation as a business redesign initiative typically achieve significantly higher returns than those approaching it as a technical system replacement.

Real-World Implementation Case Study: UK Industrial Manufacturer

The Business Profile

A UK mid-market industrial manufacturer operating two production facilities in the Midlands faced increasing operational pressure from fragmented legacy systems. The company relied on a heavily customized ERP platform, spreadsheet-based production planning, and manual reconciliation processes across procurement, inventory, and finance.

As customer demand increased and supply chain complexity grew, management identified several operational challenges:

• Limited visibility of inventory availability across production sites;
• Slow material planning cycles and manual supplier coordination;
• Delayed financial reporting due to reconciliation activities;
• High dependency on spreadsheets and legacy custom workflows;
• Increasing maintenance effort for outdated ERP customizations.

The leadership team required a modern ERP foundation that could improve operational control while avoiding the cost and complexity of another heavily customized platform.

Strategic Implementation Approach

Instead of performing a technical conversion of the existing legacy ERP landscape, the company selected a Greenfield SAP S/4HANA Cloud Public Edition implementation focused on process standardization and Clean Core principles.

The transformation followed the SAP Activate methodology, using SAP Best Practices as the baseline and limiting custom development to genuinely differentiated business requirements.

Implementation Scope:

• SAP S/4HANA Finance and Controlling;
• Procurement and supplier management;
• Inventory management;
• Production planning;
• MES shop-floor integration;
• Warehouse mobility enhancements.

Delivery Approach:

The project adopted a strict Fit-to-Standard model. Business teams validated SAP standard processes during Explore workshops, while exceptions were reviewed through governance processes rather than automatically converted into custom developments.

Clean Core Strategy:

The organization avoided in-core ABAP modifications. Where additional functionality was required, two custom mobile warehouse applications were developed side-by-side on SAP Business Technology Platform (SAP BTP).

Measured Budget and Operational Outcomes

The implementation created a standardized digital core that improved operational visibility while reducing long-term ERP complexity. By adopting SAP standard processes and extending only where necessary, the manufacturer achieved faster deployment, lower technical debt, and a scalable foundation for future automation.

For mid-market UK manufacturers, SAP S/4HANA Cloud Public Edition can deliver enterprise-grade ERP capabilities without reproducing the complexity of legacy environments. The strongest results come from combining Fit-to-Standard execution, Clean Core architecture, and disciplined change management rather than attempting to replicate every historical customization.

Implementation Pricing Models: Fixed Price vs. T&M vs. Hybrid

Selecting the right commercial engagement model is a strategic decision that directly affects budget predictability, project flexibility, and delivery risk. The optimal approach depends on implementation complexity, scope maturity, and the level of uncertainty involved.

For standardized SAP S/4HANA Cloud projects with clearly defined requirements, a fixed-price model can provide strong cost control. However, large enterprise transformations involving data migration, integrations, and process redesign often require a more flexible approach to manage evolving requirements.

Partner Commercial Engagement Models

For most SAP S/4HANA programs, a hybrid commercial model provides the strongest balance between cost control and implementation flexibility. Fixed-price contracts work well when organizations commit to standard processes early, while capped T&M allows teams to address unavoidable complexity in areas such as integrations, data migration, and business change management without creating uncontrolled budget exposure.

How to Reduce SAP Implementation Costs Without Increasing Risk

Keeping an SAP implementation on budget is less about reducing project scope and more about making the right architectural and delivery decisions from the outset. Organizations that standardize processes, limit unnecessary customization, and establish strong governance consistently achieve lower implementation costs while reducing delivery risk.

Cost Optimization Principles

Adopt a Fit-to-Standard Mindset

Use SAP Best Practices as the baseline for business processes instead of replicating legacy workflows. Custom development should only be approved when it supports a genuine competitive advantage rather than user preference.

Protect the Clean Core

Avoid modifying the SAP S/4HANA core whenever possible. Extensions, mobile applications, dashboards, and specialized workflows should be developed on SAP Business Technology Platform (SAP BTP), preserving upgradeability and reducing long-term technical debt.

Prepare Data Before Implementation Starts

Master data quality directly influences migration effort, testing, and user adoption. Profiling and cleansing vendor, customer, material, and financial master data before the implementation begins significantly reduces project delays later.

Roll Out in Phases

Rather than deploying every module simultaneously, establish a stable digital core first. Finance and Procurement are commonly implemented in the initial phase, followed by Manufacturing, Supply Chain, or Human Capital Management as the organization stabilizes.

Reuse SAP Best Practices and SAP Activate

Leverage SAP Activate methodology, preconfigured business processes, and implementation accelerators instead of designing processes from scratch. This reduces workshop time, configuration effort, and project duration.

Automate Testing

Regression testing, integration testing, and User Acceptance Testing (UAT) often consume hundreds of consultant and business-user hours. Automation tools such as SAP Cloud ALM or Tricentis for SAP help reduce manual effort while improving test coverage.

Engage an Experienced SAP Implementation Partner

An experienced implementation partner brings proven methodologies, industry accelerators, and practical experience that help identify project risks early and avoid costly redesign during later project phases.

Use a Blended Delivery Model

Many organizations balance quality and cost by combining UK-based solution architects, project managers, and business consultants with nearshore technical specialists. This approach provides strong business governance while optimizing overall consulting expenditure.

Common ERP Budgeting Mistakes

SAP implementation budgets often fail not because of unexpected software costs, but because organizations underestimate complexity, internal effort, and long-term adoption requirements. The following mistakes are among the most common causes of SAP project overruns.

Selecting an Implementation Partner Based on Price Alone

Questions to Ask Before Requesting an SAP Implementation Quote

Before requesting a formal proposal or Statement of Work (SOW) from an SAP implementation partner, executive teams should define the key scope, technical, and operational assumptions that directly influence implementation cost and delivery timelines.

SAP Software Scope

Which SAP products and capabilities are included in the transformation scope?

Define whether the project includes SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Private Edition, SAP SuccessFactors, SAP Ariba, SAP IBP, SAP CX, or SAP BTP extensions.

A clearly defined software footprint helps partners estimate configuration effort, integration requirements, and licensing implications accurately.

Deployment and Architecture Strategy

Which deployment model best fits the organization’s operating model?

Determine whether Public Cloud, Private Cloud, or a hybrid architecture aligns with business requirements, regulatory obligations, customization needs, and long-term IT strategy.

The chosen deployment model directly affects implementation approach, migration complexity, and future operating costs.

User Volume and Role Requirements

How many users and business roles will require SAP access?

Define professional users, operational users, warehouse or shop-floor users, self-service users, and approval roles.

User volumes influence licensing, security design, SAP Fiori role configuration, training requirements, and testing scope.

Organizational Structure and Global Scope

What organizational entities must be included in the implementation?

Document the number of legal entities, company codes, plants, warehouses, countries, currencies, and reporting structures.

Complex organizational models increase configuration effort, financial design complexity, and testing requirements.

Third-Party Integration Landscape

Which external systems must connect to SAP?

Identify all required integrations, including MES, WMS, CRM, e-commerce platforms, banking systems, supplier networks, payroll systems, and regulatory platforms.

A complete integration inventory prevents unexpected development effort and middleware costs later in the project.

Data Quality and Migration Readiness

What is the current condition of legacy data?

Assess the quality of customer, vendor, material, asset, and financial master data before implementation begins.

Poor data quality is one of the most common causes of migration delays and additional project costs.

Industry and Regulatory Requirements

Which compliance requirements must SAP support?

Identify country-specific and industry-specific requirements, such as HMRC Making Tax Digital (MTD), UK GDPR, Brexit-related trade processes, environmental reporting, or sector-specific regulations.

These requirements influence localization, security design, and business process configuration.

Implementation Timeline and Business Deadlines

What business milestones determine the go-live date?

Define whether the project must align with financial year-end, manufacturing shutdown periods, contract expirations, or legacy system decommissioning plans.

Fixed deadlines often require additional resources, phased deployment strategies, or accelerated delivery approaches.

Post-Go-Live Support Model

What level of stabilization and ongoing support is required after launch?

Define expectations for hypercare support, user assistance, issue resolution, and SAP Application Management Services (AMS).

Planning post-go-live support early helps avoid operational disruption after deployment.

A high-quality SAP implementation quote depends on the quality of information provided before the proposal stage. Organizations that clearly define scope, data readiness, integration requirements, and operating model decisions receive more accurate estimates and significantly reduce the risk of budget overruns.

How LeverX Estimates SAP Projects

At LeverX, SAP project estimation is treated as an engineering discipline rather than a commercial exercise. As an SAP Gold Partner and Global System Integrator with more than 20 years of SAP implementation experience, LeverX develops project estimates based on business process analysis, technical architecture assessment, data readiness evaluation, and delivery complexity.

The objective is to provide realistic implementation forecasts that minimize budget uncertainty, identify risks early, and create a clear path from initial assessment to successful SAP delivery.

The 4-Step SAP Estimation Process

1. Discovery and Readiness Assessment

The estimation process begins with a detailed evaluation of the current business and technical landscape. LeverX conducts Fit-to-Standard workshops and readiness assessments to understand existing processes, identify improvement opportunities, and evaluate migration complexity.

Key assessment areas include:

• Current ERP landscape and business process maturity;
• Legacy data quality and migration requirements;
• Cloud readiness and deployment considerations;
• Existing customizations and technical debt.

2. Scope Definition and Solution Architecture

After understanding the business environment, LeverX defines the target SAP solution scope and technical architecture.

This includes:

• Mapping business processes against SAP Best Practices;
• Identifying required SAP modules and capabilities;
• Defining integration requirements with third-party systems;
• Establishing Clean Core boundaries and SAP BTP extension scenarios.

This step ensures that customization decisions, integration effort, and technical complexity are identified before implementation begins.

3. Implementation Roadmap and Delivery Planning

LeverX creates a realistic implementation roadmap based on the selected deployment strategy, business priorities, and organizational readiness.

The roadmap defines:

• Implementation phases and milestones;
• SAP Activate delivery approach;
• Migration and testing cycles;
• Resource requirements and project governance structure.

Depending on project complexity, the delivery model may include accelerated SAP S/4HANA Cloud Public Edition implementation approaches or structured migration programs for Private Edition environments.

4. Transparent Commercial Proposal

The final estimation phase converts the delivery approach into a structured commercial proposal.

LeverX provides:

• Detailed cost breakdown by implementation workstream;
• Fixed-price, capped T&M, or hybrid commercial models;
• Clear milestone-based delivery structure;
• Defined RACI responsibilities between customer and implementation teams.

This approach gives executive stakeholders clear visibility into investment requirements, delivery assumptions, and project risks before implementation begins.

Accurate SAP estimation depends on understanding business complexity before committing to a budget. By combining process analysis, technical architecture design, data assessment, and transparent commercial planning, organizations can reduce implementation uncertainty and make better-informed transformation decisions.

Conclusion

Determining SAP implementation cost is not about finding a fixed price list - it is about understanding and managing the complexity behind the transformation. Software subscriptions provide only the foundation of the investment. The majority of project effort is driven by business process scope, deployment strategy, data readiness, integration requirements, customization decisions, and organizational adoption.

Organizations that achieve the best SAP outcomes typically focus on reducing unnecessary complexity rather than cutting implementation quality. A Fit-to-Standard approach, Clean Core architecture, early data governance, disciplined scope management, and strong implementation governance create a more predictable delivery path and lower total cost of ownership.

By selecting the right deployment model, preparing the organization before implementation begins, and partnering with an experienced SAP implementation provider, executive teams can improve budget predictability, reduce delivery risks, and maximize long-term business value from their SAP investment.

Request a Tailored SAP Budget Estimate

Remove uncertainty from your SAP investment planning with a transparent, data-backed implementation estimate from LeverX. Our SAP solution architects help UK mid-market and enterprise organizations assess scope, cloud readiness, and implementation requirements to build a realistic project roadmap.

Get Your SAP Estimate

Frequently Asked Questions

How much does an SAP implementation cost?

SAP implementation costs typically fall into three main budget ranges depending on project complexity:

• Tier 1: Standardized Mid-Market Implementation - £100,000–£500,000

  
  Suitable for single-entity organizations adopting SAP S/4HANA Cloud Public Edition with standard SAP Best Practices, limited integrations, and minimal customization.

• Tier 2: Multi-Site Enterprise Implementation - £500,000–£2 million
  
  

  Typical for organizations with multiple locations, broader SAP scope (Finance, Procurement, Manufacturing, Supply Chain), third-party integrations, and additional configuration requirements.

• Tier 3: Complex Enterprise Transformation - £2 million–£10 million+
  
  

  Applies to global organizations migrating from SAP ECC or other legacy ERP platforms, requiring multiple entities, extensive data migration, complex integrations, SAP BTP extensions, and phased rollouts.

The final SAP implementation cost depends on business process complexity, deployment model, data quality, integration requirements, customization level, and organizational change needs.

What drives the overall cost of an SAP implementation project?

Is SAP S/4HANA Cloud Public Edition cheaper to implement than Private Edition?

Yes. Public Edition utilizes pre-configured SAP Best Practices and standard workflows out of the box, drastically reducing initial blueprinting, custom coding, and implementation consulting days. It also lowers long-term TCO by including infrastructure management and semi-annual cloud updates in the standard SaaS subscription.

What is the typical ratio between software licensing and implementation consulting costs?

For most SAP implementations, software licenses or cloud subscriptions represent approximately 20%–30% of the total five-year investment.

The remaining 70%–80% is typically related to implementation services, system integrations, data migration, testing, training, change management, and internal business resources.

The exact split depends on project complexity, but implementation effort usually represents the largest share of the overall SAP investment.

How long does a typical SAP S/4HANA implementation take?

Does an SAP implementation estimate include user training and change management?

A complete SAP implementation estimate should include user training and change management activities. These workstreams are essential for successful adoption and should be clearly defined in the implementation partner’s Statement of Work (SOW).

Some lower-cost proposals may exclude training, communication, or adoption support to reduce the initial project price. Before signing, confirm that role-based training, user enablement, and change management activities are included in the project scope and budget.

How can organizations prevent budget overruns during implementation?

What UK compliance requirements must be factored into implementation budgets?

What happens after go-live, and how is post-implementation support budgeted?