Skip to content
Herowebs

04

Process · 22 January 2026

Why every engagement starts with a two-week discovery

What we deliver in a fortnight, why we charge for it, and how it pays for itself before the first line of production code is written.

We do not bid on RFPs without a discovery sprint. We do not write fixed-fee proposals without one either. The reason is boring and important: most projects are mis-scoped at the brief, and a fortnight of senior time is the cheapest way to find out.

Discovery deliverables, every time:

  • An architecture memo that names the systems, the data, and the integrations.
  • A working prototype against real data — clickable, deployed, used.
  • A phased plan with three options: minimum, recommended, ambitious.
  • An honest read on what to build, what to buy, and what to defer.

Clients have spiked engagements at the end of discovery, and we have helped a handful do exactly that. It is the right thing for both sides. The work that survives discovery is the work worth shipping.

Next entry →

The economics of retrieval

Most teams underestimate how much retrieval quality, not model choice, drives the cost and reliability of an LLM product.