Rome is solving execution drift for enterprise supply chains. LeedAB is solving operational drift for SMBs, with a local-first per-customer brain. The interesting question isn't whether we overlap — it's where we trade.
rome · enterprise
Plans hold; execution drifts.
Multi-stakeholder supply chains
Live model over SAP / APS / ERP / logistics
Cloud, deep integration, six-figure motions
Suppliers, factories, carriers, customers
tier · enterprise · motion · top-down
trade lane
leedab · smb
Ops drift; the brain is the fix.
31-agent local-first ops system
Per-customer Obsidian vault as substrate
Manifest model + SKILL.md overrides
Sales, delivery, finance, HR, ops, comms
tier · smb · motion · product-led + founder-led
enterprise SC depth ←——— different shape, same execution thesis ———→ SMB ops breadth, local-first
Three shapes worth a real conversation.
All three assume each side keeps its core moat. None of them require either of us to chase the other's customer.
shape · 01
Referral lanes, both directions.
The cleanest version. SMBs that outgrow LeedAB and hit real SC complexity get warm-handed to Rome. Enterprises Rome qualifies out as too small or too lightweight on infrastructure get warm-handed to us.
smb outgrows local · → · rome enterprise rome too-small lead · → · leedab smb
rome
Captures upside. Customers you couldn't have signed at SMB scale arrive pre-qualified, two years later, at the right tier.
leedab
Removes the ceiling. Our customers don't churn the day they outgrow us — they graduate to a known partner.
shape · 02
Rome SC depth as a LeedAB skill pack.
A subset of Rome's execution agents — the ones that translate to a 50-person ops team — packaged as a skill pack inside the LeedAB manifest. Customer keeps their local brain. Rome agents call out to your live model when SC depth is needed. Revenue share on activation.
Reach without rebuild. Your tech in front of the SMB segment without a separate product line, separate motion, separate ICP.
leedab
Depth without dilution. Customers who need SC sophistication get it without us building outside our circle of competence.
shape · 03
Joint mid-market GTM.
There's a band — call it 100 to 500-person ops orgs — that's too big for SMB tooling and too small for full enterprise SC platforms. Pre-pilot conversation: what would a joint package look like — Rome's live model + LeedAB's per-customer brain — sold as one offering with one onboarding?
rome · live SC model leedab · per-customer brain + non-SC ops = one offering · one onboarding · one contract
rome
New tier. A band of buyers your enterprise motion currently can't justify the CAC for.
leedab
New tier. A band of buyers our SMB motion currently can't justify the depth for.
before any of this
What we'd want to learn first.
What prompted the outreach — was there something specific you saw, or is this a wider sweep across the agent ops space?Helps us calibrate which shape, if any, is the actual conversation.
What's the deployment posture customers are asking you for — cloud-only, customer-VPC, on-prem?Local-first is our category. If your customers are pulling in that direction, that's probably the thread.
Where does your motion struggle — top of funnel, mid-market band, post-sale expansion?Each maps to a different shape above; we'd rather solve the real one.
What does "partnership" mean for you in the next two quarters — referrals, technical, GTM, capital, all four?So we can match the seriousness of our reply to the seriousness of the ask.