Meal Planner

How it works

What Meal Planner actually does once it is running.

Everyone votes, all week

Each member casts their own votes — say "tacos this week" and yours is counted, one per person per dish. A Saturday heads-up shows the standings, and a Sunday last call names who still hasn't voted.

Sunday sets the menu

At 5pm the ballot closes and next week's dinners are planned from it — favorites first, nothing repeated too soon, the weekend project dish saved for the weekend — and a fresh ballot opens for the new week.

4pm answers the question

Late afternoon, tonight's meal arrives with its ingredients and the recipe link, so the 6pm "what's for dinner" conversation already happened.

What you'll have

The point of running it — not the features, the result.

A week of dinners the whole household chose — dish photos on the cards, not a wall of text.

No more planning night — the rotation runs itself from the ballot.

The ingredient list and recipe link in your pocket before the store, not after.

What's inside

A template is a complete system, not a blank document with a nice name.

Its data, already modelled

Collections with the right fields, relations and views for the job — ready for your records the moment it installs.

Its automations, already wired

The workflows that keep it current, with their triggers configured. Turn them on and they run.

Its own agent

A specialist scoped to this Wapp that knows its data and tools, reachable from the same chat you use for everything else.

Yours to reshape

Add a field, change a rule, or restyle the app by describing the change. Templates are a starting point, not a cage.