What we build
Client portal development
A portal replaces the update email. Instead of a client ringing to ask where something is, they open a page that already says, and your team gets the afternoon back that was being spent answering.
What it is
A client portal is a private area where somebody you work with can see their own thing: the state of the job, the documents, the approvals waiting on them, and what happens next.
The useful ones are narrow. A portal that shows everything is a portal nobody reads, and the valuable part is almost always the one question clients ask most often, answered before they ask it.
When a business needs one
- The same status question arrives from different clients every week
- Documents go back and forth as email attachments and the latest version is a guess
- You are asking clients to create an account somewhere just to sign one thing
- Onboarding a client means a chain of emails that stalls if anyone is on holiday
- Sensitive documents are being sent by email because it is the only way that is easy
What we can build
Capability, not a claim about work already delivered. What we have actually built and run is further down the page.
- A login where a client sees their own job and nothing belonging to anybody else
- Documents behind a gate rather than on a public link anyone could forward
- A link that lets somebody sign or upload without creating an account at all
- Intake forms that file themselves into the system instead of arriving as a PDF
- E signature on a contract, with the signed copy stored against the job
- Approvals with a record of who agreed to what and when
- Notifications when something is waiting on the client, and a nudge when it stays waiting
How we approach it
Decide first what the client is allowed to see, because that decision shapes everything else. A portal is a permissions problem before it is a design problem.
Then take the single question your team answers most often and make the portal answer it. If that works, the rest is worth building. If nobody logs in, no amount of extra pages would have helped.
See it working
A short film of one of our own demonstrations, recorded from the running software. Every company in it is invented, and the link opens the real thing.
Juniper Events · Weddings and events entertainment
An extra hour asked for, priced, accepted, and only then added to the plan, with the brief reissued and acknowledged before the day counts as handed over.
Brackenhall Property Services · Construction and property maintenance
Every variation priced, sent, answered and captured, and a job that cannot be released for invoicing while there is a hole in the record.
Things we have already built
Live in software we have delivered, and part of the 123 things we have built.
A login where your client can see their own job
Clients answer their own questions at eleven at night, and the team stops being a lookup service.
Send a document without making anyone create an account
Far more people finish what you sent them, because there is nothing in the way but the thing itself.
Sharing a document without putting it on the internet
The people who should see a document can, and it is not sitting on a public URL a competitor can find.
Token link client intake forms
Everything needed to start a job comes in through one link, instead of a long back and forth of emails.
Auto contract e-sign on close
Contracts get signed as part of closing, so nobody chases paperwork or emails PDFs back and forth.
Feedback from a link, with nobody creating an account
You actually hear what people thought, because you did not ask them to register first.
Related to this
Tell us what you are trying to fix
Describe the job in your own words and we will tell you what we would build, roughly what it would cost, and whether something you can already buy would do it cheaper.