The MLI Strategic AEM Implementation deck is not a startup pitch for venture capital, but a B2B services proposal from Cognizant to Max Life Insurance (MLI). Dated January 2016, the 22-slide presentation outlines a massive digital re-engineering project. The deck is notable for its extreme granularity regarding scope, assumptions, and a sophisticated 'Risk-Reward' pricing model. It avoids typical startup tropes like 'market size' or 'competitor grids,' focusing instead on execution risk mitigation and measurable business outcomes. For founders, this deck serves as a blueprint for structuring…
Key takeaways
- The project involves consolidating three websites (Corporate, Mobile, and eCommerce) into a single responsive platform using Adobe AEM 6.1 (Slide 4).
- Cognizant proposes a performance-linked pricing model where a 'Risk-Reward' component can fluctuate based on KPI achievement (Slide 13).
- KPIs are weighted across four categories: Awareness (20%), Engagement (30%), Revenue (30%), and Other Opportunities (20%) (Slide 14).
- The deployment plan spans 8 months of active development followed by 6 months of support and warranty (Slide 10).
- Scope is strictly defined, explicitly excluding hardware sizing, environment setup, and third-party application integration like LDAP (Slide 5).
- The deck includes a rare 'Failure Points' slide, identifying risks like inadequate executive buy-in and divergent stakeholder expectations (Slide 19).
- Illustrative pricing options show a fixed price of 4 Cr (40 million INR) versus a milestone-based fee of 3 Cr with a 1.25 Cr risk-reward upside (Slide 13).
- The implementation requires manual content refinement and validation for approximately 350-400 pages (Slide 4 and Slide 8).
Introduction: The Enterprise Services Pitch
The MLI Strategic AEM Implementation deck, dated January 2016, is a 22-slide strategic proposal from Cognizant to Max Life Insurance. Unlike a venture capital pitch, this document is focused entirely on the mechanics of a massive digital transformation project. It aims to sell a specific solution—re-engineering digital assets onto the Adobe Experience Manager (AEM) platform—rather than a company vision. For founders building B2B SaaS or service businesses, this deck provides a masterclass in how to structure complex, high-value enterprise contracts.
Slides 1-3: Title and Table of Contents
The deck opens with a co-branded title slide featuring the Cognizant and Max Life Insurance logos. The title, "Online Digital Asset Re-engineering and AEM Implementation Strategic Pitch," immediately defines the technical and strategic nature of the document. Slide 2 provides a table of contents split into two main pillars: Engagement Details (Scope, Assumptions, Discovery, Deployment) and Commercials (KPIs, Pricing, Value Optimization). This structure signals a move from the 'what' and 'how' to the 'how much' and 'what if.'
Slides 4-5: Defining the Boundaries of Work
Slide 4, "In Scope," is extremely dense, listing functional and activity scopes. Key deliverables include a responsive web design (RWD) website for desktop, smartphone, and tablet, and the consolidation of three websites (Corporate, Mobile, and eCommerce). It specifies the migration of approximately 350 pages and integration with CRM and social sites. Slide 5, "Out of Scope," is arguably more important for an enterprise vendor. It explicitly excludes environment setup (DEV/QA/UAT/PROD), user training, and hardware sizing. By defining what they won't do, Cognizant protects its margins and prevents future disputes over unstated expectations.
Slides 6-8: The Foundation of Assumptions
Slides 7 and 8 list "Key Assumptions." These are the conditions under which the project's timeline and budget remain valid. Notable assumptions include: the implementation is for the English language only; brand guidelines and stock images will be provided by the client; and the design supports only portrait orientation for mobile. Slide 8 goes deeper into technical assumptions, such as the reuse of existing product models and the limitation of testing to one complete cycle. These slides serve as a legal and operational safeguard, ensuring that if the client changes the requirements (e.g., adding a second language), the price and timeline can be renegotiated.
Slides 9-11: The Deployment Timeline
Slides 10 and 11 present two options for the Deployment Plan . Both options show an 8-month development cycle followed by a 6-month support period. The Gantt charts are detailed, breaking down activities into UX Interface, Visual Design, Content Creation, Web Development, and Analytics. The charts also highlight "Critical Dependencies" like environment availability and content freeze. This visualizes the complexity of the project and emphasizes that the vendor's success is dependent on the client meeting their own deadlines.
Slides 12-15: KPI-Based Pricing and Risk-Reward
This section is the core of the "Strategic Pitch." Slide 13 introduces "KPI Based Pricing." It offers two options: a standard Fixed Price of 4 Cr (40 million INR) or a Milestone-based fee of 3 Cr with a 1.25 Cr "Risk Reward" component. Slide 14 breaks down the Value Drivers for this reward: Awareness (SEO Rank), Engagement (Page views, bounce rate), Revenue (eCommerce traffic, cross-sell), and Other Opportunities (Call center load reduction). Slide 15 explains the tiered scoring mechanism , showing how a total realization of 83.8% across these KPIs would result in a specific payout. This model aligns Cognizant's financial incentives directly with Max Life's business goals, a powerful selling point for a high-cost consultancy.
Slides 16-18: Implementation and Governance
Slide 16 outlines the "Implementation of KPI Based Approach," a four-stage process: Readiness Assessment, Select and Structure, Organize, and Implement. It covers the 'What' (KPIs), 'How & Who' (Process & Governance), and 'Systems' (Solutions). Slide 17 is a placeholder for pricing formats, while Slide 18 lists "KPI Based Pricing Assumptions," including the requirement for a Value Optimization team to monitor results for 6 months post-release. It also includes a fallback clause: if a mutual KPI model cannot be reached, the project reverts to a fixed-price model.
Slides 19-22: Risk Mitigation and Value Optimization
Slide 19, "Failure Points," is a standout slide. It lists six common reasons projects fail, such as "Feature focused instead of outcome focused mindset," and provides a specific mitigation plan for each. This demonstrates maturity and experience. Slide 21 details the "Activities and Deliverables of Value Optimization Team," breaking roles down by Digital & Domain Advisors, UX, Content, AEM, and Analytics. This ensures the project doesn't just 'go live' but actually achieves its intended business impact. The deck concludes with a standard "Thank You" slide.
What MLI Strategic AEM Implementation Does Well
Outcome Alignment: By proposing a risk-reward model based on business KPIs like SEO rank and call center load, Cognizant moves from being a 'body shop' to a strategic partner. · Scope Rigor: The explicit listing of 'Out of Scope' items is a best practice for any service provider to avoid project failure and margin erosion. · Risk Transparency: The 'Failure Points' slide builds immense credibility by acknowledging the difficulties of enterprise digital transformation and offering proactive solutions. · Structured Assumptions: The detailed assumptions slides (7-8) provide a clear framework for what the client must provide, shifting some responsibility for project success back to Max Life.
What is Missing from the Deck
Team Bios: While this is a pitch from a known entity (Cognizant), the specific leads and architects who would be on the ground are not profiled. · Case Studies: The deck mentions "Experience with Similar Engagements" on Slide 19 but does not provide specific examples or testimonials of previous AEM implementations. · Detailed Technical Architecture: While AEM 6.1 is mentioned, a high-level diagram of the proposed system architecture (how AEM interacts with the CRM and backend) is absent. · Unit Economics of Support: The 6-month support period is mentioned, but the ongoing costs beyond that period are not defined.
Lessons for Founders
Sell Outcomes, Not Hours: If you are a service or enterprise software founder, try to link a portion of your pricing to the client's success metrics. It makes a high price tag much easier to swallow. · Use 'Out of Scope' to Protect Your Team: Never assume the client knows what isn't included. Writing it down on a slide prevents 'feature creep' and keeps your developers focused. · Address Failure Head-On: Don't pretend your implementation will be perfect. By identifying risks early, you show the client you are a seasoned professional who has seen (and solved) these problems before. · Define Dependencies Early: Use your timeline slides to show the client exactly what they need to provide (content, API access, environment) for you to succeed. This protects you if the project is delayed by their internal bureaucracy.
Frequently asked questions
- Is this a startup fundraising deck?
- No. This is a strategic service proposal from Cognizant, a global IT services firm, to Max Life Insurance. It is designed to secure a specific contract for digital transformation and AEM implementation rather than to raise equity capital from venture investors. It lacks traditional startup slides like 'The Team' or 'Market Opportunity' because the parties already have an established relationship.
- What is the 'Risk-Reward' pricing model mentioned in the deck?
- Cognizant proposes a model where a portion of their fee is at risk based on performance. On Slide 13, they show an option where the base fee is lower (3 Cr), but they can earn a bonus (1.25 Cr) if they hit specific KPIs. If they achieve less than 50% of the KPI targets, the total payout drops to 3.5 Cr, effectively penalizing the vendor for underperformance.
- How does the deck handle project scope?
- The deck uses a highly disciplined approach to scope management. Slide 4 lists 'In Scope' items like UI wireframes and CRM integration, while Slide 5 lists 'Out of Scope' items like user training and hardware sizing. This level of detail is critical in enterprise services to prevent 'scope creep' and ensure both parties agree on the boundaries of the engagement.
- What specific technologies are being implemented?
- The core technology is Adobe Experience Manager (AEM) version 6.1. The deck also mentions Adobe Analytics, Dynamic Tag Manager (DTM), HTML5/CSS3/jQuery for responsive design, and OSGI for coding templates and components. It also references integration with LifeEngage web services and existing MLI backend systems via REST over JSON.
- Why does the deck include a slide on failure points?
- Slide 19, 'Failure Points,' is a sophisticated sales tactic. By identifying why similar projects fail (e.g., feature-focused mindsets instead of outcome-focused), Cognizant positions itself as an experienced partner. It builds trust by showing they have a mitigation plan for common enterprise pitfalls, such as over-stretched subject matter experts (SMEs) and poor change management.