No fictional orders
Simulate a payment in the customer view to see the order here and follow its preparation.
INDEPENDENT PIZZERIAS. DIRECT CONNECTION.
Great pizza.
Direct orders.
Less friction.
The craft stays in the kitchen. We’re building the direct ordering experience around it — from the first scan to the final handover.
Take a product tourAn early-stage product with a focused first market.
CRAFT AT THE CENTRE.A smoother path to pickup.Scan · Order · Collect
Built for independentsQR-first orderingPickup focusedLess customer data
01 / THE PRODUCT
One order.
A connected experience.
From choosing a pizza to handing it over, each person gets a view designed for their part of the service.
A merchant-branded mobile menu, card prepayment and pickup tracking. No customer account, email address or phone number required.
Interactive illustration · fictional data
These views explain the product; they are not the live application.
PRODUCT EXPLORERTry it below
19:02
Demo PizzeriaThe taste of simple things.
TakeawayPickup from 19:30
THE CLASSICQuantity
STEP 2 / PAYMENTYour order,
Your order,
direct.
1 × Margherita€12.00
Card payment
Simulation only.
No banking details requested.
FICTIONAL ORDERSee you soon,
See you soon,
.
A generated pickup name.
Fictional example: Milo Basilic.
Status
Tonight’s service
Demo · 19:02NewPreparingReadyHanded over
DEMO PIZZERIA
A menu that reflects you.
Catalog · Prices · Ingredients
The pizza menuExample
Catalog prices and ingredients appear in the customer storefront.
A workspace reserved for the owner.The kitchen keeps its Orders view.
CUSTOMER STOREFRONT01 — 03
02 / THE THESIS
Independent by nature.
Connected by design.
The opportunity: make direct ordering useful enough to become part of an independent pizzeria’s everyday service.
The restaurant
stays at the centre.
A dedicated ordering link and a merchant-branded storefront keep the journey connected to the pizzeria.
Build around
the dinner rush.
Pickup timing, order preparation and handover share one flow. The hypothesis: less time taking orders and collecting payment.
Ask for less.
Keep it simple.
No customer account or contact details to enter. A generated pickup name helps the team identify each order.
One platform. Multiple merchants.
Shared software with merchant-scoped menus, configuration and orders. A foundation for expansion; adoption still needs to be proven.
03 / PROGRESS
A working product.
A clear next proof.
PRE-PRODUCTION
The core journey is implemented. The next chapter is learning from real, unassisted service.
The product foundation
Customer ordering, staff order handling and owner catalog management. Recent interface work checked locally with fictional data.
A test payment to pickup
An end-to-end hosted journey demonstrated with Stripe test payments, through order acknowledgement and handover.
First production pilot
Observe real service, confirm operational readiness and measure where the product saves work.
Repeatable merchant value
Test repeat use, willingness to pay and the effort required to bring another pizzeria on board.
Test payments and local checks establish technical progress. They do not establish production adoption, revenue or measured time savings.
A FEW INVESTOR QUESTIONS
Focus first.
Learn quickly.
Why start with pizzerias?
A focused pickup use case makes it possible to observe a complete service: a customer chooses, the kitchen prepares, the team hands over. The first aim is to validate that workflow in a real pizzeria before expanding.
What is the commercial model?
Commercial pricing has not been validated. The next step is to test merchant value and willingness to pay during the pilot, then establish pricing around that evidence.
Does x402 mean customers pay in crypto?
The current product uses Stripe card payments. Customers do not need a crypto wallet. This presentation makes no claim of a live crypto payment capability.
PIZZA x402