Partnerships and Deal Evaluation Questions

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.

As PM I'd negotiate clauses to protect liquidity and unit economics while enabling launch.

Key contract clauses

• Exclusivity scope: narrow by geography (pilot cities), channel (app only), and duration (short, e.g., 3 months) with opt-out triggers
• Minimum guaranteed volume: commit to a realistic ramp schedule with penalties only if platform fails to meet agreed marketing/promotional commitments
• Revenue-sharing floors: platform maintains minimum take rate floor for non-exclusive merchants; exclusivity discount capped so platform contribution loss limited
• Most-favored-nation (MFN) clause with guardrails: ensure chain doesn’t get better terms than public offers, but limit to same-city MFN and exclude transient promotions
• Courier impact protections: ensure exclusivity doesn't create courier demand surge that harms other merchants—include clause to monitor courier earnings impact and require corrective incentives if courier earnings drop below a threshold
• Data & measurement: shared KPIs, transparent access to order logs, weekly cadence for review
• Exit & lift clauses: automatic rollback if negative impacts exceed thresholds (e.g., >10% drop in other merchants’ order fill rate or >5% drop in courier earnings)

Metrics to insist on

• Liquidity: match rate, average fulfillment time across platform, courier utilization, cross-merchant cancellation rates
• Unit economics: take rate impact, incremental GMV attributable to partner, contribution margin per order
• Competitive health: merchant churn rate in same category, consumer diversion metrics

Operational protections

• Pilot exclusivity in limited zones, staggered rollout, and real-time monitoring dashboard. Keep funds reserved for courier rebalancing incentives.

These clauses balance partner value with marketplace fairness and operational guardrails.

Framework: start with objective (eliminate strategic threat, capture users/tech) → evaluate defensibility → due diligence → integration risks and mitigation → valuation tied to quantified synergies.

Competitive criteria (what matters)

• Overlap with our addressable market and growth segment
• Unique tech/assets that shorten our roadmap (IP, ML models, integrations)
• Customer base quality: retention, ARPU, net revenue retention (NRR)
• Go-to-market advantages: channel, brand, distribution partners
• Regulatory or contractual protections that prevent easy replication

Due diligence checklist (defensibility-focused)

• Technology
  • Codebase health: modularity, tests, CI/CD, tech debt assessment
  • IP ownership: patents, trademarks, open-source license compliance
  • Architecture scalability and portability (cloud, data schemas)
  • Roadmap vs. our tech — overlap and gaps
• Customers & commercial
  • Customer list by ARR, churn, concentration, expansion metrics
  • Contracts: term lengths, renewal rates, price escalators, pass-through clauses
  • SLA commitments and penalty exposure
  • Key references and product stickiness indicators (custom integrations, usage depth)
• Legal & compliance
  • Outstanding litigation, data/privacy liabilities (GDPR/CCPA), security incidents
  • Third-party dependencies and vendor lock-in clauses

Integration risks & mitigations

• Product fit mismatches (UX, APIs): pilot integration, preserve both SKUs initially
• Tech integration cost and timeline: estimate engineering FTE, roadmap reprioritization
• Customer churn due to brand changes: communication plan, grandfathered pricing
• Talent flight (founders/engineers): retention packages, clear role scope
• Data migration and security: audit, phased sync, rollback plans

Valuation approach tied to synergy capture

• Base valuation using standard methods (DCF or revenue multiple) on standalone forecasts
• Synergy estimate: quantify revenue synergies (cross-sell uplift, reduced churn → incremental ARR), cost synergies (consolidation of R&D, sales, hosting)
• Build a 3-scenario model (conservative/likely/optimistic) with timelines and probability weights
• Price = standalone value + present value of achievable synergies × capture probability, less integration costs and one-time risks
• Use earn-outs or milestone-based payouts to align seller incentives for retention and synergy delivery

As product lead I'd drive technical diligence, build integration roadmap with engineering, and own product-level synergy targets and measurement (KPIs: net retention, time-to-first-integration, engineering hours spent).

Framework to evaluate the partnership — ask for specific data and map to operational, financial, and strategic questions. I’d structure it as: Goals → Data requests → Analysis/metrics → Risks & go/no-go criteria.

Goals (clarify with partner)

• What each party expects (new customers, incremental sales, margin, brand exposure)
• Exclusivity or preferred placement terms

Data requests

• Historical in-store weekly/monthly sales by SKU and channel (12–24 months)
• Average order value (AOV), basket composition, and margin by SKU
• Store footprint: count, hours, store-level pickup/delivery radius
• Customer demographics & loyalty program overlap
• Current digital/third‑party order volume (if any)
• Fulfillment capacity: average orders/hour, peak capacity, labor schedules
• Pricing/promotions history and co-marketing budgets/commitments
• Onboarding timeline & integration needs (POS/API access, menu sync)
• SLA expectations (acceptance time, cancellation rates, out-of-stocks)
• Financial terms beyond 10%: marketing contribution, minimums, disputes

Key analyses / metrics

• Incremental GMV forecast under adoption scenarios (conservative/likely/optimistic)
• Contribution margin to DoorDash after costs (delivery ops, discounts, marketing)
• CAC and estimated payback period (use co-marketing uplift vs. paid acquisition)
• Impact on marketplace metrics: merchant acceptance, ETA, cancellations, customer NPS
• Cannibalization risk: % of orders shifted from in-store/other channels
• Operational lift: hours of extra fulfillment labor, extra delivery fleet needs

Operational considerations

• Integration complexity (POS/API vs manual menu management)
• Quality control: inventory sync, real‑time availability, packaging standards
• SLA enforcement and penalties for poor performance
• Training & onboarding resources (store managers, drivers)

Strategic considerations

• Brand fit and customer perception
• Competitive dynamics (do competitors have similar partnerships?)
• Potential for exclusivity, pilot → scale path
• Long-term opportunities (data sharing, private-label, dark stores)

Experiment plan & success criteria

• Pilot 4–8 stores for 8–12 weeks with A/B control stores
• Pre-register metrics: incremental orders/week, retention rate, AOV uplift, contribution margin per order, customer satisfaction
• Go/no-go thresholds (e.g., >20% incremental orders with positive unit economics within 12 weeks)

Risks & mitigations

• High cancellation/out-of-stock → require inventory sync + short SLA
• Operational strain → cap pilot volume, provide shared training
• Poor unit economics → negotiate marketing offsets or higher commission tiers for loss leaders

Recommendation ask

• If data shows positive incremental GMV, acceptable unit economics, and low operational lift, proceed with pilot; otherwise negotiate terms (marketing support, better placement, or limited-exclusivity) before committing.

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.