Discuss a Project

Start a conversation

The most useful first message describes a specific decision, workflow or constraint that is not working, and what would have to be true for an agent to be allowed to make it. We read everything that arrives and route it to the person who can answer it, usually within one working day.

ResponseUsually one working day
First callTechnical, not sales
ObligationNone

Tell us what you need

Fields marked * are required. We ask for the minimum that lets us route this properly.

Please tell us your name.

Please provide a valid email address.

Please tell us which organisation you are with.

Please choose the closest category.

Please describe the situation in a couple of sentences so we can route this correctly.

Please do not include confidential data, credentials or personal information. If you need to discuss something under NDA, say so and we will arrange it first.

This form posts to a working endpoint on this site and the submission is recorded with a reference you can quote. It is not a decorative form.

What happens next

  1. Routing. Your message goes to the person closest to the problem — a deployment lead, an agent engineering lead, or the partnerships lead — rather than a generic inbox.
  2. A reply. Usually within one working day, from an engineer rather than a salesperson.
  3. A technical conversation. Ninety minutes, with an engineer in the room. We use it to understand the constraint and to tell you honestly whether we are the right firm for it.
  4. A proposal. Only if there is a piece of work worth proposing. If the answer is that you do not need this yet, that is what you will hear.

Direct contact

If you already know what you need, skip the form.

Email
hello@originbigdata.com

Partnerships
See how partnership works first

Before you write

  • A useful first message names a decision, a workflow or a constraint — not "we want AI".
  • It is fine if you do not know which of our four service areas applies. That is our job to work out.
  • It is also fine if the answer is that you are not ready. Plenty of first conversations end there, and that is a useful outcome.
  • Do not send confidential data, customer records or credentials. If you need to discuss those, we will put an NDA in place first.
Before you write

Questions about contacting us

Q1What happens to my message?

It is recorded with a reference and routed to the person closest to the problem — a deployment lead, an agent engineering lead, or the partnerships lead. It is not a marketing queue and it is not resold.

Q2How quickly will I hear back?

Usually within one working day, from an engineer rather than a salesperson. If your situation is time-critical, say so in the message and it will be prioritised.

Q3Do you need an NDA before we talk?

Not for a first conversation. If you want to discuss confidential data, customer records or anything under an existing agreement, we will put an NDA in place before you send anything, and we will tell you what we need for it.

Q4What should I include?

A specific decision, workflow or constraint that is not working, what you have already tried, and what would have to be true for an agent to be allowed to make it. If you do not know which of our service areas applies, that is fine — it is our job to work that out.

Q5Will you tell us if we do not need this?

Yes, and we will say it early. Plenty of first conversations end with the conclusion that the constraint is organisational rather than technical, and that the next step is a process decision rather than a project. That is a useful outcome, not a failed lead.

Q6Do you work with our existing partners?

Yes. We work with systems integrators, consultancies, workforce practices and regional specialists. Responsibilities and commercial terms are agreed per partnership. If you are considering a partnership, the partnerships route below is the right one.