Partnerships and Deal Evaluation Questions

Requirements & goals:

• Preserve/expand revenue, minimize churn, retain key customers, consolidate tech stack within 12–18 months, and eliminate duplicate costs.
• Success metrics: % customers migrated, churn rate delta, data integrity rate, platform uptime, NPS change.

High-level approach:

1. Product mapping (0–4 weeks)

• Inventory features, APIs, data models, integrations, usage metrics, and customer segments from both products.
• Create a feature matrix: keep / merge / retire candidate + usage, revenue impact, regulatory risk, and technical cost.
• Identify “must-keep” differentiators and blockers (e.g., unique workflows or integrations).

2. Migration strategy & timelines

• Phase 0 (4–8 weeks): Discovery, opt-in pilot design, compliance review.
• Phase 1 (3 months): Parallel run for low-risk customers — maintain both systems; implement SSO and unified billing.
• Phase 2 (3–6 months): Merge core shared features into primary platform; offer migration tools for higher-value customers.
• Phase 3 (3–6 months): Migrate remaining customers, retire redundant product.

Migration approaches per feature:

• Merge: For core overlapping features—rebuild/adapter layer with data mapping.
• Parallel: Maintain both offerings for incompatible or strategic segments while developing parity.
• Retire: Underused or costly features—announce deprecation, provide migration alternatives or compensations.

3. Data migration risks & mitigation

• Risks: schema mismatch, data loss, inconsistent business rules, PII/regulatory compliance, transactional integrity.
• Mitigations:
  • Create canonical data model and mapping docs.
  • Build idempotent ETL with schema validation, automated diff checks, and row-level reconciliation.
  • Staged migrations (sandbox → subset → full) with rollback points.
  • End-to-end QA including reconciliation reports and user acceptance tests.
  • Maintain immutable backups and legal hold workflows.

4. Customer communication & success

• Segment customers by ARR, usage, and complexity; prioritize high-touch support for enterprise accounts.
• Communication cadence: Announcement (3 months out) → Technical webinars & migration playbooks (6–8 weeks) → Personalized migration plans and milestones → Cutover notification (2 weeks / 48 hours / final).
• Materials: migration checklist, sandbox export/import tools, migration timeline, known limitations, support SLA, and “what stays/what changes” matrix.
• Incentives: migration discounts, extended support, dedicated TAMs for strategic clients.
• Feedback loop: early adopter councils and in-app feedback to iterate.

5. Criteria for sunsetting features

• Usage < X% (e.g., <2% of active users) and low revenue attribution
• High maintenance cost / security risk
• No technical path to integrate without disproportionate investment
• Available acceptable alternatives or migration path
• Legal/regulatory requirement to remove
• Customer impact assessment and sunset timeline (minimum 90 days for minor features; 6–12 months for major ones with enterprise impact)

Trade-offs & governance

• Use cross-functional Integration Steering Committee (product, eng, CS, legal, sales) with fortnightly checkpoints.
• Balance speed vs risk: prefer gradual, reversible migrations for critical customers; accelerate retirements for low-use features.
• KPIs reviewed weekly: migration success rate, data reconciliation % errors, customer sentiment, ARR retention.

This plan ensures data integrity, minimizes churn, communicates clearly, and balances business value with engineering cost.

I’d approach this as a structured commercial + product negotiation: prepare levers (what we’ll offer/ask for), the metrics that prove value, and the legal/operational clauses we’ll expect to negotiate.

Levers I’d prepare

• Data-driven adoption case: historic install velocity after marketing pushes, organic uplift from placements, cohort retention curves, and ARPU/LTV — to quantify the revenue opportunity for Apple.
• Retention & engagement: 1/7/30-day retention, DAU/MAU, session length, feature-usage funnels that show users keep paying (lower churn reduces Apple’s risk).
• Technical feasibility & ops: build size, install footprint, OTA/update strategy, first-run UX, single sign-on/Apple ID integration, telemetry endpoints, testing plan, and rollback strategy to show low integration cost/risk.
• Exclusivity & placement: graded options (exclusive preinstall vs. featured placement vs. default app tile) and term lengths — each tier tied to different rev-share/marketing commitments.
• Marketing commitment: co-marketing calendar, placement on setup flows, App Store banners, bundled promo codes, measurement plan and budget (paid UA credits or guaranteed impressions).

Key metrics to prove our case

• Revenue metrics: ARPU, average subscription price, LTV (90/180/365d), conversion rate free->paid, CAC and payback period.
• Retention & churn: Cohort retention at D1/D7/D30/D90, monthly churn %, and net revenue retention.
• Engagement: DAU/MAU, sessions per user/day, key feature usage rates.
• Growth/impact: historical lift from prior OEM/carrier partnerships (e.g., “placement X produced +40% installs and +25% paid conversion”), projected incremental revenue per device and breakeven timeline for Apple given proposed rev-share.
• Measurement fidelity: ability to attribute installs to the preinstall + experiment results (A/B) and third-party auditability.

Legal / operational clauses to expect and negotiate

• Revenue share & payment terms: percent, gross vs. net revenue definition, reporting cadence, currency, reconciliation, audit rights.
• Trial terms & promos: free trial length, how trials convert to paid, who pays for trial, and how promotional pricing interacts with rev-share.
• Data use & analytics: permitted data collection, PHI/PII restrictions, aggregated vs. identifiable data, retention windows, access for both parties, and compliance with privacy laws (GDPR/CCPA).
• Placement & exclusivity: exact placement guarantees, duration, scope (device models/regions), and exit/clawback for non-performance.
• Termination & SLAs: termination for convenience vs. for cause, wind-down obligations (uninstall UX, billing handoffs), notice periods, and transition of active subscriptions.
• Technical & security obligations: update cadence, vulnerability patching SLA, incident response collaboration, and acceptance testing.
• Measurement & KPIs: agreed measurement methods, attribution model, experiment boundaries, penalties or make-goods if placement underperforms.
• IP, indemnity & liability limits: ownership of integrations, use of Apple marks, indemnities, and caps on liability.
• Compliance & certification: App Store policy alignment, onboarding timelines, and beta/test device access.

How I’d prioritize in negotiation

1. Lock in placement and measurability (so we can prove uplift).
2. Secure payment & auditability terms (clear rev-share math).
3. Minimize exclusivity or make it time-limited with performance gates.
4. Protect user privacy and data access needed to measure LTV while staying compliant.
5. Define clear technical acceptance, rollback, and SLA terms.

Example ask/color: propose 30% rev-share on in-app subs for 12 months plus guaranteed placement in the setup flow for 6 months; if adoption falls below agreed KPI thresholds after 90 days, adjust placement or rev-share (performance-based tiering). This ties our marketing commitment to measurable returns and gives Apple a clear ROI story while protecting our product and data.

Start by framing objectives: validate the market is large and growing, defensible vs competitors, monetizable, and reachable at scale with acceptable regulatory risk. Checklist items below list what to verify and the evidence to request.

1. Total Addressable Market (TAM) / SAM / SOM

• What to validate: TAM size methodology, growth rates, segmentation.
• Evidence: market research reports (Gartner/Forrester/IDC), internal TAM models with assumptions, end-market revenue data, analyst slide decks, customer segmentation spreadsheets.

2. Historical & Forecasted Market Growth

• What to validate: past 3–5 year CAGR and drivers; forecast assumptions.
• Evidence: industry forecasts, government data (census, trade stats), company revenue trends vs. market, sales pipeline forecasts, slides used for investor updates.

3. Competitive Landscape & Dynamics

• What to validate: number/type of competitors, positioning, recent entrants, pricing, switching costs.
• Evidence: competitor benchmarking, win/loss analysis, product feature matrix, pricing sheets, third-party reviews, M&A activity reports.

4. Customer Concentration & Churn

• What to validate: percent revenue from top customers, churn rates, contract terms, net retention.
• Evidence: customer revenue waterfall, top-20 customer list + contract copies (redacted), cohort analyses, churn/NRR dashboards, references from key customers.

5. Pricing Power & Monetization

• What to validate: price elasticity, margin profile, ability to raise prices or add features.
• Evidence: historical price changes and impact, contract renewal pricing, gross margin P&L breakdown, pricing experiments/AB test results.

6. Threats from Substitutes & Technology Risk

• What to validate: alternate solutions, technological obsolescence, platform risk.
• Evidence: product roadmaps of competitors, patent landscape, R&D spend trends, external tech trend reports, customer feedback on alternatives.

7. Regulatory & Compliance Risks

• What to validate: existing/regulatory exposures, upcoming legislation, compliance posture.
• Evidence: legal/regulatory opinion memos, compliance certifications (SOC2, GDPR DPIAs), pending litigation, correspondence with regulators.

8. Go-to-Market (GTM) Scalability

• What to validate: CAC, LTV, channel mix, sales productivity, onboarding time.
• Evidence: CAC/LTV models, marketing funnel metrics, sales playbooks, org chart for sales/CS, onboarding/runbook, unit economics by segment.

9. Distribution & Partnerships

• What to validate: reliance on partners, exclusivity, renewal terms.
• Evidence: partner contracts, referral agreements, reseller metrics, channel revenue splits.

10. Sensitivity & Scenario Analysis

• What to validate: downside scenarios (market contraction, major customer loss).
• Evidence: stress tests, scenario P&Ls, break-even analyses, contingency plans.

For each item, request raw data plus the narrative slide or memo that explains assumptions. Where possible interview: customers, sales leaders, product leads, and independent industry analysts to corroborate documents. Use these findings to build a risk-adjusted market thesis guiding valuation and product integration planning.

As PM, I’d evaluate last-mile carriers against six core criteria. For each: a measurable acceptance threshold and a short pilot to validate.

1. Cost

• Threshold: Total landed cost per shipment ≤ $X (e.g., $6 for urban, $12 for rural) and margin impact ≤ 3% of order value.
• Pilot: Run 500 live orders across typical zones for 4 weeks, compare invoiced costs vs. expected, and measure cost-per-delivery and surge pricing behavior.

2. SLA (timeliness & reliability)

• Threshold: On-time delivery rate ≥ 95%, delivered within promise window ≥ 98%, first-attempt success ≥ 90%.
• Pilot: 1,000 time-windowed deliveries over 4 weeks; track timestamps, exceptions, and percent meeting SLA.

3. Coverage

• Threshold: Serviceable coverage for ≥ 98% of our ZIP/postal codes; delivery within target geo-times (e.g., same-day in metro).
• Pilot: Create representative order set (by ZIP density) and attempt deliveries to every target postal code over 2 weeks; report unreachable areas.

4. Insurance & liability

• Threshold: Carrier provides cargo insurance covering full declared value, liability for loss/damage ≥ $X per package, and claims turnaround ≤ 14 days.
• Pilot: Inject controlled damage/loss test cases (with consent) and submit mock claims; measure claim acceptance rate and settlement time.

5. API integration & data quality

• Threshold: RESTful API with 99.9% uptime, webhook latency ≤ 2s, standard events (pickup, in-transit, delivered, exception), <1% missed/malformed webhooks.
• Pilot: Integrate in sandbox, then run 2-week shadow mode on 500 orders to validate event completeness, tracking accuracy, reconciliation of statuses and error rates.

6. Capacity & scalability

• Threshold: Ability to scale +50% weekly volume without SLA degradation; peak handling capability for X daily deliveries.
• Pilot: Gradually ramp pilot volume by 20% increments over 3 weeks (start 200/day → 300 → 360) while monitoring SLA, drop rates, and staffing responsiveness.

For each pilot, capture KPIs, operational notes, and a post-mortem. Use results to score carriers on a weighted rubric (business impact, reliability, integration effort) before selection.

Framework (stepwise):

1. Clarify objectives & constraints: strategic priority (speed vs cost), budget, risk tolerance, integration appetite, IP/people importance, regulatory issues.
2. Define scenarios & timeline: immediate acquisition (0–6mo integration) vs build (18mo dev + ramp).
3. Financial valuation & sensitivity: NPV of incremental cash flows, IRR, payback period, and option value of control.
4. Strategic & qualitative factors: time-to-market value, customer retention/ACV impact, talent/IP capture, competitive dynamics, cultural fit, integration risk.
5. Decision rule: choose option with higher risk-adjusted NPV + strategic alignment.

Necessary metrics (quantitative + qualitative):

• Upfront cost: $50M vs $8M development + operating burn during 18mo
• NPV of incremental revenues (discount rate reflecting company WACC + execution risk)
• Time-to-market value: estimated revenue lost/gained per month of delay
• Payback period & IRR
• Probability-weighted development success (tech risk)
• Integration risk score (people, tech, go-to-market)
• Retention rate impact and churn avoidance
• Strategic moats: patents, data, customer contracts
• Opportunity cost and optionality (future M&A leverage)

Quick numeric heuristic:

• Acquisition is justified if present value of expected incremental EBIT attributable to the target over the decision horizon > $50M (adjusted for integration risk). Example: to pay back $50M in 3 years requires ~ $16.7M annual EBIT pre-tax.
• Building costs $8M + 18mo delay. If monthly lost opportunity (net EBITDA) > (50-8)/18 ≈ $2.33M, acquisition is likely better (because acquisition’s premium covers delay). Also factor probability of build failure p: effective build cost ≈ 8M + (revenue loss during delay) / p-success.

Recommendation (product-manager lens):

• If speed-to-market and customer lock-in are critical (fast-moving competitor, risk of share loss, strategic IP/talent), recommend acquiring—pay the premium to eliminate risk of delay and secure customers/talent. Prioritize if monthly lost EBITDA > ~$2.3M or if acquisition accelerates network effects / blocks competitors.
• If capability is non-core, development team has proven track record, and market can tolerate 18mo delay (low churn, low competitive pressure), recommend building to save capital and retain ownership — proceed with an accelerated roadmap, hire/contract critical talent, and set hard go/no-go milestones.

Immediate next steps:

• Run quick financial model: NPV scenarios (base, downside, upside) at company discount rate.
• Fast diligence on target: revenue quality, tech audit, customer contracts, retention, people willingness to stay.
• Estimate development probability and build timeline with engineering leads; compute combined option-adjusted NPV.
• Present a recommendation with sensitivity table showing thresholds where build vs buy flips.