Implementation BlueprintExecution layer

Offistack White-Label Client Portal Rollout (7-10 days)

A repeatable deployment that rebrands Offistack with the agency's logo and custom domain, then hands clients a branded file-sharing and approval portal. Built for agencies that want a resellable delivery surface without custom infrastructure. Time: 7-10 days.

By InnovaAI ResearchPublished

Client Portal

How do you implement it?

Blueprint

Offistack White-Label Client Portal Rollout (7-10 days)

A repeatable deployment that rebrands Offistack with the agency's logo and custom domain, then hands clients a branded file-sharing and approval portal. Built for agencies that want a resellable delivery surface without custom infrastructure.

Prerequisites
  • An Offistack plan sized to the client book: Starter (₹499 one-time) covers 200 GB and up to 50 clients, Freelancer (₹999 one-time) covers 500 GB and unlimited clients
  • Agency domain with DNS access so the portal can resolve on the agency's own URL rather than an Offistack subdomain
  • Logo files in the formats Offistack's branding settings accept, plus a one-page brand sheet for portal colors and naming
  • A folder taxonomy agreed with the client before migration, so file permissions map to real project phases
  • Named client-side approver for each active project, since Offistack approval workflows route to specific people
Execution Timeline
  • 1.Create the agency Offistack workspace and set the account name to the agency brand, not the client's
  • 2.Upload the agency logo and confirm it renders on the portal login screen
  • 3.Point the custom domain at Offistack and verify the portal loads on the agency URL
  • 1.Add team member accounts for every delivery lead who will touch client files
  • 2.Assign roles so juniors can upload but only leads can approve or delete
  • 3.Confirm the plan's team member ceiling (3 on Starter, 10 on Freelancer) before inviting more staff
  • 1.Create the first client account and a project folder inside it
  • 2.Build the subfolder structure to match the agreed taxonomy (briefs, working files, finals, approvals)
  • 3.Set access permissions per folder so the client sees finals and approvals but not internal working files
  • 1.Upload sample files to validate versioning behavior across two or three revisions
  • 2.Configure advanced sharing controls on the folders that leave the agency
  • 3.Test a share link from an incognito browser to confirm the client experience without an Offistack login
  • 1.Turn on the file approval workflow and route a test file to the client approver
  • 2.Walk the approver through approving and rejecting so the audit trail is real, not theoretical
  • 3.Check client activity tracking to confirm views, downloads, and approvals register correctly
  • 1.Migrate the client's live documents into the portal workspace in batches by project
  • 2.Reconcile migrated file counts against the source folder before deleting anything from the old location
  • 3.Set trash retention expectations (7 days on Free Forever, 15 days on Starter) so the client knows the recovery window
  • 1.Run a 45-minute training session with client staff on uploads, approvals, and finding files
  • 2.Record the session and store it in the portal as the client's own reference file
  • 3.Publish a one-page portal guide inside the client's root folder
  • 1.Package the portal into the agency retainer line item with a named monthly fee
  • 2.Draft the client-facing handover note explaining what the portal replaces (email attachments, ad-hoc cloud links)
  • 3.Confirm which Offistack plan the client book sits on and whether a plan upgrade is needed as accounts grow
  • 1.Repeat the client account setup for the next two clients using the same folder template
  • 2.Log setup time per client to price the next rollout accurately
  • 3.Review activity tracking across all live portals for anything the client has not opened
  • 1.Hand the portal to the delivery team with a short internal runbook
  • 2.Schedule a 30-day check-in to review approval turnaround and storage headroom
  • 3.Close the rollout and move the client to steady-state portal management
Tool cost is a one-time ₹499 for Starter (200 GB, up to 3 team members, up to 50 clients) or ₹999 for Freelancer (500 GB, up to 10 team members, unlimited clients). Agency delivery time of 7-10 days is the real cost; at typical agency day rates the build lands in the low four figures, with no recurring Offistack subscription to absorb.7-10 days
ROI Logic

Offistack's one-time pricing means the agency pays ₹499 or ₹999 once and can resell portal access across a client book indefinitely, so the margin is set by the retainer the agency attaches to the portal rather than by a per-seat tool bill. A single ₹999 Freelancer licence covering unlimited clients supports a portal line item on every retainer, which is why the rollout pays for itself on the first two or three clients. The constraint is delivery time, not licence cost, so the playbook's value is in templating the setup so each additional client takes hours instead of days.

Deliverables
  • Agency-branded Offistack portal live on the agency's custom domain with logo applied
  • Per-client project folder structure with permissions mapped to briefs, working files, finals, and approvals
  • Configured file approval workflow with a tested audit trail and named client approvers
  • Migrated client document set with reconciled file counts and a documented trash retention window
  • Recorded client training session and one-page portal guide stored inside the client's root folder
Definition of Done

The client has approved at least one real file through Offistack's approval workflow on the agency's branded domain, and the portal is listed as a line item on the client retainer.

Open the Offistack courseOffistack decision recordBrowse the Academy

More on Offistack

More for Client Portal