About
We are building the definition, not another place to draw a chart
Nobody in an analytics org is short of dashboards. They are short of agreement — and agreement is a thing you can only build once the definition is an artefact somebody owns.
- 2024
- Founded
- 31
- People
- 4
- Countries
- Series A
- Stage
Our story
Why this exists
Sightline began in a meeting where four people had four revenue figures and all four were defensible. Nobody had made a mistake. Each query answered a slightly different question and no two of the questions had been written down. We spent an hour reconstructing which was which and then forgot to write that down too. The problem was never the data or the charts on top of it — it was that the definition lived in whichever query you happened to open. So we made the definition the artefact, and everything else a reader of it.
Every team we knew was rebuilding that layer badly, in a hurry, under a deadline set by a demo that had gone well. It is not a differentiator for any of them and it is genuinely hard to get right, which is a fairly precise description of something that should be bought rather than built.
How we work
We ship small and we ship often, and we write down what we learn. The engineering notes on this site are not marketing; they are the internal write-ups, edited lightly.
We compute in your warehouse and we keep definitions in plain SQL and YAML, on purpose. A semantic layer that becomes the only thing able to read your own models is a hostage situation with a subscription attached, and it is not a business we want.
How we decide
Four things we argue from
Not values in the poster sense. These are the sentences that actually end disagreements here.
01
Legible over clever
If explaining what the system did requires an engineer, the system has not finished the job.
02
Default to the safe path
The guarded route has to be the quick one, or people will route around it and be right to.
03
Measure before building
We have optimised the wrong end of a funnel because it was the end we had instrumented. Once was enough.
04
Say the number
Claims on this site come with the measurement behind them, or they do not go on the site.
Team
The people behind it
Thirty-one of us across four countries. These are the ones you are most likely to end up on a call with.
Maya Okonkwo
Co-founder & CTO
Tomas Halvorsen
Co-founder & CEO
Inès Lefebvre
Head of Security
Daniel Reyes
Principal Engineer
Priya Raghunathan
Head of Design
Kwame Mensah
Head of Customer Engineering
Define the number people argue about.
Pick the one metric that starts every disagreement, write it down once, and let a week of meetings resolve against it. That is the whole evaluation.
Free for 14 days · No card required