P I X E L P E T A L S
Custom Solution · Agency SaaS

One client portal that reshapes itself for every kind of work

Dev, graphics or video — each client signs in to a workspace built around their work type, with approvals and WhatsApp updates baked in.

The Problem

An agency that does dev, graphics and video can't run every client through one rigid dashboard.

A web client wants sprints, releases and sign-offs. A graphics client just wants tickets and proofs. Show everyone the same screen and half of it is noise — and the status updates still happen over scattered WhatsApp and email.

Why it hurts

Spinning up a separate tool per client type means more logins, more places for things to slip, and no single record of what was approved and when. Clients chase you for updates; you chase your team for status. Nothing has one source of truth.

The Solution

One portal that quietly becomes the right portal for each client.

A multi-tenant agency workspace built on Laravel 11 + Livewire 4 + Tailwind + MariaDB. Each client carries a work_type (dev / graphics / video / mixed) that gates the modules they see, with Sanctum auth and approvals and WhatsApp notifications wired in through the Pixel Petals gateway.

Our Approach

Onboard the client

From one admin console we onboard a client, set their type and invite their users — the whole account is stood up in minutes.

Gate the right modules

The work_type field decides what each client sees: dev and mixed clients get sprints and deliverables tracked brief-to-sign-off on a shared board, while others get a simpler tickets-and-attachments flow.

Wire approvals & alerts

A multi-stage release approval workflow means nothing ships without a logged, dated sign-off, and every status change pings the client on WhatsApp through the Pixel Petals gateway — no chasing.

Brand each portal

Per-client name, eyebrow and accent sit behind an admin PIN, so the same codebase quietly becomes the right portal for each client.

Per-client gating

Same portal, different modules per client

A single field — work_type — decides what each client sees. A dev client gets sprints, releases and approvals; a graphics client gets a leaner tickets-and-proofs flow. One codebase, one login pattern, the right tools for each.

Approvals + WhatsApp

Approved here, notified there — automatically

Every deliverable moves through a logged sign-off. The moment it's approved, the Pixel Petals WhatsApp gateway pings the client — so the record and the notification stay in step, with no manual chasing.

Proof

One portal adapts to every client — and every approval is logged with a WhatsApp ping.

14 active clients on one adaptive portal
480+ deliverables tracked from brief to sign-off
320+ approvals logged, each with a WhatsApp notification
0 status-chase email threads — replaced by in-app approvals

Now the workspace we onboard every new client into.

700+ projects · 450+ UK/EU buyers · 5★ on PeoplePerHour

Let's build yours

Want a client portal that fits how your agency actually works?