Draft preview. Highlighted text needs real Brightyard data before launch.
How we work

Our playbook, in public.

Agents build. Engineers understand your business and make the work better. This is how we actually run projects; if something here doesn't match your experience with us, tell us.

Who does what

Agents do the building. Engineers do the understanding.

AI agents

Build everything needed

  • Turn briefs into user stories and architecture drafts
  • Write code, tests and documentation
  • Run test, security and accessibility checks on every change
  • Deploy in stages and monitor around the clock
Engineers

Understand and make it better

  • Learn your business, users and constraints
  • Make the architecture and trade-off calls
  • Review every change before it ships
  • Turn what the agents learn into a better next version
01

Before we start

A one-to-two-week discovery. You get a written summary of goals, users, risks, architecture and a costed plan. If we think you shouldn't build it, we'll say so.

02

Every two weeks

A demo of working software and a written update in four parts: done, next, risks, and decisions we need from you.

03

How we talk

A shared channel with your team, replies the same working day, and one named delivery lead accountable for the project.

04

Our quality bar

Agents write tests for every change. Every release passes automated tests, a security scan and accessibility checks, and an engineer reviews it before it ships.

05

Handover

Documentation, runbooks, architecture notes and a recorded walkthrough. Your team should be able to run the system without us.

06

Your code, your access

Code lives in your repositories from day one. When we finish, we remove our access and confirm it in writing.

What we won't do

Seven promises, in writing.

  • We won't ship agent-written code that no engineer has reviewed.
  • We won't sell you a rewrite you don't need.
  • We won't hide bad news until the next meeting.
  • We won't hold your code or your data hostage.
  • We won't put unsupervised junior engineers on your project.
  • We won't put a number on our website we can't show you how we measured.
  • We won't sell accessibility overlays or promise legal compliance.
What we believe

Four things we hold ourselves to.

Show the work

Nothing hidden

Public playbook, working software every two weeks, and a site you can inspect with Blueprint mode.

Measure, don't claim

Numbers with sources

If we can't show how we measured it, we don't say it.

Built to hand over

No lock-in

Software that's easy to run, grow and own without us.

Accessible by default

Software for everyone

Accessibility is part of every release, not a project at the end.

Press B.

Blueprint mode shows how every page on this site is built: sizes, fonts, colours, components. We think the people building your software should be comfortable showing their work.