06-reference/research

service book rollup agent first conversion

2026-05-28·research-brief·source: deep-research
service-book-rollupagency-acquisitionagent-firstmicro-peservices-wedgerdco-strategy

Service-book micro-rollup as agent-first conversion: better than micro-SaaS on the math, worse than organic-services-wedge on the targeting filter

The question

Direct follow-up from [[research/2026-05-27-agent-first-saas-rollup-unit-economics]], whose key finding was that Bending-Spoons-style SaaS rollups make their money by deleting 50-75% of acquired payroll — and that lever vanishes at the zero-employee micro-SaaS sizes a solo deployer can actually afford. The natural next test: does a service-book variant (buy a tiny agency or done-for-you retainer book, then convert delivery agent-first) restore the labor-arbitrage lever at solo-founder deal sizes, since service books do have labor to convert? And does that make it the better micro-version of the agent-first rollup playbook for RDCO specifically?

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The honest answer is yes, the service-book variant is mathematically a better micro-version of the agent-first rollup than micro-SaaS — the labor-arbitrage lever is real at sub-$1M agency scale, the multiples are accessible (2.5-3.5x SDE), financing is solved (SBA 7(a) + seller note + earnout), and the conversion math is documented. The 2026-05-03 Tampa shortlist already proved the right-shape inventory exists publicly. The micro-SaaS path is strictly worse on the same dimension: no payroll to cut.

But "better than micro-SaaS" is not the same as "good for RDCO right now," and the targeting filter (per the targeting-system prioritization memory) is where this argument breaks. Apply the four layers honestly:

  1. Targeting. RDCO's anchored niche is the agent-deployer/FDE positioning for data teams. A service-book acquisition routes the founder's attention into running an acquired agency's existing book — which is almost certainly not a data-team services book (the publicly-listed sub-$1M targets are marketing agencies, home-health platforms, behavioral-health clinics). That's a niche pivot dressed up as a conversion play.
  2. Instrumentation. The conversion mechanic (Spine → Agents → Loop, encoding the workflow) requires deep knowledge of the workflow being converted. RDCO has that knowledge for its own services workflow. It does not have it for a Tampa financial-institution marketing agency, a Pasco home-health agency, or any other off-the-shelf vertical. The instrumentation has to be rebuilt per-vertical, and the founder learns it on the job at acquisition risk.
  3. Tools. Tools are not the constraint. Agentic delivery stacks are commodity.
  4. Feedback loop. Mammoth's ~6-month payback on organic conversion is the proof that the feedback loop works when the operator already runs the workflow. Acquisition lengthens the feedback loop (months of diligence, financing, transition, then months of conversion) and adds two failure modes (seller departure breaks the book, founder attention splits between RDCO and the acquired entity). The loop runs faster on conversion-of-owned-book than conversion-of-acquired-book.

The concrete RDCO play this argues for is NOT a service-book acquisition at this stage. It argues for:

The targeting filter call: service-book micro-rollup is a shiny object at RDCO's current state, not an anchored one. Better-than-micro-SaaS is not the right comparison; the right comparison is "service-book acquisition vs. organic services-wedge build," and organic wins on every targeting-filter dimension. The expected edge from acquiring vs. building from zero is modest, anchored only after the wedge proves out, and structurally degraded by the founder-attention split that every published playbook implicitly assumes the buyer doesn't have (because every published playbook assumes an institutional buyer with an M&A team and a separate operating team).

The single highest-leverage move suggested by this brief is the inverse of acquisition: document the agent-first conversion mechanic on RDCO's own services wedge as it is built, and treat that documentation as the credentialing artifact a future Sanity Check piece, lead-magnet, or sales conversation hangs on. That is the play with the strongest evidence base (Mammoth + Vacca + the four-tier model + the rollup-conversion benchmarks all triangulate to the same conclusion).

Open follow-ups

Sources

Vault:

Web: