The four-phase loop, explained from the inside

Every Leandrive engagement runs the same four-phase loop. Diagnose, design, implement, optimize. The order matters. Skipping a phase or compressing two into one is how consultancies deliver work the client doesn’t trust and can’t operate.

This is what each phase looks like from the inside.

Phase 1 · Diagnose

Duration: one to two weeks. Output: an audit document and a prioritized recommendation list.

The diagnose phase is where we earn the right to design anything. We map your current operations end-to-end. Workflows. Tools. Handoffs. Edge cases. The work that lives in nobody’s job description but happens every week.

Most discovery engagements stop at the surface. “What tools do you use?” “What’s slow?” That’s not enough. The real question is: where does information actually flow, and where does it leak? We pull the thread on every workflow until we see the seams.

The output is two documents. An audit map showing your AS-IS state, including the messy bits everyone usually leaves out. And a prioritized list of recommendations scored by effort and impact, so you know what’s worth fixing first.

If we end the engagement here, you walk away with a deliverable you can execute on your own or with another firm. That’s the point of paid discovery. Both sides have something at stake from day one.

Phase 2 · Design

Duration: about a week. Output: an architecture document and phased pricing.

Before any code or automation, we design the system architecture. What data flows where. What triggers what. What humans still own and what becomes systematic. Where the failure modes are and how the system handles them.

This is the unsexy phase that makes or breaks the engagement. Designs that are too clever fail in production. Designs that are too simple don’t survive contact with edge cases. The right design is the one that handles your real workflows, including the irregular ones, and degrades gracefully when something unexpected happens.

The phased pricing follows the architecture, not the other way around. We don’t pre-commit to a price and then design backward to fit it. The design tells us how much work is real, and the price reflects that. You approve the design before we build.

Phase 3 · Implement

Duration: four to sixteen weeks, phased. Output: working systems running in your tools.

We build in your tools. Your Airtable. Your Make organization. Your CRM. Your accounts. Nothing is hostage to us. The systems we ship are owned and operated by you from day one.

Phase 0 ships in two to three weeks to prove value. We pick the highest-impact, lowest-risk work and ship it fast. The point of Phase 0 is for you to see the work before committing to anything bigger. Most engagements then proceed to Phase 1 (core systems), Phase 2 (optimization), and Phase 3 (handoff). Each has its own go/no-go gate.

Every deliverable ships with two artifacts. The system itself, running in production. And a single-file HTML deliverable explaining what was built, how it works, what to do if it breaks, and how to extend it. The work is yours. The understanding is too.

Phase 4 · Optimize

Duration: ongoing, monthly retainer. Output: systems that compound rather than decay.

After launch, we transition to a monthly retainer or hand off cleanly. Optimize is the phase where the architecture pays back. New edge cases get absorbed into the existing structure. Performance gets tuned. Documentation stays current. The system gets better, not worse, over time.

This is the phase most consultancies skip. They build, hand off, and disappear. Six months later the system is full of duct tape patches because nobody owned the evolution. We stay or we hand off cleanly. Never half-cleanly.

Why this order

Every shortcut in this loop fails the same way.

Skip diagnose and you build the wrong thing fast.

Skip design and you build the right thing wrong.

Skip implement and you have a beautiful blueprint nobody operates.

Skip optimize and the system degrades to where it was before you started.

The four phases aren’t a marketing structure. They’re a forcing function for the kind of work that holds.