# AI Agency, Architecture and Editorial Website Builder

Canonical: https://uvilno.com/use-cases/agency-and-client-websites
Updated: 2026-11-07

Use Uvilno to plan and build a multi-page website around the client's actual audience, offer and material. Ask for editorial hierarchy, distinct project stories and a real next action. Review responsive layouts and requested interactions, refine the saved result and unlock the source when ready. Hosting and managed services remain separate operational choices.

## Bring the details that make the client recognizable

A useful brief includes actual services, project stories, audience, tone and available photography. Name the primary conversion action and the sections that support it. Approved typography and palette should carry into subsequent edits. Avoid placeholder claims, invented awards or testimonials that a client cannot substantiate.

## Prepare a complete handoff

Review every route at phone and desktop sizes, test forms and navigation and confirm the legal and contact details. Source unlock provides a permanent project entitlement, while hosting, domain setup and third-party services remain separate. If the client needs a mobile portal or desktop operational tool later, plan it as a companion with deliberately shared managed records.

## Platform plan

| Platform | Generated experience |
| --- | --- |
| web | A responsive homepage, work index, project stories, services and contact journey. |
| mobile | An optional client portal or touch-first companion for approvals and updates. |
| desktop | An optional operational workspace for reviewing client requests and shared project records. |

## Declared collections

| Collection | Fields | Access |
| --- | --- | --- |
| projects | title, approved_copy, media_reference, visibility | Public work presentation and separately authorized editing. |
| inquiries | contact, requested_service, message, status | Keep inquiries private to authorized business accounts. |

## Acceptance checks

- Verify each declared route and link at phone and desktop widths.
- Submit a real inquiry and confirm its authorized saved outcome.
- Check keyboard focus, image descriptions and reduced-motion behavior.
- Review the exported source, referenced media and hosted dependencies before handoff.

## Setup and launch boundaries

- A source unlock is separate from generation allowance, domains and hosting.
- Brand imagery, factual copy and rights to supplied assets remain the project owner's responsibility.

## Editable starting brief

Build a distinctive multi-page website for an independent architecture studio. Ask me for actual studio facts, project narratives, location and licensed imagery. Use an editorial homepage, work index, individual project stories, services and contact. Establish one approved type pairing and palette and preserve them through edits. Keep a clear inquiry action with real validation and private saved inquiries where configured. Verify phone and desktop layouts, keyboard navigation, reduced motion and every route. Prepare clean source handoff with asset references after unlock. Later, I may link a client approval companion to the same authorized project records.

## Common questions

### Does source unlock cover future hosting costs?

No. The one-time purchase permanently unlocks that project's source. Domain, hosting, managed services and future generation have separate terms.

### Can I refine a client site after the first build?

Yes. Use saved versions and scoped chat edits, keep approved design choices explicit and verify the changed routes before publishing.
