FINANCE & GROWTH / FIELD GUIDE
Which customers actually drive profitable growth?
Connect the data. Check the insight. Approve the action. Measure what changes.
No form to read or download. No booking until you choose a time.
FIRST, AGREE ON THE QUESTION
One person. Two contracts. Three CRM records.
Finance, growth and operations can use different definitions of customer, activation and revenue. A correct count is not useful until everyone knows what it counts.
An illustrative example: three records can describe one person with two contracts. None of those counts is interchangeable. Agree on the entity and time window before comparing teams.
Who defines ‘customer’?- Customer
- Person, account or contract? Resolve duplicate CRM records and name the counting unit.
- Activation
- Account created, first transaction or another approved milestone? State the event and window.
- Revenue
- Recognized, invoiced or collected? Align dates, exclusions and acquisition-cost treatment.
ILLUSTRATIVE WORKFLOW / DEMO DATA
Ask. Check. Act. Measure.
Ask
Join CRM, transactions and acquisition costs. Ask which defined customer cohort merits a growth or margin investigation.
Check
Inspect approved metric rules and the executed query. Verify joins, counting unit, dates and exclusions before accepting the insight.
Act
A human approves a named follow-up or investigation and its owner. Execute through a supported integration, such as Jira, with a scoped task and deadline.
Measure
Monitor execution status and the agreed activation, revenue or margin metric. Schedule an impact review, for example in 14 days; an observed change is not proof of causality.
ACT / HUMAN-APPROVED EXECUTION
Investigate cohort margin · Finance owner
Approval → supported Jira task
Owner, scope and deadline are explicit. Review the executed query before approving.
MEASURE / SCHEDULED IMPACT REVIEW
Review in 14 days (example)
Track task state separately from the agreed business outcome. These are illustrative states, not claimed customer results.
Illustrative workflow. Deployment and supported actions scoped with your team.
DEFINITION / EVIDENCE / LIMITS
One customer. Show the definition.
Attach the entity, approved activation rule, reporting period and revenue basis to the result. Keep the executed query inspectable. If teams use different definitions, show them rather than silently blending them.
Observed changes are not causal uplift. Agree on the evaluation method before claiming an effect.
BOOK A DUKE DEMO
Bring the question. See the workflow.
What counts as an active customer in this cohort? Walk through the definition, evidence, approved execution and review with our team.
Load Calendly only when you choose. The scheduler requests the identity and time slot needed for a reservation. We add no separate qualification form, and do not prefill personal details from a campaign link.
Reading, downloads and booking work without tracking. With an explicit Analytics choice in Cookie settings, PDF requests and demo-button clicks from a campaign link may be noted against its existing recipient in our CRM. Links may be forwarded: this is not proof of your identity. A click is not a demo request or a confirmed booking. Change your choice at any time. Privacy policy
DON'T DASHBOARD. DECIDE.
Book a DUKE demo