Documentation
How Briedo fits
Briedo is discovery infrastructure. It sits between the systems you already run and the work your team already does: context comes in, Briedo works out what is missing and closes what it can, and a structured record goes where the work continues. This page is the implementation map — what connects today, what is configured with us, and what is not built.
The shape of it
Briedo does not replace the systems around it. It takes what they already hold, works out what is still missing, and returns something the next person can act on.
Your existing systems
- CRM
- Forms
- Your own systems
- Company registers
- The client
Briedo
- Understand
- Detect gaps
- Research and verify
- Ask what remains
- Structure and keep provenance
Your existing workflow
- Structured discovery record
- Brief and views
- Open questions
- Evidence
- Readiness
The examples above are categories of context, not a list of native connections. Which of them can actually reach Briedo today — and how — is the table further down.
Three statuses, used everywhere on this page
Usable on the current production path. Nothing has to be switched on for you.
Built and running, but switched off by default. Turning it on is a deliberate action on our side, per workspace — it is not something you can enable yourself yet.
Not usable today. It may be designed, partly built or simply intended; either way you cannot plan around it.
Before, During, After
These are the same three words the product uses in Settings → Integrations, and they mean the same thing here. They describe when something participates, not what kind of technology it is.
Before — bring existing context in
Everything that gets context into Briedo, and anything Briedo does to prepare the conversation. A client opening your discovery link is Before. A CRM deal arriving through a connection is Before. So is Briedo putting a meeting in your calendar.
During — understand, detect, research, ask
The discovery layer itself. Briedo reads what it already has, works out which of your service requirements are still unresolved, verifies and researches what it safely can, and asks the client only for what genuinely remains.
After — deliver structured context
Where the finished record goes. Your workspace and the notification email are the destinations every workspace has. Sending the result onward into a CRM, a project tool or your own endpoint is built and running, but switched off by default.
One word, two meanings — and they are not the same thing
In this product “During” is used twice, and confusing them is how people end up expecting something that does not exist.
- The discovery lifecycle: what Briedo does while a discovery is running, plus everything that keeps the client connected after it starts — secure client access, follow-up requests, messages, corrections and files the client sends back. That ships.
- The integration stage: using a connected third-party system while discovery runs, so Briedo can check a detail against a tool your team already trusts instead of asking the client twice. No provider ships for that. It is Coming later.
Connection availability
Every mechanism and provider that exists, with what it actually does. A row marked Pilot is implemented — it is not marketing for something unbuilt — but it is off by default and we turn it on per workspace.
| Connection | Stage | Direction | Status | Setup | What it actually does |
|---|---|---|---|---|---|
| Hosted discovery link | Before | Into Briedo | Available now | Self-serve | A branded page at your own address. You send the link; the client answers without an account. |
| Website embed | Before | Into Briedo | Available now | Self-serve | The same discovery experience inside your site, loaded by a script tag. Requires the embed to be enabled and at least one allowed origin. |
| Signed inbound webhook | Before | Into Briedo | Available now | Self-serve | Any system you run posts a signed request with the context it already holds. Briedo verifies the signature, records it and routes it into the right discovery workflow. |
| Google Calendar | Before | Both ways | Available now | Self-serve | Briedo creates the meeting and the Meet link in your connected calendar. The Google permission also lets it read events on calendars you own, but Briedo reads your meetings only if that is switched on with you. It does not create discoveries from calendar events, and has no access to Gmail or Drive. |
| Typeform | Before | Into Briedo | Pilot | Briedo-assisted | A form you already collect on becomes an input. A submitted response arrives signed and can create or link a discovery instead of sitting in a spreadsheet. |
| HubSpot | Before | Both ways | Pilot | Briedo-assisted | Inbound: a deal created or changed in HubSpot can start or link a Briedo discovery. Outbound: Briedo status, discovery coverage, the brief link and the Briedo reference can be written back onto that deal. The write-back half is configured as a destination. |
| Asana | After | Out of Briedo | Pilot | Briedo-assisted | One task opened where the work continues, carrying the finished context. Nothing is read back — Briedo never learns a task’s status. |
| Google Drive | Before | Into Briedo | Pilot | Briedo-assisted | Attach a document someone picks. Per-file access only — Briedo never browses your Drive. |
| Signed outbound webhook | After | Out of Briedo | Pilot | Briedo-assisted | Briedo signs and posts the finished record to an endpoint you configure, so anything that can receive JSON can be a destination. |
| Machine API | After | Both ways | Pilot | Briedo-assisted | Signed machine access to the discovery lifecycle: your system can read a piece of work’s state and, with a write key, create work, answer an open question and manage handover. Switched on with you. |
| TidyCal | Before | Both ways | Coming later | — | Scheduling through TidyCal. Designed, not shipped. |
| Connected context during discovery | During | Into Briedo | Coming later | — | Checking a client’s answer against a system you already run, while the discovery is still going. Nothing ships for this — it is the future half of the During stage. |
| Mailbox and document storage | Before | Into Briedo | Coming later | — | Briedo does not read your mailbox and does not read a document store. There is no connector for either, gated or otherwise. Context from an email thread or a document reaches Briedo because a person puts it in, or because the client is asked. |
Where your existing context can actually enter
Context categories are not connections. This table is the translation between the two: for each kind of context a team already holds, the routes that exist today.
| Kind of context | How it reaches Briedo today |
|---|---|
| CRM records and deals |
|
| Forms and lead capture |
|
| Your own systems, automations and internal tools |
|
| Email threads and documents | No connector. A person puts it in, or the client is asked for it during discovery. |
| Call and meeting context | No connector. A person puts it in, or the client is asked for it during discovery. Pilot |
| Public and registered company information | No connector. A person puts it in, or the client is asked for it during discovery. Briedo looks this up itself where its registers reach — see below. Available now |
| What only the client knows |
|
What Briedo can find out itself
Research happens so the client is not asked for something Briedo could establish on its own, and so a claim can be checked rather than accepted. Every capability below is bounded. None of it is general enrichment, and none of it runs against systems you own.
| Capability | Reach | Status |
|---|---|---|
| Company register and filed financials | Romania. Identification and up to five filed years. | Available now |
| VAT registration check | Italy, Germany, Spain, France, through the EU VIES service. It proves VAT registration and nothing more. | Available now |
| Public web research | Bounded public search, used to build the insight report attached to a discovery. | Available now |
| Gap research after submit | Bounded public search over the specific gaps frozen at submit, not an open-ended crawl. | Available now |
| Requirement-driven acquisition | Briedo decides which unresolved requirements it can safely obtain itself — from a website, a register or a search — and stops when enough trustworthy context exists. | Pilot |
| Call and meeting context | Context from a call becomes part of the discovery record rather than living in someone’s notes. | Pilot |
Company lookups run when a discovery is created with an identifier to look up. Public research and gap research run after the conversation is submitted, against the record as it was frozen — never as a live step in the conversation.
Anything Briedo finds is recorded as research, never as something the client said. The two never merge: a fact carries where it came from for the life of the record.
Readiness and evidence
Two different things that are easy to collapse into one. They answer different questions and neither one is a quality score.
Context readiness
Context readiness describes how complete, clear and usable the available context is against the requirements of the service being discussed.
Ready means there is enough mandatory context for an informed first conversation. It does not mean rich, and it does not mean good. A discovery can be ready and still have plenty worth asking about — the open questions are where that lives.
Readiness verdict
A record can also carry a verdict label, such as Ready for the call or Not ready yet. It is derived from context readiness, not from a separate qualification policy: Briedo has no configurable qualification or scoring policy. It does not decide whether a client is worth working with; that judgement stays with your team and its own criteria.
Where each fact came from
Every fact in a record carries its origin, and the record shows it in plain words rather than internal codes. These are the labels your team will see:
The client answered this directly.
The client was shown this and confirmed it.
The client’s own raw answer, quoted. Briedo recorded no structured value for it — so it is a sentence, not a figure.
Briedo’s reading of what the client said, not a statement the client made. Inferred, not fact.
Established from a source outside the conversation.
Someone on your team entered it.
Found by research after the intake finished.
This is the part that makes a record usable by someone who was not in the conversation. A client’s estimate and a figure from a public register are both useful, and they are not the same kind of thing — so they never look the same. Briedo does not label anything “verified”, “trusted” or “confirmed as fact”, because nothing in the system produces that claim.
Open questions
What is still unresolved, and why — which matters more than the count. A requirement can be open because it is missing, because the answer was partial, because two answers contradict each other, because the client deferred it, because the client genuinely does not know, or because Briedo’s own summary of an answer has not been confirmed.
What Briedo produces
One record, several views of it. The record is the thing that is true; the brief, the recap and the rest are ways of reading it for different audiences.
| Structured discovery record | Every fact, its origin, its state, and what is still open. Everything else is derived from this. | On every discovery |
|---|---|---|
| Professional brief | The internal read, for the team who will do the work. | On every discovery |
| Client recap | The client-facing read of the same discovery, filtered — internal scoring, notes and team information never appear in it. | On every discovery |
| Context readiness | How complete and usable the available context is, with what is driving the number. | On every discovery |
| Open questions | What is unresolved and why, ranked so the first conversation can start with the real ones. | On every discovery |
| Evidence and research | What was established outside the conversation, and where it came from. | Not on every discovery |
| Company profile | Registered identity and filed financials, where the registers reach. | Not on every discovery |
| Insight report | A bounded read of public information about the company, attached to the discovery. | Not on every discovery |
| Follow-up requests | Specific things asked of the client after discovery started, tracked on the record instead of in a mailbox. | Not on every discovery |
Rows marked “Not on every discovery” depend on the workflow, on what was actually collected, or on a capability being switched on. They are real, and they are not guaranteed.
Where the result can go
| Destination | What it actually does | Status |
|---|---|---|
| Your Briedo workspace | Always. Every discovery lands here and this is where your team reviews it. | Available now |
| Email notification | Your team is notified with a link to the brief; the client is notified with a link to their own view. Sent once the Briedo team has switched your workspace to active; a new workspace sends no email. | Available now |
| Client portal | A private, time-limited way for the client to open their own record, answer follow-ups, message your team, send files and correct their own answers. | Available now |
| Signed webhook | The finished record, signed and posted to an endpoint you configure. | Pilot |
| CRM write-back | Briedo status, discovery coverage, the brief link and the Briedo reference written onto the originating deal. | Pilot |
| Project task | One task opened where the work continues, carrying the context. | Pilot |
| Machine API | A signed read interface, for a system that would rather pull the record than be sent it. | Pilot |
Discovery workflows
A workflow is the service being discussed — it decides which requirements exist, what counts as enough, and what the brief is shaped like. These are the ones that can be configured.
| Workflow | Service-specific depth | Status |
|---|---|---|
| Advertising | Full | Available now |
| SEO and organic search | Narrower | Available now |
| Email marketing | Narrower | Available now |
| Social media management | Narrower | Available now |
| Road freight | Narrower | Available now |
| Legal discovery | — | Coming later |
Nothing in the engine is marketing-specific, but these are the workflows that exist today. Any other one needs product work before a team can run it.
What your team configures
Some of this you do yourself in Settings. The rest we set up with you — including everything in Pilot, which is off by default and stays that way until we turn it on for your workspace.
Self-serve — a workspace admin does this
- Which discovery requirements are enabled — Turn a standard requirement off and Briedo stops chasing it. It never blocks readiness, and if the client volunteers it anyway it is still captured.
- Branding, logo and your public address
- Which contact details are collected, and which are required
- The embed, and the sites allowed to load it
- Signed inbound connections, and their secrets
- Team members and their roles
Briedo-assisted — we set this up with you
- Which discovery workflow your workspace runs
- Whether qualification is shown, and in what vocabulary
- Connected CRM and form accounts, and their routing rules
- Where finished context is sent
A policy change applies to new discoveries only. A discovery that has already started keeps the policy it started with, so a record never changes shape underneath a client who is halfway through answering.
Does your team have to adopt another tool?
Briedo has a workspace, and this is the honest version: it is where discovery is set up, where records are reviewed, and where your team acts on what came back. It is not trying to replace the CRM or project tool you already run.
- Your team does open Briedo — to review a record, resolve an open question or send a follow-up. That is the work, and it has to happen somewhere.
- The client never creates an account. They open a link, answer, and can return to their own view later.
- Where a supported connection exists, context can arrive from the system you already use and the result can be sent back to it — so Briedo becomes a step in a workflow rather than a second place to live. Which connections those are is the table above.
- What Briedo is not is a daily destination. Nobody needs to work inside it. But “you never open Briedo” would not be true, so it is not something claimed here.
Implementation methods
The four ways context gets in and out, each with its trigger, its input, what Briedo does, what it produces and where the result lands.