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

“How will they know what a good pizza means in your pizzeria?” Neira asked.

The starting point is a digital job and employee skills profile: responsibilities, authorisation to perform operations, training programme, practical exercises, assessment results, reassessment dates and applicable hygiene requirements. Personal information is accessible only to authorised staff.

Training can proceed through ingredient receiving and storage; dough preparation; shaping; portioning; oven operation; finished-product inspection; cleaning; and shift handover. Each stage ends with an observable practical assessment: the employee performs the operation to the approved standard and a mentor records the result.

The Veteran admitted that each shift supervisor in his business trained newcomers differently. Neira advised agreeing on one standard before automating training records; otherwise the digital system would simply spread inconsistent instructions faster.

The management and economics side of this module connects competence, staffing plans, operating costs and accountability. It does not authorise Neira to make automatic decisions about dismissal, pay or disciplinary sanctions. Such decisions remain with responsible people under applicable law.

5.5. Module Four: Sales, Marketing and Delivery

Neira displayed three questions on a hypothetical screen: “What did we sell? What did we earn? Why did the result differ from the plan?”

Revenue alone is not enough. The owner needs order counts, average order value, product mix, food cost, write-offs, payroll, rent, delivery commissions, advertising expenditure and repeat purchases. Every metric must have a clearly identified source and reporting period.

Illustrative calculation: 100 orders per day at an average value of 850 monetary units generate 85,000 units in daily revenue. If variable costs are assumed to be 42% of revenue, the contribution available to cover fixed costs is 49,300 units a day. This is not net profit: fixed costs, taxes and other obligations must still be accounted for. The figures are illustrative, not a currency conversion or a profit forecast.

“Could we simply launch a 20% discount?” the Veteran asked.

“First calculate how many additional orders it would need to generate,” Neira replied. “A discount can increase sales and make the business less profitable at the same time.”

Neira also checks whether the kitchen could handle the promoted volume without compromising quality. A proposed campaign proceeds through calculation, a limited test and measurement of the result.

For the Beginner, this means a preliminary financial model and opening campaign. For the Veteran, it means investigating deviations and testing improvements. No forecast is a guarantee of profit.

5.6. Module Five: Procurement and Manufacturers

“If the flour runs out on Friday evening, no marketing campaign can rescue the shift,” Neira observed.

This module connects demand forecasts, recipe standards, usable stock, delivery lead times, minimum order quantities and ingredient quality. Its goal is to keep production supplied without building excessive inventory.

Illustrative calculation: sales of 300 pizzas are expected over the next three days. At 180 g of flour per pizza, the requirement is 54 kg. With 19 kg of confirmed usable stock and a 10 kg safety reserve, the preliminary purchasing requirement is 45 kg: 54 + 10 − 19. Before ordering, check existing purchase orders, shelf life, pack sizes and storage capacity.

The Veteran proposed sending a mozzarella producer test results for melting and stretch. Neira supported the idea but stressed that exchanging information with a factory is a separate integration project, requiring agreement between the parties, a data format, confidentiality rules and verified measurement methods.

A supplier order should initially be a draft. Sending it, changing commercial terms and assuming financial obligations require approval from an authorised employee.

5.7. Module Six: Developing a Pizzeria Network

The sixth module looks beyond a single location. It uses comparable data from operating sites to assess whether the business is ready to expand, what capacity is missing and which operating standards can be replicated. Growth is not automatically justified by higher demand.

For the Beginner, network development remains a future option: document processes and data consistently from the first location so that a second site can eventually be evaluated. For the Veteran, the immediate task is to compare locations using consistent definitions of revenue, product cost, labour, defects, stock losses and service performance.

Before approving expansion, the owner must test demand, investment needs, available managers, production capacity and the reliability of existing sites. Neira can organise evidence and scenarios; she does not approve leases, financing or openings.

5.8. How the Six Modules Work Together

Imagine a Friday evening. A forecast suggests more orders. The sales module estimates demand; production calculates dough-ball requirements and oven load; personnel and management check staffing and competence; procurement verifies flour, cheese and sauce stocks; the business-development module considers capacity constraints; and the network module checks whether a recurring bottleneck points to a broader growth decision.

This creates a closed loop: plan, prepare, execute, measure and correct. Digital recommendations still pass through human checks, safety rules and the manager’s authority to decide.

“So I am not just a talking picture,” Neira said with a smile. “My purpose is to help people do their work better—and to say clearly where my knowledge or access ends.”

5.9. Neira’s Architecture: What Exists and What Must Be Built

The proposed architecture has five layers. First, data sources: till transactions, accounting records, recipes, stock documents and technical measurements. Second, data validation: units, dates, completeness, provenance and access rights. Third, Neira’s industry rules: pizza-production standards, calculation methods and control points. Fourth, user interfaces for owners and staff. Fifth, an audit trail of recommendations, approvals and outcomes.

Connections to accounting and management systems are possible only through agreed, technically available interfaces. Product capabilities must be verified against current documentation and access conditions. A design concept must not be presented as a finished product.

Every recommendation must answer six questions: What problem is being addressed? Where did the data come from? How was the result calculated? How reliable is it? Who may approve the action? How will its effect be checked?

5.10. Beginner Workshop: A Profile of Six Modules

Prepare a six-row working profile. For each module, specify one main goal for the first 90 days, three necessary inputs, an accountable person, a deliverable and an acceptance criterion. Mark missing information “to be verified.”

For procurement, for example: goal—avoid production stoppages caused by missing core ingredients; inputs—sales plan, consumption standards and usable stock; owner—manager or buyer; deliverable—approved purchasing plan; checks—number of stock-related stoppages and value of excess inventory.

For network development, the initial deliverable may simply be a consistent set of operating standards and a documented decision on whether expansion should be considered later.

Do not purchase equipment or sign long-term contracts solely on preliminary calculations. Verify assumptions first.

5.11. Veteran Workshop: Problems and Priorities

Review the last four complete weeks. For each of the six modules, record one problem and a measurable sign: complaints, portion deviations, staff turnover, falling contribution margins, ingredient shortages or inconsistent performance across locations. Assess severity, frequency and whether the evidence can be checked. Select no more than two tasks for the first pilot.

For each task, create a card containing a baseline metric, measurement period, responsible person, hypothesis, action plan and date for reassessment. Compare like with like; do not attribute a change to Neira if it may have resulted from seasonality, price changes or external advertising.

5.12. Neira’s First Advice

The Beginner put his future pizzeria profile on the table. The Veteran brought a list of problems at his existing business. Neira asked them to start with reliable data and approved production standards: both are necessary.

“I cannot promise to solve everything for an owner,” she said. “But I can help an owner avoid deciding blindly.”

Their first rule was that each module must deliver verifiable improvement, not merely more advice. Their second was that new functions should be designed and introduced in stages, with the participation of people responsible for production and money.

Review Questions

Name the six modules and one deliverable from each.

Why should the Beginner not start by purchasing an oven?

What must be checked before concluding that cheese is being overused?

Why does a digital employee profile not replace practical assessment?

How does contribution available for fixed costs differ from net profit?

What information is needed to calculate a flour order?

Which actions require human approval?

Why must a proposed integration not be described as already operating?

What evidence should a Veteran examine before expanding to another location?

Workshop Deliverable and Acceptance Criterion

Produce a six-module roadmap with named owners, input data, pilot outputs and acceptance criteria. The roadmap passes review only when each module has a measurable result and proposed capabilities are clearly distinguished from existing tools.

Chapter Summary

Neira organises the life cycle of a pizzeria into six connected modules. The Beginner receives a structure for planning the first location; the Veteran receives a framework for diagnosing an operating business and evaluating growth. The next step is to turn these modules into one practical sequence of decisions, measurements and responsibilities.

Chapter 6. Two Paths to One Goal: Quality Pizza and a Profitable Business

Pizza quality and business profitability are often discussed separately. A technologist talks about dough, cheese and ovens; a manager talks about revenue, payroll and expenses. Yet the customer receives one product, and the owner receives one financial result. Neira therefore treats quality and economics as two sides of the same management problem.

6.1. A Morning Conversation: The Same Goal, Different Starting Points

Beginner: “I want to make the best pizza in town. If it tastes good, people will definitely come.”

Neira: “Delicious pizza is necessary, but it is not a business plan. You must be able to make it consistently, every day, on every shift, at a reasonable cost.”

Veteran: “Customers praise my pizza and I have plenty of orders, but at the end of the month there is hardly any spare cash.”

Neira: “Then we have two starting points. The Beginner must test whether the future business model is viable. The Veteran must find out why the existing model is not producing the expected result. We will begin with facts.”

Neira establishes one shared success criterion: the pizzeria must produce safe, consistent pizza that customers want, serve them within the promised time and generate enough cash to sustain and develop its operations.

6.2. What “Pizza Without Mistakes” Means

The motto “Pizza Without Mistakes” does not promise impossible perfection. It describes a process for preventing, identifying and correcting deviations. Every requirement must be measurable, every check practical and every decision assigned to a responsible employee.

Food safety is governed by applicable local regulations and the company’s approved procedures. AI does not replace the person responsible for food safety.

6.3. Five Measures That Must Not Be Confused

Neira displays five separate lines: “Revenue,” “Gross Profit,” “Operating Profit,” “Cash Flow” and “Quality.” These are not synonyms. High revenue can accompany a loss. A strong customer rating does not guarantee an adequate margin. Positive accounting profit does not mean that enough money is available to pay suppliers.

Cost definitions must be consistent across reports, or comparisons between months and locations lose their meaning. Taxes, depreciation, interest and delivery expenses may be treated differently in different management models; the owner and accountant should approve the precise definitions.

6.4. Beginner: From an Attractive Idea to a Testable Hypothesis

Neira: “Let us start not with buying an oven but with four assumptions: who the customer is, how many orders they will place, the average order value and the cost of serving an order. We must also add production constraints: pizzas per hour, dough preparation time and the availability of suitable ingredients.”

The Beginner writes down a delivery-and-takeaway format, a small range of familiar pizzas, an assumed average order value of RUB 900 and a target of 60 orders a day. These are teaching assumptions, not a demand forecast. Before signing a lease, he must test them through observation, lawful trial sales and competitor analysis.

Illustrative calculation: 60 orders × RUB 900 × 30 days = RUB 1,620,000 in monthly revenue. If variable costs account for 45% of revenue, RUB 891,000 remains to cover fixed costs. With assumed fixed costs of RUB 750,000, the operating remainder before other unaccounted items is RUB 141,000. This is not net profit and does not guarantee payback.

Break-even volume under this simplified model: 750,000 ÷ (900 × 0.55) ≈ 1,516 orders per month, or approximately 51 orders per day over 30 operating days. If demand is only 40 orders a day, the model becomes loss-making even if the pizza is flawless.

Beginner: “So a good recipe is not enough?” Neira: “Correct. You must connect the recipe to production capacity, costs and repeatability before committing your money.”

6.5. Veteran: Why “Lots of Orders” Does Not Mean “Lots of Profit”

The Veteran brings a hypothetical monthly report: revenue RUB 3,000,000; variable costs RUB 1,560,000; fixed operating expenses RUB 1,350,000. The operating remainder under this model is RUB 90,000, or 3% of revenue, before other unaccounted expenses.

Veteran: “Three million in turnover, and so little is left. Should I raise prices?” Neira: “First check the sales mix, discounts, returns, expenses and daily trends. Raising prices without understanding demand may reduce order volume.”

Neira continues: “We should also check production losses. How much cheese and sauce actually goes onto each pizza? How much dough is discarded? How many pizzas are remade?”

Suppose spot weighing reveals an average cheese overportion of 18 g on each of 100 pizzas per day. At a hypothetical purchase price of RUB 600 per kilogram, the extra monthly cost is 0.018 × 100 × 600 × 30 = RUB 32,400. This demonstrates a method; real overportioning and purchase prices must be established by measurement and records.

Neira emphasises that cheese portions must never be reduced below the approved recipe simply to save money. The aim is to eliminate deviations above the standard without damaging the product. If the standard itself is flawed, it should change only after production trials and an assessment of customer outcomes.