Source: value-proposition.md (channel-by-channel value propositions)

What this source is

The customer-facing value proposition document — Version 4.1, dated April 9, 2026. Companion to business-case. While the business case is for Squire leadership, this document presents the value propositions for the three customer segments (NetSuite customers, Business Central customers, Multi-ERP customers) and the three revenue channels (Partner, Direct, Enhancement).

Key claims (new content beyond business-case)

Customer ROI by segment (NEW specificity)

1. NetSuite customer ROI: $450Kannualsavings/$29,940 investment = 15:1 ROI → roi-scenarios
2. Business Central customer ROI: $400Kannualsavings/$29,940 = 13:1 ROI
3. Multi-ERP customer ROI: $700Kannualsavings/$29,940 = 23:1 ROI (highest-value segment)

Channel-specific pricing detail (NEW)

4. Partner white-label license: $10K/year—unlimitedclientdeployments,white-labelbranding,partnertraining,businesshourssupport.PartnerYear1profit:$214,700 (2,147% ROI) if they deploy to 5 clients.
5. Enhancement modules (NEW granularity): Tier 1 ($995/mo)=AIFieldMappingonly;Tier2($1,495/mo) = AI Field Mapping + Intelligent Error Recovery + Predictive Analytics + Data Quality Monitoring.
6. 30% of enhancement customers upgrade to full platform within 2 years — built-in upsell path.

Module-specific business impact (NEW)

7. SupplierCentral integration: 75% reduction in vendor onboarding time (5 days → 1.25 days), 90% elimination of duplicate vendor records, $120K annual savings.
8. InstallerCentral integration: 40% improvement in installer utilization, 60% reduction in scheduling conflicts, $200K annual revenue increase.
9. PayoutCentral integration: 95% reduction in commission calculation errors, 80% faster payout processing (10 days → 2 days), $300K annual savings.

Stale/drifted claims in this source (flagged for wording governance)

10. “14 Production Connectors” — contradicts canonical 6. This doc is using a different counting methodology or an older/broader definition.
11. “9 AI providers” — contradicts canonical 4 real + 2 experimental + 1 fallback = 7. May include providers counted differently.
12. “766K+ records/second” sync throughput — NEW number not seen elsewhere in the corpus. Not verified against the canonical wording.
13. “96.2% AI accuracy” — NEW number vs canonical 95-99%. May be a specific benchmark value.
14. “Shopify” and “QuickBooks” named as connectors — neither is in the canonical 6.

These drifted claims suggest this document has not been refreshed to match 26-canonical-metrics-and-wording. Per that style guide’s governance rule: “Any document added to NotebookLM should conform to this file before packaging.”

Pages updated by this ingest

Updated (2 existing pages):

• revenue-model — added channel-specific pricing detail, customer-segment ROI ratios, enhancement tier breakdown, 30% upsell rate
• module-library — cross-linked module-specific business impact numbers (SupplierCentral, InstallerCentral, PayoutCentral)

Cross-references / contradictions

• Stale wording drift (claims 10-14): multiple numbers in this doc don’t match canonical wording. This is a style-guide compliance issue, not a factual contradiction — the document predates the canonical wording refresh or hasn’t been updated.
• Customer success stories (“Acme Industrial”, “TechInstall Solutions”) — likely illustrative/aspirational examples, not real customer references. Treat as positioning, not evidence.
• **$50K/yearenterpriselicense\ast \ast intheROIAnalysisFrameworksectiondoes{n}^{\prime }tmatchthe$2,495/month Direct Sales pricing elsewhere in the same document. These are different tiers: $50K/yearistheenterprise-tier;$2,495/month is the direct-SaaS tier. Both are valid at different customer sizes.

Notes

• This is a sales-facing document. Its tone is deliberately enthusiastic (”🚀”, ”💰”, ”🏆” emoji headers). The Brain1 wiki should use the facts from this document but not adopt its tone (per CLAUDE.md §3: “without overly selling”).
• The module-specific business impact numbers (claim 7-9) are the first formally-ingested per-module ROI numbers. They strengthen the value-first narrative for the wiki’s curated reading paths.
• Version 4.1, dated April 9, 2026 (same vintage as business-case.md — both refreshed 2 days ago as of this session). These are the freshest strategic sources in the corpus.