Fixed quote after a free call

An MSP client portal with live QBR dashboards

We build a branded client portal for your IT support company: client contacts sign in to log and follow tickets, submit starter and leaver requests, see SLA performance, device age and license counts, and open QBR reports built from your PSA, RMM and security data. Your vCIO reviews every QBR figure before it is shared. Portals typically cost $5,000 to $15,000 and take eight to twelve weeks.

The problem

Why MSP clients only see you at the QBR

Clients judge an MSP on what they can see, and usually they see very little: an email when a ticket closes and a QBR deck once a quarter, if they are large enough to get one.

Account managers build QBR packs by copying ticket counts from the PSA, device ages and warranty dates from the RMM and security scores from several consoles into slides. The effort means smaller clients rarely get a review at all.

What we build

What our MSP client portal includes

Client sign-in and roles

Single sign-on with Microsoft Entra ID or Google, with roles for the client owner, office manager and staff.

Tickets and requests

Log a ticket, follow its status and submit starter and leaver forms that feed your workflows.

Service dashboard

SLA performance, ticket volumes by category and response times from your PSA.

Device and license view

Device ages, warranty dates, patch status and license counts from your RMM and reconciliation data.

QBR reports

Quarterly reports built from live data with a vCIO review step before the client sees them.

Your brand and domain

Hosted on your subdomain with your logo, colors and contact details.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Data synced

    Tickets, agreements, devices and licenses sync from the PSA and RMM on a schedule.

  2. 02 Automated

    Dashboards updated

    Each client sees only their own figures, refreshed automatically.

  3. 03 Automated

    QBR drafted

    Each quarter a draft report is generated from the period's data.

  4. 04 Technician review

    vCIO reviews

    The vCIO checks every figure, adds recommendations and publishes the report.

  5. 05 Engineer or vCIO decides

    Roadmap and budget

    Technology roadmap and budget advice stay a conversation between the vCIO and the client.

How it behaves

How the client portal behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the client sees

  • Their tickets and requests in one place
  • SLA, device and license dashboards for their company only
  • Quarterly reports reviewed by their vCIO

What your team sees

  • Requests arriving in the PSA with details complete
  • QBR drafts ready for review each quarter
  • Which clients use the portal and what they open

What the automation does

  • Syncs PSA and RMM data on schedule
  • Keeps each client's data separate
  • Generates QBR drafts and waits for vCIO approval

Edge cases and fallbacks

Sync source unavailable
Dashboards show the last good data with a timestamp.
Contact leaves the client company
Their portal access is removed when the PSA contact is deactivated.
Figure looks wrong in a QBR draft
The vCIO edits or removes it before publishing.
Client has several sites
Dashboards filter by site, with a company total.

Architecture

An MSP client portal at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
PSA Tickets, agreements RMM Devices, patches Sync service Scheduled jobs Portal database Per-client data Client portal Laravel web app QBR draft Quarterly report vCIO Reviews, publishes
  • Input
  • Logic and services
  • Data
  • Output
  • AI step
  • People

How it flows

  1. 1 Tickets, agreements, devices and patch status sync from the PSA and RMM on a schedule.
  2. 2 The portal database keeps each client's data separate and the dashboards read from it.
  3. 3 Clients sign in to log tickets, submit requests and see their service and device dashboards.
  4. 4 Each quarter a QBR draft is generated, and the vCIO reviews and publishes it.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

MSP client portal & QBR dashboards project plan

Typical time to launch: about 10 weeks, then support

  1. 01

    Discovery

    About 1 week

    What clients should see, data sources, roles and the QBR template you use today.

  2. 02

    Design

    1 to 2 weeks

    Wireframes, branding, dashboard metrics and the QBR layout.

  3. 03

    Build

    4 to 6 weeks

    Sign-in, ticket and request forms, sync jobs, dashboards and QBR generation.

  4. 04

    Test

    1 to 2 weeks

    Data accuracy checks per client, security testing and accessibility.

  5. 05

    Launch

    About 1 week

    Pilot with a few clients, then invite the rest.

  6. 06

    Support

    Ongoing

    New dashboards, data sources and QBR changes.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

Laravel Microsoft Entra ID or Google sign-in ConnectWise PSA, Autotask or HaloPSA API NinjaOne, Datto RMM or N-central API MySQL or PostgreSQL Your hosting or cloud account

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and UX

    Requirements, roles, metrics and wireframes.

    $800 – $2,000

  • Design

    Branding, dashboard and QBR layouts.

    $700 – $2,000

  • Build

    Sign-in, forms, dashboards, sync jobs and QBR generation.

    $2,500 – $7,500

  • Integrations

    PSA, RMM and license data.

    $500 – $2,000

  • Testing and launch

    Accuracy, security and accessibility checks, pilot launch.

    $500 – $1,500

  • Total project estimate

    $5,000 – $15,000

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Depends on the number of data sources, dashboards and whether ticket write-back is included. Hosting is billed to you directly.

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 or cloud provider.
  • Domain and certificate: Your registrar; certificates can be free through Let's Encrypt.

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
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

Client data separation

Each client sees only their own data, enforced in the application and tested before launch, in line with least-privilege guidance for MSPs.

Source: www.cisa.gov

EU and UK: processor terms

The portal holds client staff names and ticket content, so hosting and any sub-processors are listed in your GDPR Article 28 terms.

Source: gdpr-info.eu

Accessible to every client user

We build to WCAG 2.2 AA so client staff using assistive technology can log tickets and read reports.

Source: www.w3.org

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 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. 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. 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. 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

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

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

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

MSP client portal & QBR dashboards questions, answered.

At minimum, ticket logging and status, starter and leaver requests and a service dashboard. Device health, license counts and QBR reports turn it into something clients open between reviews.

Partly. The portal generates QBR drafts from live PSA, RMM and security data in your template, and your vCIO reviews and publishes them. It replaces copy and paste, not the vCIO conversation.

PSA portals are good for tickets. A custom portal adds data from your RMM, licenses and security tools, your branding and the starter and leaver forms that drive your workflows. Many MSPs keep the PSA portal for tickets and add ours for reporting.

You do, on your own cloud account or hosting, under your domain. We hand over the code and deployment notes.

Sync jobs run on a schedule you choose, commonly every 15 minutes for tickets and nightly for devices and licenses.

Clients signed in each month, tickets and requests logged through the portal, QBRs delivered per quarter and time spent preparing each one.

Free 20-minute call

Want this for your it support & msp?

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.

Book a free 20-minute call