From trade to live site, in three steps.
A baker, a plumber or a driving service picks their trade, answers a short set of questions, and watches a complete website assemble — copy, photos, prices, Google listing details and search setup included. If they like it, they pay, and it deploys to a real domain.
It began as a generator for one trade and now covers more than fifty, from restaurants and barbers to garages, bakeries and building trades.
The people who most need a website are the ones least able to buy one.
A local business owner asking for a website gets one of two answers: a few thousand euros and several weeks from an agency, or a builder subscription that hands them a blank canvas and their own evenings. Most take the third option and end up with a Facebook page.
Underneath that sits a trust problem. Buying a website means paying first and seeing it afterwards — which, for someone who has been burned once, is enough reason not to start.
Invert the order: build first, charge second.
The whole product turns on one decision — the site is generated and shown in full before any payment. Not a template preview or a mockup: the actual site, scrollable, with their trade's sections and their own details in it. The purchase decision becomes "do I want this thing I am looking at", which is a far easier question than "do I trust you to make something good".
The second decision was to make the trade the unit of design rather than a theme colour. A plumber's site leads with a quote request, a restaurant leads with the menu, a practice leads with booking — each trade has its own sections, its own copy and its own price presentation, because a generic template with the noun swapped is exactly what these owners have already rejected.
The wizard is deliberately short. Three steps, plain language, no jargon, and the preview visible as early as possible — every extra field before someone sees something real is another chance to lose them.
Taking real orders.
Azurcrea Studio runs in production with live payments: an order triggers a deploy, and the customer's site goes up on its own domain without anyone touching it in between.
One detail I would call out as design rather than plumbing: the generated sites are prepared to be found by AI assistants as well as by search engines. For a local trade, "which plumber near me" is increasingly a question asked to a chatbot, and being legible to it is now part of the product rather than a future nicety.
