LIVE · IN PRODUCTION

A B2B partner-program portal

How a multi-tenant onboarding portal with e-signature went live in about a day and a half — and grew durable reminder workflows on top, in hours.

Project code: CASE-003
Domain: B2B · PARTNER ONBOARDING
Investment: from CHF 2,000

A multi-tenant partner-program portal — group-based admin auth, multi-user partner organisations with roles, invites and team management, a full agreement-signing pipeline (inline docx preview and a countersigned PDF), a deals pipeline, a media resources hub with self-healing thumbnails, a public landing with an intro-meeting gate, and an admin dashboard. The core was live in about a day and a half — and once it was, durable signup + signature reminder workflows were added on top in hours, because the foundation was built to extend.

At a glance

Core portal, live: ~1.5 days
Workflow add-on: Hours
Status: Live

Map the landscape

Understand

The partner program worked — but it ran by hand. Agreements went back and forth over email, signatures were chased one reminder at a time, and partners, deals and resources lived in spreadsheets and inboxes. It scaled with effort, not with software.

The audience: The program admins running onboarding, and the partner organisations — several people per company — signing agreements and managing their own teams.
The baseline: Manual onboarding — agreements emailed for signature, deals tracked in a sheet, reminders sent by hand, resources scattered across drives.
The groundwork: The program's shape was already clear — partners, agreements, deals, resources. The job was to give it a real, self-serve system, not to invent the process.

Draw the boundaries

Shape

The portal is really five feature blocks. The cut: build the core onboarding product first — and design it around one auth and policy model so the durable reminder workflows could be added later, on top, in hours rather than as a rebuild.

In the cut: Group-based admin auth, multi-user partner orgs (roles, invites, team management), the agreement-signing pipeline (docx → countersigned PDF), a deals pipeline, a resources hub, a public landing with an intro-meeting gate, and an admin dashboard.
Designed to extend: The durable signup + signature reminder workflows were deliberately left for after launch — a solid foundation makes them a bolt-on, not a project.
The discipline: One auth and resource-policy model, paid for once, that every later feature inherits for free.

WIREFRAME

The agreement-signing pipeline — an inline docx preview becomes a countersigned PDF with a click-to-scroll outline and highlighted signature placeholders.

Ship something real

Build

Built in focused passes. The core portal — auth, the e-signature pipeline, multi-user partner orgs and the resources hub — was live in about a day and a half. Then, once it was in production, the durable reminder workflows were added on top in hours.

The core: Multi-user partner organisations (roles, invites, a team switcher), the agreement-signing pipeline (inline docx preview, countersigned PDF with an outline and placeholder highlighting), the resources hub with self-healing async thumbnails, and the admin dashboard.
The extension: Durable signup + signature reminder workflows — with backfill, de-duplication and an audit ledger — bolted onto the finished portal in hours, not weeks.
The stack: Maravilla Cloud — group-based auth, per-partner resource policies, document database, object storage with async thumbnails, and durable workflows. No servers.

WIREFRAME

Multi-user partner organisations — each company runs its own team, with roles, invites and statuses, all scoped to that org by per-partner policies.

Hand over the keys

Hand over

The program got a live, multi-tenant portal that runs itself: partners onboard, sign and manage their own teams; admins watch a dashboard; and the reminders fire on their own — no more chasing signatures by hand.

WIREFRAME

The durable reminder workflows the team now owns — signup and signature nudges that fire on schedule, deduped and backfilled, with a full audit ledger.

The takeaway

Most of what looks like a multi-week B2B build is the foundation — the auth model, the policy model, the signing pipeline. Build that once, sharply, and the rest compounds: this portal's durable reminder workflows were added to a live system in hours. The FastTrack cut is what decides which work is foundation and which can wait.

That's why "two weeks max, usually faster" is a floor, not a boast.

POST-LAUNCH

Live and multi-tenant — partners onboard, sign and manage their own teams, and the reminders fire on their own.

Built on Maravilla Cloud

None of this was bespoke infrastructure. Every capability below is a Maravilla Cloud building block — so the engagement spent its time on the product, not the plumbing.

Authentication: Group-based admin sign-in, and multi-user partner organisations where each company's people log in.
Authorization: Per-partner resource policies scope every organisation to its own agreements, deals and resources.
Database: Partners, agreements, deals and resources in the document store — the system of record for the program.
Storage: Uploaded agreements and resource files in object storage, served straight to the portal.
Media Transforms: docx agreements rendered to countersigned PDFs, and resource uploads thumbnailed asynchronously.
Workflows: The durable signup + signature reminder nudges — surviving restarts, with backfill, de-dup and an audit ledger.
Push Notifications: Those reminder nudges reach partners as Web Push — the prompt lands in the browser, no inbox required.
Edge Runtime Platform: The whole portal — SSR, the public landing, the admin dashboard — runs on the edge with no servers to keep alive.

EXPLORE MARAVILLA CLOUD →

BEGIN YOUR PROJECT → MORE CASE STUDIES