Frequently asked questions

Briedo is pre-call discovery infrastructure for professional teams. It runs a structured discovery conversation after a meeting is booked and prepares a structured pre-call brief before it starts. It evaluates the readiness of the available context, not the quality of the prospect: Briedo shows what is known, missing, or uncertain before the first call, and your team decides whether and how to pursue the opportunity.

No. A generic chatbot can generate questions or summaries. Briedo executes your team's configured, service-specific discovery requirements, maintains structured context, and prepares a reliable handoff before the first call.

Professional teams that run repeated discovery before a first call, where the context needed for that call is currently scattered across forms, emails, notes, and the client's own head. Which discovery workflows can be configured today is a separate question, answered below.

Advertising, the service also known as Paid Ads, and SEO / Organic Search. Advertising has the deepest current examples and product-specific coverage; SEO is active and supported with a narrower service-specific layer. Because those two are what exists, the current cohort is digital marketing agencies running them. Other discovery workflows cannot be configured yet, and contacting Briedo about one is not a promise of support.

Yes, if the team has enough repeated discovery volume to benefit from a structured pre-call workflow. Very low-volume teams may not need more than a simple form.

Not yet. The product category is broader than any single workflow, and nothing in the engine is specific to marketing, but Advertising and SEO are the only discovery workflows configured today. Any other workflow needs product work before it can be provisioned, and we will not claim otherwise.

Briedo Connect is the client-facing execution layer for your team's pre-call discovery process. After the first call is booked, the prospect uses the branded discovery link to complete a guided conversation and structured submission.

Briedo Flow is a planned product for internal request clarification: a colleague in another department opens a request, Flow runs a guided clarification conversation, and the receiving team gets a complete request brief before work starts. It is on the roadmap and not available today.

We are recruiting a pilot group of 10 teams, Romania-first, with verbal commitments in place. We can share aggregated metrics once the pilot has 30 days of data, happy to set up a call once we have first results.

A prompt can generate questions or summarize text. Briedo is an operational workflow: your team configures a service and which discovery requirements are enabled, then Briedo executes them consistently through a branded conversation, structured state, readiness visibility, and team handoff.

Forms are fixed. Briedo can clarify vague answers, surface gaps, ask follow-up questions, and organize the result into a usable brief instead of a flat response sheet.

A form collects what the prospect already knows; Briedo also explains unfamiliar terms, clarifies answers, shows context readiness, and delivers a structured brief instead of a spreadsheet export. Form tools are good at collection and generic chatbots are good at conversation; Briedo is built for discovery workflows that need structured outputs, open questions, and a reliable handoff.

The recommended workflow is direct-link first: after the first call is booked, send briedo.com/a/your-slug by email, message, or CRM automation. An optional website widget or embed remains available for selected workflows.

A complete intake typically takes 6 to 12 minutes. If someone stops early, the partial context is preserved for the team to review; abandonment is not treated as a judgment about prospect quality.

You see the partial conversation in your dashboard, and any information the lead already provided is preserved, so you can follow up manually. Inactive sessions are marked as abandoned and flagged in your dashboard.

Yes. It explains why each question matters, in plain language. If the lead asks an off-topic question, it redirects them back to the intake.

It will, occasionally. That is why every brief shows you the full conversation transcript, you can verify any answer that looks off before acting on it. There are also guardrails: numeric values are normalized (so "2k lei" becomes 2,000), and obviously inconsistent answers get flagged.

Yes. It is currently optimized for Romanian and English, and works in other major European languages with some quality variance. Confirm the languages you need with us during onboarding.

Briedo prepares a structured pre-call brief for the team. The underlying discovery record can include a Professional Brief, Client Recap, context-readiness status, missing-information prompts, and optional AI insights or research-backed context when available. Supported views distinguish prospect-provided context, research-backed evidence, inferences, missing or uncertain items, and topics for the first call.

No. Briedo is meant to improve preparation before the call. It helps teams start the conversation with clearer context, fewer gaps, and better internal alignment.

No. It supports teams by collecting, organizing, and clarifying information. Decisions still belong to the team using the platform.

No. Your team defines the service and which discovery requirements are enabled. Briedo turns that setup into a repeatable client-facing process, handles clarification and structure, and prepares the team before the first call.

Within the supported Advertising and SEO templates, you can create a named editable copy and configure which discovery requirements are enabled. The configured catalog names the Advertising service after the Paid Ads workflow it covers. Pilot onboarding helps configure this setup. Arbitrary custom questions and a full methodology builder are not current self-service capabilities.

Yes, and we recommend it. Logo, primary color, secondary color, and font preset. The intake URL (briedo.com/a/your-slug) shows your brand, not ours, and the client-facing recap looks like it came from your agency.

Not yet in full. The guided discovery experience uses the agency logo, colors, and direct link, but it carries Briedo branding. Full white-label is on the roadmap, not available in the current version.

Not directly in the pilot, briefs are accessed via the Briedo dashboard and emailed to you. CRM integrations are on the roadmap for after the pilot validates the core product. If your CRM has a Zapier or webhook integration, we can discuss a workaround.

A workspace can enable supported services and keep standard templates plus named custom copies. Custom templates can change which discovery requirements are enabled. If your use case needs multiple workspaces or more complex routing, confirm the exact setup during onboarding.

Briedo's core infrastructure runs on Google Cloud (Firebase) in European regions (primary region europe-west1, Belgium), with data encrypted in transit and at rest on that infrastructure. Some sub-processors, including AI providers, may process data outside the EU/EEA under appropriate safeguards; see the sub-processors page for the current list.

Yes. Leads see a consent checkbox before any data is submitted, and the consent is logged with timestamp and version. You are the data controller for your leads and Briedo is the processor, our Data Processing Agreement (DPA) is incorporated in the Terms or available separately at briedo.com/legal/dpa.

We use Anthropic Claude and OpenAI's GPT-4.1 models for the conversation, AI insights, and brief generation, and Brave Search for the research layer. None of these providers train on data submitted through their APIs, that is contractual via their DPAs. The full list of sub-processors is at briedo.com/legal/subprocessors.

No. The AI providers Briedo uses do not train on data submitted through their APIs, this is contractual via their data processing agreements. Client data is processed only to deliver the service; see the privacy and sub-processor pages for the exact terms.

You do. We process it on your behalf. You can export, delete, or transfer it at any time.

Forward the request to privacy@briedo.com. We have a documented procedure to find and erase that lead's data across all systems within 30 days, as required by GDPR.

In the current version, all members of a workspace can see all briefs. Briefs can be assigned to a specific team member for ownership and filtering, but per-member visibility restrictions are on the roadmap rather than available today.

Briedo provides privacy, GDPR, security, and DPA information through public legal pages. The platform is positioned for professional workflows where data handling, access control, and responsible use matter.

Starter is €99 per month with 30 briefs included. Growth is €279 per month with 100 briefs. Enterprise starts at €999 per month with custom volume. All three are paid; there is no free tier.

It is the number of finished briefs included in each monthly billing period. An intake a prospect starts and abandons before it produces a brief does not use one. The count is advisory: if you go past it, Briedo keeps working and we talk about capacity rather than cutting you off.

The first 5 Starter seats are €49.50 per month for 6 months, then €99 per month. It is limited to 5 agencies and applies to Starter only.

You apply, we talk, and Briedo invoices you monthly. There is no self-serve checkout yet, so no card is collected on the site and nothing is charged automatically.

Yes. The commercial relationship is monthly with no annual commitment. Tell us before the next period starts and we will not invoice it. Your data and templates stay available while your workspace is active; on request you can export everything and we delete it within 30 days.

Ask for more capacity from inside your workspace. A person reads the request and follows up. There is no automatic overage charge and no purchase flow.

About 60 minutes total: a 30-minute setup call where we configure supported services, templates, and branding together, then time to test the direct discovery link and review a sample run. The website widget is optional and secondary.

Direct access to the founder via a dedicated email at support@briedo.com. Response within 24 hours on business days. For urgent issues during the pilot, we will set up a direct line.

We monitor the platform with error monitoring (Sentry) and cloud logging. During the pilot we don't offer formal SLAs, but we treat any outage as urgent: you would be notified by email and we would give a post-incident summary. If your intake is critical during the pilot, we recommend keeping a backup contact form on your site as a fallback.