Delivery standards

Quality control: what we will not skip

Every studio says it values quality. Here is the specific list we hold ourselves to — ask us to show our working at any point.

Before building

  • A written problem statement and named first users.
  • A "now / later / never" scope list agreed with you.
  • A tested prototype of the main journey.
  • Cost ranges per build cycle, with assumptions written down.

While building

  • A working preview at the end of every cycle.
  • Every change reviewed by a second developer.
  • Automated tests for business rules, run on each change.
  • Short written summaries after each review session.

Before release

  • Accessibility checks against WCAG 2.2 AA as our working target.
  • Security review: secrets out of code, dependencies updated, data minimised.
  • Release checklist and rollback plan.
  • Release during working hours.

At handover

  • Source code in a repository you own.
  • Accounts transferred and our credentials removed.
  • A run-book: how to deploy, back up, restore and update.