ParleHub | Shared, budgeted AI for firms that bill by client
Sign in
Start free
Security<br>Pricing<br>Blog<br>Sign in
For firms that bill by the client
Every hour has a<br>client code. Your AI spend has none.
ParleHub gives every project a shared thread, its own budget, and<br>your own expense code. AI cost lands on the engagement that caused<br>it, and exports straight into the system you already bill from.
Start free at app.parlehub.com<br>arrow_forward
See how it works
Anthropic
OpenAI
Gemini
Azure OpenAI
Google Drive
SharePoint
Entra ID
Google Workspace
Project · Ashworth M&A<br>ENG-4417
Can you check clause 4 of the vendor contract?
Clause 4 caps liability at 12 months' fees. Flagging for legal<br>review
Project budget<br>$620 / $1,000
Project · Ashworth M&A<br>ENG-4417
Can you check clause 4 of the vendor contract?
Clause 4 caps liability at 12 months' fees. Flagging for legal<br>review
Project budget<br>$620 / $1,000
Anthropic<br>OpenAI<br>Gemini<br>Azure OpenAI<br>SharePoint<br>Google Drive<br>Entra ID<br>Google Workspace
Visibility
Your team is already using AI on client work
On personal accounts, with client documents, under terms nobody<br>reviewed. You cannot say which clients, which files, or whose<br>agreement covered it. That is also the honest answer to the AI<br>section of every client security questionnaire you sign.
check_circle<br>Access tied to Microsoft Entra ID, so offboarding actually<br>removes it
check_circle<br>Project files stay in your own SharePoint site, under per-site<br>permissions, never leaving your tenant
check_circle<br>Model calls run on your provider keys and your agreement, or on<br>models we host under ours, never a personal consumer account
check_circle<br>Four levels of role, and projects only their members can see
Cost allocation
Timesheets for your AI agents
Your people book their hours to a client. Your AI books nothing.<br>It arrives as one provider invoice with no client on it and lands<br>in overhead, where the practices that barely touch AI quietly<br>subsidise the ones that live on it.
check_circle<br>A budget scoped to the project, not the person, because your<br>people work across six of them
check_circle<br>Your own project code on every project, carried through to the<br>export
check_circle<br>Spend and token usage broken down by project, person, provider,<br>or model, over any range
check_circle<br>One canonical token ledger behind both the report and the<br>enforcement, so there is a single number
Every project carries your own expense code, straight through to<br>the export. AI cost lands where every other cost already lands, so<br>you can recharge it, price it into a fixed fee, or cut the<br>engagement type that does not pay.
Control
Find out before the invoice, not after
Metered spend with no ceiling is the opposite of how a firm plans.<br>One enthusiastic user, one runaway loop, and the number turns up<br>at month end with an explanation attached to it.
check_circle<br>Pre-flight enforcement blocks the send before it exceeds the<br>project budget
check_circle<br>An 80% warning state, so the team sees it coming
check_circle<br>Personal and org-wide caps stacked as backstops above every<br>project
check_circle<br>Blocked? Request an increase in one click, routed straight to an<br>admin
The ceiling becomes a number you set rather than a number you<br>discover, and it does not stop the work, because there is a path<br>through it.
Shared context
The best work your firm did last week is in a closed tab
Private chat histories mean context rebuilt from scratch at every<br>client switch, by every person. Two people on the same engagement<br>ask the same question a day apart, against different documents,<br>and get different answers. When someone rolls off, what they<br>worked out leaves with them.
check_circle<br>Shared project threads every member can see, live
check_circle<br>Presence indicators for who is viewing, typing, or waiting on a<br>reply
check_circle<br>Keyword and semantic search across every conversation in the<br>project
check_circle<br>Promote a personal chat into a shared project when it turns out<br>to matter
check_circle<br>Branch by editing and resending, without losing the original
Defensible work
When a partner asks where the number came from
Work nobody can review gets re-done by whoever has to sign it, at<br>their rate. In regulated practice it cannot be used at all, so the<br>engagement pays for the analysis twice: once quickly, once<br>defensibly.
check_circle<br>The whole exchange stays in the thread: the question, the reply,<br>and which model produced it
check_circle<br>Real tool calls against the project's own files, so the work is<br>grounded in your documents
check_circle<br>Exact find-and-replace and diffs, so a reviewer sees what<br>changed, not a silent rewrite
check_circle<br>Sensitive actions in an audit log enforced append-only at the<br>core platform level
You still check the work. The difference is that there is<br>something to check, instead of a paragraph that appeared from<br>nowhere.
Governance
Built for the person who fills in the security questionnaire
Enterprise SSO, files...