Position · the first
No identifying-data resale
We will not sell access to identifying customer data, derived data, or behavioural data. The graph is the product. Identifying data belongs to the entity it identifies.
There is no salesforce, no SDR layer, no qualification call before the briefing. A request to the desk is answered by the desk, usually within a working day, by the analyst who will run the session. What follows is a description of the engagement, written plainly, so that nothing about it is a surprise.
The clock starts the moment a briefing request arrives on the desk. By the end of the first working day a member of the analyst desk has acknowledged it, with the name of the analyst who will run the session and the proposed window for the conversation. By day four we have held the briefing itself — a forty-five minute working session against your live portfolio, in which we put the graph through the entities, lanes, counterparties and bank chains you tell us matter most. The output of that session is a short written report, between four and nine pages, that lists what we found, what we did not, and what the next thirty days of work would look like if you wished to continue.
If you do continue, the next two weeks are an integration window. The analyst who ran your briefing is the analyst you continue to work with; the engineering desk wires up the API surfaces you need; the workspace seats are provisioned with role-based access aligned to the policies you already operate against your other systems. By day twenty-one the workspace is in production use and the next briefing — the first operational briefing, run against the work your team has been doing through the platform — is on the calendar.
| Day | Phase | Held by | Output |
|---|---|---|---|
| D + 0 | Request received | Front desk | Acknowledgement within 1 working day |
| D + 1 – 3 | Preparation | Analyst desk | Portfolio loaded against the graph |
| D + 4 | Briefing session | Analyst desk · client | 45-minute working session; 4 – 9 page report |
| D + 5 – 10 | Methodology review | Analyst desk · client | Findings reviewed; integration scope agreed |
| D + 11 – 18 | Integration | Engineering desk · client SecOps | API surfaces, role-based access, audit hooks live |
| D + 19 – 20 | Workspace provisioning | Analyst desk | Seats, dashboards, watchlists, alert rules |
| D + 21 | First operational briefing | Analyst desk · client | The graph in routine use; engagement is live |
The session is a working forty-five minutes between an analyst and one or two people from your side — typically a compliance officer or a trade-finance underwriter and, if the team is larger, the head of the function. We open with the portfolio. You name the entities, lanes, counterparties or bank chains that matter; the graph answers, live, on screen. Where the graph disagrees with your existing screening — and the graph usually does, at some point in the first hour — we go straight to the evidence: the customs filings, the sanctions list versions, the counterparty appointments, the freight movements that the disagreement rests on.
The output of the briefing is a written report, prepared the same day, that lists every disagreement, every finding, and every methodology question that the session raised. We do not leave the methodology questions to a sales follow-up. Where the methodology behind a particular finding is not yet published in the Library we will say so on the page, and add a date by which it will be.
The list below is the same one that hangs above the analyst desk. It is not a marketing position; it is the operating rule under which the desk runs, and it is the rule against which a contracted client may, at any time, hold us. If a member of staff is asked to take an action that contravenes any of these positions, the request escalates to the director, and the director's only available answer is no.
We will not sell access to identifying customer data, derived data, or behavioural data. The graph is the product. Identifying data belongs to the entity it identifies.
We will not enrich the contact details left on a briefing request form into a marketing CRM or a third-party intent dataset. The inbox is not a lead funnel; it is a desk.
We will not operate a "premium tier" of sanctions screening, entity resolution or counterparty analysis with different evidence standards from the base tier. The evidence standard is the methodology.
We will not publish customer logos, references, case studies, podcast appearances or panel placements without explicit, written, recently re-confirmed permission. Silence is not consent.
Every finding in a briefing report carries the primary-source citation it rests on. Where a finding rests on a model output the model version, training window and calibration set are named in the report.
We will not commit to a feature on the back of a sales conversation. Roadmap moves are agreed by the analyst desk and the engineering desk against the methodology, not against quarterly bookings.
Demand for briefings is, at the time of writing, larger than the desk. We operate a brief queue rather than a sales pipeline, and the first reply to any request will tell you where you sit in it and what the realistic timing looks like. We do not run that queue against bid amount; we run it against the order requests arrive and against the analyst capacity available against the topic.
There are also briefings we decline. If the request sits outside our methodology — if it asks us to render a judgment that the graph cannot defensibly support, or to perform work that another firm is more obviously suited to — we will say so on the first reply and refer you to that other firm. We have done both more often than the marketing copy of this industry would suggest is normal.
Send the entities, lanes, counterparties or bank chains that are on your mind. One paragraph is enough; the desk will write back the same day.
Request a briefing