Diversity and inclusion
The platform works only if hosts of many gathering types and chefs of both professional tiers can use it with equal access and equal dignity.
Access
The ecosystem has to work for more than one kind of table.
Traditional catering has long been expensive and closed. Independent chefs have lacked the infrastructure to reach private clients. Inclusion at Cheffar means opening that access without lowering verification, payment protection, or professional standards.
What we mean
Diversity is who is on the platform. Inclusion is who can operate on it.
Hosts need to book in their own language of gathering. Chefs need storefronts, calendars, and pricing control without being forced through restaurant hierarchies.
Cheffar is an African hospitality platform. That means many cities, many home traditions, and two chef tiers. It does not mean one model dinner for a whole continent.
We publish practices we can keep. Programs we cannot defend do not appear here for appearance.
How we practice it
Main commitments
Four practices we use when we hire, design product, and onboard supply.
Everyday accountability
Bias, feedback, and power are discussed in hiring and product work. They are not reserved for campaign weeks.
Inclusive product design
Booking flows, discovery, and copy have to work for first time hosts, busy planners, Executive Chefs, and Cordon Bleu cooks. Western dinner party defaults are not the product standard.
Language that people recognize
English and French stay at the same quality. Gathering language stays real. Support stays human when a booking is under pressure.
One professional bar and even pay discipline
Roles are graded by the work, not by who is loudest. Labor fees stay labeled. Compensation and chef tiers stay clear. We correct when the numbers show a gap.
Professional access
Two tiers. Equal standing.
Executive Chef and Cordon Bleu name different services. They do not rank people as more or less worthy of trust. Both get the same verification, the same review loop, and the same payment protection.
Screen with a high bar
Who cooks in a home is never a soft rule. Identity, food safety, and professional standards stay high. Taste is not used as a cover for bias.
Hosts of every gathering type
Ceremony mornings, association tables, weekly pots, and plated dinners all belong on the platform. Product language has to hold all of them.
A team that can disagree
Hard debate, respected people. Credit the outcome. Titles do not win arguments.
What we hold
Checks we use before a decision ships
These are operating questions, not posters. We use them when a change might close the platform to someone it should serve.
"Would they still be able to book or list after this decision?"
If the answer is no, redesign the path before it goes live.
"Can hosts and chefs hear themselves in the product?"
Copy and flows should match how people actually gather and cook at home.
"Is the work labeled as work?"
Labor fee stays labor fee. Dignity is not a bonus feature.
Help keep the platform open
If you care about independent chefs, fair access for hosts, and honest inclusion in product, payments, operations, design, or growth, tell us how you work.