Greyquill

Services

How we build

Working documentation on the methods behind our modernisation and product engineering work. Written to be useful on its own, whether or not you ever talk to us. Every page carries a one-page summary you can save as a PDF and take into a meeting.

Modernisation

The parallel run Replacing a legacy system without a big-bang rewrite. Pick a seam, build alongside, run both against the same work, and classify every difference until you can prove the new one is right. One-page summary included Mapping an estate before you touch it What to write down about a legacy estate, how to find the dependencies nobody documented, and when to stop mapping and start work. One-page field guide included Where automation stops and a person starts Sorting the steps of a process into plain software, agents, and human accountability. How to set the review threshold and how to move it on evidence. One-page decision guide included

Product engineering

Definition of done for an AI feature What evaluation, guardrails and an audit trail have to mean in practice, written as gates somebody can check, with which of them block a release. One-page gate list included The discovery week What one to two weeks of discovery should produce before anyone writes production code, day by day, and the four tests that say whether the output is good enough to build from. One-page agenda included
Going deeper

Several of these reference the verification and evidence machinery behind our own agent work. That is documented in full at Harness and verificationPrivate and Champ Agent Swarm.