Why now

Expand from expense to procurement workflow

Current position

We already control card spend, receipt capture, approval routing, and policy analytics. Procurement is the adjacent workflow where customers currently lose visibility.

  • 42% of enterprise customers still run vendor requests outside the product
  • Finance teams want spend before commitment, not only after payment
  • Existing approval engine can be reused for purchase requests and PO review
Expansion revenue at risk$6.2M
Customers requesting procurement31%
Median tooling sprawl3 apps
Projected win rate lift+9 pts
Decision needed: pursue platform expansion

Opportunity

Customer problem in one frame

Observed gap

Expense controls happen after spending. Procurement controls happen before vendors are selected, budgets are committed, and legal review is skipped.

  • Budget owners cannot see incoming requests early enough
  • AP teams still reconcile off-platform approvals
  • Procurement teams want request intake without rolling out a heavyweight suite

Initial wedge

Start with software and recurring services purchases under $25k, where approval routing is more important than complex sourcing workflows.

Scope: request, approve, vendor visibility, PO handoff

Strategy

Three-phase rollout

Phase 1

Purchase request intake, approval routing, vendor fields, and budget checks. Reuse policy engine and Slack approvals.

Phase 2

PO generation, vendor onboarding checklist, and contract metadata capture for finance and legal teams.

Phase 3

Procurement analytics: committed spend, vendor concentration, renewal exposure, and approval cycle time.

Reuse > net new where possible

Risks and tradeoffs

Where expansion can go wrong

  • Too much procurement depth too early turns the wedge into a suite rewrite
  • Legal and security reviewers may expect richer vendor risk workflows than phase 1 supports
  • Sales positioning must stay simple: "control commitments before spend" not "full source-to-pay"
Main execution riskScope drift
Main GTM riskMessaging dilution
Main technical leverageApproval engine
Main moatUnified spend graph
Mitigation: tight wedge + named non-goals

Decision

Recommendation: yes, with a narrow wedge

Approve if

  • Phase 1 stays limited to request, approval, and visibility
  • Two design partners commit to weekly feedback during build
  • We keep vendor risk and sourcing out of v1

Do not proceed if

  • The market demands full sourcing depth immediately
  • Phase 1 cannot reuse approval and policy primitives
  • Sales cannot explain the value in one sentence
Final call: fund discovery + wedge build
Speaker notes
Stress adjacency, not reinvention. Keep wedge small. Decision slide should end discussion, not restart scope debate.
Hosted onPagrยทShare your HTML files