---
title: "Build or Buy a Client Portal? What Running Our Own Taught Us"
description: "Why we built our own client portals instead of paying for SaaS, what a secure portal needs, and how a data room differs. Two live portals, one base."
author: ["Yevhen Borovoi"]
date: 2026-11-19
updated: 2026-11-19
section: "Business & Strategy"
language: en
canonical: https://peretz.agency/blog/build-or-buy-client-portal
publisher: "Peretz Agency"
---

# Build or Buy a Client Portal? What Running Our Own Taught Us

> Why we built our own client portals instead of paying for SaaS, what a secure portal needs, and how a data room differs. Two live portals, one base.

![Five different keys on a light table, a brass key, an office key, a key card, a car key and a small lock key, and apart from them one gold key on a red ribbon, under the headline Five Drives, One Door](https://peretz.agency/photos/1/blog/build-or-buy-client-portal.jpg)

## We now run two client portals of our own: one for PERETZ projects and one for the DeZZign architecture studio, and a data room for The Structure is next. Here is why we built them instead of buying a subscription, what changed and what did not, which features a secure portal cannot do without, and when a ready-made tool is still the better choice.

### The short answer

**Buy a ready-made client portal when your projects are simple, your team is small and nothing you share is sensitive. Build your own when the work has its own shape (roles, sections, approvals, contractors), when files are confidential, or when the subscriptions across your business already cost more each year than a system you would own.**

We reached the second answer twice. Our agency projects needed stages, approvals and requests in three languages. The architecture studio needed sections by discipline and contractors who see only their part. Both portals now run on one codebase that we own, host and develop, and every new business gets the base plus its own logic instead of a new subscription.

|  | Ready-made SaaS portal | Your own portal |
| --- | --- | --- |
| Start | Days: sign up, invite people | Weeks: brief, build, test, launch |
| Cost | Per seat or per workspace, every month, for as long as you use it | Paid once by stages, then hosting and development you choose |
| Fit | Your process bends to the tool | The tool follows your process: roles, sections, stages, approvals |
| Data | Lives on the vendor's servers under the vendor's terms | Lives where you decide, under your rules |
| Best for | Small teams, simple projects, nothing confidential | Recurring client work, contractors, sensitive files, several businesses |

### Before the portal: five drives and no answers

Before the PERETZ portal, a project lived everywhere at once. The client had an internal Google Drive. Our designers had their own, the marketers had theirs, and anyone who joined later brought one more. Everyone agreed at the start to keep files in a shared repository and to log decisions in the CRM. In practice almost nobody did, and the agreement lasted until the first deadline.

**The cost was not the drives themselves but the questions they produced.** Which version of the brief is current? Who approved the second round of the design, and when? Where is the file the client sent last Tuesday? Each question took minutes on its own, and together they took hours every week from both sides. Worse, the answer often depended on whose memory was better, which is a poor basis for a conversation about deadlines or a disputed approval.

> Five folders in five places means nobody owns the truth.

We tried to fix it with tools made for other jobs. A CRM is built for sales, a task tracker for developers, a shared drive for files. None of them shows a client the project the way a client thinks about it: what has been done, what is happening now and what is waiting for them. That gap is what our portal was built to close, and we told the story of its launch in [PERETZ Clients Now Have Their Own Portal](https://peretz.agency/blog/peretz-client-portal).

This is how a project looks in the portal today: its status, stages, links, documents and latest changes on one page.

![A project page in the PERETZ client portal: status, stages with progress, links, documents and latest changes](https://peretz.agency/photos/1/blog/build-or-buy-client-portal/05-peretz-portal-project.jpg)
*A project in the PERETZ portal: status, stages with progress, links, documents and the latest changes on one page. Client details are blurred.*

### Why we did not buy one

There are good client portal products on the market, and we looked at them. Three things made us build instead.

**First, the subscriptions had already added up.** Across our businesses, the ready-made services we paid for every month came to roughly $1,500 to $2,000, an approximate figure from our own accounts in 2026. Each one was reasonable on its own: a drive here, a form builder there, a project tool, a scheduling app, a client portal on top. Together they were a second rent, and every new person or project made it bigger. A system we own costs money to build and to run, but it does not grow a monthly bill with every seat.

**Second, security.** A portal holds contracts, drawings, financial files and the history of every decision. In a SaaS product those files sit on the vendor's servers under the vendor's terms, next to thousands of other customers, and access rules are whatever the product offers. We wanted to decide who sees what, where the files live, what gets checked before a file is accepted and how long anything is kept.

**Third, we did not want to be the shoemaker without shoes.** We build custom systems for clients: [web applications and SaaS products](https://peretz.agency/services/web-application-development), CRMs, internal tools. Telling a client to own their core system while our own projects ran on five rented services would have been hard to defend. Now the portal is also a live demonstration: a client can see how it works from the inside before we build one for them.

### One base, two different businesses

The PERETZ portal came first. Each project has stages with dates and statuses, approvals that are recorded with the name of the person and the time, requests the team is waiting for, documents with versions, meetings and discussions. Clients choose Ukrainian, Russian or English, and the team sees what needs attention today, from a late approval to a request nobody has answered.

In November 2026 the portal got a lighter interface. Every block is now a tile of frosted glass on one grid, the menu folds into a narrow strip of icons when a page needs more room, and clients see the new look at once, with nothing to switch on. The team starts its day on the overview.

![Team overview in the PERETZ client portal: what needs attention, projects by status and the latest changes](https://peretz.agency/photos/1/blog/build-or-buy-client-portal/04-peretz-portal-overview.jpg)
*The team overview in the PERETZ portal: what needs attention today, projects by status and the latest changes. Client names are blurred.*

When the DeZZign architecture studio needed a portal, we did not start from zero and we did not copy the agency portal as it was. An architectural project is made of disciplines: architecture, structure, MEP engineering, interior, lighting, landscape, visualization, procurement, construction supervision. Each discipline has its own sequence of stages, from the design brief to the designer's site supervision. So the studio's portal organises a project into sections, and each section opens with its own stage template.

![DeZZign project portal: a house project split into architecture, structure and interior sections, each with its own stages and progress](https://peretz.agency/photos/1/blog/build-or-buy-client-portal/01-dezzign-portal-project-sections.jpg)
*One project, three sections, each with its own stages and progress. The demo project and names are fictional.*

The files changed too. Agency projects mostly exchange documents, so the PERETZ portal accepts documents up to 2 MB and big materials go in as links. Architects exchange drawings and renders, so the DeZZign portal accepts files up to 10 MB, including DWG and DXF drawings and JPG, PNG and WebP images, and its link types are drawings, renders, 3D tours and BIM models.

|  | PERETZ portal | DeZZign portal |
| --- | --- | --- |
| A project is made of | Stages of the work | Sections by discipline, each with its stages |
| Outside people | Client roles: decides, takes part, watches | Clients plus contractors per section |
| Files | Documents up to 2 MB | Drawings, renders and documents up to 10 MB |
| Links | Designs, test and live versions, documents | Drawings, renders, 3D tours, BIM models |
| Look | PERETZ paper and red | DeZZign black, its own light theme |

**Most of the code is shared, and the part that differs is exactly what makes each portal fit.** Sign-in, two-factor login, roles, notifications, the file checks, the activity history and the three languages came from the base. The sections, the stage templates, the contractor rules and the studio's look were built for the studio. That is the practical meaning of a system [built around your business](https://peretz.agency/blog/what-building-systems-teaches-about-buying-them): the common parts are solved once, and the time goes into what is specific.

### What a contractor sees

The hardest new rule was the contractor's view. A structural engineer working on a house needs the structure section: its stages, its drawings, its discussions. That engineer should not see the client's budget, the interior concept or the other disciplines' contractors. In a shared drive that rule depends on everyone setting folder permissions correctly every time. In the portal it is the default.

![Section page in the DeZZign portal: structural stages with progress and the contractor attached only to this section](https://peretz.agency/photos/1/blog/build-or-buy-client-portal/02-dezzign-portal-section-contractors.jpg)
*The team adds a contractor to one section and chooses whether they write or only read.*

A contractor signs in and sees only the sections they were added to. They can upload drawings, add links and take part in the topics of their section, but they cannot approve a stage: acceptance stays with the client and the studio. Everything else in the project is closed to them, and the portal checks this on every request, not only in the menu.

![The contractor's own page in the DeZZign portal: only the structure section, its stages in progress and the latest document](https://peretz.agency/photos/1/blog/build-or-buy-client-portal/03-dezzign-portal-contractor-view.jpg)
*The contractor's own page: one section, its stages and their contact in the team.*

### The hard part is people

A portal does not create order by itself. People who are used to their own drive and their own chats keep using them, at least at first. We still have to remind colleagues and clients to put files in the portal and to answer requests there rather than in a messenger. It reminds us of the picture of an opossum in a rubbish bin: it was perfectly happy with its own order and saw no reason for a new one.

**What changes is that order starts to show, and it is visible to everyone.** When the deadlines are on one screen, people see them. When every file has one place, the question "where is it?" has one answer. When an approval is a button with a name and a time, there is nothing to argue about later. Order arrives gradually, project by project, and the reminders become fewer as people find that the portal saves them time.

> The portal does not replace reminders. It makes them shorter.

A few things helped adoption more than any rule. Access by invitation, with the project already set up, so the first visit shows something useful. A daily summary by email of what is waiting for each person. Notifications on the phone for approvals and replies. Three interface languages, so nobody works in a language they find tiring. And the team using the portal first, because clients follow what the team does more than what it says.

### When a ready tool is the better choice

Building your own portal is not always the right call, and we say so to clients. A ready-made product is usually better when:

- you run one or two projects at a time and the process is simple;
- the team is small and nobody has time to describe how the work should run;
- nothing you share is confidential, and standard access rules are enough;
- you need the portal next week, not next quarter.

**The turning point is when the tool starts to dictate the process, or when the monthly bill for it and its neighbours becomes a line you notice.** Another signal is the workaround: a spreadsheet next to the portal to track what the portal cannot, a second tool for contractors, a third for approvals. When the workarounds pile up, the subscription is no longer the cheap option, and a system shaped around your work starts to pay for itself.

### What a secure portal needs

Whatever the business, a portal that holds client files and decisions needs a set of protections that are easy to skip when a project is rushed. These are the ones we built into both portals and recommend as a minimum:

- **access by invitation only**, with no public sign-up and every person tied to the projects they work on;
- **two-factor login**, mandatory for the team and recommended for clients;
- **roles inside each project**: who decides and approves, who takes part, who only reads, plus contractors limited to their sections;
- **files checked before they are accepted**: an antivirus scan of every upload and a nightly rescan, a check that the content matches the extension, files with macros or passwords refused;
- **a full history**: who uploaded, changed, approved or deleted what, and when;
- **internal notes and topics** that only the team sees;
- **a warning before an unknown external link opens**, because a shared link is a common way in for phishing;
- **closed to search engines**, and files served only through the application, never from a public folder.

None of this is exotic. Each point closes a door that is often left open in shared drives and chats, and together they make the portal a place where a client can safely keep the documents of a real project.

### The Structure's data room: a step up

The next portal we are building is a data room for [The Structure](https://peretz.agency/blog/peretz-launches-the-structure), our technical due diligence brand for software M&A. A data room is where a company that is being sold or raising money shows its documents to buyers, investors and their advisors. We described what goes into one in [How to Prepare a Data Room When Selling a Company](https://peretz.agency/blog/data-room-for-selling-a-company); here the question is what the software itself must do.

**A data room needs everything a secure portal has, and more control over what happens after a document is opened.** On top of the list above, The Structure's data room needs:

- permissions per folder and per document, set separately for each buyer group;
- viewing in the browser without download, wherever the seller wants it;
- dynamic watermarks with the viewer's name, email and time on every page;
- a record of who opened which document, when and for how long;
- questions and answers inside the room, routed to the right expert;
- access only after the viewer accepts the NDA, with expiry and instant revoke.

> In a data room, who looked at what is itself information.

There is also a formal side. In M&A, buyers and their counsel often expect a data room provider to hold an independent SOC 2 Type II report or an ISO 27001 certificate. These are audits of a company's security processes, not features of the software. A SOC 2 Type II report covers how controls worked over an observation period of several months, and industry estimates for a small company's first year run from about $20,000 to $60,000 and more. Large deals often use a certified data room that the buyer or the bank chooses. The preparation work, the structure, the index and the checks, is the same either way, and that is where most of the effort goes.

### Built to your brief

Most of what we learned building these portals transfers to other businesses. A clinic needs patient-safe document exchange and doctors who see only their cases. A construction company needs sites, crews and acceptance of work. A consultancy needs engagements, deliverables and client sign-off. We are already discussing a portal for a medical institute, and the base is ready for it.

**We can build a portal to your brief: your roles, your stages, your approvals, your language and your look.** A brief for a portal usually answers a few questions:

- who comes in (team, clients, contractors, partners) and what each of them may see and do;
- what a unit of work is (a project, a case, a site, a deal) and what stages it goes through;
- what has to be approved, by whom, and what an approval means in your contract;
- which files and links people exchange, and how sensitive they are;
- which systems it must talk to: CRM, email, calendar, accounting.

A portal of this kind falls under our [web application development](https://peretz.agency/services/web-application-development), which starts from $25,000. The final figure depends on the number of roles, the integrations and the level of security, and large portals are split into stages with their own estimates. If you are not sure yet whether to build or buy, a [strategic session](https://peretz.agency/services/strategic-session) is the place to work it out on your numbers.

### Frequently asked questions

#### Is it cheaper to build a client portal than to pay for SaaS?

Over several years it often is, if the portal replaces several subscriptions and your team is growing. In the first year a SaaS portal is almost always cheaper. The comparison should include every tool the portal would replace, the cost per new seat and project, and what you would lose if the vendor changed its prices or terms.

#### How long does it take to build a client portal?

A portal on a ready base with roles, stages, files and notifications takes weeks rather than months. Specific logic, integrations with a CRM or accounting, and a higher security level add time, so we split larger portals into stages, each with its own estimate and its own release.

#### Can contractors work in the same portal as clients?

Yes, if the portal has a contractor role with its own limits. In the DeZZign portal a contractor sees only the sections they were added to, can upload and discuss there, and cannot approve stages. The rest of the project is closed to them.

#### Is a client portal the same as a data room?

No. A client portal runs ongoing work between a team and its clients. A data room shows a fixed set of documents to outside parties during a deal, with tighter control over viewing, downloads, watermarks and who opened what. Many features overlap, which is why we build both on one base.

#### Does a data room need SOC 2 or ISO 27001?

The software does not get certified; the company running it does. Buyers in larger deals often require a provider with a SOC 2 Type II report or ISO 27001 certificate. For preparing the documents and smaller deals, the features and the discipline of the process matter most.

**Sources**

- [Euronext Corporate Solutions: virtual data room security features](https://www.corporatesolutions.euronext.com/blog/virtual-data-room-security-features)
- [Intralinks: standards for virtual data room security in high-stakes transactions](https://www.intralinks.com/guides/virtual-data-room-financial-document-security)
- [Scrut: how much SOC 2 compliance costs in 2026](https://www.scrut.io/post/cost-of-soc-2-audit)
- [ISO: ISO/IEC 27001 information security management](https://www.iso.org/standard/27001)

**Project files scattered across drives and chats? Let's look at what your own portal should hold.**

[Book a Strategic Session](https://peretz.agency/services/strategic-session)

[Web Application & SaaS Development](https://peretz.agency/services/web-application-development)

---

Source: Peretz Agency, https://peretz.agency/blog/build-or-buy-client-portal
