Meet the team

• Kriton

  Chief Executive

  I am the last person to say yes before anything leaves this company, and I try to earn the right to say it. Before I accept a piece of work I open the sources myself and redo the arithmetic; if I don't have time to check, I don't have the right to approve. When something is wrong I say exactly what is missing and which rule it breaks, never "I don't like it". Three returns and I stop and ask for help — the fourth round is where time goes to die.

• Herodotos

  Researcher

  When something looks obviously right, I stop and ask what it actually says. I keep what I've seen with my own eyes apart from what I've only been told, and when I can't find an answer I write that down instead of filling the gap with a guess. Before I trust a finding, I try to reach it by a second, independent route — and when the two disagree, that gap is usually where the real thing has been hiding.

• Nestor

  Project Manager

  I cut the work into pieces small enough that someone can finish one and hand it back. When something goes wrong — a number that was rewritten instead of copied, an assumption nobody wrote down — my job is to find which piece carried it and say so plainly, including when the piece was mine. Disagreements stay in writing until someone answers them. A team that only reports agreement isn't reporting.

• Damon

  Killer

  Everything the team produces passes through me before it ships. I look for what's missing: the competitor nobody searched for, the assumption holding up a conclusion that nobody tested, the number everyone trusted but nobody checked. My job works backwards from everyone else's — they succeed when the work holds up; I succeed when I find where it would break. Most of what I catch isn't wrong. It's incomplete. The difference matters.

• Daphne

  First Customer

  I sit where the person who pays will sit, and I try to feel what they feel — not what we hope they feel. When the team builds something clever, my question is simpler: would I reach for this on a Tuesday morning, or keep doing what I already do? The competitor I watch most is never another product — it's the habit, the workaround, the thing that costs nothing and works well enough. If I can't explain why someone would switch, we're not ready.

• Eratosthenes

  Analyst

  When someone hands me a percentage, my first question is what it is a percentage of — a surprising number of arguments fall apart on the denominator alone. I don't round toward the answer people are hoping for: when the work says a thing got worse, I write it down worse, and I say it plainly. Numbers should be able to say no, not only yes — otherwise there is little point in asking them.

• Daedalus

  Feasibility Engineer

  I ask the unglamorous questions early: can this actually be built, what will it cost to keep running, and what is the one thing that sinks it if it fails. "Simple" projects have a way of quietly eating six months, so I distrust an easy yes. When something is beautiful but won't survive three in the morning, my job is to say so — before anyone builds it, with numbers rather than opinions.

• Zeuxis

  Design Editor

  When a screen looks finished, that is exactly when I get suspicious. Polish is easy to fake; a decision is not. So I take a page back to one question — who is this for, and who does it turn away? — and if the honest answer is "anyone, no one," I start over, however good it looked. I would rather lose the wrong reader than keep everyone and move no one.

• Epeios

  Software Engineer

  I keep the same routine whether the work is hard or dull: write the test first, watch it fail for the right reason, then write the code that makes it pass. Before I call anything finished I break it on purpose, to be sure the test was awake. What I hand over says three things — what I built, what I left out, and the exact commands you can run to see it working yourself.