DEV3 Briefcove – White-Label Agency Client Portal SaaS Laravel Script with Approval Rounds, Pay Links, Custom Domains

Briefcove is a white-label client portal that agencies run for their clients, built by DEV3 Technologies on Laravel 12 and Filament 4. You run it as the operator: you sell plans to agencies, and each agency gives every client a branded portal on its own subdomain or custom domain to follow projects, review and approve files, talk in threads, read status updates and pay simple invoices.

What it does

• Approvals with rounds. Every upload becomes a numbered version. Clients open the artwork or PDF in the page, drop numbered pin comments, then approve or ask for changes with a short reason. Rounds can be limited per deliverable; a manager can allow one more. Older versions say they were replaced and link to the current one.
• Projects the client can follow. Milestones, deliverables, files in folders, weekly status updates written once, requests that the agency accepts or declines, and threads that update live (Reverb, or polling every 10 seconds). Agency-only notes never reach the client.
• Agency studio. A Filament panel with the Review Tide (open, late and clearing reviews by client), key numbers, project health, a kanban board, tasks, project templates, contractor release before a client sees a file, and an approvals-waiting list with reply deadlines.
• Simple invoices. Build an invoice from approved milestones or from custom lines, add tax, send a pay link, take partial payments, refund with a reason and chase overdue invoices with reminders. Monthly retainers are billed on a schedule. PDFs come from the same numbers.
• Your brand, their address. Logo, accent colour and welcome note, a subdomain per agency, an optional custom domain with a verification token and an SSL status, plus a portal in English and right-to-left Arabic, light and dark.
• Money you can reconcile. Client payments go to your gateway as merchant of record. Each agency has a takings wallet with a payout hold, weekly payout statements and durable pending refunds. A briefcove:check command proves invoices, payments and wallets agree.
• Operator panel and API. Agencies, plans, subscriptions, platform invoices, client payments, payouts, pending refunds, domains, quarantined files, an outbox, an audit log and audited view-only support sessions. A scoped REST API with an OpenAPI document and signed webhooks.

Quality checks

The release passed seven gates on the final code: Larastan level 6 with 0 errors, 262 Pest tests (6,273 assertions), a build well inside the page budget, migrations and the full demo seed on MySQL 8 and SQLite, a headless smoke test of 118 pages with 39 happy-path checks and eight race groups run on MySQL (parallel approvals of one version, payments and refunds against one invoice, payout runs and more), the installer driven from the zip, and a secret scan. The home page scores 93 for performance and 100 for accessibility on mobile.

What you should know before buying

• You are the merchant of record. Client payments go to your gateway (simulated by default) and you pay each agency out from its takings wallet. Agencies cannot connect their own Stripe account in this version.
• Custom domains need your proxy. Point DNS and terminate TLS at your web server or proxy (a Caddy on-demand TLS setup is documented). Domain verification is simulated by default, and SSL status is reported, not issued.
• Previews cover images and PDF only. Other files download. A video poster frame needs ffmpeg on the server. Storage is local or S3-compatible.
• Proofing is pin comments on images and PDF pages. There are no drawing or markup tools.
• Retainers on real gateways are not configured. The simulated driver shows the full flow; a real driver throws recurring_not_configured until you add stored-payment-method support.
• Not a time tracker. Tasks carry estimate and actual hours as plain fields. Invoices are deliberately simple, and approvals are click-and-comment sign-offs on files, not legal documents.
• Simulated drivers. Mail, payments, virus scan, DNS and recurring charges all have working simulated drivers; real ones need your own accounts.
• A cron entry every minute and a queue worker are required. Web only: there are no mobile apps. Node.js is not needed (assets are prebuilt).

How it is different

It starts after the deal is won: delivery, review and payment, with a client-facing portal as the product. It is multi-tenant, with each agency's clients scoped by agency and by client on every query, so it suits an operator who wants to sell a portal to many studios rather than run one internal tool.

Included

Source code, the web installer, a buyer guide with API contract, demo data with fictional agencies, clients and people (design, web and film studios with a year of projects, files, messages and invoices), a cron entry for the scheduler, and six months of support.