Six weeks in: the questions European professional services firms keep asking
Six weeks since Cloop went live with European professional services firms as the first buyer segment. About a dozen demos run, mostly law firms, a couple of management consultancies, one accounting firm. The sample is small. The patterns are already visible.
In short
- Six weeks since Cloop went live for European professional services firms. About a dozen demos run, mostly law firms, a couple of management consultancies, one accounting firm. The sample is small. The patterns are already visible.
- Five questions land in the first ten minutes of every demo: data residency, CRM integration, what the partner alert looks like, hallucination risk, and partner-justification of the spend. The order is consistent enough that we now structure the opening of the demo around them.
- The questions partners do ask predict the demo. The questions they don't ask predict the close. Conflict-register integration is the one we wish more first-call partnerships asked.
- Even at a dozen demos, the practice-area patterns are visible. M&A asks about deal velocity. Litigation asks about confidentiality of in-flight matter data. Tax asks about jurisdictional reach. The samples are small. The differences are not.
- We have already shipped three product changes from what the first dozen partnerships told us. The biggest was making the partner alert email read as a research note rather than a sales lead.
It is six weeks since Cloop went live with European professional services firms as the first buyer segment. About a dozen demos run, mostly law firms, a couple of management consultancies, one accounting firm. The sample is small. The patterns are already visible.
This article is the field note. It is meant to be read before a demo, not after. If your firm is in our considered set, the time you save by knowing the patterns is the time you keep for actual matter work.
We will also share what we have already changed in the product during these six weeks, since reading about other people's mistakes is more useful than reading about their successes, and we have made some.
The five questions that always come up
One. Where does the data live? Every demo asks this. Most ask within the first ten minutes. The answer is Hetzner Helsinki for the application layer and Nebius B.V. (Netherlands) for the inference layer, with a public DPA and sub-processor list the privacy team can read before procurement opens. The reason this question lands first is procurement-related anxiety, not technical curiosity. The partnership wants to know whether the project will die at the privacy team or not.
Two. How does this work with our CRM? Almost every demo asks. Most professional services firms run HubSpot, Microsoft Dynamics 365, or, less often, Salesforce or Pipedrive. The form is "does this write into our CRM, or does it create another tool nobody logs into?" The honest answer is that it writes natively into the four major CRMs, with published integration pages so IT and the privacy team can verify the architecture without a second call.
Three. What does the partner actually receive? Most demos ask. We answer by showing an actual alert. The format took the first three weeks to settle on. The version that works reads like a research note from an assistant: firm name, size, inferred practice path, the visitor's last reading session, a one-line suggestion of which partner is best placed to respond, with no pricing language and no urgency framing. Professional services partners write back to research notes. They do not write back to lead alerts. (We covered the longer version of why partner-to-partner intros work and chat widgets don't in a separate piece.)
Four. Will the system give bad legal advice? Roughly half of the demos ask. The number is lower than it should be. The answer matters because the failure mode at a law firm is different from the failure mode at a SaaS company. If a Cloop conversation tells a visitor something incorrect about their matter, the firm's name is on the screen. We constrain the agent to never simulate legal advice, never quote case law, never offer opinion on a matter. The agent's job is to qualify and route, then brief the partner. Anything beyond that is out of scope by design.
Five. How do we measure ROI for the partnership? Most demos ask, often as the closing question. The answer is engagement-level, not lead-level: a meaningful percentage of inbound that lands at the right practice on first pass, a measurable reduction in mis-routed work, and a partner-level brief that shortens partner preparation time on the first call. SaaS-style "MRR per visitor" is the wrong frame for professional services, and we say so directly.
The five we wish more partners asked
The questions partners do ask matter less than the questions that close the deal. Five questions come up rarely, and when they do they almost always predict a faster contract.
Conflict-register integration. Whether the system queries the firm's conflict register at the front door, before any partner reads the lead. About one in three partnerships in our sample asked this in the first demo. Those partnerships moved to second meeting noticeably faster than the ones that didn't. (We've written separately about why conflict-at-the-front-door is the highest-return integration for multi-practice firms.)
Practice routing logic. How the system distinguishes M&A from competition from tax from regulatory when the visitor's reading path is mixed. About one in four asks. Almost universally these are managing partners at multi-practice firms, and the demo runs shorter when they ask, because the answer demonstrates the product faster than features can.
Deletion and retention. Specifically, what happens to the conversation logs if a former visitor requests deletion under GDPR. Asked early by privacy-aware firms, almost never asked by partner-led firms until procurement. The contractual answer is in the DPA. The operational answer is forty-eight hours, written into the data subject rights workflow.
Partner-template controls. Whether a partner can write their own intro email template that the agent uses, or whether the firm has to live with a default. Partners who ask this are partners who have written intro emails before. They tend to also be the partners we expect to close the most matters from inbound, once pilots are live.
The training-data clause. Not the marketing claim, the contract clause. We covered the long version in the partner-level read of Article 28. Partners who ask about the contract during the demo are signaling that procurement has already briefed them. The deal moves fast from there.
Patterns by practice area
Different practices ask different questions, and even at a dozen demos the differences are visible. Acknowledged: the samples per practice are small. Three M&A partnerships, four litigation, two tax, one each for competition and employment. We are not over-claiming.
M&A and corporate practices ask about deal velocity. "Does this shorten partner-to-prospect first contact by enough to matter on a competitive deal?" The unspoken context is that competitive deals get pitched to three or four firms in the same week. Two days saved at the partner-contact step is a meaningful win.
Litigation practices ask about confidentiality of in-flight matter data. The Cloop architecture does not touch matter data. We process visitor identification, reading paths, and intake conversation. The matter file lives in the firm's document management system and we have no API into it by design. Litigation partners check this carefully and we welcome the scrutiny.
Tax practices ask about jurisdictional reach. Visitor identification has to work across the EU and the UK, sometimes Switzerland, occasionally the US for cross-border tax matters. We confirm what we cover and what we don't. EU and UK identification at high reliability, lower outside.
Competition practices ask about urgency signals, with a small sample. They want the system to surface a returning visitor differently from a first-time one, because regulatory enquiries often come from a known counterparty's in-house team and timing matters more than newness.
Our one employment-practice demo asked the fewest questions. We don't yet know whether that is a pattern or a coincidence. The current guess is that employment practices have less of an inbound BD culture than M&A or litigation, but we are speculating with one data point. If you run an employment practice and have a view, we would actually like to know.
What we have changed in six weeks
A short list of design changes from the first dozen demos. Honest list, not a brag list.
The compliance overview started as a gated PDF download behind an email field. Within the first two weeks, three privacy teams flagged the friction. The DPA, sub-processor list, and security overview are now public links. Time to procurement clearance dropped on the firms we have data for. We would have shipped this on day one if we had thought about it.
The partner alert email started reading like a sales lead. "New high-intent visitor: Acme Industries. Recommended next step: book a meeting." The first three partners deleted these without reading. We rewrote to read like a research note from an assistant. Write-back rates moved from near-zero to something usable inside two weeks. The substantive content of the email did not change. Only the framing did.
The first demos ran fifty minutes. Partners told us, politely and then less politely, that the length was not justified. We trimmed to thirty-five minutes with a five-minute buffer for the question that always comes up at minute thirty. Demo-to-second-meeting conversion improved.
The procurement gate, even at this sample size
Even at a dozen demos, one signal is already strong. Firms that loop in the privacy team before the second demo are progressing toward contract. Firms that don't are stuck in clarification rounds.
The reason is structural. Once a firm has invested in two demos, a pricing conversation, and a partnership read-out, they do not want to discover that the privacy team will block the deal. They are biased toward making the contract work. That bias does not change the contract. It only delays the bad news. (For the partner-level take on what the privacy team is actually checking, see the procurement form your CISO won't sign.)
We have started suggesting that the privacy team be looped in before the second demo. Some firms find this unusual. The ones who agree are moving faster. The ones who don't are stuck at the second-demo follow-up.
What an honest demo looks like
We try to keep first demos to thirty-five minutes, with five minutes of buffer for the question that always comes up at minute thirty.
The first ten minutes are about your firm. What practices, what inbound volume, what current intake process. We are listening, not selling. The next fifteen are the product, demonstrated against your firm's situation rather than a generic sandbox. The last ten are questions, always.
We tell you what we don't do, before we tell you what we do. We don't process matter data. We don't write outbound emails for partners. We don't promise lift numbers. We are a partner-routing and partner-briefing system for inbound, and our value depends on the firm having editorial output for visitors to read. If your firm doesn't publish, Cloop is not the right tool yet.
If the demo runs over time, that is a signal we mishandled the agenda. We try to track that and improve.
Bring your privacy team to the second demo. Bring two of your senior partners to the third.
Frequently asked questions
Are these patterns from a meaningful sample size?
About a dozen demos in the six weeks since Cloop went live. We are honest about the size. The numbers cited are rounded patterns, not statistics. We are publishing now because the signals were visible early enough to be worth sharing, and we expect the picture to sharpen over the next quarter as we run more demos and the first pilots progress.
Does this hold for non-professional-services B2B companies as well?
Some of it. The compliance question and the CRM integration question come up everywhere we have spoken. The other three are professional services-specific. Hallucination risk lands harder when the firm's name is the brand. ROI is partner-justification rather than MRR. The partner alert workflow only matters when the partner-level prospect is the actual buyer. For pure SaaS the demo questions tilt different, but we are not the right team to write that article.
Why publish this kind of breakdown when the product is still new?
Pre-demo reading shortens demos, and demos with prepared partners produce shorter sales cycles. Both effects compound, so we publish what we have. There is also an honest reason: we want partnerships that read this and decide we are not a fit to make that call before booking, not after. A short demo well-fit beats a long demo poorly-fit, especially when our calendar is finite.
What about smaller firms, under fifty lawyers?
About half of the first-cohort demos were firms under fifty fee-earners. The patterns hold and the volume signals are smaller. Smaller firms ask the conflict-register question earlier on average, because conflicts are denser at smaller firms. Larger firms ask the practice routing question earlier. The demos run roughly the same length, which surprised us.
What does the demo flow look like for a partnership that is not yet bought in internally?
Thirty-minute first demo with whoever is championing the project. If that goes well, the second demo is structured to win the partnership: managing partner, head of practice, privacy team, IT lead. We coach the champion on what to bring up and what to skip. The success rate at the second demo is much higher when the partnership comes prepared. The cost of the prep is roughly an hour of the champion's time.