Client Portal Software for Interior Designers: What to Look For

· 9 min read

Client portal software for interior designers needs to do four things: show the client the current estimate with photos, let them approve or reject each item, show dates and payments, and keep the studio's internal figures private. Everything else is optional. A portal that does these four things, without forcing the client to create an account, replaces most email attachments and message threads.

Why email and messengers stop working

On a small project, a PDF estimate sent by email is enough. The problems start when the project has 60 or more items, several rounds of changes and a client who answers in three different channels. Then you spend time answering one question: which version is current, and what did the client actually approve?

The table compares the usual channels with a dedicated portal.

CriterionEmail with PDFMessengerShared spreadsheetClient portal
Client always sees the current versionNo, old attachments stay in the inboxNo, files get buried in the chatYes, but the sheet often shows too muchYes, one link
Approval is recorded per itemNo, it hides inside a replyNo, it is a message such as "ok, the sofa is fine"Only if the client edits a cellYes, approve or reject on the item
Questions are tied to an itemNoNoComments, if enabledYes
Control over visible dataFull, but manual for each fileFull, but manualHard: hidden columns can be unhiddenSettings by data type
Effort for the clientLowLowMediumLow if no registration is needed

The spreadsheet row deserves attention. Hiding a column in a shared sheet does not mean the data is protected: the client can often unhide it. If your estimate contains purchase prices and markup, do not share the working file with the client. See the comparison of spreadsheets and a dedicated tool for more on this.

The core features of a simple portal

Most studios do not need a complex client area. They need a small set of functions that match how a design project moves from concept to installation.

Estimate with photos and status

The client should see a readable list: photo, name, quantity, price, dimensions and the current status of each item. A bare table of names and numbers causes questions, because clients identify furniture by how it looks, not by SKU.

Approval and rejection per item

Approval is the main reason to have a portal. A client who clicks approve on a specific item gives you a clear signal to order. A client who rejects an item gives you a reason to offer an alternative. Check that the portal supports a view-only mode as well: some clients should only look, for example a family member or a contractor.

Questions on the item

A question asked inside the item card reaches you with the context attached. Compare that with a message that says "what about the grey one?" and no indication of which grey one.

Timeline and payment schedule

Clients ask the same two questions again and again: when will it arrive, and when do I pay? If the portal shows the timeline and the payment schedule, a large part of those messages disappears.

Here is a practical split of features by priority.

PriorityFeatureWhy
Must haveEstimate with photos and statusesThe client sees what they are buying
Must haveApprove / reject per itemA clear decision record
Must haveAccess by link, no client accountClients rarely finish registrations
Must haveControl over visible fieldsProtects margin and supplier terms
Should haveQuestion button on each itemKeeps questions in context
Should haveTimeline and payment scheduleReduces status requests
Should haveLink expiry and revocationEnds access when the project ends
Nice to haveDelivery documents and acceptance photosUseful for clients who want proof
Skip at firstChat inside the portal, custom branding, mood boardsAdds setup time without changing decisions

Controlling what the client sees

Visibility is where a portal can go wrong. The client should see what helps them decide, and nothing that exposes how the studio earns. Purchase price, supplier discount and markup are internal. Supplier invoices and supplier payment status are internal by default for most studios, though some choose to share them under a cost-plus agreement.

Suggested defaults

DataDefaultComment
Photos and galleryShowCore of the decision
Client priceShowNeeded for approval
Supplier name and product linkDependsHide it if you do not want the client to buy directly
SKU and dimensionsShowHelps check fit
Purchase price, markup, profitHideInternal economics
Supplier invoices and supplier paymentsHideShow only if the contract requires it
Planned and actual datesActual only, or bothPlanned dates create expectations
Date changesHide at firstShare them when you can explain the reason

Checklist before sending a link

  • Open the portal in preview mode and read it as the client would.
  • Confirm that purchase price, markup and profit are not visible anywhere.
  • Check that rejected and optional items are labelled clearly.
  • Decide whether dates are shown as actual only or as planned and actual.
  • Set an expiry date for the link if the project has a fixed end.
  • Choose view-only or approve and reject permissions for each recipient.
  • Check that the same rules apply to documents: receipts and acceptance photos should follow the same visibility settings.

One technical point is easy to miss. Hidden data should not be sent to the client's browser at all. If a portal only hides a field visually, the value may still be readable in the page source. Ask the vendor how this works, or test it with a colleague. Also check that document links stop working when you revoke access.

How to test a portal on a real project

A feature list does not tell you whether the portal fits your workflow. A short pilot on one live project does.

  1. Pick a project with at least one room and 15 to 30 items, including a few with alternatives.
  2. Enter or import the estimate and add photos for every item.
  3. Set visibility rules before you generate any link.
  4. Open the preview and look for anything the client should not see, such as internal notes.
  5. Send the link to one client who is comfortable with technology and ask them to approve two items, reject one and ask one question.
  6. Check that you received the question with the item attached, and that the approval is recorded where your team will see it.
  7. Revoke the link and confirm that the portal and the documents no longer open.

After the pilot, count what changed. Did the number of status emails drop? Did approvals arrive faster? If not, the problem may be the content you showed, not the tool.

Habits that make any portal work

  • Send one link per project and tell the client it is the only place with the current estimate.
  • Group approvals: ask for decisions room by room, not item by item over several weeks.
  • Always give a cheaper or faster alternative next to an item you expect to be rejected.
  • Reply to questions in the same place the question was asked.
  • Mention the portal in your contract or onboarding message, so that clients know approvals there count as decisions.

How to do it in ArchiBoard

The client portal feature works through a link, so the client does not need to register. The client sees the estimate with photos and deadlines, the "Saved for you" list, the payment schedule and the timeline. Project basics are described in the projects chapter of the help center.

  1. Open the project and go to "Client portal".
  2. On the "Link access" tab, create a link and choose the permission: "View only" or "View + approve / reject". Add an expiry date if you need one. You can revoke the link at any time.
  3. Open the "Client preview" tab to see the portal through the client's eyes.
  4. In the block "What the client sees in the item card", tick the data to show: "Photo and gallery", "Price", "Supplier and link", "SKU and dimensions", "Receipts", "Supplier invoices", "Acceptance photos", "Supplier payment", "Date changes" and "Question button". For dates, choose "Actual only", "Actual + planned" or "Hide".
  5. To change what one item shows, open that item in the preview and use the "Visibility of this item" block at the bottom of the card. "As in project" returns it to the project settings.
  6. Send the link. When the client asks a question on an item, it arrives as a task for the responsible person.

By default the client does not see supplier invoices, supplier payment or date changes. Hidden data is never sent to the client's browser, and documents stop opening once the link is revoked or has expired. More detail is in the step-by-step client portal guide.

FAQ

What is the best client portal software for interior designers?

The best choice is the one that covers your must-haves without extra setup: estimate with photos, per-item approval, access by link and control over visible fields. Test two or three options on one live project, as described above, and compare how many status messages you still receive afterwards.

Does the client need to create an account to use a portal?

It depends on the tool, but for most design clients, no account is better. Registration is a common point where clients stop. Access by a private link works well if you can set permissions, set an expiry date and revoke the link when the project closes.

What should I hide from the client in a portal?

Hide purchase prices, supplier discounts, markup and profit. Many studios also hide supplier invoices, supplier payment status and date changes, unless the contract says otherwise. Always check the preview before sending a link, and confirm that hidden fields are not only masked on screen.

Is a portal worth it for a small studio with few projects?

Yes, if you handle more than a few decisions per project. The benefit is not the number of projects but the number of approvals and questions. A studio of one or two people loses the most time when the same decision is spread across email, messages and phone calls.

Can a client approve items without seeing prices?

Yes, if the portal lets you switch price visibility on or off. This is useful when a fixed fee covers the whole scope, or when a decision maker approves design while another person handles payment. Set the rule once at project level, then change individual items only when needed.

Read next