Same file. One of these took four days.
Chasing documents by email is somebody's job at most firms. A portal does not replace the relationship — it removes the eleven messages that were never part of it.
Thirty minutes · no predetermined package
The smallest one removes most of the email.
Read-only status is a fraction of the cost of self-service and does most of the work.
Read-only status
The smallest useful portal: where is my file, what do you still need, and what did I already send.
Collect and sign
Upload, validate, confirm receipt, chase what is missing and capture a signature, all against the same record.
Multi-party
Submissions with credentials, accept or reject in-request, and a partner who can see their own pipeline.
Transactional
Requests, changes and payments handled without a person. Only worth it at volume, and rarely the first build.
What a missing portal looks like from inside.
Someone asks for an update, and answering it means opening four systems.
The signed document is in an inbox, and nobody can say whose.
A customer sends the same file twice because nobody confirmed the first one arrived.
The status a client is told and the status in the system are different, and both were true once.
Chasing documents is somebody's actual job.
A partner cannot see whether their submission was accepted without emailing to ask.
Six questions before building a portal.
The first one is a security question, and it decides most of the rest.
Five stages, and permissions come first.
Decide what is visible
the permission mapEvery field, who may see it and who may change it. This is the deliverable of week one and the whole risk lives here.
Read from the record
one sourceThe portal shows what the system holds. Nothing is typed twice, so nothing drifts.
Handle the unhappy path
rejectionsWhat happens when a document is wrong, expired or missing. Portals that skip this fall back to email.
Notify without noise
the right nudgeA message when something needs the customer, silence otherwise. Over-notifying is how portals get ignored.
Instrument adoption
measuredLogins, uploads and status views per file, so you can see whether it replaced the email or just added to it.
Wherever documents move between two parties.
Lending and financial services
Applications, stipulations, signatures and funding status, usually with an ISO or broker in the middle.
Legal and professional services
Matter status, document exchange and approvals, where privilege makes the permission model non-negotiable.
Home services
Quote approval, scheduling and warranty documents, mostly consumed on a phone.
Insurance
Policy documents, certificates and claims status, across brokers and insureds with different rights.
Client portal software for accountants, where collecting the documents is the whole job.
A practice does not usually have a status problem. It has a collection problem — the return cannot be filed until the client sends the thing, and chasing it is most of the calendar between January and April.
The PBC list, with an ageing clock
Prepared-by-client items as tracked records rather than a checklist emailed in January and never looked at again. Each one knows how long it has been outstanding and who was last asked.
Documents that were never safe as attachments
W-2s, K-1s, bank statements and org charts. Encryption in transit is the easy half; the harder half is that an emailed copy sits in two inboxes forever and neither is yours to delete.
One client, several entities
A personal return, two LLCs and a trust are four permission sets, not one login. A spouse who should see the joint return and not the operating company is the case that breaks a portal bolted onto a document store.
Who has not sent what, across the book
An accounting client portal earns its place at the partner level, where the question is which fifty returns are blocked and on what — not whether one client uploaded a file.
What people ask about client and customer portals.
What is a client portal?
An authenticated view where a customer sees the status of their own file, submits documents and approves steps, without emailing anyone. The value is removing status requests, not adding a website.
What should a customer portal show?
Where the file is, what is still needed, and what has already been received. Anything beyond that is scope you can add once the first version is used.
How much does client portal development cost?
It scales with the permission model and the number of document types, not with the number of screens. The rules about who sees what are the expensive part.
Should we build a portal or buy one?
Buy when your process is standard and the portal only needs to read a common system. Build when the status comes from a system nobody else integrates with, which is most custom platforms.
Can a portal work with our existing CRM?
Usually. A portal reading a CRM through its API is cheaper than replacing the CRM, and it keeps one source of truth for status.
What is a partner or broker portal?
The same idea for a third party who sends you work. They submit with credentials, get accepted or rejected immediately, and can see their own pipeline without calling.
How do you keep portal status accurate?
By reading the operational record rather than maintaining a copy. A portal updated by hand is a second system that will disagree with the first within a month.
What about security and access control?
The permission map is the first deliverable, not an afterthought. Every field gets a rule about who may see it and who may change it, and that document outlives the build.
Do customers actually use portals?
Only when using them is easier than sending an email. That means no chasing them to log in, notifications only when something needs them, and a rejection path that works.
Can clients sign documents in the portal?
Yes, and it is usually the strongest reason to build one. Signature captured against the record removes the version confusion that email creates.
How long does a portal take to build?
A read-only status view is weeks. Documents and signature is longer. Full self-service is a different project, and rarely the right first one.
What is a white-label client portal?
A portal carrying your brand rather than a vendor's. Worth it when the client relationship is the product, which for most professional services it is.
What is an accounting client portal?
A portal scoped to how a practice actually works: prepared-by-client requests as tracked items with an ageing clock, secure exchange of tax documents, and permissions per entity rather than per login. The value is that nobody has to email a client asking whether they received the last email.
Can a client portal replace secure email for tax documents?
Yes, and that is usually the point. Emailing a K-1 or a bank statement leaves a copy in two inboxes permanently, neither of which the firm controls or can delete. A portal keeps one copy, in a place with an access log and a retention rule.
How should a portal handle a client with several entities?
As several permission sets, not one account. A personal return, two operating companies and a trust have different people entitled to see them, and a spouse who should see the joint return but not the LLC is the case that breaks a portal bolted onto a shared document folder.