I’m six months into Beancount. Built a practice setup (chart of accounts, importers, scripts). Starting to get clients. But when I pitch them, they ask: “are you trained? Do you have credentials?” I say “I know Beancount well,” but they want proof.
This is different from saying “I’m a CPA” (3 years of study, credential, regulatory backing). Beancount has no equivalent. So I’m thinking: would a “Certified Beancount Practitioner” credential help? Something that signals competence without the years/expense of CPA?
Or would that be bad for the community (gatekeeping, commodifying knowledge)? Looking for perspective from people further along. If you run a Beancount practice, do clients ever ask for credentials? How do you prove competence?
Certification would be a mistake. It would gatekeep knowledge, let someone profit off community work (who owns the cert program?), and create false sense of standardization (every practitioner’s setup is different). Beancount’s strength is flexibility. A credential encourages homogeneity.
Better: build a portfolio (show 3 clients’ work), get testimonials, be transparent about your skills (I’m strong in importers but new to Python automation). Clients can see what you’ve done.
Real question: did clients hire you because you had a credential, or because you could solve their problem? Most small clients care about results, not letters after your name.
CPA took me three years (study, exam, ethics course, continuing education). Expensive ($5K+), time-consuming, worth it for signal to the market. But Beancount isn’t in that space. You’re competing on competence, not credentials. If a client wants “certified accountant,” they probably want full-service firm (audit, tax strategy), not plain text bookkeeping. Know your market. A credential won’t help you there.
What if instead of one certification, community maintained case study templates (show how you handled multiurrency, complex recon, script automation) that practitioners could point to? “I’ve solved these problems,” without formal gatekeeping.