For MSP partners · binary1702.com/msp

The call you make when the client's non-IT stack is a mess.

I'm not an MSP. I don't sell endpoint security, M365 administration, SOC services, or compliance attestation. I sell the layer underneath — the business operations stack your clients run their actual business on. When a client's founder is the integration glue and audit prep is a fire drill, that's me.

01 — The diagnostic

One product. One price. One week. That's the whole engagement you're sending me into.

The diagnostic is the only thing I'm asking your shop to refer. It's a self-contained, one-week engagement that gives the client a complete operational map of their business — every tool, every integration, every place a human is serving as glue — plus a written Sprint 1 roadmap prioritized by founder time bought back.

What happens after the diagnostic is the client's decision. They can hire me to ship Sprint 1, take the architecture map and execute themselves, shop the roadmap elsewhere, or shelve it. None of that changes our arrangement or requires anything from you.

This is deliberately the simplest possible referral. One product to understand, one price to quote, one deliverable to put your name next to. Co-sell, white-label, or productized versions are options for later — once we've both seen the first one through.

Phase 1 — Diagnostic
Map the spine.
$2,000 · 1 week
  • End-to-end map of every tool, every integration, every manual handoff.
  • Written report identifying the highest-ROI automation targets and the bottlenecks costing the founder the most hours per week.
  • Sprint 1 roadmap, prioritized by founder time bought back — not by what's technically interesting.
  • Immediate bleeders — broken invites, dead links, sync failures — fixed in the same week.
02 — The flow

Three steps. One week. The client walks away with a map.

01 — You see the gap
A client whose non-IT operations are a mess.

Audit prep is a fire drill. The founder is the bottleneck. Ten-plus tools, none of them talking. None of it is in your SOW — and there's nowhere clean to send them.

02 — You make the call
I run the diagnostic at $2,000.

One week. End-to-end systems map. Written diagnostic report with prioritized recommendations. The immediate bleeders fixed in the same week.

03 — They get the map
The client owns the architecture and the roadmap.

What they do next is their decision. The deliverable stands on its own. Your shop earned the credit for sending them — and the client is now defended on a layer you don't compete on.

03 — Where this fits

I'm an answer to a specific question. Not a replacement for what you do.

Where this fits

MSPs and MSSPs serving compliance-heavy verticals — manufacturing, healthcare, legal, defense, financial services. The operational evidence side of compliance, not the controls themselves. Founder-led $2–5M service businesses where one person is the integration glue across a decade-plus of tool sprawl.

CMMCSOC 2HIPAAFTC SafeguardsNISTISO 27001

Where this doesn't fit

I don't replace anything your MSP does. I don't touch endpoints, identity, networking, RMM, SOC operations, or compliance attestation. If a client needs a vCISO, that's still you. If they need someone to attest controls, that's still you. The diagnostic answers a different question — the one your clients are asking that you don't currently have a clean referral for.

04 — What the deliverable looks like

Here's a live engagement, mid-flight.

Week 1 of 5 · Sprint 1 in flight

13 systems. One founder. 25 years of growth, no architectural strategy. A $2-5M service business with a 50,000+ contractor database, 16,000+ community members, and enterprise-level customer relationships. Solo founder. Everything ran on her calendar and her memory.

13 tools. None of them talked cleanly. Audit prep was a 2-day fire drill every quarter. A 45-day drip sequence stranded warm leads the moment it ended. The founder personally synced data every morning because nothing else did.

If you're an MSP, you've probably onboarded this client. Your team has fixed their endpoints, their M365, their backup, maybe their SOC 2 controls — and watched the founder still drown because everything outside your scope was held together with Zapier and willpower. This is the case for the call.

The numbers on the right are what the diagnostic identified and what Sprint 1 is targeting. The diagnostic alone gets the client a map; whether they engage further is up to them.

Full case study at binary1702.com/#case, updated weekly with actuals as Sprint 1 ships.

Manual sync work
~10 hrs/wk to near zero
Audit prep
2-day fire drill to routine
Founder time back
~1.5 days/week
13 disconnected systems
one operational spine
05 — Commercial model

Simplest possible referral. Nothing else required of you.

Referral fee on the diagnostic. Flat amount per closed diagnostic, paid on engagement. That's the entire economic relationship for v1.

I want it kept that simple on purpose. Co-sell mechanics, margin splits, and white-labeled productization are real options later — but they cost both of us time to negotiate and set up, and the first referral doesn't need any of it. Let's get one client through the diagnostic together. If the experience earns it, we'll talk about what v2 of the partnership looks like.

If Phase 2 (Sprint 1) happens, that's a conversation between me and the client. It doesn't change our arrangement and requires nothing else from your shop.

Referral model
You send the intro. I run the diagnostic.
  • Fixed referral fee on each diagnostic that closes.
  • No co-sell obligation. No margin split to administer. No SOW from your side.
  • Anything that happens after the diagnostic — Sprint 1, ongoing engagement — sits between me and the client, on its own terms.
06 — About

Ben Basuni · Operating Partner, Binary 1702

I run fixed-scope engagements because the consulting industry has trained founders to expect open-ended retainers, scope creep, and PowerPoint decks they can't act on. None of that is what a $2–5M service business needs. What it needs is a person who maps the actual stack, ships the priorities, and hands the architecture back to the founder.

Binary 1702 is a Wyoming LLC. The engagement model is fixed. The deliverables are real. The founder owns the work at the end. That's the entire pitch — and that's what makes the diagnostic clean for an MSP to refer: no scope ambiguity, no retainer for the client to dread, no risk of me drifting into territory that's actually yours.

Run an MSP? Recognize a client in any of this?

Email is the fastest. I'll walk you through what the diagnostic deliverable looks like, you tell me whether the referral model works for your shop, and we'll know within a short call whether this is real.