::
=>
11001
FF
01
::
//
::
11001
01
//
0xA3
{}
::
{}
FF
0xA3
=>
FF
=>
All case studies
Portail clientNext.jsHubSpot

A client portal that replaces the status email

A single client area for sales, invoicing and shipments — powered by a custom REST API and kept in sync with HubSpot.

ClientWobz

Visit the site
Screenshot of the Wobz website
The client

A support team saturated with status questions

Wobz tracks sales, invoicing and shipments across several systems. As long as clients cannot reach that information, every status question — where is my order, can you resend that invoice — goes through a person.

That volume is not a sign of poor organisation. It is a sign of information that is accurate but unreachable from the outside.

The challenge

Exposing distributed data without duplicating it

The data already existed, spread across sales, invoicing and logistics tools. Building a parallel database to feed a portal would have created two versions of the truth, and therefore discrepancies.

The portal also had to stay consistent with HubSpot, where the commercial relationship and conversation history live, without forcing the team into double entry.

The solution

A REST API as the single point of truth

We built a dedicated API layer that aggregates data at the source and exposes it to the portal, rather than copying it. The portal reads; it does not store.

01

Real-time sales tracking

Clients see their orders and progress without going through a contact. Statuses come straight from the management systems, which removes the gap between what the client sees and what the team sees.

02

Self-service invoicing

Invoices and supporting documents are available on demand. Document resend requests, a significant share of inbound contacts, drop out of the support queue entirely.

03

Integrated shipment tracking

Logistics tracking is brought into the portal rather than pushed out to a carrier site. Clients keep one entry point for the whole life of an order.

04

HubSpot synchronisation

The portal and HubSpot share the same commercial reality. Teams keep their CRM as their working tool, with no double entry and no manual exports.

Tech stack

The technologies we chose

Laravel for the API and aggregation logic, a reactive client interface, and the HubSpot API to keep the commercial relationship in sync.

Next.js

Node.js

API REST

HubSpot API

The outcome

Support handles requests, not status checks

Recurring tracking and document questions now resolve on their own. The time the team spent on them goes back to work where they genuinely add value.

MPWB

Working on something similar?

Give us thirty minutes. We will tell you plainly what is feasible, at what budget and on what timeline.

Response within 24h 100% confidential No commitment