Portal

A portal is a secure section of your website where users log in to see only their own information: orders, documents, pricing, status, and downloads. We build them for companies tired of endless back-and-forth emails. Live in weeks, not months.

Which type of portal

A client portal is for your customers: their files, invoices, and progress. A dealer portal is for your sales channel: dealer-specific pricing, ordering, and technical documentation. A marketing portal is for everyone working with your brand: imagery, logos, and campaign materials. And an internal portal is for your own team, closer to a dashboard. The underlying technology is largely the same; the difference lies in who logs in and what they are permitted to see.

When you need this

People call or email to request information you already have. You send the same documentation to the same hundred addresses every quarter. Prices vary by customer and are currently shared via PDF. Someone asks for the status of something that is already visible in your system. Wherever that happens, a portal belongs.

What a portal does

Log in with a personal account. Permissions per role, so one person sees different prices or documents than another. Data from your own systems, current instead of an export from last month. Download documents, place or track orders, submit requests. And an admin environment for you, so you can manage users and content yourself.

How we approach it

We start with the process, not the screen. Who logs in, what should they see, what are they allowed to do, where does the data come from? Then we build the smallest version that solves that and take it live. Users start using it, we observe, and we expand based on that feedback. That is faster and cheaper than spending a year on specifications.

With what

The interface in Webflow, in your brand style. Login, permissions, and logic via Wized. Database and API in Xano. If your data is already in Airtable or an ERP, we can connect to that. For complex interfaces with large amounts of data per screen, we build in Next.js.

Standard package or custom build

There are off-the-shelf portal packages available. These work well if your process is similar to everyone else's: sharing documents, creating a ticket. As soon as pricing varies by customer, data needs to be pulled from your own systems, or the portal needs to look like your own website, you will hit their limitations. That is when we build it ourselves, using a stack where most components already exist. You won't be paying for a login screen to be reinvented.

What it costs and how long it takes

That depends on the number of roles, the integrations, and the amount of data involved. We typically build a first working version in four to eight weeks. We work with a fixed price per phase, so you know exactly where you stand at every step. In addition, you pay for the subscriptions for Webflow, Wized, and Xano, which usually total anywhere from a few dozen to a few hundred euros per month.

Who it is not for

If you only want to restrict a few pages for members, then Memberstack is simpler and cheaper. If you have a handful of clients who request something once a year, a portal won't pay for itself. And if a standard package does what you need, then go with that package. We’ll tell you if that’s the case.

Where we’ve done it

For Mitsubishi Turbochargers & Engines Europe we built an environment where dealers across Europe can filter marine engines based on the specifications that matter in their sector, with the correct spec sheet for every engine. Hundreds of engine types, managed from a single source and synchronized to the site via API.

Read more

Connect to your ERP or CRM: system integrations. Documents that automatically update with your data: document generation. If you are unsure which type of portal you need, send us an email describing who needs to log in and what they currently request. You will hear back within a few days about the most efficient version for your needs.