Catering and large orders
When one recipe is not enough
A brand, a website, an app, or the whole spread at once. Large orders start with a conversation, the same five steps the previous shop used for corporate cake orders, because the steps were right.
A brand
Name, voice, visual system and the entity work that makes assistants and search engines know who you are. Delivered as files you own and a site that uses them.
A website
Designed, written, built flat and deployed. Every page answers a question someone actually asks. Comes with schema, sitemap, redirects and a month of watching the oven.
An app
iOS, web or both. Product thinking first, then a working build, then the store listing. See The Recovery Toolbox for one that shipped.
All of it
Brand, site, app and the visibility work as one order, sequenced so each layer is done before the next goes on. This is the baumkuchen.
How a large order works
- Tell Anni what you needUse the form below. Say what you want built, who it is for, roughly when you need it, and what exists today.
- TastingWithin two business days Anni replies with questions or a call. This is where the order gets specific enough to price.
- Go or no go from the kitchenAnni takes the order back to vizmeta. You get a written recipe: scope, layers, bake time and a fixed price. Or an honest no, with a referral if one fits.
- OrderYou approve the recipe. A deposit starts the oven. Method of payment depends on the order.
- DeliveryLayers ship as they finish, so you see progress, and the whole bake lands on the agreed date. Anni stays on the cooling rack for a month after.