From Dining Tables to Data Tables: Why I'm Building AllergenIQ
Every week, someone in Australia has a severe allergic reaction to food they thought was safe. Restaurants do their best — but managing allergen information across a full menu, across multiple suppliers, across rotating specials, is genuinely hard. A spreadsheet here, a laminated sheet there, a chef's memory filling in the gaps.
I kept seeing this problem. And I decided to do something about it.
The Idea: AllergenIQ
AllergenIQ is a restaurant allergen matrix system — a platform that lets restaurants in Sydney (and eventually across Australia) map, manage, and communicate allergen information clearly, accurately, and in real time.
The core product is simple in concept: a dynamic allergen matrix that links every dish to every ingredient, flags the 14 major allergens, and surfaces that data to both kitchen staff and diners. Behind the scenes, it handles the complexity — supplier ingredient changes, menu updates, cross-contamination risk — so the front-of-house experience stays clean and confident.
The goal isn't just compliance. It's trust. A diner with a nut allergy should be able to sit down at any restaurant and feel genuinely safe, not just reassured.
Building in Sydney
Sydney is a brilliant city to launch a food-tech startup. We have one of the most diverse dining scenes in the world, a tech ecosystem that's maturing fast, and a community that genuinely cares about food culture and inclusivity.
But it's not without friction.
The restaurant industry here runs on thin margins and long hours. Getting a time-poor head chef or a small business owner to adopt new software — even software that clearly helps them — is a real sales challenge. You're not just selling a product. You're asking someone to change their workflow during the busiest hours of their day.
Regulatory complexity adds another layer. Australian food labelling law is strict, and rightly so. Understanding how to build a product that helps businesses meet their obligations without drowning them in legalese has been one of the most interesting design challenges so far.
Why I'm Doing This Anyway
Because the problem is real, the risk is real, and the existing solutions are nowhere near good enough.
I started this because I care about it — not because it was the obvious next career move. There's something about building something that could genuinely prevent harm that makes the hard days feel worth it. When I picture a parent of an anaphylactic child actually being able to trust a menu — that's the motivation that gets me back to the laptop at 11pm.
There's also a personal thread here. Navigating food restrictions, watching friends or family have to quiz waitstaff and then still feel uncertain — that experience is more common than people realise. AllergenIQ is the product I wish already existed.
The Study-Work-Startup Juggle
If you're reading this thinking "how does anyone do all three?" — genuinely, some days I'm not sure either.
I'm currently balancing coursework, a part-time job, and building AllergenIQ from scratch. The calendar is tight. Sleep is negotiable. Priorities shift constantly.
What I've learnt: ruthless focus wins over maximum hours. I can't out-grind a full-time founder, but I can be more deliberate about which problems actually need solving right now. The startup brain wants to boil the ocean. The student-worker brain has to pick the smallest pot.
The flip side is that studying while building is genuinely additive. Concepts from class land differently when you have a real product they apply to. And working part-time keeps you connected to how organisations actually function — which shapes how you design for them.
The Tech Underneath
AllergenIQ is being built with scalability in mind from day one. The allergen matrix isn't just a table — it's a relational data model that handles complex ingredient hierarchies, sub-recipes, and real-time supplier updates. The vision: a supplier updates an ingredient, the matrix flags affected dishes, the kitchen team gets an alert, and the menu display updates instantly.
Longer term: AI-assisted allergen detection from recipe text, POS integrations, and a consumer-facing layer so diners can filter menus by their allergen profile before they even walk in the door.
The principle is fixed: data integrity over flashy features. In this space, being wrong is not an option.
What's Next
Right now I'm in early validation — speaking with restaurant owners, kitchen managers, and allergy advocates across Sydney to make sure I'm solving the problem they actually have, not the one I imagine they have.
If you run a restaurant, manage a kitchen, or live with food allergies and want to help shape AllergenIQ — I'd love to hear from you.
This is just the beginning. But every great product started as someone frustrated enough to build the thing themselves.
Follow along as I build AllergenIQ — the challenges, the wins, and everything in between.