Sample result
Growth Plan Architect for Restaurants
The owner asked this:«I have already decided: this quarter I raise the lunch ticket and I move the platform orders over to my own delivery. Put that into a calendar that holds.»
① What was decided, translated into deliverables you can see
A decision cannot go into a calendar. A deliverable can.
| What the owner decided | Translated into something observable | The number that confirms it |
|---|---|---|
| «Raise the lunch ticket» | Three written suggestive-sells on Bandeja de la casa, Sancocho de tres carnes and Trucha al ajillo, each with its two-sentence script | Average ticket for the 12:00–14:30 window, Tuesday to Friday, against today's 48,000 COP |
| «Move orders to my own delivery» | One WhatsApp message per order delivered, carrying the own channel and a reason to use it next time | Orders through the own channel over total delivery orders, week by week |
What falls out of the plan: the third location the owner mentioned in passing. It does not move the margin goal within 12 months and it does not start within 90 days. It goes back to the table with a date, not into a drawer.
The yardstick that orders the quarter: across the 4,458 tickets in the month, every 1,000 COP of average ticket is 4,458,000 COP of additional sales. That is not the goal: it is what each fortnight is measured with.
SUPUESTO: the commission the delivery platform charges today comes from the contract the owner has in front of him, not from a sector figure; here it stays as A FIGURE TO CONFIRM. The plan does not depend on its exact value: what decides the fortnight is how many orders migrate to the own channel, not what the platform charges. If the commission turned out lower than the owner believes, the lever still holds —the customer data becomes his— but it drops below the lunch ticket in priority.
② The six fortnights, with fortnight zero on top
| Fortnight | Action | Prerequisite | Owner (role) | Close | Confirming number |
|---|---|---|---|---|---|
| 0 | Sign the standard recipe for the 3 star dishes, with gram weights | — | Chef, location 1 | Day 14 | 3 signed sheets, not 2 |
| 0 | Define which dishes do NOT go out on delivery | Standard recipe signed | Owner | Day 14 | Exclusion list posted at the pass |
| 1 | Write and rehearse the 3 suggestive-sells with the floor team | Standard recipe signed | Floor manager | Day 28 | 6 servers say them without reading |
| 2 | Suggestive-sells live: location 1 only, lunch only | Fortnight 1 closed | Floor manager | Day 42 | Ticket for the Tue–Fri window |
| 3 | WhatsApp message on every delivery order | Exclusion list | Administrator | Day 56 | % of orders through the own channel |
| … |
The rule that holds the table up: two fronts per fortnight and one active lever per owner. With 24 people and one owner, the third front does not run late — it gets abandoned, and it takes the morale of whoever started it with it.
Why fortnight zero exists: growing on top of an operation run by eye spreads the disorder across the whole business. The three suggestive-sells push the three star dishes; if the standard recipe is not signed, each location serves them differently and the suggestive-sell teaches the customer to expect something that does not always arrive. Fortnight zero is not preparation: it is the first fortnight that can fail.
The full example has 1 more part(s): you see them inside the library, with your account.