Strategy walkthrough: CompanyExpenses Tracker
Read how a B2B expense product moves from idea to audit-ready strategy pack — and reuse the pattern in your workspace.
This is a training case study, not a technique primer. It follows one fictional-but-realistic product — CompanyExpenses Tracker — through the same strategy journey Sculptor supports: discover → market → strategy → customers → goals → brand → organisation → go-to-market → risk → validation.
The narrative matches Sculptor’s seed demo project (Settings → seed demo project). You can read this article first, then open the seeded workspace and inspect each artefact (SCOPE-001, BMC-001, VPC-02, and so on) in the library.
How to use it as training material:
- Read one section per sitting and note which decisions each phase forces.
- After each section, open the linked guide (e.g. Business Model Canvas) if you need method detail.
- In your own project, ask: “Do I have an equivalent artefact, or am I skipping this decision?”
CompanyExpenses Tracker is local-first B2B expense management for small startups. Finance teams capture receipts on mobile, auto-categorise spend, and export accountant-ready packs to Xero or QuickBooks — without ERP onboarding.
| Dimension | Choice |
|---|---|
| Segment focus | B2B |
| Offering | Software product |
| Stage | MVP |
| Beachhead | SMB finance ops (20–200 employees) |
| Wedge | Accountant-native export on day one |
Core problem: Finance teams lose hours reconciling receipts, categories, and external accountant formats. Month-end becomes spreadsheet archaeology.
Success measures (stated at intake):
- Cut monthly expense ops time by ~50%.
- Zero-setup onboarding for SMB finance teams.
- Accountant-ready CSV/PDF exports from the first close.
Constraints called out early: GDPR-aware receipt storage; export paths for Xero/QBO; MVP scope only — no full general ledger.
Sculptor’s Strategy Pack runs 38 phases for this demo. They are grouped below the way practitioners think — not as a checklist to complete blindly.
| Stage | Demo phases (examples) | Question answered |
|---|---|---|
| Discover | Intake, brain, DNA | What venture are we building and why us? |
| Market | PESTLE, competitors, Wardley | What external reality constrains choices? |
| Strategy | BMC, VPC, SWOT, ERRC | What business design do we commit to? |
| Customers | Personas, journeys, CX | Who buys, who uses, what do they experience? |
| Goals | NSM, OKRs, roadmap, backlog | What do we ship first and how do we measure it? |
| Brand & UX | Brand, naming, visual, prototype | How does strategy show up to humans? |
| Org & tech | Tech canvas, org, compliance | Can we deliver and operate it? |
| GTM | Sales, marketing, pricing | How do we win customers? |
| Risk & validate | Risks, PMF, validation report, critique | What could break, and did we stress-test? |
Good strategy design threads references between artefacts (Refs in: blocks in the demo). If your BMC segment names do not appear in personas and VPC slots, you have a traceability gap.
Intake (SCOPE-001)
Intake is the contract for the run. For CompanyExpenses Tracker it locks:
- Product boundary: expense capture + categorisation + export — not payroll, not invoicing.
- Segment hypothesis: B2B, MVP, includes software.
- Evidence standard: exports must satisfy external accountants on first submission.
Training prompt: Before any canvas, can you state problem, segment, and “done” in one paragraph? If not, intake is incomplete.
Strategic brain (BRAIN-001)
Brain consolidates direction:
- Vision: Every startup finance team closes books with audit-ready expenses without spreadsheet archaeology.
- Mission: Unify receipt capture, categorisation, and accountant exports for SMB finance ops.
- Bets: OCR-first capture, accountant-native exports, local-first trust.
Founders’ DNA (PV-001, MOT-001, PSW-001)
DNA translates founder intent into positioning:
- Purpose: Make expense operations disappear so finance builds for the future instead of reconciling the past.
- Wedge line: The only expense tool that ships accountant CSV packs on day one for SMB finance ops.
Training prompt: Your wedge should be ** falsifiable**. Could a competitor claim the same line? If yes, sharpen it.
PESTLE (PEST-001)
Macro forces that ** favour** the wedge:
- Political: Digital receipt mandates for VAT audits — export packs beat binders.
- Economic: Tighter runway → finance automation survives budget cuts.
- Social: Mobile-first founders; accountant recommendations drive SMB adoption.
- Technological: OCR accuracy crossed usability thresholds; explainable categorisation matters for buyers.
- Legal: GDPR retention and audit trails — immutable export logs become feature, not overhead.
Competitors (COMP-001 … COMP-004)
The demo maps Expensify, Ramp, and a “self” row. The point is not listing logos — it is differentiation:
- Card-first incumbents optimise corporate card spend.
- CompanyExpenses optimises non-card receipt chaos and accountant rework.
Training prompt: For each competitor row, write one sentence: “We win when the buyer cares about ___ more than ___.”
Business Model Canvas (BMC-001)
Three customer segments share one product but different economics:
- Solo founders / freelancers — mobile capture, minimal accounting literacy.
- SMB finance ops teams — policy inbox, NSM dashboard, weekly review under 30 minutes.
- Accountants serving multiple clients — standardised export schema, referral channel into SMB pilots.
Each segment gets its own Value Proposition Canvas slot (VPC-01, VPC-02, VPC-03).
Value Proposition Canvas — SMB finance ops example (VPC-02)
| Block | Example content |
|---|---|
| Customer jobs | Close books without receipt chasing |
| Pains | Six-hour reconciliation loops; late policy surprises |
| Gains | Weekly review under 30 minutes |
| Products & services | Auto-categorised ledger + policy inbox |
| Pain relievers | Xero/QBO export pack removes ~4h rework per close |
| Gain creators | NSM dashboard shows same-day categorisation before period lock |
Training prompt: Pick your primary segment. Can every VPC pain point trace to a backlog story or risk? In the demo, US-002 (auto-categorise) maps directly to VPC-02 pains.
SWOT and ERRC
SWOT captures internal + external at a point in time. ERRC (eliminate / reduce / raise / create) asks what you will stop doing to stand out — e.g. eliminate manual CSV reformatting for accountants; raise confidence transparency on categories.
Personas
Three persona types appear across segments:
- Founder (
PER-U-01) — captures receipts mobile; cares about speed, not accounting jargon. - Finance ops buyer (
PER-B-01) — owns close; cares about policy and NSM. - External accountant (
PER-U-02) — accepts or rejects export packs; cares about schema consistency.
Training prompt: Name one anti-persona (who you will not serve in MVP). The demo implicitly avoids enterprise AP teams needing full ERP.
Customer journey (CXJ-001, CXJ-MAP-001)
Journey maps stage finance ops close: capture → categorise → review exceptions → export → accountant acceptance. The demo’s policy inbox story (US-004) exists because a journey stage (exception review) was missing in v0 tools.
North Star Metric (NSM-001)
Same-day categorisation rate — % of receipts categorised on the day of capture above confidence threshold. It connects founder behaviour (mobile capture) to buyer value (close readiness).
OKRs (OKR-001)
Objectives link NSM to measurable key results, e.g.:
- KR: 85% auto-categorisation accuracy on pilot receipts.
- KR: Three accountant export packs accepted on first submission.
Roadmap and backlog
Roadmap (ROAD-001) sequences initiatives; backlog (INI-001, FEAT-*, US-*) decomposes into user stories with acceptance criteria:
- Must: Mobile receipt scan with OCR (
US-001). - Must: Auto-categorise above 85% confidence (
US-002). - Must: Accountant export pack (
US-003). - Must: Policy exceptions inbox (
US-004).
Training prompt: Every “Must” story should cite a persona or VPC ref. If it does not, it may be scope creep.
Delivery programme (PROG-001)
Q1 plan ties roadmap to cadence: two-week sprints, Friday finance-ops demos, NSM reviewed each sprint.
Brand (BRNDSP-001)
Promise: Audit-ready expenses without the spreadsheet tax.
Tone: Calm, precise, accountant-trusted — not “AI magic” hype.
Proof: Pilot quotes from finance leads; co-marketing with accountant channel.
Naming (NM-001)
CompanyExpenses Tracker — category + audit trail clarity. Rejected names (ExpenseFlow, Receiptly) failed SEO or consumer-tone tests.
Sales and marketing (SLS-001, MKTG-001)
- Sales wedge: Live Xero/QBO export demo in first call.
- Pilot offer: 90-day cohort; success = 85% same-day categorisation + 3 accepted export packs.
- Marketing: Accountant newsletters, finance Slack communities, “spreadsheet tax” calculator lead magnet.
Pricing (PRICE-001)
Per-seat SaaS aligned to finance headcount; export fidelity and policy features justify premium over consumer receipt apps.
Tech solution canvas (TECH-001, TECH-002)
Core bets: OCR pipeline API, mobile client, export job workers, immutable audit log. Dependencies flagged (OCR vendor SLA in PART-ID-1).
Org and talent (ORG-001, TLNT-001)
Q1: contract full-stack on OCR/export; fractional finance advisor for policy UX. Q2: CS lead for accountant channel.
Finance and funding (FINC-001, FUND-READ-1)
Unit economics and runway model feed fundraising readiness checklist — MVP shipped, pilot metrics, export acceptance — before seed narrative.
Compliance and legal (PRIV-001, LEGAL-CHECKLIST-1)
GDPR retention, receipt storage jurisdiction, PIIA for contractors — linked from tech and export stories.
Risk matrix (RISK-001)
Top risks: OCR vendor dependency, low founder adoption of mobile capture, accountant channel slow to refer. Each ties to mitigation in backlog or partnerships.
Customer validation (VAL-Q-001)
Opportunity-solution tree style questions: Which assumptions must be true for NSM to move? What is the smallest experiment this sprint?
Validation report (VALIDATION-REPORT-001)
Summarises evidence from pilot: categorisation accuracy, export acceptance rate, time saved in weekly review.
Critique report (CRITIQUE-REPORT-001)
Structured review of pack coherence — do segments, VPC, backlog, and GTM tell one story? The demo seed is designed to pass traceability gates (market → strategy → execution links).
Training prompt: Run critique on your pack before fundraising or major build commitments. Look for orphan artefacts (canvases nothing references).
Strong strategy design reads as a graph, not a folder of documents:
SCOPE-001 (intake)
→ BRAIN-001 / DNA (direction)
→ PEST-001 / COMP-* (market)
→ BMC-001 (segments)
→ VPC-01..03 (fit per segment)
→ PER-* / CXJ-* (people & journey)
→ NSM-001 → OKR-001 → ROAD-001
→ FEAT-* / US-* (build)
→ VALIDATION / CRITIQUE (evidence)
When you change a segment name in the BMC, downstream refs should update — personas, VPC slots, sales ICP, and backlog “As a …” lines.
In Sculptor, open the library asset graph or journey strip to see whether your project matches this mesh.
This walkthrough follows the startup product path (CompanyExpenses Tracker). The same phase sequence applies to other venture types — only the artefacts and metrics change.
Corporate product
Northvale Systems runs a mandated supplier onboarding portal across plants. Intake scopes ERP-integrated compliance; PESTLE emphasises due-diligence regulation; BMC centres tier-1 suppliers; personas include Supplier Compliance Manager; NSM = % suppliers audit-ready within SLA. Use the seed demo to see structure; swap domain nouns for your internal product.
Startup product
CompanyExpenses Tracker (this article) — B2B SaaS for SMB finance ops. Wedge = accountant export on day one; NSM = same-day categorisation; GTM = accountant channel + finance communities. Seed the demo project to inspect live artefacts.
Service business
Harbor Consulting lean manufacturing diagnostics — no software SKU. BMC emphasises consultant utilisation and referral channels; VPC focuses on plant manager anxiety at proposal stage; backlog is workshops and playbooks, not user stories. Journey maps often show wait time as the main pain between evaluate and buy.
NGO
Clearwater Initiative community water monitoring — grant-funded, community-owned data. BMC segments = villages and district offices; success = on-time tests and repair speed, not revenue; risk matrix highlights volunteer burnout and donor concentration; validation = community can run meetings without NGO staff present.
Training prompt: Pick your venture type, then re-read each phase section above and ask what the equivalent artefact ID would be in your pack.
- Open your organisation workspace → Settings.
- Use Seed demo project (CompanyExpenses) to materialise the full pack in Postgres.
- Walk phases in order (or jump via journey strip) and compare each asset to this article.
- Use Guides in the chat top bar or ⓘ on canvases for technique help.
- Ask Mentor from a guide drawer to question your own version (“Is my VPC aligned with BMC segment 2?”).
Seeding can take up to two minutes — keep the dialog open until completion.
Work through these in your project after reading:
- One-paragraph pitch — Problem, segment, wedge, NSM — no jargon.
- Segment stress test — Remove one BMC segment. What breaks in VPC and backlog?
- Export story — Write acceptance criteria for “accountant accepts pack first try.”
- Anti-persona — Who will you refuse in MVP and why?
- Trace audit — Pick
BMC-001and list five downstream refs; fix any orphan. - Critique dry run — What is the weakest link in your pack today?
- Intake Charter — write your own
SCOPE-001. - Business Model Canvas — segment and economics.
- Value Proposition Canvas — fit per segment.
- Personas — buyers vs users.
- OKR — measurable commitments.
- Validation Report — evidence before scale.
Related techniques
Sources & further reading
- Osterwalder, A., & Pigneur, Y. (2010). Business Model Generation. Wiley.
- Torres, T. (2021). Continuous Discovery Habits. Product Talk LLC.