FAQ

The practical questions.

What it costs, what you can do before anything is connected, how it fits your systems, who does what and what a pilot looks like. Short answers. For the long ones, we schedule a call.

What determines the price, and is there a minimum?: Two parts: a fixed fee for the organization and a fee per seat. A seat is a person who practices. We don't count sessions or roleplays; everyone practices as often as they need.; Number of seats, term and any pilot are agreed up front and put in writing. Ask for a quote for your team size.
What can a team do before any systems are connected?: Everything to do with practice. You define the capabilities and what good looks like, build roleplays from a single sentence, a page from your playbook or an uploaded recording, bundle them into programs and enroll people. Everyone gets feedback and their own development view after every roleplay. Managers see the team view, based on practice results.; The only thing that needs a connection is listening in on real conversations. You can add that later. Or never.
Which integrations exist today?: A full API and an MCP server. That makes Converz usable from the tools your people already work in: your CRM, Slack, Teams or an AI agent. And your own systems can create roleplays, enroll people and pull development data.; Real conversations can come from any source: call recordings, meeting tools, telephony, transcripts. If it produces a conversation, Converz can work with it.
What do we need to provide, and who sets it up?: You decide the content: which capabilities count and what good looks like, which roleplays and programs you want, and what they are based on — a playbook, a few recorded calls, your own examples. That is deliberate. What good is, you decide. Converz works within that definition.; We take care of onboarding: we help formulate the first capabilities, build the first roleplays together, set up groups and programs, and connect a conversation source if you want one.
What is in a pilot, and how do we measure success?: A pilot is paid and clearly scoped: a fixed group, two or three capabilities, one program, a start and an end date, and the onboarding above.; We measure success the way Converz itself works. Before the pilot, we assess the agreed capabilities in real conversations; at the end, again, with the same rubric. The difference in real work — that is the result. How much practice happened only tells you whether people used it. It is never the outcome.

The rest we'd rather discuss.

Thirty minutes, about your own situation. Within one business day we'll propose two times.