How the team runs
Every pod works toward one number: revenue per transacting customer. First value is where it starts.
A sign-up is a promise. First value is proof. Until value lands, the customer hasn’t experienced the product. They’ve experienced the paperwork.
First value is the moment the product first proves itself. For a merchant, it’s the first payment. For a developer, the first successful API call. For a platform, the first payout.
The org is designed around first value as its first milestone. A customer who reaches first value once and leaves costs a full acquisition cost for a single transaction. So the engine keeps going past it, toward retention, a second product and a referral.
Activation over acquisition. Fixing the path to first value compounds every channel. Buying traffic into a leaky path compounds the leak.
Depth over breadth. A customer on three products is worth more, stays longer and costs nothing to re-acquire.
Every plan starts with a customer profile. It says what kind of business this is, how it buys and operates today, and what it needs working this week.
One funnel for everyone is the wrong unit. Different profiles reach first value by different paths.
Profiles also decide the adoption path. They say which product comes second, and when.
The customer sees six moments. Three pods and one system work under each.
| Discover | Sign up | First value | Adopt | Expand | Advocate | |
|---|---|---|---|---|---|---|
| Customer does | Looks for a way to accept payments | Creates an account and completes verification | Completes the first real transaction and sees it land | Keeps balances on the platform, pays suppliers and payroll, puts spend on cards | Takes credit to grow, moves more volume | Recommends the product to another business |
| Customer asks | “Can I trust them?” | “Is this built for a business like mine? How long will this take?” | “Did it work?” | “Can this run more of my business?” | “Can you help me grow?” | “Is it worth recommending?” |
| Touchpoints | Press, creators, content, search and AI answers | Website, pricing, docs, sign-up and verification flow | Dashboard, API, the first transaction | Dashboard, in-product offers, lifecycle emails | Credit offers, product launches | Referral program, customer stories, reviews |
| Line of visibility | ||||||
| Brand & Communications | Earned media, creator partnerships, content, claims review | Brand consistency on every page | Launch PR | Customer stories, word of mouth, community | ||
| Product Marketing | Customer profiles, positioning, competitive intelligence | Pricing and packaging, messaging, onboarding copy | Adoption-path positioning, in-product messaging | Next-product positioning, launch tiers, sales enablement | Case studies | |
| Growth | Paid, SEO and answer engines | Landing-page, sign-up and verification experiments | Time-to-first-value tracking, activation nudges | Attach triggers, lifecycle experiments | Eligibility-triggered offers, expansion experiments | Referral program mechanics, referred-cohort tracking |
| Line of internal interaction | ||||||
| The system | Canon: customer profiles, approved claims, product status. Skills. Gates. Experiment loop. Measurement and attribution. Unit economics: CAC payback, LTV:CAC by channel. | |||||
| We watch | Earned coverage, organic reach | Qualified sign-ups, cost per sign-up, sign-up-to-activation | Time to first value | Products per customer, month-N retention | Revenue per transacting customer, net revenue retention | Referral rate, referred-customer share of sign-ups |
| referred customers arrive with trust | ||||||
Advocate returns to Discover: referred customers arrive with trust.
Each pod owns one reason a customer drops out before first value. They don’t trust us. They don’t think it’s for them. Or it takes too long.
Trust risk
Relevance risk
Friction risk
Fintech is built on code, but it lives or dies on clarity and credibility.