NEIRA. AI in the Pizza Business. Volume 1. From the First Idea to Pizza Production: A Practical Guide for Beginners and Experienced Entrepreneurs

In the next chapter, the Beginner will describe the dream of opening a pizzeria, and Neira will help turn that dream into a testable project.

Practical Outcome and Verification Criteria

Create an interaction diagram showing which questions Neira handles, which information may come from operational or accounting systems, and who approves decisions. For every action, identify its data source, responsible person and automation boundary.

Additional Workshop: The First Working Session

The Beginner arrives with the idea for a first pizzeria; the Veteran brings figures from an operating chain. Neira proposes one method for both: define the task, obtain baseline information, check its quality, calculate, choose an action and measure the result. “I do not replace your decisions,” she explains. “I help turn scattered information into a verifiable plan.”

The Beginner describes the city, service format, approximate floor area, budget and timeline. Neira lists missing information and three possible concepts without presenting invented demand forecasts as facts. The Veteran provides anonymised sales, waste, recipes and stock balances. Neira identifies discrepancies and asks what might explain them. Until a real system integration is implemented, the information is uploaded by a person.

Throughout this guide, Neira is a single character and the concept for an independent, industry-specific platform. The dialogues demonstrate a working method, not automation already in operation. Every automated action would require appropriate software, permissions, testing and an audit log.

Chapter 2. The Beginner: “I Want to Open a Pizzeria”

2.1. A Dream That Has Not Yet Become a Project

“I want to open a pizzeria,” said the Beginner. “I love pizza, I see people ordering delivery, and I think: why shouldn’t I try? I’ve even come up with a name.”

“A wonderful starting point,” Neira replied. “But loving pizza does not prove that your business will attract customers or make a profit. Today we are not buying anything or promising anyone an opening date. First, we test the idea.”

Neira opened a blank project profile. “Let’s separate what you know from what you assume. You will need an accounting or management system later, but a sound data structure is useful from the outset. I can help you organize information and questions. This is a teaching scenario for a proposed future solution, not a claim that an integration already exists.”

The Beginner admitted that he had wanted to choose an oven, order an attractive sign, and find a pizza chef immediately. Neira suggested a different sequence: customer → demand → format → product → production model → premises → equipment → finances. Reversing that order could lead to expensive rework.

Practical action. Describe your idea in one sentence: “We make [what kind of pizza] for [whom] in [which area], through [which channels], at [which price level].” If there are blanks, do not conceal them behind appealing language: identify them as hypotheses.

2.2. The First Conversation: Who Needs Your Pizza?

“Who is your customer?” Neira asked. “Everyone in town,” the Beginner answered confidently. “Then you have not yet identified anyone in particular,” Neira observed. “We need customer segments, purchasing occasions, and reasons for choosing you.”

Neira suggested at least three scenarios: an evening family order; a lunchtime order near offices; and a weekend order for a group. For each scenario, investigate desired delivery speed, pizza size, typical order value, menu expectations, and purchase frequency. Do not assume one segment’s preferences apply to everyone.

A segment profile includes: location and service radius; reason for ordering; expected fulfillment time; estimated orders per week; typical basket; competitors’ alternatives; selection criteria; and a way to test the hypothesis. Record the source separately: observation, interview, public information, or assumption.

Assignment for the Beginner. Conduct at least 15 short interviews with potential customers from different segments. This is an initial learning target, not a statistically representative sample. Ask about their most recent actual pizza purchase, rather than merely whether they intend to buy from you. Record answers without reshaping them to fit your idea.

2.3. Choose the Business Format Before the Premises

“A pizzeria is not a single business format,” Neira explained. “A delivery-only kitchen, a small takeaway outlet, a family pizzeria with seating, and a production kitchen serving several channels require different premises, processes, and investments.”

Compare formats against eight criteria: initial investment; rent burden; accessible customer base; production capacity; staffing complexity; delivery; hygiene and engineering requirements; and expansion potential. Lower rent alone does not make a format superior: consider the complete customer journey and full economics.

Neira suggested a decision table. Each row represents a format; each column, a verifiable criterion, supporting data, and confidence level. She added a production filter: can this format consistently make pizza of the required quality during peak periods?

Outcome: identify the two most promising formats and the conditions under which each makes sense. Make the final choice only after assessing demand, economics, and premises requirements.

2.4. The First Numbers: How Many Orders Will You Need?

“Can we calculate my future profit right away?” the Beginner asked. “We can build scenarios,” Neira replied. “But we cannot present a scenario as a forecast supported by sales that have not happened.”

Illustrative example (all figures and amounts are hypothetical). Average order value: 1,000 monetary units. Variable cost per order, including ingredients, packaging, and variable delivery costs and commissions: 450 units. Contribution margin per order: 550 units. Monthly fixed costs: 660,000 units.

Break-even order volume = fixed costs ÷ contribution margin per order = 660,000 ÷ 550 = 1,200 orders per month. With 30 operating days, that is an average of 40 orders per day. This calculation excludes profit taxes, financing, seasonality, and additional one-off expenses; a real business plan requires a fuller model.

“Forty orders isn’t much!” the Beginner exclaimed. “Not so fast,” Neira cautioned. “An average is not the same as peak demand. If half the orders arrive within a few evening hours, your oven, assembly line, and couriers must handle that peak. You must also demonstrate that the market will provide those orders.”

Test sensitivity: at 30 orders per day for 30 days, total contribution is 495,000 units, giving a result of minus 165,000 units before other items; at 50 orders per day, contribution is 825,000 units, giving plus 165,000 units. Both are illustrations, not profit guarantees.

2.5. How Neira Organizes the Work

Neira identifies production constraints: pizza types; dough, fermentation, storage, assembly, and baking requirements; capacity benchmarks; and quality risks. She does not claim that any chosen recipe will automatically achieve a specified food cost.

In this proposed scenario, Neira helps structure source information, compare scenarios, prepare indicators for future recordkeeping, and identify missing data. Access to actual management-system records and automated data exchange would require separate agreement, interface validation, access permissions, and implemented integration.

Decisions about the concept, investment, and acceptable risk remain with the entrepreneur. When assumptions are disputed, Neira should explain what evidence is needed rather than pretend to be certain.

2.6. What Happens at the Veteran’s Pizzeria on the Same Day

While the Beginner studied the market, the Veteran arrived at his operating pizzeria. “I have everything: premises, ovens, staff, and customers. But at the end of the month, there is hardly any money left. Maybe I just need more advertising?”

“Advertising can increase orders while also increasing losses if each additional order has a negative contribution margin,” Neira noted. “Let’s examine the economics of each sales channel first.”

Neira asked the Veteran to select his three best-selling pizzas and provide their recipe specifications, actual ingredient weights, defects, and waste. She also suggested gathering revenue, order counts, average order value, discounts, refunds, delivery-platform commissions, payroll, and rent for a comparable period. Missing data must not be replaced with invented numbers.

The Veteran learned his first diagnostic rule: do not change prices, recipes, schedules, and advertising all at once. Establish a baseline, choose indicators, and verify data quality first. Otherwise, you cannot tell what actually changed the outcome.

2.7. The Beginner’s Idea Profile

Complete the project profile:

1. Working name and person responsible.

2. City, district, and proposed delivery area.

3. Target customers.

4. Purchasing occasions.

5. Two formats under consideration.

6. Preliminary menu.

7. Expected average order value range.

8. Proposed sales channels.

9. Available investment budget and contingency reserve.

10. Timeline and constraints.

11. Competitors.

12. Sources of information.

13. Untested hypotheses.

14. Date of the next decision.

Label each numerical figure “fact,” “estimate,” or “hypothesis.” Do not give precise amounts when you have only a rough impression. Specify who will collect the information and by when.

Completion criterion: the entrepreneur can explain whom the business will serve, why customers might choose it, which format will be tested first, and what information is still needed before making financial commitments.

2.8. The Veteran’s Diagnostic Profile

Prepare the following information about the operating business:

1. Number of outlets.

2. Formats and sales channels.

3. Period under review.

4. Revenue, orders, and average order value.

5. Cost of goods sold.

6. Discounts and commissions.

7. Waste and refunds.

8. Rent, utilities, and labor.

9. Recipe specifications.

10. Actual ingredient usage standards.

11. Complaints and defects.

12. Peak workload.

13. Availability and quality of source data.

Perfect reporting is not required on day one. What is required is an honest map of what is known, what is missing, and which data contradict one another. Use that map to choose the first area to investigate.

2.9. Workshop: Making a Decision Without Premature Spending

The Beginner must prepare three documents: a one-page concept description; a comparison table for two formats; and a list of market checks and financial assumptions. Until these are ready, do not sign a long-term lease or buy equipment based on enthusiasm alone.

The Veteran must prepare three different documents: a baseline performance summary; a list of production and financial deviations; and a plan to collect missing information. Give priority to checks with a clear cost, deadline, and measurable outcome.

A shared checklist for both: the objective is defined; an owner is named; the period is specified; facts are separated from hypotheses; assumptions are recorded; a validation method exists; and a follow-up date is set.

Review Questions

1. Why should you not choose an oven before choosing the business concept?

2. Why is an interview about the last actual purchase more useful than asking “Would you buy from us?”

3. How is contribution margin per order calculated?

4. Why does average daily order volume not determine peak production load?

5. Why should the Veteran avoid changing every business parameter simultaneously?

6. Which functions of the single assistant described in this book are still proposals rather than implemented capabilities?

Chapter Summary

The Beginner stopped confusing a dream with a finished business plan. He now has testable hypotheses, criteria for selecting a format, and an initial economic model. The Veteran began with baseline data rather than hasty decisions. Neira’s guiding rule is simple: ask the right questions first, verify the answers, and only then recommend action.

“So we haven’t opened a pizzeria today?” the Beginner asked. “But today we started building it properly for the first time,” Neira replied. “That matters more than a beautiful sign.”

In the next chapter, the Veteran will explain why a busy pizzeria can sell a great deal and still earn very little.

Practical Deliverable and Acceptance Criterion

A pizzeria idea profile covering target customers, business format, approximate investment, and outstanding questions. Acceptance criterion: every key assumption has a way to be tested before money is committed.

Neira and Management-System Integration — BEGINNER: “I WANT TO OPEN A PIZZERIA”

From the outset, the Beginner should design the pizzeria so that sales, recipe, inventory, and staffing data can eventually flow from a management system into Neira. Proposed integrations should reduce duplicate data entry and connect the business plan with actual operating results. Until interfaces are agreed and implemented, controlled file exchange is an acceptable interim approach.

Chapter 3. The Veteran: “My Pizzeria Is Running, but I’m Not Happy with the Profit”

3.1. When a Full Pizzeria Does Not Mean a Profitable One

On Saturday evening, not a single table was free in the Veteran’s pizzeria. Couriers collected boxes one after another, the cashier took new orders, and a queue formed at the oven. Surely the owner should have been pleased. Yet when he opened the financial report on Monday, there was little to celebrate: revenue was rising, while available cash was shrinking.

Veteran: “There’s a line at the counter and dozens of delivery orders. Why am I constantly scrambling to pay wages, rent, and suppliers?”

Neira: “Because the number of pizzas sold is not the same as profit. First we need to find out which operations make money and which lose it. We’ll begin with the records available—sales, returns, discounts, purchases, stock, waste, and expenses—and check how complete and reliable those records are.”

The Veteran expected advice to raise prices or cut staff. Instead, Neira proposed a diagnosis. This is a proposed use case, not a claim that Neira is already connected to the pizzeria’s management software. She applies industry-specific analytical rules to information actually available to the business. Some figures will need to be collected manually.

3.2. The First Rule: Do Not Treat the Business by Guesswork

Owners often begin with whatever is most visible: changing advertising, buying a new oven, dismissing an employee, or reducing the amount of cheese. Yet an obvious symptom may have a less obvious cause. Delayed orders, for example, may result not from insufficient oven capacity but from poorly timed dough preparation or an uncoordinated assembly station.

Neira: “For the first week, we won’t change recipes, ingredient specifications, or prices. We’ll establish what is actually happening and then run limited, controlled tests.”

Veteran: “So we shouldn’t even touch the cheese?”

Neira: “Especially not the cheese. Saving five grams per pizza could cost more than it saves if the taste deteriorates and customers stop returning. Measure first.”

Food-safety violations, unsafe storage, sanitation problems, and clear risks to employees or customers are exceptions: correct them immediately rather than waiting for the financial review.

3.3. Seven Questions That Need Answers

Neira prepared an initial list for the Veteran. Answers must refer to the same period and, wherever possible, the same outlet; otherwise comparisons become misleading. No single indicator provides a complete diagnosis. Low ingredient cost achieved by sacrificing quality is a dangerous victory, and high revenue driven by excessive discounts does not guarantee profit.

Question

What to check

1. What sells?

Revenue, order count, average ticket, item and channel mix.

2. What remains after ingredients?

Standard and actual food cost, packaging, variable expenses.

3. Where does inventory go?

Stocktakes, waste, returns, substitutions, deviations from standards.

4. How does each shift perform?

Staff hours, productivity, queues, downtime, errors.

5. What happens to quality?

Defects, complaints, remakes, temperature, dispatch time.

6. What does marketing deliver?

Discounts, commissions, acquisition cost, repeat orders.

7. Where is the cash?

Rent, payroll, utilities, taxes, liabilities, cash flow.

3.4. Management-System Data and the Reality of Production

Neira: “Give me the dates, the specific pizzeria, and the metrics. For example: ‘Compare sales by day, channel, and category for the last four complete weeks; show refunds and discounts separately.’ Then we’ll verify what happened on the production floor. A report showing that a Margherita was sold cannot tell us how the dough was stretched, how much cheese was used, or why the crust was underbaked.”

The work has two streams. The digital stream covers recorded transactions—sales, purchasing, transfers, write-offs, and other available events. The production stream checks actual weights, temperatures, times, compliance with recipes, defects, and causes of loss at the workplace.

If records are missing or unreliable, Neira must not present guesses as facts. Instead, create a list of missing data and a temporary observation log. Until an approved integration is implemented, information may be supplied by report export, secure data transfer, or manual entry. Only authorized staff should have access.

3.5. Example: How Revenue Turns into a Loss

Consider a hypothetical pizzeria. Every amount below is invented for training and does not describe a real business. Monthly revenue is 3,000,000 monetary units. The owner sees a large sales figure, but Neira breaks it into components.

Monthly metric

Illustrative amount (monetary units)

Revenue

3,000,000

Ingredients and packaging

1,050,000

Payroll and related charges

900,000

Rent and utilities

390,000

Delivery and payment-processing fees

300,000

Marketing and company-funded discounts

210,000

Other operating expenses

210,000

Operating result before excluded items

−60,000

Calculation: 3,000,000 − 1,050,000 − 900,000 − 390,000 − 300,000 − 210,000 − 210,000 = −60,000 monetary units. For simplicity, depreciation, interest, certain taxes, and inventory movements are excluded. Discounts must be recorded without subtracting them twice from revenue. This is a management-training example, not a statutory financial statement.

Veteran: “So I could sell three million worth of pizza and still lose sixty thousand?”

Neira: “Yes, with these assumptions. But before drawing conclusions, check the period, the revenue-recognition method, and whether all expenses have been included. Then investigate causes—not just order everyone to save money. Remakes, inconsistent portioning, and poor dough planning may be part of the problem.”

3.6. Five Places Where a Pizzeria Loses Money

First: excess preparation. Making more dough balls than demand requires may lead to waste or use beyond the approved technological holding period. Compare the demand forecast with actual sales and batch-level dough movements.

Second: inaccurate portioning. Adding ingredients by eye creates variation in both cost and quality. Weigh a sample of finished pizzas, compare the results with approved recipes, and train staff without degrading the product.

Third: baking defects. Undercooked, dried-out, or burnt pizzas require remakes and delay dispatch. Record defect type, shift, oven, settings, timing, and dough preparation conditions.

Fourth: poorly scheduled shifts. Too many people in quiet hours and too few at peak times raise costs and damage service. Compare demand by time interval with actual paid hours.

Fifth: sales without margin analysis. A popular promotion may produce many orders but little contribution after discounts, commissions, and variable costs. Evaluate each channel and offer, including repeat purchasing behavior.

3.7. The First Walk Through the Pizzeria

Neira suggested following a customer order from receipt to handover. The Veteran took a notebook; Neira prepared a list of digital events to compare with what they observed.

Order receipt. Record the arrival time, sales channel, and promised completion time. Check that the order matches the production ticket.

Ingredient storage. Check labeling, batches, storage conditions, and shelf life. Flour belongs in designated clean containers, not transport sacks on the worktable. Record refrigerator temperatures and stock-rotation practices.

Dough. Check dough-ball weight, proofing or maturation time and conditions, and availability before the rush. Record forced substitutions and shortcuts.

Assembly. Compare the recipe with actual ingredient quantities in a sample of pizzas. Use scales, not visual guesses.

Oven. Check approved settings, actual loading, and recurring defects. Do not change settings without a controlled trial.

Handover. Record completion time, packaging, order accuracy, and reasons for delays. Follow established hygiene and glove-use procedures when handling ready-to-eat food.

After the walk, separate findings into three categories: confirmed noncompliance, probable cause, and a hypothesis that still needs testing.

3.8. The Veteran’s Profiles: Business and Problem

Instead of a long account of how things used to be better, the Veteran completes two short documents. They establish a baseline for later chapters and allow results to be compared after changes.

Business profile

What to record

Outlet

Name or site code, location, format, floor area, opening hours.

Production

Electric oven types, workstations, menu.

Sales

Channels, period, orders, revenue, average ticket.

Staff

Headcount, actual shifts, hours, responsibilities.

Records

Management software modules, completeness, available reports.

Constraints

Contracts, equipment, safety requirements, seasonality.

Problem profile

What to record

Symptom

What concerns the owner, without assuming a cause.

Metric

How the problem is measured and over what period.

Baseline

Verified value or “no data”.

Hypothesis

Suspected cause requiring verification.

Test

Observation, export, stocktake, or controlled trial.

Owner

Who gathers evidence and approves action.

Deadline

Review date and outcome criterion.

3.9. Workshop: The First Seven Days of Diagnosis

Day 1. Record baseline metrics, data sources, and access permissions. List what the management system does not show.

Day 2. Compare sales and discounts by day, hour, item, and channel. Do not confuse revenue with cash received.

Day 3. Sample-check ingredients, recipes, and actual portions. Document every deviation.

Day 4. Check inventory balances, batch movements, write-offs, and discrepancies. Arrange a stocktake if necessary.

Day 5. Measure order-processing times, downtime, and oven utilization by interval. Investigate remakes.

Day 6. Consolidate expenses and calculate operating results. Show unverified figures and assumptions separately.