As a freelancer you are the designer, the developer, the project manager and the person who answers the client's messages on a Sunday. Briks takes the build off your plate: you write the brief from your client call, it plans, builds and checks the site, and you spend your time on the parts clients value most.
Below are templates you can start a client's site from, how client work is kept apart, and what to settle before you hand a site over.
The opening line of the brief behind SaaS Landing, a website template by the Briks teamQuillo is an AI support app for online shops and subscription businesses, built in Dublin, Ireland, and live since 2023.
One workspace per client keeps the brief, the pictures and the people together. Choose a client in the drawing to see their roles, then try making the client an Owner.
Write the brief from your notes: the business, the customers, the pages and the feel. Briks asks about anything you left open before it builds.
Keep up to 10, each with its own projects, media library, plan and credits. When a project ends, its workspace can go with the client.
On Pro or above, invite them as a Viewer to see previews and analytics without changing anything, or as an Editor if they want to make changes themselves.
Browse and edit the files written for the site, and on a paid plan download a published version as a zip.
There is no separate handover button: invite the client as an Owner, which works on any plan, then step back or stay on as an Editor for ongoing work.
Workspaces3 of 10
Viewer: Sees projects, previews and analytics, and changes nothing.
A drawing of how workspaces and roles fit together, not a screenshot of the studio.
Each step is something Briks does today. Follow a link for the details of each feature, including whether it needs a plan or a switch.
Write down what the client told you. Briks asks which pages the site needs and anything the brief left open, so gaps surface before the build rather than after.
Questions before buildingOn every planClients always have sites they like. Add the one they like most, with screenshots, and Briks reads its layout, spacing, type and motion.
Build from a site you likeOn every planContrast is checked in the code before publishing. The first publish goes to a preview at its own briks.live address, kept out of search, ready to send to the client.
Checks before publishingOn every planPaste the client's feedback into the studio chat in plain words. Briks builds and publishes each change as a version.
Changes in plain wordsOn every planUndo, redo or restore any version. When the client prefers last week's header after all, you can bring it back.
Versions and undoOn every planIf you code, edit the files written for the site directly, with edit rights, and on a paid plan download a published version as a zip.
Your site's codeOn every planMake the client an Owner of the workspace, and decide together whether you stay on as an Editor for care work.
Teams and workspacesTeams from ProChange the details to your own and use it as your starting point.
Wildstem is a florist in Frome, Somerset, run by Ruth Okoye since 2020. She makes seasonal bouquets with British flowers, does wedding and event flowers, and runs wreath-making workshops in December.
Bouquets start at £35, with local delivery in Frome from Tuesday to Saturday. Wedding enquiries need the date, the venue, guest numbers and a budget, and Ruth replies within two days.
Ruth's customers are locals buying gifts and couples planning weddings within 30 miles. She wants the site to feel wild and seasonal, with lots of her own photographs, which she will upload.
Pages: home, bouquets, weddings and events, workshops, about Ruth, and contact. This is a client project: Ruth joins as a Viewer while we work and becomes the Owner at launch.
Use this brief opens sign-up, then a new project with these words filled in. Change anything before you build.
An honest list, checked against what Briks does on 8 October 2026. Where Briks does not cover something, the usual way around it is in the same row.
| What you need | With Briks today | Status |
|---|---|---|
| A first version from the brief | Planned, built, checked and published to a preview address. | Included |
| A workspace per client | Up to 10 per person, each with its own projects, media library and credits. | Included |
| Client feedback rounds | Changes in plain words, each one a version you can undo. | Included |
| Quick edits without a build | Words and pictures changed on the page in the Visual Editor, on paid plans, with no credits used. | Paid plans |
| Editing the code yourself | Browse and edit the files written for the site, and download them on a paid plan. | Included |
| Handover | Invite the client as an Owner, on any plan; there is no separate handover button. | Included |
| The client's own domain | From Starter, with the certificate issued and renewed automatically. | Paid plans |
| Billing your client through Briks | Not today. Invoice clients yourself. | Not today |
| Removing the Built with Briks badge | Off on every paid plan. Free sites show a small link in a corner. | Paid plans |
| White-label under your own name | Not today. | Not today |
When the build takes less time, your value is the discovery, the words and the judgement. Price projects for those, and say so in your proposal, so a faster build never reads as less work.
A first version the client can click through changes the conversation. Feedback on a real page is clearer and kinder than feedback on a mock-up.
Changes are quick to make, which makes endless rounds tempting. Agree how many are included, and what counts as new work.
Who owns the workspace, who pays for the plan, who makes changes after launch. A short note at the start avoids an awkward conversation at the end.
Yes. Keep up to 10 workspaces, one per client, invite clients with roles from Pro, and make the client an Owner when you hand the site over, which works on any plan.
Yes. The first publish goes to a preview at its own briks.live address, kept out of search, which you can send them. On Pro or above, invite the client as a Viewer to see previews and analytics without changing anything.
Yes. With edit rights you can browse and edit the files written for the site, and on a paid plan download a published version as a zip. The zip does not include the shared parts every Briks site runs on. On paid plans those files can also be kept in a GitHub repository, in step both ways.
Each workspace has its own plan and credits, and its Owners manage billing, so agree it with your client. Paid plans are bought online at checkout.
A sentence is enough to start. You get 50 free credits when you sign up, no card needed.