Contact

Start a conversation

Email is the fastest route and it reaches us directly — no form, no queue, no ticket number.

Make it useful

What to put in the first email

None of this is required — a single paragraph is fine. But the more of it you include, the more useful the reply will be.

The problem, from where you sit

Described as it affects the business, not as a technical specification. “It takes two days to answer a bid” is more useful than “we need a RAG pipeline.”

What you’ve already tried

Including the things that didn’t work. Knowing what’s already been ruled out saves everyone a first meeting.

Constraints that are real

Deadlines, budget range, regulatory obligations, systems that can’t be touched. Constraints shape the answer more than requirements do.

Using BidBrief

Questions about the product, a pilot on your own document sets, or early access to the iOS build. Say which and we’ll route it.

Solutions & builds

Assessments, integration work, business intelligence, or a second opinion on something already in flight. See Solutions for the shapes these usually take.

Everything else

Partnerships, press, or a question that doesn’t fit anywhere above. The same address reaches us.