Agency Engagement Playbook

The phases that matter

Phase 0: Scope brief (1 to 2 weeks)

Before talking to agencies, write a one-page scope brief: comp plan structure with specific rules, distributor count target, integrations needed (CRM, analytics, marketing automation), hard launch date, budget cap. The brief should be specific enough that an agency can quote against it without follow-up calls. Vague briefs produce padded quotes; specific briefs produce competitive quotes.

Phase 1: RFP to three agencies (2 weeks)

Send the brief to three agencies in your shortlist. Score each on five axes: domain experience (have they shipped MLMs at your scale?), honest SaaS take (when does SaaS beat custom in their view?), pricing model (fixed-price beats T&M for full builds), named team members (the senior architect on your account, not just the sales team), and references. The top score advances to Phase 2; the others get a polite decline.

Phase 2: Discovery and technical design (2 to 4 weeks)

Fixed-fee discovery contract, typically $5K to $15K. Output: a technical design document plus a revised fixed-fee proposal for the build. If discovery exposes scope you missed in the brief (which it usually does), this is the cheapest place to discover it. Phase 2 also reveals whether the agency's senior architect is actually engaged with your project or just pitching during sales.

Phase 3: Build (3 to 6 months)

Fixed-fee, milestone-billed. Weekly demos. Change requests are formal: written scope, written estimate, signed before work begins. Resist scope creep mid-build; the cost of a redirect mid-Phase-3 is roughly 3x the same scope changed during Phase 2.

Phase 4: Warranty (60 days post-launch)

Free bug-fix window. Critical for finding edge cases the test suite missed. Distributor-facing edge cases tend to surface in week 2 to 4 post-launch as real-world usage patterns hit the platform.

What can go wrong

Three patterns surface repeatedly. Scope creep without process: the burn rate doubles, the deadline slips, the relationship with the agency degrades. Mitigation is the formal change-request process from Phase 3. Agency staffing changes mid-build: the senior architect moves to another project, junior developers take over, quality dives. Mitigation is named team members in the contract with notice clauses for changes. Comp plan rule discovered late: an edge case nobody documented surfaces during testing, adding 4 to 8 weeks to the timeline. Mitigation is investing in Phase 2 discovery to surface edge cases before commitment.

What works

Weekly demos consistently green. Change requests rare and well-documented. Launch within 10% of original timeline. Warranty period: under 5 critical bugs surfaced in 60 days. This profile is achievable but requires discipline on both sides. The buyer's job is the formal scope and change-request process. The agency's job is honest weekly status (including bad news early) and senior-architect engagement throughout.

Cost expectation

Standard MLM platform builds run $80K to $300K all-in for SMB scope. Custom plan rules, integration work, white-label depth, multi-region capability all push toward the high end of that range. Below $80K, the agency is either junior or the scope is too narrow to be a real platform build (in which case contractor or SaaS is probably the right answer instead).

BPract AI's typical engagement runs $80K to $250K depending on scope and timeline. Other reputable MLM-specific agencies cluster in similar ranges. Agencies quoting under $50K for full platform builds are usually offshore generalists who've never shipped MLM-specific code; the discount disappears in the warranty period when the team can't fix the bugs they shipped.