Skip to content
VEYQON
Company · Leadership/04

Six seats, and where each decision stops.

A leadership page is usually photographs and a sentence about a previous employer. This one is organised by seat rather than by person, and states what that seat is accountable for — because when something goes wrong, the useful question is which decision it was, not whose face it was next to.

Organised by accountability·Names published on appointment

Seats · 6/01

The seats.

The remit and the decisions below are real and current. The names go up as each appointment is confirmed; a placeholder is more honest than a title attached to somebody who has not signed anything.

To be announced

Chief Executive

Owns what the company says yes to, and — more often — what it says no to.

Decisions that stop here

  • Which markets we enter, and in what order
  • Whether a commitment made on a page can be honoured
  • Pricing structure, and the decision not to price per agent
To be announced

Chief Technology

Owns the platform architecture and the boundary between the record and the agents acting on it.

Decisions that stop here

  • The single-ledger rule, and any exception to it
  • Which of our changes go upstream to the open foundation
  • Deployment topologies we are prepared to support
To be announced

Head of AI

Owns what an agent is permitted to do, and what it is never permitted to do.

Decisions that stop here

  • Agent scopes, ceilings, and escalation rules
  • Grounding: what an agent may retrieve and cite
  • The evaluation set every agent has to clear before release
To be announced

Head of Delivery

Owns whether the wave plan on the page is the wave plan you get.

Decisions that stop here

  • Programme shape: phases, waves, and rollback points
  • The first go-live date, and the decision to move it
  • Whether a scope change becomes a wave or a variation
To be announced

Head of Security

Owns isolation, access, and the audit trail that proves both.

Decisions that stop here

  • Tenant isolation and key handling
  • Sub-processor list, and any addition to it
  • Disclosure: what customers are told, and how quickly
To be announced

Head of Customer

Owns the answer a customer gets when something has gone wrong.

Decisions that stop here

  • Support tiers and the response times attached to them
  • Escalation into engineering, and who can trigger it
  • Whether a customer story goes on the site
How a decision is taken/02

How decisions actually get taken.

The seats above describe where a decision lands. This describes how it gets there, and it is the same process whether the decision is a pricing change or a schema change.

  1. 01

    Written proposal

    One document: the decision being asked for, the options considered, what each one costs, and the recommendation. No deck.

  2. 02

    Objections recorded

    Anyone affected can object in the document, with their name on it. Objections are not resolved by volume.

  3. 03

    Owner decides

    The seat that owns the decision takes it, in the document, with reasoning. Not in a meeting, and not by silence.

  4. 04

    Reviewed against reality

    Significant decisions carry a date to be checked again. The original objections are still attached when that happens.

Escalation/03

What reaches leadership, and what does not.

Most of what a company escalates should never have travelled. These are the four categories that always do.

A published commitment is at risk
Anything on a public page — a wave plan, an exit right, a response time — that we may not be able to honour. This goes up the same day.
A security or data event
Suspected or confirmed, before it is understood. The Head of Security owns the disclosure decision and the clock starts immediately.
An agent acted outside its scope
Treated as a production incident regardless of whether it caused harm, because the scope is the product.
A customer is being managed rather than helped
If the plan for an account has become communications rather than engineering, that is a leadership problem and not an account one.

Next step

Talk to the seat, not the switchboard.

Contact routes name which team receives them and what happens next.