How to Set Up a Branded Client Portal Without Hiring a Developer

If your couple’s last memory of your wedding is a Pixieset URL with a random hash in it, you’re handing the last impression of your work to someone else’s brand. It’s a small thing. Wedding clients notice small things, and they tell other couples.

You can set up a fully branded client portal on your own domain in a weekend. Your logo, your colors, your URL. No developer required. Below is the playbook.

What a “branded portal” actually means

A real branded portal does three things. It runs on your custom subdomain — portal.your-studio.com, where the client’s browser shows your domain from the very first pixel, not a FlowShot-served URL. It uses your visual identity — your logo, your color palette, your typography, not whatever default theme the tool ships with. And it hosts the entire client flow — proposal, contract, invoice, delivery, questionnaire — all at URLs under your domain, not a mix of docusign.net and pixieset.com and a payment page on a fourth hostname.

If only the delivery is on your domain and the rest sits on external URLs, that’s a gallery, not a portal.

Step 1: Buy the domain you want

If you already own your-studio.com, skip ahead — you’ll be using a subdomain (portal.your-studio.com) and that’s free.

If you don’t own a domain yet, buy one at Cloudflare Registrar or Namecheap. $10–15/year. Pick something short and spell-able. vesna-films.com beats vesnafilms-studio.com. The phone test: can you say it on a phone call without spelling it letter by letter? If not, pick a better one.

Step 2: Pick a tool that supports custom domains

This is where most studio tools quietly fail. Custom-domain support falls into one of three buckets. Some tools don’t offer it at all — you’re stuck on the vendor’s URL forever. Some lock it behind enterprise plans starting at $100+/mo. Some offer it but make you figure out A records and CNAMEs on your own without a setup wizard.

What you want is custom-domain support on your paid plan, with a verification wizard that walks you through the DNS step in plain English.

Tools that check this box for photo and video studios in 2026:

• FlowShot — Business plan ($89/mo) includes custom domain on portal.*. Starter ($25) and Pro ($49) host on a FlowShot-served URL with full Brand Kit
• Pixieset — Studio plan includes custom domain (galleries only)
• ShootProof — Pro plan includes custom domain
• HoneyBook — custom domain on Premium ($79/mo)
• Squarespace — custom domain included, but you’re hand-building the portal

I’ll use FlowShot for the rest of this tutorial because I know it best, but every step works conceptually with the others. Read your vendor’s “custom domain setup” doc — they’re 80% the same.

Step 3: Add the DNS records your tool gives you

This is the technical step. It’s the one that scares most studio owners, and it takes 60 seconds.

Log into your DNS provider — Cloudflare, Namecheap, GoDaddy, wherever you bought the domain. Find “DNS records” or “DNS settings”. Add a new record:

• Type and target: whatever your tool’s custom-domain wizard tells you to add (some tools issue a CNAME, others issue an A-record + TXT pair — copy the exact values from the wizard, don’t guess)
• Name: portal (or whatever subdomain you want)
• TTL: leave default (usually 1 hour)

Save. Wait 5–60 minutes for DNS propagation. Go make coffee.

If you’re on Cloudflare

If your tool issues a CNAME (some do, some issue an A-record + TXT pair instead), the subdomain needs to be DNS-only (grey cloud), not proxied. Click the orange cloud icon to flip it to grey. Cloudflare’s proxy interferes with the SSL handshake your tool performs and is the single most common cause of “portal verified but doesn’t load” issues. For A-record setups this is usually not needed, but check your tool’s docs.

Step 4: Verify and turn on HTTPS

Back in your tool’s custom-domain settings, click “Verify”. It should flip to a green check. HTTPS is automatic on every modern tool — you don’t need to buy a certificate from anyone.

Test it: open portal.your-studio.com in an incognito tab. You should see your portal, with a padlock icon, with your domain in the URL bar.

Step 5: Upload your brand kit

In FlowShot this is one screen called “Brand Kit”. You upload a logo, pick an accent color, and the whole portal renders with those tokens.

A few rules that save pain later:

• Logo: SVG if you have it, otherwise a 2000px PNG with transparent background. Don’t use JPG — it gets fringed against any non-white background.
• Accent color: one color. Not five. More colors mean more decisions that won’t agree with each other across modules. Use your second color only for tiny callouts.
• Typography: most tools default to system fonts. If you want a custom face, make sure it’s a Google Font or uploadable as a WOFF2 file.
• Favicon: often overlooked, but it’s what shows in the browser tab when the client has 30 tabs open.

Step 6: Wire the modules together

The portal is live. Now turn on the modules you actually use:

• Proposals — for pre-booking package selector
• Contracts — for e-signing
• Invoices — for retainer + balance
• Delivery — for final galleries
• Questionnaires — for pre-shoot intake

In FlowShot these are per-project toggles, so a corporate one-off doesn’t show “Contract” if you don’t need one, and a questionnaire-only intake doesn’t show “Invoice”. Toggle on what matches the project, nothing more.

Step 7: Send a test project to yourself

Before any real client touches it, create a dummy project and assign yourself as the client. Walk through every module the way a couple would. Can you approve the proposal? Does the contract render correctly on mobile? Does the invoice display correctly, and can you mark it paid? Can you send the delivery link from the portal once the balance is marked paid? Do the notification emails go out with your domain in the From line?

Test on mobile. 80%+ of wedding clients open the portal on their phone first.

The before/after

Before, the typical client flow is fragmented:

• Proposal: a PDF attached to a Gmail thread
• Contract: a DocuSign URL (docusign.net)
• Invoice: a separate URL or email attachment outside your domain
• Delivery: a Pixieset URL (pixieset.com/abc123)

That’s 4 separate URLs across 4 separate domains. Clients get confused, they lose links, and they email you asking “where’s the gallery again?” two months after the wedding.

After, the same flow lives on one URL:

• portal.your-studio.com/anna-lars — every module, one address, your domain

The client bookmarks one page. They come back to it. They forward it to their mom. Your brand is the first and the last impression.

The weekend checklist

If you start Friday evening, this can be live by Sunday night:

• Friday: buy domain (if you don’t already own one), pick the tool, plan the subdomain
• Saturday morning: add DNS records, wait for propagation, verify
• Saturday afternoon: upload brand kit, set up your first project template
• Sunday: walk through a dummy project end-to-end, test on mobile, polish copy

Total: roughly 6 hours of actual work spread across a weekend. Most of the elapsed time is waiting on DNS.

---

If you want a portal that covers all 5 modules (proposal, contract, invoice, delivery, questionnaire) on your own domain, out of one tool — that’s FlowShot’s client portal. Custom domain is on the Business plan ($89/mo). Starter ($25/mo) and Pro ($49/mo) host the same portal on a FlowShot-served URL with your Brand Kit applied.