A client website with its own point of view.
Build a distinctive multi-page client website, refine it by chat and permanently unlock one project's source for a one-time payment.
Review the prepared brief in Studio. A build starts when you send it.
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.
Give each screen its own job.
These are proposed interfaces for your brief. Build and verify the core workflow before adding connected companions.
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.
Plan the records and their owners.
Suggested collections for this editable blueprint. Opening this page creates no database records. The plan must declare supported field types, relationships and access rules before building.
| Collection | Suggested fields | Access to decide |
|---|---|---|
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. |
Verify the outcome, then expand.
- 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.
From this brief to your first version.
Review the proposed workflow
Start with this editable blueprint brief. Confirm the primary action, target platform, actual business information and declared collection permissions before approving a plan.
Build and check the result
Review the isolated preview and execute the checks listed on this page. Begin with A responsive homepage, work index, project stories, services and contact journey. Resolve missing service setup and save verified progress before expanding the scope.
Connect or export when ready
Use App connections to review owned companions and shared backend changes. Unlock source when ready to export, then verify the target deployment, packaging and hosted-service configuration.
Make the starting point your own.
Questions before you build.
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.