A client portal for professional services is one place where each client sends requests, shares files, and approves work. Dora gives every client one under your name, then briefs each request, keeps scope in check, and gets the work signed off. For consultancies, IT and managed service providers, development firms, and the services teams inside B2B companies.
- 1
Set up your services
Add your website and Dora drafts your request types and client library in about a minute. Group request types into the services you sell, like implementation, advisory, or support.
- 2
Bring in your clients
Paste your clients as websites, emails, or names, up to 50 at a time. Each gets a portal with their people invited, and open work moves over by forwarding the email thread.
- 3
Run the work through Dora
Requests arrive briefed and go to the account lead. Hand over with a preview link, the client approves in one click, and the month's record fills itself in.
What changes when every client account has a portal and Dora answers first.
A portal per client account
Each client gets a private portal with their requests, files, and history. They see their own work and the people on their account, nothing else. Internal notes and team-only files stay on your side.
Requests that arrive scoped
Clients ask in the portal, by email, or from their own AI. Dora checks each request against what that kind of work needs, asks for what's missing, and writes the brief before anyone on your team picks it up.
Scope you can point to
Each client's agreement lists the services they have and, if you like, a monthly request allowance. Work outside it goes out as an estimate the client approves or declines in one click, so change requests stop slipping in as favors.
An account team for every client
Give each client a lead and a team. New requests go to the lead unless they're away, and Dora suggests who should take the rest, or assigns them herself if you turn that on.
Sign-off on record
Hand work over with a note, a preview link, and files. Clients approve or ask for changes in one click, and the approval stays on the request. If nobody replies, the work approves itself after the days you set.
A monthly record per client
Each client gets a record of what shipped, what they approved, how fast it went, and which estimates they said yes to, with a recap Dora writes. Bring it to the quarterly review or the renewal call.
Consultancies and advisory firms
Engagements full of small asks: analyses, decks, reviews, and revisions. Each one is briefed before it starts and signed off when it's done.
IT and managed service providers
Project work and change requests for each client, with the request type deciding what Dora asks for first, and estimates for anything outside the contract.
Development and engineering firms
Features, fixes, and releases with a preview link on every handover. Developers can pick up Dora's briefs in Claude Code and hand the work back for review.
Services teams inside B2B companies
Implementation, onboarding, and professional services teams doing project work for customers. Each customer account gets a portal, and the monthly record shows what was delivered.
Firms that work from client files
Accounting, bookkeeping, and other firms that need documents from clients. Dora asks for the missing file on each request and keeps everything in the client's library.
Fractional and embedded teams
Fractional leaders and specialists working across several clients at once, with one inbox for all of them and a portal for each.
A client portal for professional services is a private space where each client sends requests, shares files, and approves deliverables, instead of scattering them across email threads. Dora is one, with an AI account manager built in: she briefs every request, keeps work inside the agreed scope, and gets sign-off on each deliverable.
Work sold as expertise and time rather than as a product: consulting, IT and managed services, development, accounting, legal, and the implementation and services teams at B2B companies. If your team takes requests from clients and delivers work back, Dora fits.
No. A PSA (professional services automation) runs your side of the business: resourcing, time, and billing. Dora is the client side: requests, briefs, files, estimates, and approvals, in a portal each client actually uses. Keep your PSA or project tool for internal planning, and connect it through the API or webhooks.
Yes. Add each customer as a client: they get a portal for implementation tasks, change requests, and files, and your services team gets one inbox across every account. Webhooks send request events, like new requests and approvals, to your other tools, and the API covers the rest.
Each client's agreement lists the services they have, so they only see those request types, with an optional monthly request allowance. Work outside it goes out as an estimate the client approves or declines in one click. Change requests sent as an estimate don't count toward the allowance.
No password and no app. The invite email signs them straight into their portal, and after that they sign in with a link sent to their email. They can also email requests to their own request address and reply to any update from their inbox, where the reply lands on the right request.
Yes. People at the same client share one portal and see the same requests, and clients can invite their own colleagues. You pay per client, never per person on their side. When a request is waiting on the client or ready for review, the whole client team is emailed; routine updates go to whoever asked.
Everyone on your company's team can work across your clients, and what they can change follows their role: owner, admin, or member. Clients only see the team on their account. Internal notes, team-only files, and team-only rules never reach the client. The same rules are checked in the app, the API, and over MCP.
Your first client is free, forever. Each client after that is $10 a month, charged when you add them. Team seats are unlimited, and you don't pay for the people on the client's side either. Archive a client you've stopped working with and it drops off at your next renewal, with its requests and files kept.
Yes. Dora has an MCP server and a full API on every plan. Anyone on your team can connect Claude, ChatGPT, Claude Code, or Codex, and it works as them, with their access and no more. Your own AI over MCP has no usage limit. Webhooks send request events to any URL you choose.
Dora's AI runs on Claude, made by Anthropic. We don't train AI models on your content, and under its commercial terms Anthropic doesn't either. Data is encrypted in transit and mainly processed in the United States. To export or delete your company's data, email legal@dora.work; deleted data is removed within 30 days and from backups after that.
Add your website and your portal is set up in about a minute.
- Free for your first client
- No card needed
- Set up in a minute
- Works with Claude and ChatGPT