Ok .... You've run an Assessment and, following proof of concept best practices, taken the output to plan a Proof of Concept (POC) and production migration. You've built the POC and are planning to scale it up and out to support the migration to production and the Transformation of the enterprise, including sap hana cloud migration scenarios where appropriate.
Summary
This piece urges leaders to focus on business outcomes over technology hype while scaling from POC to full production, particularly in cloud and SAP HANA migration contexts. It emphasizes choosing partners based on proven expertise, credibility, and commitment, validated through assessments and POCs, and warns against both overpaying and underbidding. A balanced sourcing model—using large integrators for planning/PMO and firms like Genesis10 for hands-on delivery—can control costs without sacrificing quality. The guidance culminates in the APT (Assess, Prove, Transform) methodology as a pragmatic roadmap for successful transformation.
Let's pause a moment and remember why we are here. With all this fantastic technology coming online, AI, IOT, Cloud, Advanced Analytics, it is tempting to become evangelists for this convergence of the latest technologies. Nothing wrong with that BUT, we are not here to sell shiny toys!
Whether we are the CIO or whether we are vendors to the IT organization, we are here to produce business outcomes.
Expertise, credibility, commitment
There's a tremendous amount of hype around HANA cloud migrations (including sap hana cloud migration). There is a lot of money, hundreds of billions of dollars in fact, that is going to be spent over the next 5-10 years on cloud migrations and thousands of consulting companies are looking to get a piece of that. Let's be frank, there is a frantic effort in these companies to differentiate themselves to try to win this business, and often there is not much differentiation to be had.
Yes, there are tools that help migration, yes, there are methodologies—having a clear sap migration methodology helps—yes there is this and there is that and no shortage of promises that this time it will be different if you only select MY company.
True differentiation is not just a shiny new product, it's also expertise, credibility, commitment, communication, integrity and a history of successful results .... these things have been important since the beginning of time and will never stop being important.
Look for a company that gives you confidence and has the experience to deliver the expertise, and that you can count on as a true partner. If you have gone through a successful Assessment, and a successful POC, then you already have a candidate company for your Transformation. Especially having done a POC, you've had the opportunity to work closely with that vendor and you should be aware of their capabilities for the final stage.
A name brand has its place, but don't be seduced by brand-name companies with sky high costs.
Do your due diligence, learn what you can, compare the proposals, get second opinions, and make sure you are getting the right people while aligning with cloud migration best practices.
Rewards of transformation waiting
A lot of this may seem obvious, yet how often is the obvious ignored with a headlong rush into projects that end up in disaster? There are reasons that these basic, common-sense suggestions are obvious.
Leading your team and your company through this requires confidence, vision and no small amount of courage.
Stand your ground, don't overpay and don't lowball.
- If you pay too much, you will deplete your budget and the relationship with your vendor will be tense as you try to get more work before your budget crashes and fingers start to point.
- If you pay too little by beating down the price in a competitive bidding war, then the quality of the end result will suffer, your risk factors will escalate, and you might join the list of companies with expensive, failed implementations. It's only cheaper if you do it one time, and do it well.
Many companies want a large branded company to be their systems integrator for many reasons. While theoretically they have the resources to deliver the project, these large integrators often come to Genesis10 and companies like us to actually staff the project. The resources are likely to be presented as employees of the Big Brand, with the corresponding high prices.
If you must use a branded integrator, a better model is to use them for planning, management, and/or PMO support and use a company like Genesis10 for the analysts, architects, developers, testers and others to do the hands-on work. There are significant savings to be realized with this approach.
There is a middle path through all this and the rewards of a successful Transformation are waiting.
And once you've selected your vendors, consider the Genesis10 SAP methodology we call APT ..... Assess, Prove and Transform.
Q&A
Question: What is the core message when moving from POC to production?
Answer: Prioritize business outcomes over technology hype. While AI, IoT, Cloud, and Advanced Analytics are exciting, the goal isn’t to showcase “shiny toys” but to deliver measurable results for the business. As you scale from a successful assessment and POC to production—especially in cloud and SAP HANA contexts—align decisions to outcomes, not trends.
Question: How should we choose partners for cloud and SAP HANA migrations?
Answer: Select partners based on proven expertise, credibility, commitment, communication, integrity, and a record of successful results—not just tools or branding. Validate these attributes through your assessment and POC work; if a vendor performed well there, they’re a strong candidate for transformation. Conduct due diligence, compare proposals, seek second opinions, and ensure you’re getting the right people while following cloud migration best practices.
Question: Why not default to a big-brand systems integrator for everything?
Answer: Big brands can be valuable, but they often come with high costs and may still rely on firms like Genesis10 to staff the hands-on work. A balanced model can control costs without sacrificing quality: use the large integrator for planning, management, and PMO oversight, and a firm like Genesis10 for analysts, architects, developers, testers, and other delivery roles.
Question: What’s the danger in overpaying or underbidding on a transformation project?
Answer: Overpaying drains budgets and strains vendor relationships as you try to stretch scope. Underbidding raises risk and degrades quality, increasing the chance of costly failures. It’s only cheaper if you do it once and do it well—avoid both extremes to protect outcomes and budgets.
Question: What is the APT methodology and why does it matter?
Answer: APT stands for Assess, Prove, and Transform. First, Assess to understand needs and constraints; then Prove through a POC that validates approach, partners, and technology; finally, Transform by scaling to production based on what you learned. This pragmatic sequence reduces risk, strengthens vendor selection, and keeps the initiative anchored to business results.
