A client portal for marketing agencies, built on the tools you already use
Clients ask the same questions every week: how is it going, what needs my approval, where is the report, what did we spend. We build a branded client portal that shows live dashboards, monthly reports, items waiting for approval, open requests and invoices in one secure place, pulling from your project tool, reporting data and accounting system. Projects typically cost $6,000 to $16,000 and take seven to eleven weeks.
The problem
Why agency clients keep asking for status updates
Agencies scatter client information across email, shared drives, Looker links, proofing tools and invoices. Clients lose links, ask for status updates and approve things in the wrong place.
Off-the-shelf client portal software works for some, but agencies with their own reporting, approval and request flows often end up with yet another tool to keep in sync. A portal built on your existing systems shows clients the truth without double entry.
What we build
What our agency client portal includes
Live dashboards
Key performance figures per client from the reporting data, refreshed on schedule.
Reports and files
Monthly reports, strategy documents and assets in one library per client.
Approvals inbox
Items waiting for the client's approval with one-click sign-off recorded against the version.
Request form
Clients submit requests that become tasks in your project tool, tagged in or out of scope.
Invoices and retainer usage
Invoice status from accounting and retainer hours used, where you choose to show them.
Secure access
Per-user logins with roles, two-factor authentication and an access log.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Client signs in
Client users log in with two-factor authentication.
-
02
Automated
Data shown
Dashboards, reports, approvals and invoices load from connected systems.
-
03
Automated
Client acts
Approvals and requests flow back into your project tool.
-
04
Account team review
Account team responds
The account team picks up requests and checks approvals.
-
05
Account lead or agency owner decides
What clients see
Which data and documents appear in the portal is decided by the account lead.
How it behaves
How the client portal behaves
What the client sees
- One branded login for everything about their account
- Live figures and the latest report
- Approvals and requests in one place
What the agency sees
- Requests arriving as tasks
- Approvals recorded with the version
- Fewer status-update emails
What the portal does
- Reads from your existing systems on schedule
- Writes approvals and requests back
- Enforces roles and logs access
Edge cases and fallbacks
- Connected system is down
- The portal shows the last refreshed data with a timestamp.
- Client user leaves their company
- The account lead disables the login; the access log is kept.
- Request clearly out of scope
- Tagged for the account manager before work starts.
- Suspicious login attempts
- Rate limits and alerts; two-factor authentication blocks access without the second factor.
Architecture
A branded client portal for an agency at a glance.
- Input
- Logic and services
- Output
- People
How it flows
- 1 The portal backend reads tasks, approvals, reporting data and invoices from your existing systems.
- 2 Clients see a branded portal with dashboards, reports, approvals and requests behind two-factor login.
- 3 Client approvals and requests are written back to your project tool.
- 4 The account team responds, and the account lead decides what each client can see.
Project planner
How the project runs, phase by phase.
Branded client portal for agencies project plan
Typical time to launch: about 9 weeks, then support
-
01
Discovery
About 1 week
What clients ask for most, systems to connect, roles and branding.
-
02
Design
About 2 weeks
Screens, information per role, approval flow and accessibility.
-
03
Build
3 to 5 weeks
Backend, integrations, dashboards, approvals, requests and access control.
-
04
Test
About 1 week
Security review, accessibility checks and a pilot with two clients.
-
05
Launch
2 to 3 days
Roll out to clients with a short guide.
-
06
Support
Ongoing
New widgets, integrations and security updates.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and audit
Client needs, systems and roles.
$700 – $1,600
-
Design
Screens, roles, approval flow and accessibility.
$1,300 – $3,200
-
Build
Backend, dashboards, approvals, requests and access control.
$2,600 – $7,400
-
Integrations
Project tool, reporting data and accounting.
$800 – $2,200
-
Testing and launch
Security review, accessibility, pilot and rollout.
$600 – $1,600
-
Total project estimate
$6,000 – $16,000
Optional monthly care after launch is quoted with your proposal. Fixed quote after discovery. Hosting and any paid APIs are billed to you directly. You own the code.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Hosting: Billed by your hosting provider.
- APIs: Most project and accounting APIs are included in your existing plans; any paid API is billed to you.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
Accessibility
We build to WCAG 2.2 success criteria so client users with disabilities can use the portal.
Source: www.w3.orgClient data in the portal
Portal hosting is a processor for your clients' data and needs Article 28 GDPR terms; access is role-based and logged.
Source: gdpr-info.euAds data access
Live Google Ads figures depend on an approved Google Ads API access level for your Google Cloud project.
Source: developers.google.comFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Branded client portal for agencies questions, answered.
A secure website where each client logs in to see their dashboards, reports, approvals, requests and invoices in one place, under your agency brand.
If a ready-made portal fits your workflow, buy it. A custom portal makes sense when you want it to sit on your existing project, reporting and accounting tools without double entry, or to show data no product supports.
Yes. Approvals are recorded against the version and written back to your project tool, so the sign-off record lives with the work.
Users have their own logins with roles and two-factor authentication, data is encrypted in transit and every access is logged. We run a security review before launch.
Yes. Widgets are per client, so a performance client sees dashboards and a creative client sees approvals and assets.
Client logins, approvals completed in the portal, status-update emails avoided and requests submitted through the form.
Free 20-minute call
Want this for your marketing agency?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for marketing agencies
All servicesCRM automation for marketing agencies: new business pipeline
Track every enquiry, referral and pitch in one agency CRM pipeline, with research briefs before discovery calls, proposal follow-ups and a clean handover to onboarding when a client signs.
From $1,000 · About 4 weeks Details
Client onboarding automation for agencies
Turn a signed contract into a kickoff checklist, access requests for ad and analytics accounts, a welcome pack and scheduled reminders, so the first month goes on strategy instead of chasing logins.
From $1,000 · About 3 to 4 weeks Details
Automated client reporting with draft commentary
Pull GA4, Google Ads, Search Console, Meta and LinkedIn data into branded monthly reports, with anomalies flagged and first-draft commentary the account lead rewrites before anything is sent.
From $1,000 · About 4 to 5 weeks Details