Persona — CFO

The CFO is persona #3 in the Six Personas framework. They often don’t show up to the first meeting — but they’re always in the room at final approval. The CFO is not a bean counter; they’re a risk manager whose job is to protect the business.

Unknown block type "horizontal-rule", specify a component for it in the `components.types` option

Who They Are

  • The reality check to the CEO’s vision
  • Has probably seen failed software projects before — and remembers them
  • Operationally conservative: not trying to kill deals, but will pressure-test everything
  • Often closely aligned with the VP of Supply Chain (both are operational, conservative, outcomes-focused)
  • Controls budget and budget exceptions
Unknown block type "horizontal-rule", specify a component for it in the `components.types` option

What They Care About

  • ROI — specific, measurable, time-bounded return on investment
  • Cost to implement — total cost including internal resources, not just license fees
  • Working capital impact — how does this affect cash flow timing?
  • Cost-to-serve reduction — automating manual order entry, reducing error costs
  • Risk reduction — less manual process = less exposure to errors and pricing mistakes
  • Visibility — more data to manage the business with
Unknown block type "horizontal-rule", specify a component for it in the `components.types` option

What They Fear

  • Committing budget to a project that doesn’t deliver measurable results
  • Pricing errors that expose the company to financial or customer relationship risk
  • Projects that balloon in cost after signing (scope creep)
  • Being unable to show the board/CEO a clear ROI story
Unknown block type "horizontal-rule", specify a component for it in the `components.types` option

How to Speak Their Language

Do:

  • Build a clear business case with specific financial levers
  • Quantify reduced order entry costs ($/order × volume)
  • Show cash flow improvement from faster digital payments
  • Frame automation as margin recovery, not just efficiency
  • Show how you reduce risk (fewer manual touchpoints = fewer errors)

Don’t:

  • Pitch features — pitch levers
  • Use vague language like “improved efficiency” without numbers
  • Ignore total cost of ownership (TCO); they’ll find it themselves
  • Underestimate how much they talk to the VP of Supply Chain

Key financial levers to use:

  • Reduced order entry costs
  • Fewer pricing/fulfillment errors
  • Better cash flow from faster digital payments
  • More margin from automation
  • Lower cost-to-serve per customer

Key framing:

“You’re not buying software. You’re gaining control — over costs, errors, and visibility.”
Unknown block type "horizontal-rule", specify a component for it in the `components.types` option

CFO + VP Supply Chain Alliance

In many organizations, the CFO and VP Supply Chain are closely aligned — both operational, both conservative, both focused on making the machine run better. Position messaging that speaks to both simultaneously:

“Our solution will reduce inventory carry costs by improving order accuracy.”
“We’ve helped companies like yours shave 2% off logistics spend while improving fill rate.”