A useful place to start

Five questions.
One conversation
your team needs to have.

Answer on your own. Ask product, engineering and revenue to do the same. Compare the answers. Choose one disagreement to investigate.

Answers stay in this tab. Download a copy to keep them.

01 / Expansion

What increases a customer’s bill without a new negotiation?

Look for actual seat, usage or module expansion. “Our account manager asks” is a different mechanism.

02 / Buyer and user

Who uses the product, who pays, and what does each need to see?

Name the operator, champion, approver and economic buyer. They may be the same person.

03 / First value

What must happen before the first useful outcome?

Include migration, configuration, approvals and other people’s work. Use observed time, not the best case.

04 / Retention

What would a customer need to rebuild or give up to leave?

Look for workflow dependency, accumulated data, switching work or real network value.

05 / Market fit

Which segment can adopt the product as it exists today?

Separate customers you can serve now from accounts that need a different product.

A completed example: first value +

Our answer: “A user sees value in their first session.”
Evidence: Five onboarding calls included a data import. The first useful report arrived between days 8 and 14.
Another team’s answer: “They need an administrator to connect the data.”
What we need to check: Time to first useful report, by customer segment, over the last ten accounts.

This illustrative example starts a decision: shorten the setup, guide the onboarding, or choose a motion that can support it.

Choose one discrepancy
to investigate first.

Your answers are not sent to us. This exercise begins the diagnostic; the full frameworks cover ten Product DNA dimensions and eight GTM DNA components.

Keep connecting the dots.