Customer-Covered Projects Share

Goal of the analysis:

Quantify the extent to which R&D project costs are funded by customers (e.g., non-recurring engineering fees, reimbursed engineering services, paid pilots, co-development contracts). The goal is to measure how much of the portfolio’s effort is externally financed, where funding is concentrated, and whether coverage aligns with strategy and margin expectations. For executives, this indicates burn-rate relief, commercialization signal strength, dependence on bespoke work, roadmap drift risk, and the health of customer co-creation models.

Data required:

• Portfolio and project master:
  • Project IDs, names, business unit, product/platform, start/end dates, stage/gate status, strategic classification (core/adjacent/breakthrough).
  • Project type (new platform, derivative, customer customization, maintenance), priority tier, and commercialization intent.
• Contracts and commercial terms:
  • Executed SOWs, MSA/contract metadata, NRE clauses, reimbursable expense terms, milestone/billing schedules, payment terms.
  • Funding source tags (customer co-fund, government grant, partner in-kind) and IP/licensing ownership terms.
• Financials and billing:
  • Project-level R&D costs: labor (timesheets, loaded rates), materials/prototypes, external services, labs/capex allocations.
  • Revenue and invoicing tied to projects: NRE revenue accounts, reimbursed expenses, grants; invoice status, collections (DSO), credit/debit memos.
  • Budget vs actuals; planned vs contracted funding; cost capitalization flags.
• Resource and time tracking:
  • Timesheets by project/WBS, labor category, location; standard and burdened rates.
  • Allocation plans (PPM) and actual utilization (ALM/PSA).
• Pipeline and opportunity data:
  • Open opportunities for funded projects (CRM), forecasted NRE amounts, stage probability, expected start dates, customer segment.
  • Win/loss outcomes for past proposals and reasons.
• Governance and definitions:
  • Policy defining “customer-covered” (e.g., recognized or contracted external funding that offsets R&D cost; exclude implicit pricing concessions).
  • Chart of accounts mapping (which GL accounts constitute customer funding vs product revenue).
• Systems and sources:
  • ERP/Finance (SAP, Oracle), PPM (Planview, Clarity), PSA (NetSuite OpenAir), CRM (Salesforce, Dynamics), CLM (Icertis), ALM/Jira for work logs, BI warehouse.
• Historical and benchmark data:
  • Historical coverage ratios, project-level margins, customer concentration, and commercialization outcomes.

Detailed step-by-step instruction on how to conduct the analysis:

1. Define scope and measurement conventions. Specify the project set (active in last 12–18 months). Decide whether to use recognized revenue or contracted funding for coverage, and whether to calculate count-based and spend-weighted views. Clarify cost basis (fully burdened R&D cost including overheads) and periodization (monthly/quarterly, rolling 12 months).
2. Standardize “customer-covered” classification.
   • Included: NRE fees, reimbursed engineering services, paid pilots/POCs, government grants tied to projects.
   • Excluded: volume price premiums, implicit discounts, post-sales services unrelated to product R&D, internal chargebacks.
   • Edge cases: in-kind contributions (mark as non-cash), multi-customer co-funding (allocate by contract), pass-through materials (treat consistently).
3. Extract project cost and funding data. From ERP/PPM/PSA, pull actual R&D cost by project/WBS and period. From ERP/CRM/CLM, pull recognized NRE/reimbursement revenue and contracted future funding with milestones and amounts. Reconcile to the GL to ensure completeness.
4. Link contracts to projects. Use project IDs, WBS, or contract references to join SOWs and invoices to the correct projects. Where one contract funds multiple projects, allocate by planned hours or value; document allocation rules.
5. Compute core metrics per project.
   • Customer Funding (actual) = Recognized NRE + Reimbursed expenses + Grants (cash).
   • Coverage Ratio (actual) = Customer Funding / Total R&D Cost (same period).
   • Coverage Ratio (contracted) = Contracted Funding Remaining / Forecast R&D Cost to Complete.
   • Coverage Bands: Fully covered (≥100%), Partially covered (50–99%), Low (<50%), None (0%).
   • Profit after coverage (optional) = Product revenue margin impact + NRE margin − R&D cost not covered.
6. Aggregate portfolio metrics.
   • Customer-Covered Projects Share (count-based) = Number of projects with Coverage Ratio > 0 / Total projects.
   • Spend-weighted Share = Sum(R&D cost for projects with Coverage Ratio > 0) / Sum(R&D cost for all projects).
   • Coverage Depth = Sum(Customer Funding) / Sum(R&D Cost) for the portfolio.
   • Backlog of Committed Funding = Sum(contracted funding not yet recognized).
7. Segment, compare, and trend. Break out by BU, platform, project type (new vs derivative vs customization), customer tier/industry, geography, and stage/gate. Build monthly/quarterly time series for shares and depth metrics. Add pipeline conversion: expected funded projects starting next 2–3 quarters.
8. Assess concentration and sustainability.
   • Top-5 customers’ share of funded value; Herfindahl index for concentration risk.
   • Milestone adherence and DSO on NRE invoices; identify late collections impacting cash flow.
   • IP terms: % of funded projects where IP is retained vs customer-owned.
9. Quality of coverage and economics.
   • Compare coverage to project gross margin and to eventual product revenue outcomes.
   • Flag low-price “coverage” that substitutes for discounts (e.g., large NRE paired with below-target product pricing).
   • Analyze post-launch cannibalization of roadmap or maintenance burden due to bespoke features.
10. Validate findings with Finance, Sales, and R&D. Review allocations, exclusions, and IP classification. Resolve mismatches between CRM commitments and ERP recognition. Adjust for capitalization policies where relevant.
11. Automate and govern. Establish a data pipeline and monthly refresh in BI. Create governance that tags every new project with funding status and target coverage at gate entry.

Format of the output of analysis:

• Executive summary with count-based and spend-weighted shares, coverage depth, and YoY trend.
• Stacked bar charts of coverage bands (none, low, partial, full) by BU/platform and by stage.
• Waterfall showing total R&D cost and portions covered by customers, grants, and internal funds.
• Customer concentration view (top-10 customers’ funded amounts) and DSO for NRE invoices.
• Scatter/bubble of projects: coverage ratio vs strategic score, bubble size by cost; color by margin risk.
• Pipeline-to-coverage bridge: expected funded starts vs current share.
• Appendix tables with project-level details, contract terms, and IP ownership flags.

How to interpret results:

• High share and depth reduce net R&D cash burn and validate customer demand, but watch for roadmap drift toward bespoke features, IP give-aways, and customer concentration risk.
• Low share may be appropriate for platform creation or regulated innovation where IP retention is strategic; if persistent across customization-heavy businesses, it signals pricing and commercial discipline gaps.
• Segment differences: customization and enterprise solutions should show higher shares than standard product lines; early-stage platforms may be lower but should improve as paid pilots scale.
• Quality indicators: healthy coverage pairs with on-time milestones, reasonable DSO, and favorable IP terms. Coverage paired with below-floor product pricing or long DSO may be value-destructive.
• Trend patterns: improving coverage during downturns can cushion budgets; sudden spikes limited to a single customer elevate dependency risk.

Steps a company can take to improve on this measure:

• Process and commercial policy:
  • Institutionalize a co-development/NRE pricing playbook with rate cards, markup policy, and minimum coverage thresholds by project type.
  • Gate criteria: require evidence of external funding (e.g., signed SOW and initial payment) for customer-specific features before build.
  • Standardize IP frameworks (e.g., background IP retained, field-limited licenses) to avoid value leakage.
  • Milestone-based billing with clear acceptance criteria to accelerate cash conversion.
• Data, systems, and tooling:
  • Integrate CRM–CLM–PPM–ERP so funding status, contract value, and costs roll up automatically at project level.
  • Add project metadata fields for funding type, IP terms, and customer tier; enforce mandatory tagging at project creation.
  • Dashboards for coverage ratio, DSO on NRE, and customer concentration with alerts for breaches.
• Capability and governance:
  • Train Sales/BD on solution scoping and NRE value articulation; equip with case studies and ROI calculators.
  • Establish a funding council to review exceptions, set annual coverage targets by BU, and monitor pipeline health.
  • Align engineering resourcing with funded priorities; limit un-funded customization via intake controls.
• Product and offer design:
  • Create modular architectures and configurable options to channel customization into paid, reusable modules.
  • Develop paid pilot/POC packages with predefined scope, price, and conversion paths to productization.
  • For strategic platforms, seek grants/consortia or multi-customer co-funding to diversify risk.
  • If coverage is high but margins are weak, reprice NRE, tighten scope control, and negotiate usage fees where outcomes create lasting value.

Benchmark comparisons:

General benchmarks:

• Count-based share of customer-covered projects in mixed B2B portfolios often falls in the 20–40% range; spend-weighted shares can be higher where large custom programs dominate.
• Depth of coverage (funding divided by R&D cost) commonly targets 30–60% for customization-heavy businesses and 5–20% for product-platform businesses.
• Healthy operations keep DSO on NRE within standard terms (e.g., 30–60 days) and cap top-customer exposure (e.g., top-1 < 25% of funded value).

Segment- or industry-specific benchmarks:

• Aerospace/defense and public-sector programs can see 50–80%+ of R&D funded externally under contract structures.
• Enterprise software/SaaS often see 5–15% funded via paid pilots or implementation engineering; solution integrators can be higher.
• Automotive Tier-1 suppliers and industrial OEMs commonly target 30–60% coverage for customer-specific engineering and tooling-related work.
• Where external data are limited, build internal benchmarks by BU and project type, compare top quartile teams, and ratchet targets by +5–10 pts after standardizing pricing and intake.