This guided setup captures what our engineers need to deploy your Data Bloodstream — the work of two or three scoping meetings, in about 20 minutes. Nothing here is final: your Forward Deployed Engineer reviews every answer with you at kickoff.
A list of the systems you use, who owns them internally, and — if easy — a recent CSV export from one of them. No passwords: we never ask for credentials in this form.
Your answers go to our team, an engineer is assigned, and you get a kickoff invite within one working day. First clean data typically lands inside two weeks.
The basics — so your engineer arrives knowing your business.
Who we'll work with. All three can be the same person in a smaller team.
Owns the outcome
Answers our questions
Grants system access later
The one thing you'd point to and say "this is why we're doing this." Plain words — your engineer builds the deployment around it, and it becomes the yardstick for week four.
What should be true in six months? Pick everything that applies.
Three kinds of places, in the order we usually connect them. Pick everything that applies — missing something is never a blocker.
Databases & warehousesRough answers are fine — this sets the order we connect things in.
Documents & free text: ingesting unstructured data is on our roadmap — flagging it now helps your engineer plan the deployment around it.
A recent export — customers, orders or products, CSV or Excel — lets your engineer confirm the field mapping before kickoff instead of during it. Exports only: never send passwords or API keys here.
Do you have a recent export you could share?Nothing is uploaded here. Your engineer will share a secure folder for the files after the first call.
Pick what matters most — these become the quality rules that run on every load, before anything reaches your master tables.
These are the clean, deduplicated tables we build and keep current — the single version of the truth your reports and AI run on. Every business's set is different: define yours, and the key each table is structured around.
Example only: the rows below are from our jewellery reference build. A homeware trade business might instead master Contacts, Products, Orders and Designer relationships. Rename, remove or add until it's yours.
A rule we often propose: marketing tools can update a record — but never create a new one. Your engineer will suggest rules like this per table, for your sign-off.
In plain words: which tables relate, and how. This becomes the map of your business that lets AI answer questions accurately.
Example only — a trade business might add: Designers place orders for Clients, or Firms employ Designers.
The outputs we build first. Pick everything that applies — the first one you'd want in week four matters most.
We never collect passwords in this form. Access is handed over in a scheduled security session after kickoff — usually read-only API keys, created by your IT owner with your engineer on the call.
A quick look before it goes to your engineer. Click any step in the sidebar to edit.
When would you like to kick off?Your answers are with our team. An engineer will be assigned today, and you'll get a kickoff invite within one working day. The security session for system access gets scheduled at kickoff — nothing else is needed from you right now.