Skip to content

Inclusive Practices for Community Finance

How to build community finance systems that welcome everyone


Community finance is supposed to be for everyone. That is the point, alternatives to extractive financial systems, built by and for communities. But too often, community finance ends up serving the same people who are already served well: those with technical knowledge, social capital, financial cushion, and time.

Exclusion happens not because communities are unwelcoming, but because default designs exclude. The tech-heavy onboarding process excludes those without technical skills. The evening meetings exclude those working night shifts. The jargon-filled discussions exclude those new to the space. The informal networks, which depend on who you already know, exclude those outside the existing community.

In East Africa and the Horn of Africa, exclusion from formal financial systems is already a lived reality for millions of people. Informal saving mechanisms like chamas in Kenya, iqqub in Ethiopia and Eritrea, or hawala networks have long served communities that banks refuse to touch. These systems work because they were designed by communities, for communities. Your community finance system must do the same, not replicate the exclusions of banks while claiming to be different.

Intentional inclusion is not just ethical. It is practical. A community finance system that only serves the already-privileged is not regenerative. It is just a smaller, more niche version of the extractive systems it claims to replace.


Inclusion is not one thing. It operates across multiple dimensions:

Can people with limited financial resources participate?

  • No minimum deposits or membership fees, or use a sliding scale
  • Alternative contributions accepted, time, skills, care work, not just money
  • Small transaction minimums, allow one-hour timebank trades, not just large exchanges
  • Access to community funds, if you have them

Can people with limited technical knowledge participate?

  • Low-tech options, not everyone can use a wallet. Can they participate through a trusted friend, a simplified interface, or even paper records for small amounts?
  • Jargon-free communication, explain terms, do not assume knowledge
  • Patient support without condescension

Can people with limited time participate?

  • Flexible meeting times, rotate between morning, afternoon, evening, and weekend
  • Async participation, not everyone can attend meetings. Allow input through written proposals, group chats, or recorded updates
  • Variable commitment levels, not everyone can be a core member. Create meaningful roles for casual participants

Can people from different backgrounds participate?

  • Neutral, accessible spaces
  • Culturally appropriate events, food, language, and norms matter
  • Explicitly welcoming, do not assume people know they are welcome. Tell them

Can people with disabilities participate?

  • Physical accessibility where possible
  • Clear language, written materials, processing time
  • Quiet spaces, written agendas, permission to step out

Words signal who belongs and who does not.

Do:

  • Use plain language in all communications
  • Define technical terms when you must use them
  • Offer translations if your community is multilingual
  • Ask: “Is this clear?” and actually wait for the answer

Do not:

  • Use jargon without explanation, terms like “gas fees,” “rug pull,” or “DeFi” need defining
  • Assume everyone knows the context
  • Talk over people’s heads
  • Dismiss questions as basic

Not everyone enters the same way. Create options:

  • In-person onboarding for those who prefer face-to-face
  • Digital onboarding for those comfortable online
  • A buddy system pairing newcomers with existing members
  • Graduated engagement, start low commitment, increase over time

Default practices center whoever designed them. Rotate:

  • Meeting times: morning, afternoon, evening, weekend
  • Event types: social, educational, working, celebratory
  • Decision spaces: formal meetings, informal conversations, written input
  • Leadership roles: different people facilitate, organize, represent

Do not assume people know they are welcome. Say it directly:

  • “This is for anyone interested in local exchange”
  • “No experience necessary”
  • “All are welcome regardless of background”
  • “We value diverse perspectives”

And mean it. Inclusion requires intention, not just words.

Make inclusion visible:

  • Track who is participating and who is not
  • Ask about barriers directly: “What is preventing you from participating more?”
  • Address patterns, if certain groups are consistently absent, find out why
  • Name inclusion as a value and measure it

Inviting diverse people but not changing power structures. True inclusion means sharing power, not just having diverse faces in the room.

Designing for a hypothetical average person who does not exist. Multiple options beat single defaults every time.

Expecting excluded people to educate others, do inclusion work, or represent their entire group. This is labor. Compensate it or redistribute it.

Retrofitting accessibility is expensive and incomplete. Design inclusively from the start.

Counting heads is not enough. Do people feel valued? Do they contribute? Do they stay?


Not everyone understands economics, tokens, or accounting.

Solutions:

  • Financial education as a core offering, not an add-on
  • Paired transactions, walk people through their first trades
  • Simple interfaces that hide complexity until users are ready

Wallets, keys, blockchain, these can be intimidating, especially for people who have never used a smartphone for financial transactions before.

Solutions:

  • Custodial options for those who cannot manage their own keys yet
  • Trusted intermediaries who can help
  • Low-tech alternatives, paper ledgers or verbal agreements for small transactions while people learn
  • Visual, step-by-step guides in local languages

Those most excluded from traditional finance often work multiple jobs, run households, or have extensive care responsibilities. Asking them to attend evening meetings or spend hours learning new technology is a significant ask.

Solutions:

  • Async participation options, do not require real-time attendance for meaningful input
  • Value time contributions equally to money
  • Low-time-commitment roles for those with less availability
  • Remember that “free” time is itself a resource, people with more of it should not dominate

Those harmed by extractive financial systems, banks that refused them service, predatory lenders, institutions that dismissed their communities, may distrust any financial system, including yours.

Solutions:

  • Start with small, bounded interactions with low stakes
  • Build relationships before transactions, trust is the foundation
  • Be radically transparent about how the system works
  • Acknowledge historical harms openly, do not pretend the financial system has not failed many of the people you are trying to serve
  • Show, do not just tell, demonstrate trustworthiness through consistent action over time

Beyond practices, culture matters:

  • Name exclusion when you see it: “I noticed we just used a lot of jargon. Let me translate.”
  • Welcome questions, no question is too basic
  • Correct condescension: “That is not a dumb question. It is a good one.”
  • Celebrate diversity, different perspectives make the community stronger
  • Iterate, inclusion is a practice, not a destination

Beyond culture and individual practices, think about your systems:

Decision-making processes: Are they accessible to people who cannot attend meetings? Do they value different kinds of input, not just the loudest voice in the room?

Contribution tracking: Are you capturing all the ways people contribute, not just the ones that look like traditional financial participation? Someone who organizes childcare during events is contributing as much as someone who makes a large deposit.

Conflict resolution: Who handles disputes? Is the process accessible to people with different communication styles and backgrounds? Are there language barriers that prevent people from raising concerns?

Onboarding: Is there a clear, low-pressure process for new people to join? Do they know what to do after their first event? Is someone checking in with them?


Ask yourself regularly:

  • Who is participating? (Demographics, without being invasive)
  • Who is not? (Who is missing from the room?)
  • What barriers exist? (Ask directly, do not guess)
  • Do people feel valued? (This is different from participation, feelings matter)
  • Do diverse voices actually influence decisions? (Observe who speaks up and who gets heard)

Look at your last community event or meeting through the eyes of someone who has never been. Ask yourself:

  • Would they know when and where it was happening?
  • Would they understand the language used?
  • Would they feel like they belonged?
  • Would they know what to do to participate?

Then fix the one thing that stands out most. Start there.


Inclusion is not a box to check. It is an ongoing practice. There is no destination where you have arrived and the work is done.

Start by asking: who is not here that should be? What barriers might they face? What would make this space genuinely work for them?

Then act on what you learn. Come back and ask again. The work is never done, and that is the point.


  • Inclusive community design principles
  • Equity in economic systems and community finance
  • Accessibility guidelines for community organizations