A growing cloud account can look like a straightforward success. Customer usage increases, the relationship expands and the revenue report moves in the right direction. Yet the team may also be spending more time on support, optimisation and requests that were never clearly priced.
For cloud and hosting providers, the commercial question is whether the revenue, service promise and cost of delivery are developing together. Understanding that relationship helps you support the customer without leaving your people to absorb an open-ended commitment.
Separate the revenue streams before judging growth
A cloud relationship can include a migration project, recurring management fees, platform consumption, licences and additional professional services. Combining them into one account total can make it difficult to see what is changing.
Review each stream against the costs that relate to it. Consider whether increased consumption creates a meaningful contribution for your business, and whether the managed service fee still reflects the estate and responsibilities being supported.
Agree the definitions with finance. Sales and delivery need a consistent view of the account, particularly where reported revenue includes substantial third-party charges.
Make the transition into service explicit
A migration win creates work before it creates a settled operating rhythm. Discovery, planning, testing, documentation and customer coordination all require capacity. If assumptions remain unresolved, the transition can become more demanding than either side expected.
Before signing, establish the starting position, the customer's responsibilities, the acceptance criteria and what happens when something outside the agreed scope is discovered. Involve the people who will deliver the transition in assessing the plan.
The objective is to give the customer a credible route into service and the team a commitment it can fulfil. Uncomfortable questions are easier to resolve before they become a delivery problem.
Define what the recurring fee actually includes
Terms such as optimisation, management and support can carry different meanings for different people. Explain the activities included, the coverage provided and how substantial changes will be handled.
- Does the fee cover the current environment or a defined range of usage and complexity?
- Who owns cost reviews, technical recommendations and approval of changes?
- What support is included outside normal working hours?
- When does additional engineering become separately scoped work?
- How will both sides review the service when the customer's requirements change?
Clear boundaries help customers plan. They also reduce the risk that helpful individual decisions create a service neither side consciously agreed to.
Understand vendor and commitment dependencies
Where pricing depends on a cloud vendor, distributor or partner programme, identify the assumptions behind your proposal. Consider licence terms, customer commitments, discounts and how a change would affect your own commercial position.
Do not build the account plan around an incentive or purchasing commitment the business has not confirmed. Where you are making commitments on a customer's behalf, ensure the relevant people understand the implications and have agreed the arrangement.
Use account reviews to connect value and economics
A useful review brings the account owner, delivery lead and finance perspective together. Look at the customer's priorities, the work being performed, unresolved service issues and the contribution from each revenue stream.
If the economics have weakened, establish the cause before proposing a price change. The answer might involve better documentation, a scope adjustment, a different support arrangement or a candid discussion about requirements that have grown.
Start with three accounts where revenue has increased. Ask whether service effort and contribution have moved in the same direction. That conversation gives you a more useful foundation for growth than celebrating consumption alone.