How we operate the platform
Culture at Cheffar is the standard we use to hire, build, and ship product for hosts and independent chefs. It is not a slogan for a stage.
Operating culture
Every decision has to work in a real home kitchen.
We build a two sided hospitality platform. Hosts need a chef who can take over shopping, cooking, and cleanup. Chefs need digital tools to book, price, and get paid. Culture here is what still holds when both sides depend on the product at the same time.
How decisions get made
Start with both sides of the ecosystem.
A useful debate always includes the host and the chef. If a change only helps our internal metrics and leaves the booking harder to complete, it is not ready to release.
We keep the argument rigorous and the people respected. Weak work is not excused by warmth. Credit the outcome, not the loudest voice. Host product, chef product, payments, and support share one standard.
Titles do not win. Clarity does. A junior note that makes a booking safer can outrank a senior idea that only sounds impressive in a meeting.
What we optimize for
Three habits you will feel in the work
Product
Build for the private kitchen
We are not building restaurant theater. Hosts need a chef in their own home. Chefs need storefronts, calendars, and pricing control. If a feature only works in a demo, keep going until it works under real service pressure.
Clarity
Write so a host can act without a glossary
Labor fee and market budget stay labeled. Payment protection, chef tiers, and next steps stay plain. Product, support, and policy use the same register. If a line needs extra explanation, rewrite it before it goes live.
Trust
Never trade verification for volume
A booking puts a chef in another family’s house. Identity checks, food safety review, two sided ratings, and protected payments are the job. Growth does not outrun that duty, even when a chart makes it look easier.
Homes trust us with the room where family is fed. We treat that as the whole job.
In the room
Lines that actually get used
These are operating questions, not wall slogans. They end a review or open a hard conversation.
“Would you leave this alone in your mother’s kitchen?”
If the answer is no, the chef, the product, or the process is not ready.
“Is the host still in the room with their guests?”
If the host is still running the kitchen, we did not deliver zero stress hospitality.
“Prefer the short line.”
Clarity beats clever copy. Fees, timing, and next steps have to be obvious.
“One standard for both sides of the platform.”
Host product, chef product, and support share the same bar for quality and care.
Who thrives
You will like it here if infrastructure still matters after the meeting
People who thrive here care about independent chefs, protected payments, and homes that stay private. If you want costume Africa, loud hype, or credit before the work ships, this will feel quiet in the wrong way.
Come build the operating standard
Product, payments, operations, design, and growth. If you want work that scales private hospitality across Africa, tell us how you move.