Company

Built from real restaurant shifts

We are restaurant people first. That Menu App grew out of the questions, bottlenecks, allergy conversations, translation gaps, and staff training problems we have lived through on the floor.

Our story

The idea started in 2013, while serving tables and watching guests struggle with the same menu questions shift after shift. Menus were still treated like static documents, even though guests needed a flexible guide and staff needed a reliable source of truth.

Development began in 2015 with a simple goal: turn the menu into a living database that could help guests decide, help staff answer accurately, and help operators keep changes from getting lost between the kitchen, floor, website, and printed materials.

Today, we are still building from that same operator lens. If a feature does not reduce real shift friction, improve clarity, or protect hospitality, it has to earn its place.

Restaurant-first

Built by people who have worked across dish, bus, serve, bar, and management roles.

2013 spark

A table-service problem became the idea for a smarter menu system.

2015 onward

We started building around the realities of service, not generic software workflows.

Why we built it

The problems we are solving every day

That Menu App is not another generic restaurant tool. It is our answer to the everyday friction that slows service, overloads staff memory, and leaves guests unsure what to order.

Guests need clarity

Guests ask about allergens, ingredients, dietary preferences, removals, substitutions, and translations because they want confidence before they order.

Staff need one source of truth

Servers, bartenders, managers, and kitchen teams should not have to memorize every change or guess where the latest answer lives.

Operators need less busywork

A menu change should not create a chain reaction across PDFs, websites, printed materials, training notes, and staff reminders.

Hospitality still matters

Technology should support the floor, not replace the human connection that makes restaurants work.

Menus should sell intelligently

Pairings, preferences, and filters should help guests find the right choice faster while making upsells feel natural.

Training should survive turnover

Teams need ways to learn the menu quickly without relying on binders, hallway explanations, or whoever happens to be on shift.

Get White Glove Setup Features Watch the videos

How we build

The product is shaped by restaurant reality: rushes, allergies, staff turnover, menu changes, language barriers, and limited operator time.

Practical over flashy

Every feature should make daily menu operations easier for owners, managers, FOH, BOH, or guests.

Low disruption by design

Restaurants are already busy. We build around the way service actually happens and make setup easier with White Glove when teams want help.

Built to protect hospitality

The goal is not to remove people from the experience. The goal is to reduce uncertainty so staff can spend more time being hospitable.

Team

The people building the restaurant tool we wish we had

That Menu App is built by a small team of operators, developers, and growth partners turning real service problems into practical software for restaurants.

Founder / CEO / Developer

Jeremy Hodges

Started the idea from a table-service problem and keeps the product centered on what restaurants actually need during a shift.

Co-founder / Lead Developer

Michael Abraham

Leads core development and helps turn menu data, filters, and ordering context into dependable product infrastructure.

Co-founder / COO

Jason Hodges

Keeps the operational lens sharp, focusing on launch flow, adoption, and making the product easier for restaurant teams to use.

Co-founder / CMO / Developer

Jazek Creacy

Brings marketing and development together so the product story stays clear for operators, staff, and guests.

Co-founder / CSO

Alan Crynes

Helps shape sales strategy and customer fit so restaurants can see where That Menu App can make the biggest difference.