Skip to content
01Applications

A private place for your customers

One sign-in where your clients see their documents, their progress and their invoices, and talk to you without an email chain. Built around how you already work with them.

Build time
4–20 weeks
Per project
Quoted
Code ownership
100%
Who it is for

You will knowif this is you.

01You send the same documents, updates and invoices to clients by email and then answer questions about where they are.
02Clients ring to ask how the job is going, and the answer is in three places none of them can see.
03You handle files that should not be sitting in an inbox: contracts, plans, ID, medical or financial records.
04You want clients to approve things, sign things or pay things without a back and forth.
What it does

Everything the systemtakes off your desk.

Each capability is built to your process and shipped with its own controls. Nothing generic is bolted on.

01

Accounts and access

Each client signs in to their own space. You decide who on their side sees what.

  • Email, password and passkey sign-in
  • Two-factor authentication
  • Roles per client: owner, staff, view-only
  • Invite links that expire
02

Documents

Every file in one place with a history, so the latest version is never in question.

  • Upload from your side or theirs
  • Versions kept, old ones never lost
  • Folders per project or job
  • Signed downloads, no public links
03

Messages and requests

A thread per client that both sides can see, instead of an inbox neither can search.

  • Threads per job or topic
  • Attachments in the thread
  • Request forms with required fields
  • Read receipts and reply times
04

Progress and notifications

A stage tracker the client reads instead of ringing, and a notification when it moves.

  • Stages you define
  • Email and in-portal notifications
  • Due dates and what is waiting on whom
  • Activity log per client
05

Quotes, approvals and payment

Send a quote, take an approval and collect payment inside the portal.

  • Quotes with line items
  • One-click approval with a record
  • Card payment through Stripe
  • Invoices and receipts as PDF
06

Security and audit

Built for the files that should never travel by email.

  • Row-level access in the database
  • Encrypted storage
  • Full audit trail of who saw what
  • Data export and deletion on request
The screens

What a clientactually sees.

A portal is five screens done well. The rest is your process, expressed in those five.

01HomeWhere things stand: the current stage, what is waiting on them, the last message, the next date. Nothing they have to hunt for.
02DocumentsTheir files, in folders that match how you work: by job, by property, by case. Upload both ways, versions kept.
03MessagesThe conversation with you, searchable, with attachments in context. Replaces the email chain without replacing email: they still get a notification.
04MoneyQuotes to approve, invoices to pay, receipts to download. Payment by card, recorded against the job.
05AccountTheir people, their notification preferences, their security settings. Self-service, so you are not the help desk.
Scope and timeline

Sized to the job,quoted per project.

Three sizes from the catalogue's application tiers. Most businesses land on the middle one.

01

Starter portal

Quoted

4–6 weeks

  • Sign-in and client accounts
  • Documents with versions
  • One message thread per client
  • Stage tracker
  • Branded to you
02Most popular

Business portal

Quoted

8–12 weeks

  • Everything in Starter
  • Roles and permissions per client
  • Request forms and approvals
  • Quotes, invoices and card payment
  • Notifications by email
  • Audit log
03

Advanced portal

Quoted

12–20 weeks

  • Everything in Business
  • Integrations with your existing systems
  • E-signature
  • Multiple brands or offices
  • Client-side reporting
  • API for your other tools

Timelines are the ones in the catalogue. The quote fixes the scope, the price and the delivery date before work starts.

Built on the platform

The Lounge isa client portal.

Every Quooro customer already signs in to one: the Lounge, where they see their website, their files, their invoices and their messages with us. A portal for your customers is built on the same foundations, so it inherits security, notifications and payments that are already in production.

  • See the Lounge

    The portal our own customers use, and the platform yours is built on.

  • Messages, files and tickets

    The same modules, configured for your clients instead of ours.

  • Payments through Stripe

    Cards, receipts and refunds the way the platform already takes them.

What you own

Yours outright, on the day it launches.

  • The complete source code and the database schema
  • Deployment to hosting in your name, or on ours if you prefer
  • Admin documentation and a training session for your team
  • A support period written into the quote: 30, 60 or 90 days by scope
  • Your clients' data is yours; export it at any time

The same terms as every build: read ownership and handover.

How it is built

Four stages, no surprises.

Whole buildSet in your proposal

01

Discover

Starts when you say go

We map how the work gets done today.

What happens

  • Workshops with the people who will use it
  • Your current process mapped, step by step
  • Your data and the systems it lives in audited
  • A written specification of what to build first

What you get

  • The specification
  • A staged plan and a fixed quote

What we need from you

  • Time with the team who do the work
  • Access to the tools you use now
02

Design

After you approve the specification

A clickable prototype before a line of code is written.

What happens

  • Screens and user journeys for each role
  • A clickable prototype the team can try
  • The data model and the integrations agreed
  • Permissions: who can see and change what

What you get

  • The prototype
  • The agreed data model

What we need from you

  • Feedback from real users
  • Sign-off on the prototype
03

Build

After you approve the prototype

Built in stages, with a working demo at the end of each.

What happens

  • Features built in the agreed order
  • A working demo at the end of every stage
  • Your existing data moved across and checked
  • Tested against the real process, not a script

What you get

  • A working system at each stage
  • A test environment to try it in

What we need from you

  • Testing time from your team
  • Decisions when questions come up
04

Launch

After you approve the finished build

Rolled out, taught and supported.

What happens

  • Rolled out to the team, in stages if that suits
  • Training for each role
  • Documentation for how it works and how to run it
  • Support after go-live, with a retainer if you want one

What you get

  • The live system
  • Full ownership of the code and data

What we need from you

  • A go-live date that works for the business
Straight answers

Asked beforeyou ask.

01Can clients upload files as well as download them?Yes. Uploads go into the folder you choose, with a notification to you, and a virus scan before anything is stored.
02Does it replace email?It replaces the chain, not the notification. Clients still get an email when something changes; the conversation and the files live in the portal where both sides can find them.
03Can it take payments?Yes, by card through Stripe, recorded against the job with a receipt. You can also mark bank transfers as paid by hand.
04What about clients who will not sign in?Each item can also be sent as a secure link that expires. Most clients sign in once the second document arrives.
05Who hosts it?Either. It can run on our platform under a management plan, or be deployed to hosting in your name with the source code handed over.

Stop beingthe status update.

Tell us how you work with a client today, from first enquiry to final invoice. The quote describes the portal that replaces the chasing.