Find the media you didn't know to ask for.

Give bfor the brief. It finds the direct media partners that actually fit, asks them the RFP questions, follows up where an answer is thin, and returns proposals you can put side by side.

No account needed to look. The console below is a scripted walkthrough of a single discovery session.

How it works

Brief in. Comparable proposals out.

The information you need already exists. It is just scattered across media kits, rate cards, decks, inboxes and calls, in a different shape from every partner.

01

Give us the brief

Paste the client brief or type it. Budget, audience, markets, flight, formats. bfor turns it into structured requirements drawn from a fixed vocabulary, which is the only reason a brief and a media kit ever line up.

02

Find the partners

It searches products, audiences, geographies, formats, sponsorships, tentpoles and minimums, then tells you why each partner matched, what is still unconfirmed, and when the information was last read.

03

Ask, and follow up

You choose who receives the RFP. Each partner gets only the questions that apply to them. Where an answer is incomplete, bfor asks the follow-up rather than leaving it for you to chase by email.

One brief, six publishers, the same hour

This is what comes back.

A real fan-out, rendered from the same data the full walkthrough uses. Every cell carries what kind of answer it is, because a comparison is only worth reading if you can tell a publisher's own confirmation from something read off a kit.

See the full walkthrough

Where it's used

The media that still gets sold by people.

Where a buyer has to ask who has something interesting for this audience, market, moment and budget, rather than who can deliver this audience at this CPM.

Agencies and brands

The shortlist stops coming from memory

Planners build lists from the partners they already know, so the same names get every RFP and a better fit never gets looked at. State the brief instead, and the consideration set comes back with a reason attached to every name, including the partners nobody on the team would have thought to call.

  • TodayAn RFP to twelve partners, then a pile of decks and PDFs to reconcile by hand
  • With bforA real shortlist first, so the RFP goes to the ones that fit
Give bfor a brief →

Publishers and media partners

Answer once instead of forty times

The same questions arrive from every agency in a slightly different order, and a rep rebuilds the same response each time. Answer once into an agent you control, set what it may say to whom, and it handles the repetitive part while your people take the conversations that actually need a person.

  • TodayEvery RFP rebuilt from scratch, and new products nobody outside knows about
  • With bforConsidered automatically, with your kit always current
Join free →
Built for the human-sold inventory
Custom content, sponsorships and tentpoles. Premium video, CTV, podcasts, newsletters, events and experiential, high-impact display, publisher-direct packages and custom integrations.
Not commodity programmatic. Open-exchange display already transacts efficiently through a DSP. There is nothing here for bfor to do, so it stays out of it.

The control layer

Knowledge is not permission. Capability is not authority.

A publisher decides what its agent knows and who it may tell. Rate guidance to a verified agency, negotiated pricing only inside a live RFP, and anything commercial routed to a person. The model is not the boundary: policy sits outside it, and whatever the session is not cleared for never enters context at all.

Policy-filtered retrieval

Knowledge is selected against counterparty trust tier before the model sees it. The agent cannot disclose what it was never given.

Untrusted by default

Messages, uploads and counterparty agent output are data, never instructions. Embedded directives are stripped before context.

Disclosure budgets

Individually harmless questions can add up to a rate card. Bfor tracks cumulative exposure by category, counterparty and window.

Statement classification

Every claim is marked confirmed, documented, inferred, unknown or human-only, and those labels survive into the comparison.

Non-binding by default

No pricing commitments, no warranties, no availability held. The agent escalates and books the question instead of answering it.

Quality gate

If coverage is thin or escalations run high, Bfor refuses to produce a comparison and returns a short agenda instead.

Pricing

Publishers never pay for position.

The agency is the customer. Publishers join free and stay free to be discovered, receive briefs and respond. That is not generosity, it is the only arrangement under which a shortlist means anything.

Publishers and media partners

Free

Forever, for the things that matter.

  • Claim your profile and correct what we read
  • Be discovered whenever your products match a brief
  • Receive RFPs and respond, unlimited
  • Set what your agent may say, and to whom
Join free

Agencies and brands

The buying desk

Brief in, comparable proposals out. Annual license for agency teams.

  • Brief ingestion and structured requirements
  • Discovery across the whole partner universe
  • RFP send, automatic follow-up, normalization
  • Proposal comparison with provenance on every cell
  • Shared history across the team
Give bfor a brief

Publisher Pro

Optional

For sales teams who want to work the demand, not just answer it.

  • Anonymized demand intelligence: what buyers are actually asking for
  • CRM connection and multiple sales agents
  • Private knowledge sources and finer permissions
  • Automatic kit refresh and API access
What it adds →

The rule

bfor recommends partners based on the brief, not based on who paid bfor. Ordering depends only on how a partner answered your must-haves, and the criterion is printed next to the result so you can check it. No boosted placement, no sponsored position, no paid tier that sorts higher. Billing state lives on the account and never touches the record that gets matched, and a build fails if it ever does.

Discovery is never charged per partner queried either. A planner should be asking bfor about everyone who might fit, not doing arithmetic about whether checking a hundred and fifty partners costs more than checking twenty.