Market Analysis
Purpose
Answers: Is this opportunity real, and how big? Market Analysis is not Competitive Analysis or Business Case. It owns market sizing, growth trajectory, and the sub-approaches under consideration. Competitive Analysis owns competitive pressure, alternatives, and defensible positioning once a direction is chosen. Business Case owns investment logic (cost, ROI, go/no-go).
Authoring guidance
- Name the sub-approaches — if the opportunity spans distinct supply chains, cost structures, or buyer segments, size and discuss each rather than collapsing them into one pitch.
- Cite every figure — every market-size or growth-rate number traces to an entry in Sources; do not present modeled or recalled figures as sourced fact.
- Separate facts from assumptions — mark confidence explicitly when a claim is a stated market-report driver versus an inferred implication.
- Defer decisions, don’t make them — sub-approach commitment, sourcing relationships, and positioning anchors belong in Frame; record them here as Open Questions, not as conclusions.
- Stay evidence-first — Strategic Implications should read as “what the sizing and competitive-density data imply,” not as an independent pitch.
Quality checklist from the prompt
- Every sub-approach the opportunity could take is named, not collapsed
- Every market-sizing figure cites a source
- Key Drivers separate stated market-report findings from inferred trends
- Strategic Implications are grounded in the sizing/competitive-density data above them, not asserted independently
- At least one Open Question is explicitly deferred to Frame
- Sources section lists every citation used in the body
Example
Show a worked example of this artifact
---
ddx:
id: market-analysis
authoring:
home: repo
---
# Market Analysis: SMB Expense-Report Automation
**Activity:** Discover
**Status:** Draft
**Date:** 2026-03-01
## Concept
Automated expense-report capture and approval for small and mid-size
businesses (SMBs, 10-250 employees), evaluated across two distinct
sub-approaches since they imply different integration and pricing models:
1. **Standalone SaaS** (receipt capture, OCR, approval workflow, sold direct
to finance teams)
2. **Embedded add-on** (same capability, sold as a module inside an existing
SMB accounting platform's marketplace)
## Market Size & Growth
- Global expense management software market: **$5.5B (2026) → $9.8B
(2032)**, ~10.2% CAGR.
- SMB-segment expense management specifically: **~$1.2B in 2026**.
- Embedded finance / accounting-platform add-ons (all categories): 24%
CAGR 2025-2031 — the fastest-growing distribution channel in the broader
market.
**Read:** the standalone-SaaS lane is larger today but growing in line with
the category average; the embedded-add-on lane is smaller but growing more
than twice as fast, suggesting distribution-channel choice matters more than
product-category choice for a new entrant.
## Competitive Landscape
### Standalone SaaS
- **Established direct competitors**: Expensify, Ramp, Brex — all target
SMB-to-mid-market and bundle expense management with a corporate card
product.
- **Incumbents moving in**: QuickBooks and Xero have each shipped native
expense-capture features in the last two years, narrowing the gap a
standalone tool needs to close.
### Embedded add-on
- **Marketplace competitors**: a small number of narrow OCR-only apps listed
in the QuickBooks and Xero app marketplaces; none bundle approval workflow.
- Fewer than 10 marketplace listings combine capture and approval as of
2026 — the add-on lane is less contested than standalone SaaS.
## Key Drivers
- SMB finance teams are a stated market-report driver toward "fewer
point-tools, more embedded workflow" — not just a niche preference.
- Card-linked expense products (Ramp, Brex) are growing faster than
capture-only tools, suggesting a card attachment may matter more than
OCR accuracy as a differentiator.
- Accounting-platform marketplaces are actively promoting embedded
add-ons as a growth lever for their own platforms, which lowers
distribution cost for an add-on entrant.
## Strategic Implications
- **Standalone SaaS**: the lane is larger but already has three well-funded
direct competitors plus two incumbents encroaching — a new entrant needs a
differentiator sharper than "capture and approve expenses."
- **Embedded add-on**: less crowded and higher-growth, but ties the product's
reach to a single accounting platform's marketplace and distribution
decisions.
- **Pricing signal**: standalone competitors bundle a card product to
capture interchange revenue; a pure software play without a card may not
sustain comparable margins.
## Open Questions
**For Frame:**
- Does this venture commit to standalone SaaS, the embedded-add-on lane, or
a phased path (embedded first, standalone later)?
- Is a card-issuing partnership available, or is this a pure software
entrant competing against card-subsidized incumbents?
- What functional differentiator, beyond capture-and-approve, anchors the
positioning once a lane is chosen?
## Sources
- [Global Expense Management Software Market Report (example)](https://example.com/expense-management-market)
- [Embedded Finance Distribution Trends (example)](https://example.com/embedded-finance-trends)Reference
| Activity | Discover — Validate that an opportunity is worth pursuing before committing to a development cycle. |
|---|---|
| Default location | docs/helix/00-discover/market-analysis.md |
| Requires | None |
| Enables | None |
| Informs | Competitive Analysis Business Case Opportunity Canvas |
| Generation prompt | Show the full generation prompt |
| Template | Show the template structure |
Innsigle seal: model-primary by HELIX
The signature covers the markdown source of this page, not these HTML bytes. This page quotes that seal; verify it against the source file.
- Composition
- model-primary
- Issuer
- HELIX
helix - Signing key
ed25519:b0865d76d834a52c48506414d16f4e5a(build key)- Signed source
artifact-types/discover/market-analysis.md- Signed
- 2026-09-23T14:11:58Z
- Content digest
sha256:13219251…74c87200
This build key is endorsed by the human key for build signing; the signature is not a detector and not a truth guarantee.
Raw attestation JSON
{
"payload": {
"innsigle": "1",
"type": "https://innsigle.dev/claim/colophon/v1",
"issued_at": "2026-09-23T14:11:58Z",
"issuer": {
"id": "helix",
"name": "HELIX",
"key_id": "ed25519:b0865d76d834a52c48506414d16f4e5a",
"key_url": "https://documentdrivendx.github.io/helix/.well-known/innsigle/keys.json"
},
"subjects": [
{
"uri": "https://documentdrivendx.github.io/helix/artifact-types/discover/market-analysis/",
"digest": {
"alg": "sha256",
"value": "13219251704ed6bfce5ebbd9e043ccf3a97b6d30515a6fbb5d4d0a2e74c87200"
}
}
],
"colophon": {
"schema_version": "1",
"composition": "model-primary",
"ingredients": [
{
"kind": "model",
"name": "Claude",
"role": "draft"
},
{
"kind": "tool",
"name": "sloptimizer",
"role": "rewrite"
},
{
"kind": "human",
"name": "operator",
"role": "structure-edit"
}
],
"notes": null
}
},
"payload_encoding": "json",
"signatures": [
{
"key_id": "ed25519:b0865d76d834a52c48506414d16f4e5a",
"alg": "ed25519",
"sig": "3tpacLhnybR4EA8rw3l3_k-uhCcMH3drpG4rnqcJ4CwMG6TJ4018mUN_YhIRffVEz4dMMOfaCjGOX3UWbgQpCQ",
"signed_at": "2026-09-23T14:11:58Z"
}
]
}