About
One builder, and someone to break it.
I'm Muhideen. I designed and built Menuraq end to end — the menu engine, ordering, POS, kitchen operations, the multi-tenant data model, and the security that keeps every branch's data separate.
- Based in
- Accra, Ghana
- Writing code since
- 2020
- Building Menuraq since
- 2024
How it happened
Weeks in
A menu on a phone
QR code on the table, prices that change without a reprint. The small, obvious problem.
Then
The menu got asked to do more
If a guest can see it, they want to order. If they order, the kitchen needs it. If it's ready, the counter needs to know.
Two years in
One layer underneath everything
Every surface reads the same items, prices and rules. Not five products stitched together — one system, six business types.
Menuraq is two years of the six I've spent writing software. I started with Python in 2020, moved into TypeScript and Postgres as the things I wanted to build outgrew scripts, and have been shipping ever since.
I haven't run a food business, and I don't claim to have. What I've done is spend two years paying attention to people who do, and build against what they told me rather than what I assumed. It's also why Abdul Rahim tests it as an owner would — after two years you stop being able to see your own product.
What I build with
- TypeScript
- Python
- Next.js
- PostgreSQL
- Supabase
- Row-level security
- Offline-first sync
- Idempotent writes
- Multi-tenant architecture
- Mobile money payments
How I decide
Four rules I actually use
Adapt to the venue
A caterer shouldn't translate 'table' into 'event' in their head. The system should already say 'event'.
Proof over claims
No invented metrics, no borrowed credibility. If I can't point at the thing, I don't say it.
Build for the bad day
Power cuts and dead networks aren't edge cases here. They're the design brief.
One module understood beats five ignored
Depth an owner actually uses is worth more than a feature list they never open.
Connect