The Pizzeria Build Day
A developer builds your app with Pizzeria UI from your HTML prototype and written spec, one tested screen at a time, with a pull request you merge at the end of each day.
You have a prototype that shows every screen and a spec full of business rules, and nobody free to build them. A developer who has to guess at your rules will get some of them wrong, and you find out from your users.
Book a day and list your screens, most important first. One of our developers builds each screen with Pizzeria components and wires it to your existing API or to a new Laravel database. They write tests that check the acceptance criteria in your spec. If a rule is unclear, they ask you in writing and wait for your answer before building it.
Your screens carry no colours of their own, so you can switch to any Pizzeria theme later, or have The Custom Pizzeria Theme put your brand on every component. Each day ends with a pull request for you to merge, with one commit per screen and a list of what comes next.
What's included
- A full working day of a named developer building your screens, in the order you choose
- On your first day, a new SvelteKit or Laravel with Inertia app set up with Pizzeria, your chosen theme and its test tools, plus email-and-password sign-in on Laravel if you want it
- Each screen laid out from your prototype with Pizzeria components and wired to the data your spec names: your API, stand-in data until your API is ready, or the app's own Laravel database
- Tests for every business rule and form, with each acceptance criterion matched to the test or recorded check that covers it
- Questions in writing whenever your spec is unclear, and a log of every answer, so nobody guesses a business rule
- Screens with no hard-coded colours, so any Pizzeria theme switches in, and a screenshot under a second theme to show it
- Screenshots at desktop and phone widths, and one pull request per day with a commit per screen for you to review and merge
How it works
- 01
Book and send access
Book online with your ABN or NZBN. We tell you exactly what access and material we need; the clock starts once we have it.
- 02
We do the work
An experienced employee who specialises in this task works through it, and asks before anything outside the scope.
- 03
Delivered with evidence
You get everything listed on this page, with a written account of what was done.
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
- A GitHub, GitLab, Bitbucket or Forgejo repository our developer's own account can push to: empty apart from one starting commit for a new app, or a Svelte 5 app already on Pizzeria
- Your prototype as HTML files, Figma frames or images, one for each screen
- A screen card for each screen, from our template: what it shows, where its data comes from, what each button does, its business rules and how to check it works
- Your data: a test version of your API with its description, or our entity sheet filled in for a new Laravel database or stand-in data
- Your choice of Pizzeria theme, and your screens in priority order
- Someone who can answer business-rule questions in writing during the day, and your consent if you want our developer to work with Claude, our AI coding assistant
Who it's for
A team with a prototype and a written spec that wants a working Svelte app on Pizzeria, built and tested one screen at a time.
Questions
How many screens fit in a day?
It depends on your screens. A screen of average size, with one form or one table, a few actions and up to five business rules, takes us 90 to 150 minutes including the data, tests and screenshots, so most days after the first build two to four. A new app's first day also sets up the project and usually reaches your header and navigation plus one or two screens. We finish each screen before starting the next, and the pull request lists the ones we didn't reach.
What if our spec is unclear?
We ask you. Two working days before your day, we read the first screen cards and send you our questions. During the day, if a question waits more than 30 minutes, we switch that rule off with a marker, move to the next screen and finish the rule once you answer. We act only on written answers, and we quote them in the report.
Will the app look like our prototype?
It will have the same sections, fields, text and actions in the same order. Colours, spacing and type come from the Pizzeria theme, so we don't copy your prototype pixel for pixel or design anything new. If you don't have a prototype yet, start with The Designer Day.
Should we book this or The Customer Portal?
If you need a portal where your customers sign in to see their orders, documents and support requests, The Customer Portal (non-Tandemity) builds one at a fixed price and deploys it for you. If your staff need to manage the records in your existing database, that's The Admin Panel. Book Build Days for screens of your own design, including new screens on a portal we built.
What if our app already uses another component library?
This day builds new screens. Moving existing Svelte screens onto Pizzeria is The Pizzeria Conversion Day. If a conversion left components that Pizzeria doesn't have, add them to your list here and we build replacements inside your app.
Who owns the code, and do you deploy it?
You own it from the first commit, in your repository, and you merge every pull request. Pizzeria is open source under the MIT licence, so the copy we add is yours to keep and change. We don't deploy or host the app: you run it from the README or through your own pipeline, and The Laravel Developer Day or The Svelte Developer Day can deploy it for you.
Do you use AI, and when do you work?
We use Claude, our AI coding assistant, only if you consent. Our developer blocks your secrets from it and reads every change before committing it, and we delete our copy of your code within 24 hours of each day's pull request. We work from India, 06:00 to 14:00 or 14:00 to 22:00 India time on weekdays, so in North America only the end of the evening shift overlaps your morning.
Often booked alongside
- General & Administrative
The Data Entry Day
One of our data entry team spends a day typing records from your scans, PDFs, emails or web pages into your system or spreadsheet, to a brief you approve. A second person checks a sample, and your report gives the error rate they found.
A$360 From A$180 on a plan
- Testing & QA
The User Manual Review Day
A technical support specialist does each step of your user manual draft in your running app and reports where the page and the app disagree, with a screenshot of what the app shows and suggested wording for the fix.
A$360 From A$180 on a plan
- General & Administrative
The Virtual Assistant Day
A full day of an experienced assistant, on the dates you book, clearing the admin that never reaches the top of your list. They work inside your own accounts and write up every hour.
A$360 From A$180 on a plan