Ayuda Hosting · design prototypes

Experiment 1 — a new public website

Two independent proposals for a new public-facing Ayuda Hosting website, produced from the same brief under the same conditions. They are presented here for review side by side.

Neither of these is the live Ayuda website. Both are design prototypes. Forms do not submit anywhere, and nothing on these pages creates an account, a quote or an enquiry. The real site is ayudahosting.com.au.

Draft 1

Homepage plus a three-question qualifier that routes to a contact form or a “might not be the best match” outcome.

Draft 2

Homepage plus a qualifying contact page with an intake form and direct contact details.

Experiment 2 — recovering a website from a backup

Two independent proposals for how a hosting customer recovers their website from a previous backup, including where a member of staff has to be involved. Each mirrors pages from both a customer portal and an internal operator portal.

These are mirrors, not the product. Every site, person, server and backup in them is invented. Nothing here restores anything, and no page is connected to a real system.

Proposal A

Three-step restore request, a trackable status timeline, and an operator who can approve, ask for more information, or decline.

Proposal B

A backups list with expiry and per-row restore, a structured request, and an operator screen with a change diff, preflight checks and a typed confirmation.

Experiment 3 — a website that stopped working

Two proposals for helping a customer whose site stopped working after a change. The brief named no solution, so deciding what the customer actually needs was part of the task. Each spans a customer portal and an internal operator portal.

Recovery drafts

Two independent answers to the same brief, with a shared landing page and notes on how to walk them.

Experiment 4 — connecting a domain without losing the email

Two proposals for a customer who wants visitors to reach their new website using a domain they already own, while their existing email keeps working. The brief named no solution and no journeys, so deciding what the customer actually needs was part of the task. Each spans a customer portal and an internal operator portal.

Domain drafts

Two independent answers to the same brief, with a shared landing page, both left exactly as their authors made them — including their known defects.

Experiment 5 — the same brief, run by a team of agents

The same customer brief as Experiment 4 — reach the new website on a domain the customer already owns, without breaking their email — but this time each proposal was produced by a team rather than a single agent: a coordinator, two independent investigators, three designers, and one reviewer who took no part in building it. Both teams had the same shape, the same tools and the same budget. Each decided its own answer.

Matched multi-agent drafts

Two independent answers to the same brief, with a shared landing page, both left exactly as their authors made them — including their known defects.

Walking these
Start on the customer side, request a restore, then open the operator screen and act on it — approve it, or decline it. Then go back to the customer's page and see whether it moved. That round trip is what the two proposals differ on most.
Source of business facts
ayudahosting.com.au — both drafts were asked to take Ayuda's real positioning, services and contact details from here, and to invent no pricing, guarantees or capabilities.
Design reference
cloudflare.com — used as a reference for how a technical service provider structures information and guides visitors. Not a statement that Ayuda offers what Cloudflare offers.
Reviewing these
The drafts are deliberately unlabelled as to how each was produced, so they can be judged on what they are. Follow the links on each homepage — the second page is where the two differ most.