In short: your community is the practitioners who advise your segment and the customers willing to be named; give them a job, pay them openly, and measure referred funded accounts.
Key points
- The first hundred should be eighty practitioners who advise your segment and twenty customers willing to be named.
- A practitioner programme has four parts: education, early access, a direct line to a named person, and disclosed payment.
- A hidden referral fee becomes a trust problem the day it surfaces; a disclosed one is how the market works.
- No incentivised reviews, no unsubstantiated testimonials, and nothing that reads as an unapproved financial promotion.
- Measure referred funded accounts by practitioner and channel, with 90-day and 365-day retention.
Who the community actually is
Part 21 set out the order buyers check: who's behind it, who holds the money, who else like me. The third question is answered by people, not copy.
In fintech those people fall into two groups. Practitioners: accountants, bookkeepers, advisers, fractional finance leads, payroll bureaus. And users: the treasury team, the SMB owner, the operations manager who lives in your product.
Neither group wants a server to hang out in. They want to look competent in front of their clients and their boards. Your product either helps with that or it doesn't.
So drop the word community if it leads you to build a chat room. Build a vouching system instead.
The job, Part 5 applied
Part 5 said give the community a job before you count it. In fintech there are three jobs, and they are measurable.
Referrals. A practitioner who recommends you to a client is the cheapest route to a funded account you will find. Part 23 covered the channel economics. Here the point is the relationship behind the number.
Product feedback from power users. A treasury team that reconciles daily will find your edge cases before your QA does. An SMB owner will tell you what the onboarding form got wrong. Both are worth more than a survey.
Public trust signals. Reviews on the platforms your segment reads. References you can hand to a procurement team. Complaints answered in public, quickly.
Each job gets an owner, a cadence and a number. That is the whole difference between a community and a mailing list.
The first hundred, fintech version
Part 6 described the first hundred as people chosen on purpose. For fintech the composition is specific.
Eighty practitioners who advise your target segment. Not followers. People who sit with your customers and are asked "what should I use for this?"
Twenty customers willing to be named. Named means a logo, a quote, a reference call, or a case study with a real number in it. Each of the twenty should map to one of the beliefs from Part 21's claims register.
Recruit the practitioners first. A practitioner who already trusts you brings the named customers with them.
The practitioner programme
A practitioner programme has four parts. Keep it that simple.
Education. Short, useful sessions on the problem, not the product. How to run client treasury. What changes when a client crosses a payment threshold. Practitioners share things that make them look sharp.
Early access. Let them see the feature before their clients ask about it. It costs you nothing and turns them into the person who knew first.
A direct line. One named person they can message when a client is stuck. Not a ticket queue. This single thing does more than any incentive.
Payment. Pay per funded account if you choose to, and disclose it to the client every time. A referral fee that is hidden becomes a trust problem the day it surfaces. One that is disclosed is just how the market works.
For SMB and institutional products, add a user advisory group. Six to ten customers, quarterly, with a roadmap in front of them. They tell you what to build. You tell them what you decided and why.
Reviews and complaints as infrastructure
Review platforms are part of the vouching system whether you manage them or not. Someone will check. Claim the profile, respond to every review, and ask satisfied customers to post without offering anything for it.
Complaint handling is the other half. A complaint answered in public, within hours, with a clear fix, is a trust asset. A buyer reading it learns how you behave when it goes wrong. That is the fourth question in Part 21's order, answered by evidence.
Build the process before you need it. Who sees the complaint, who answers, how fast, what they are allowed to say.
The lines you don't cross
Some things make a community asset into a liability overnight.
No incentivised reviews. A discount for a five-star review is a disclosure failure at best and a breach at worst.
No testimonial you cannot substantiate. If a named customer says they saved a number, you need the number in a file.
Nothing that reads as a financial promotion without the required approval. A practitioner's post about your yield product may be a promotion in your regulator's eyes. Give them approved wording and a review step.
Then measure the thing that matters: referred funded accounts, by practitioner and by channel, and their 90-day and 365-day retention. Referrals that fund and stay are the only proof the community is doing its job.
The checklist
- [ ] List the eighty practitioners who advise your segment and the twenty customers willing to be named
- [ ] Give each of the three jobs (referrals, feedback, trust signals) an owner, a cadence and a number
- [ ] Write the practitioner programme: education, early access, a direct line, disclosed payment per funded account
- [ ] Stand up a user advisory group for any SMB or institutional product
- [ ] Claim review profiles and write the public complaint-handling process before the first complaint
- [ ] Report referred funded accounts and their 90/365-day retention monthly
Common questions
How should a fintech company build a community?
Build a vouching system of practitioners, such as accountants, bookkeepers and advisers, and named customers. Give it three measurable jobs: referrals, product feedback and public trust signals.
Should fintechs pay accountants or advisers for referrals?
You can pay per funded account, but disclose it to the client every time. A hidden referral fee becomes a trust problem when it surfaces.
Can I offer customers a discount for a five-star review?
No. An incentivised review is a disclosure failure at best and a breach at worst. Ask satisfied customers to post without offering anything.
What metric shows a fintech community is working?
Referred funded accounts, by practitioner and channel, and their 90-day and 365-day retention.