The same loop, every project.
The Reimei BuildLoop is the seven steps we run on every engagement — discover, map, design, build, validate, launch, improve. No agency theatre, no surprise reveals. Each step leaves a concrete artifact, so the next person who touches the work has a clear story.
We don't pitch a process. We rehearse the same one until it ships every time.
Most projects fail in the gaps — the thing nobody scoped, the decision nobody wrote down, the reveal at the end that's nothing like what was wanted. A repeatable loop closes those gaps. Because we run the same seven steps every time, the boring-but-critical bits — the decision record, the success metric, the rollback plan — never get skipped under deadline pressure. It's not heroics; it's the opposite. The drama is engineered out so the result is predictable.
Every engagement runs this loop.
- 01
Discover
We start by learning what's true, not what's assumed. Stakeholder interviews, a system audit, and a hard look at the real constraints — budget, deadlines, the legacy thing nobody wants to touch. We'd rather surface the awkward truth in week one than discover it in month three.
ArtifactA findings brief & a constraints list - 02
Map
The problem becomes an architecture and a scoped statement everyone signs. Diagrams, decision records — including the options we rejected and why — and the one success metric we agree to be judged on. Nothing gets built until this is settled.
ArtifactArchitecture diagram, decision records, the success metric - 03
Design
Information design and UI, pressure-tested with your stakeholders before a line of production code. We sketch, wireframe, and prototype the flows that matter, so the expensive part — building — starts from something everyone has already seen and approved.
ArtifactWireframes & a clickable prototype - 04
Build
Trunk-based development, tests as we go, and a working demo every week. No big-bang reveal at the end — you watch it come together and steer as it does. We write code the next engineer can actually read, because someone always inherits it.
ArtifactShippable increments & a green test suite - 05
Validate
We measure against the success criteria set in step 02: eval suites for AI, performance budgets, security checks, and stakeholder sign-off. “It works on my machine” isn't validation — clearing the bar we agreed is.
ArtifactAn eval & test report, signed off - 06
Launch
A staged rollout with observability wired in from the first deploy: dashboards, alerts, runbooks, and a rollback that actually works. Plus a handover the team taking over genuinely wants — not a zip file and good luck.
ArtifactA live system, runbooks & a real handover - 07
Improve
The loop doesn't end at launch. Quarterly architecture reviews, performance and cost work, and the next wave of features — under a retainer or a fresh sprint. We stay close to what we ship, because that's where the next improvement is hiding.
ArtifactA review cadence & the next backlog
A loop, not a line.
Launch is a milestone, not the finish — the same seven steps carry into the next wave.
The cheap steps come first.
A change is cheapest on a napkin, slightly more on a wireframe, expensive in code, and brutal in production. So the loop front-loads the cheap places to be wrong: we discover, map, and design — and disagree, and redraw — before the costly part begins. By the time we build, the hard decisions are already made and agreed.
- Disagreements happen on paper, not in a pull request
- Every decision is written down — with the options we rejected
- The build starts from something already seen and approved
What each step actually looks like.
Three reasons it ships, not surprises.
No surprise reveals
A working demo every week means you're never shown a finished thing you didn't shape. Course corrections happen while they're cheap.
Every step has an artifact
A brief, a diagram, a decision record, a test report — so the story of why is always written down, for us and for whoever inherits it.
The loop never really ends
Launch is step six, not the last step. Improve feeds back into discover, and the system gets better instead of quietly rotting.
Run your project through the loop.
Tell us what you're trying to build. We'll walk you through how the BuildLoop would apply to it — the first artifacts you'd see, the success metric we'd agree, and what the first few weeks look like.