- Intake & triage
Three Wurqurs, Receptionist, Dispatcher and Exception Handler, hold the inbox, and nobody sorts mail any more.
~$19,000 saved a year for a property manager
See howNothing was ever consistently broken. It just depended on somebody remembering, at exactly the right moment.
Pre-flight Check and Evidence Clerk run the same release checklist a ~40-person B2B SaaS team used to hold in their heads, gating every release and keeping the evidence for each one.
B2B SaaS company · ~40 people · four systems
The checklist
Automated tests were solid. The final checks before release weren't. After a merge, someone had to remember to check whether documentation was updated, whether the Contentful entries were ready, whether accessibility requirements were met, whether the release notes matched the change. Nothing was consistently broken. It just depended on a person recalling a checklist at exactly the right moment.
The engineering manager had already worked out the structure: what to check, and in what order. His team wanted to build it themselves, but between features, customer issues, bug fixes and enhancements, they never found the time, and it kept slipping later.
It just depended on somebody remembering, at exactly the right moment.
What we found, and left alone
The rules already existed, in the engineering manager's head and in the structure he brought to the first conversation. This was mostly a matter of building the gate correctly and connecting it to what they already had running, not inventing new requirements. The final quality decision stayed exactly where it was: with him.
What we built
A release gate across GitHub, GitHub Actions, Contentful and Slack. When a pull request reaches release stage, Pre-flight Check checks the associated documentation and metadata, runs accessibility checks, and compares release information against the change, producing evidence for each one and blocking what fails with a specific reason. Evidence Clerk takes that evidence and assembles it into a pack for the release. Failures go to the release channel with the reason attached; passes are recorded with the release.
Pre-flight Check
Checks the release against the standard, produces evidence for each check, and blocks what fails with a specific reason.
- audit-entry
Evidence Clerk
Collects that evidence and assembles it into a pack for the release.
What changed
clearing a release
A remembered checklist
Under 10 min
180–240
releases a year, gated
180–300 hrs
a year, back to engineering
~$12,000
a year
What used to cost them roughly $1,000 a month by hand now runs on two Wurqurs for $91/month.
Where the humans stayed
The final quality decision. An informal checklist became an actual gate, run consistently on every release. The engineering manager who owned the spec stayed the human in the loop: nearly everything still passes through him to review, approve, or revisit.
What it connects
Where a release starts, the two Wurqurs that gate it, and where the result lands.
where it arrives
- GitHubthe pull request reaching release stage
- GitHub Actionstriggers the gate
what runs
- Pre-flight Checkchecks the release against the standard
- Evidence Clerkassembles the evidence into a pack
where it lands
- Contentfulmetadata checked against the release
- Slackthe release channel, pass or fail, with the reason
What it took
Four weeks. Three to build, one to shadow-run.
The same idea, somewhere else
An inbox nobody sorted by hand any more, three Wurqurs deep.
Every team has a checklist somebody has to remember.
Tell us the job. We will tell you whether a Wurqur can hold it.