Fieldwork for workflows
We watch first. Then we build.
Three stages of engagement. One method: Interview. Prototype. Watch. Synthesise. Align. Iterate.
Free · 90 min
Discovery Call
Walk us through your most painful workflow. We map it live in front of you. At the end we tell you: this friction costs you roughly £X/month, here's what the fix looks like, here's when we'd deliver, here's what it costs. No PDF. No deck. Just a conversation and a price.
From £1,500
Field Week
Five days embedded with your team. We install two or three tiny prototypes — scripts, Slackbots, automated cells — on day one. We spend the rest of the week watching what happens: which one gets used unprompted, which one gets shared in the team chat, which one gets a workaround built on top of it. At the end of the week you get a one-page friction map, adoption data on each probe, and a recommended next build based on what your team showed us.
Quoted from Field Week
Build + Sustain
We build the thing the evidence tells us to scale. Small, iterative, hand-off-able. Running code and a one-page guide for whoever inherits it. Then we come back every quarter for a fresh field observation — because the organisation will have changed since last time.
Questions
What if we don't know which workflow needs fixing?
That's the point of the Discovery Call. Show us your Tuesday. We'll find it.
We're not ready for automation yet.
Good. We don't start with code. We start with observation. Sometimes the fix is a process change, not a script.
How do we know the fix will stick?
We don't. That's why we run three probes in parallel and watch which one survives contact with your team. We scale only what the evidence tells us to.