A client portal for web developers that turns scope, sign-off and payment into a paper trail
A website project doesn’t usually collapse because of the code. It collapses in the margins: a scope that was “obvious” to you and different to the client, a “small tweak” that turns into a new feature, a launch date that moved because content never arrived, and a final invoice that sits unpaid while the client already has the live site.
CloveDesk gives each client one private, branded space for the whole build. You send the scoped quote, get the contract signed, ask for milestone sign-off, route extra requests through new quotes, share handover files, and invoice from the same place. Your client opens a link from an email. No account, no password.
Where web projects usually go wrong
Every developer has lived some version of these:
- The scope is a conversation, not a document. Pages, features and integrations were agreed on a call. Six weeks later, nobody remembers whether the booking form was included.
- Small requests quietly become free work. “Can you just add a filter?” is easy to say yes to and hard to price after the fact.
- Approval is vague. The client said the design “looked good” in a message. Now they say they never approved it, and you are rebuilding the header.
- Content and assets arrive late, or never. The project stalls on copy and photos, and the timeline slips on your side of the ledger.
- Launch and payment are tangled. The site goes live before the final invoice is paid, and you lose the only leverage you had.
- Ongoing work has no home. Hosting, maintenance and small updates after launch get handled by email, with no clear agreement or invoice.
- The real cost is invisible. Hosting, premium plugins, themes, domains and a freelance designer are paid by you and forgotten when you price the next build.
A client portal doesn’t write better code. It gives the project a record, so the work is judged against what was agreed.
How a website project runs in CloveDesk, step by step
Here is a realistic flow for a small business website build. The how it works walkthrough shows each screen with screenshots.
1. Create the workspace and the project
Set up a workspace for the client, then a project for the build. When the client later wants a store, a redesign or a maintenance plan, each becomes its own project in the same workspace, so history stays together.
2. Quote the build like a spec, not a guess
Break the quote into lines that mirror the work: discovery and sitemap, design, development, content migration, SEO setup, testing and launch. Use the notes to list what is included, how many revision rounds apply, what you need from the client and when, and what is out of scope, in the client’s currency. Or upload your own proposal. The client approves, asks for changes or declines, and every revision is kept in a history, so the agreed scope is never up for debate.
3. Get the contract signed first
Upload your development agreement, covering scope, timeline, payment milestones, ownership of code and content, hosting responsibilities and support after launch, and send it for signature. The client signs by drawing or typing on any device, and you both receive the signed PDF with a certificate page and an audit trail. For side agreements, such as an NDA for a subcontractor or a separate hosting and maintenance agreement, Universal E-Sign lets you send any PDF to anyone through a private link.
4. Invoice the deposit before you build
Create an invoice for the first payment, with payment terms and a due date. Add your payment links, such as PayPal, Stripe or Wise, and the client sees a Pay button on the invoice, in the email and on the PDF. The money goes straight to you. Mark it paid with the date when it lands, so you know the project is funded before you start.
5. Show progress with stages the client can see
Move the project through stages such as “Discovery”, “Design”, “Build”, “Review” and “Launch”. Clients can see where things stand without a status email, and you decide when each stage changes. It also makes it obvious when a stage is waiting on them.
6. Get milestone sign-off in writing
Before moving on from design or from a build milestone, upload a short acceptance document that states what was delivered, what is approved and what comes next, and ask the client to sign it. It takes a minute, and it replaces the “I thought you meant…” conversation with a signed record. Share design files, mockups or walkthrough documents alongside it, and the client can comment on each file in a thread shared with them.
7. Route extra requests through a new quote
When the client asks for something outside the scope, answer with a short quote for the change instead of a vague “sure”. They approve it, ask for changes or decline, and you only start once it’s agreed. After a while, clients learn that new features have a price and a process, and the awkward conversations become routine.
8. Hand over files only when you have been paid
You choose what the client can see. Keep launch packages, documentation, backups and handover notes private until the final invoice is paid, then share them and email the client that they are ready. Many file types and sizes are supported, within your plan’s limits. Labels help you organize files by milestone; they are for you, and clients don’t see them.
9. Know when the client has seen things and chase calmly
You can see when a quote, contract, sign-off or invoice was opened and when the client last visited the portal. A dashboard shows everything waiting on a client, with one-click reminders. Overdue invoices are flagged automatically, and reminders can go out on their own.
10. Track what the build really cost you
Log hosting, premium plugins, themes, domains, stock assets and any subcontractor against the project, in the currency you paid. The project shows its own revenue and costs, and the workspace adds up the whole client. The guide to freelance expense and profit tracking explains how to read those numbers and spot the projects that underpay.
What your clients experience
Your clients are business owners and marketing managers, not developers. They get an email with a link and open a clean page with your logo and colors. They see exactly what is waiting on them: a quote to approve, a contract to sign, a milestone to accept, an invoice to pay. They can approve, sign, ask for changes, comment on files and pay through your links. There is no login to create, which means fewer messages saying “I can’t get in” and fewer excuses for a stalled approval.
Features developers use most
| What developers need | How CloveDesk handles it |
|---|---|
| A scope the client agrees to | Quotes with line items, notes and terms, plus a revision history |
| Contracts and ownership terms | Upload your own agreement and have it e-signed, with an audit trail |
| Milestone acceptance | Upload a sign-off document and have the client sign it |
| Extra requests with a price | A new quote the client can approve, change or decline |
| Visible progress | Project stages the client can follow |
| Staged payments | Invoices with payment terms and Pay buttons using your own links |
| Handover on your terms | You choose which files the client can see, and when |
| Clients who go quiet | Open tracking, overdue flags and reminders |
| Real project margin | Expenses per project or client in many currencies |
The features page has the complete list.
What CloveDesk doesn’t do for developers
- It’s not a project or bug tracker. There are no tickets, task boards, staging previews or code tools. Use your usual development stack for that and keep CloveDesk for the client-facing paperwork.
- Clients can’t upload files. They can view, download, sign and comment, but they can’t send you copy, photos or logos through the portal. Collect content and assets another way.
- Don’t send credentials through it. Share logins and API keys with a password manager, not as files in a client portal.
- No time tracking. It suits fixed-price and milestone work. If you bill hourly, pair it with a time tracker, or look at the Bonsai alternative comparison for a platform that includes timesheets.
- No messaging. Conversations stay in your email or chat tool. Comments exist on files only.
- One person per account. It is built for solo developers and tiny studios, not teams that need shared seats.
- Payments happen outside CloveDesk. Clients pay through your links, and you mark the invoice as paid.
- Branded, not white label. Your logo and colors appear throughout, but the portal runs on a CloveDesk address.
Who this suits
CloveDesk fits freelance web developers, WordPress and Webflow builders, front-end and full-stack contractors and small web studios who:
- work on fixed-price or milestone-based projects
- want scope, change requests and sign-offs in writing
- need to stay in control of when handover files and launch go out
- offer maintenance or support after launch and want it on paper
If you also handle branding and visual work, see the client portal for graphic designers page. For the full picture, start with the client portal for freelancers guide.
Moving over from email, Trello and Google Drive
- Start with your next quote. Send the scope and contract through CloveDesk from the first yes.
- Bring live projects over at a milestone. The start of a new phase or a fresh invoice is a natural moment.
- Save your defaults once. Business details, standard terms, payment links and branding are reused on every quote and invoice.
- Keep your development tools as they are. You don’t need to replace your repository, task board or staging setup.
Frequently asked questions
What is a client portal for web developers?
It’s a private place where each client can see the quote, sign the contract, approve milestones, download handover files and look at invoices, without digging through email. It replaces scattered attachments and approvals with one organized space per client.
How do I handle scope changes?
Send a short quote for the extra work. The client approves, asks for changes or declines, and you start once it’s agreed. Every quote version is kept, so there’s a clear record.
Can I get clients to sign off on milestones?
Yes. Upload a short acceptance document and send it for signature. The signed copy comes with a certificate page and an audit trail.
How do I stop launch happening before payment?
You decide what the client can see. Keep launch packages and handover files private until the final invoice is paid, then share them. Moving the live site itself is up to you, and your contract should say when ownership transfers.
Do my clients need an account?
No. They open a link from their email. There’s no password and no sign-up.
Can clients send me content and assets?
Not through the portal today. Clients can view, download, sign and comment, but file uploads from clients aren’t available.
Can I charge for hosting or maintenance?
Yes. Create a project for the retainer, send a quote and agreement, and invoice each billing period from your saved details. Reminders help you follow up on late payments.
Are e-signatures legally valid?
Signed documents come with a certificate page and an audit trail. E-signature rules vary by country and document type, so check what applies where you and your clients are based.
Can I try it before paying?
Yes. You can start free and run a real project through it.
Give your next build a paper trail
Create a workspace, send the scoped quote, and get the contract signed before the first commit. It takes about as long as writing the email.