Client Portal Development: Three Real Builds in Six Weeks, Two Weeks, and One Day

A client portal earns its keep when it moves one real workflow behind a login on the client's own domain. Client portal development at webvise has produced three shapes of this: a fintech request portal, an internal AI-agent portal, and an admin dashboard that went live in one day.

The three builds took six weeks, two weeks, and one day.

If your client requests live in an inbox and your status updates are screenshots, a portal is the obvious fix, and every SaaS vendor sells one. This article shows what three real webvise portals cover, what they cost, and how long each took. Every number below comes from a project that is in production today.

• One workflow behind a login is the whole job. OHYP's portal is a 10-step financing application, MP Bau's is two AI agent tools, and Gabrys' is a usage dashboard with file exports.
• The skeleton repeats, the workflow is the new work. The agent portal that took two weeks to build at MP Bau was ported to an architecture practice in one day.
• Portal builds at webvise have run from a four-figure add-on up to a full-stack build under €10,000. Larger operations platforms reach into five figures.
• Request turnaround is the payback metric. OHYP answers financing requests in under 24 hours through an admin dashboard that covers the whole request lifecycle.

If one workflow in your business is ready for a login, webvise builds client portals and business apps with auth, roles, file uploads, status tracking, and an admin backend as the standard kit. The scoping call names the workflow your v1 should cover and the price band it lands in.

Three Portal Shapes, Three Timelines

Client portal development covers more ground than the phrase suggests. The three portals webvise shipped solve different problems behind the same kind of login: one faces a fintech's customers, one gives a construction firm's staff AI tools, and one gives an architecture practice a closed admin workspace.

The timeline column is the honest one. New workflow takes weeks: the 10-step form and certificate pipeline at OHYP, the two agent tools at MP Bau. Auth, roles, and protected routes repeated in every build, and porting a finished workflow to a second company took a single day.

OHYP: A Financing Portal in Six Weeks

OHYP needed its core business behind a login: a customer applies for financing, the team processes the request, a certificate goes out. webvise built the full-stack portal in six weeks. Applicants move through a 10-step form, and the portal generates the PDF certificate automatically.

An admin dashboard covers the whole request lifecycle, from new application to issued certificate. Turnaround sits under 24 hours, and that is the number OHYP's customers feel. The build scores 96 on Lighthouse.

For a fintech the portal is the product, so the budget bought the entire request pipeline rather than a marketing site. Where that price sits against other build shapes is mapped in the custom web application cost guide.

MP Bau: An AI-Agent Portal on the Client's Own Domain in Two Weeks

MP Bau, a construction firm, became the first webvise client with a production internal AI-agent portal. The portal is password protected, runs on the company's own domain, and staff sign in by email.

Inside are two drag-and-drop agent tools, a curated model list served over one gateway, and per-run cost tracking, so every run shows what it cost. Results survive closing the tab. What the two tools do day to day is covered in the document automation article.

The build decision came out of an on-site workshop, and the portal was live within about two weeks of it. An internal portal needs a login, the tools, and the cost line, and little else. That narrow scope is what a two-week timeline looks like.

Gabrys Architektur+: The Same Portal Shape, Ported in One Day

Gabrys Architektur+, an architecture practice, got the same two agent tools in a portal of its own, built in one day. The build added a dashboard with a run, token, and cost overview, file upload with export to CSV and XLSX, and closed signup: accounts exist only when the admin creates them.

One day is the category's economics in a single number. Auth, roles, the gateway, and the tool pattern already existed, so the second portal paid only for what was new to it. That reuse is the reason webvise scopes portals around workflows and treats the login skeleton as solved.

What Belongs in a Portal v1

All three builds drew from the same module list, the one webvise's portal offer names outright.

• Authentication and roles. Email login, closed signup where accounts should stay admin-created, and a permission model that decides who sees what.
• Protected routes and file uploads. Documents live behind the login, with export paths like the CSV/XLSX download at Gabrys.
• Status tracking and request workflows. OHYP's 10-step application and lifecycle dashboard are this module at full size.
• Admin backend and notifications. The team side of the portal, plus the messages that tell both sides something changed.
• Integrations. CRM, payments, email, and analytics connect when the workflow calls for them.

The v1 rule across the three builds: take the modules the one workflow needs and skip the rest. OHYP's budget went into the request workflow and the certificate pipeline. MP Bau's went into the agent tools and the per-run cost line. A v1 scoped this way lands in the timelines above.

What a Client Portal Costs at webvise

Portal builds at webvise have run from a four-figure add-on to an existing client site up to a full-stack request portal under €10,000. Larger operations platforms reach into five figures. The driver is how much new workflow goes behind the login, because the skeleton repeats across builds.

webvise has delivered 25+ projects, and the three portals above are all in production. If one workflow in your business should live behind a login, describe it in two sentences and send it over. The reply names the shape, the price band, and the timeline.