Pillarix has gone deep on construction PM. LeedAB has gone wide on local-first SMB ops. The licensing thesis: your wedge plus our substrate is something neither of us ships alone. Three concrete shapes for how it could work.
pillarix · vertical
Construction PM, agentic.
Construction project management workflows
60% reduction in contractor / consulting fees
3× PM productivity · 90%+ accuracy
Direct relationship with construction firms
tier · vertical · depth · construction
trade lane
leedab · horizontal
SMB ops, local-first.
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 · breadth · horizontal
construction depth ←——— same customer, different surface area ———→ horizontal SMB ops, local-first
Three license shapes worth pricing.
All three preserve our local-first sovereignty pitch. None require us to give up source. None require Pillarix to rebuild what they've already built.
shape · 01
Substrate license.
Pillarix builds on top of our per-customer brain and manifest framework. Your construction agents are the value-add; ours is the runtime they sit in. Customer keeps one local brain — your agents and ours both read from it.
pillarix construction agents → run on ← leedab brain + manifest = one local vault per customer
pillarix
Skip the runtime build. Your team focuses on construction depth, not multi-tenant infrastructure or per-customer state.
leedab
Validates the substrate. Per-active-vault license fee compounds as your customer base grows. Construction is a use-case proof of "vertical-on-horizontal."
shape · 02
Co-sell bundle.
Your construction agents + our horizontal ops layer (sales, finance, HR, comms, delivery) sold to construction firms as one stack, one onboarding, one contract. Two SKUs but a single product experience for the customer.
ARPU lift. Existing customers expand into ops surface they currently bridge with spreadsheets and Xero exports.
leedab
Distribution. Pre-qualified construction-firm pipeline without our team learning the vertical sales motion.
shape · 03
OEM / co-brand.
Pillarix sells a LeedAB-powered offering under your brand to your customers. Co-brand "Powered by LeedAB" in product UI; you own the commercial relationship; we provide the managed runtime. Per-tenant license fee + tier-2/3 support SLA from us.
pillarix · brand + customer relationship leedab · managed runtime + tier-2/3 support = one offering, two parties
pillarix
Speed. Ship a broader product to your customers without expanding scope of your engineering team.
leedab
Predictable revenue. Per-active-vault fee scales with adoption; we keep the codebase, you keep the brand. Co-brand keeps our category-build alive.
commercial · prefer
Per-active-vault license + minimum.
Aligns with our usage model. Predictable for both sides. Floors our revenue and caps your downside if adoption is slow.
commercial · consider
Rev-share on attributed customers.
If you bring volume, we'll share. Gross-revenue %, not net. Defined attribution rules so neither side is guessing at quarter-end.
commercial · avoid
Source transfer · flat one-time fee.
Source-code transfer is off the table — managed runtime only. Flat one-time fees cap our upside and misalign incentives over a multi-year roadmap.
before we paper anything
What we'd want to nail down.
What's the gap your customers ask for that you can't ship today?So we can match the shape (substrate vs bundle vs OEM) to the actual need, not the hypothetical one.
Deployment posture — cloud, customer-VPC, on-prem? Our local-first pitch is non-negotiable; customer brains stay on customer machines.Confirms whether the licensing shape preserves both sides' core stance.
Exclusivity scope. Vertical-exclusive in construction is fine. Cross-vertical exclusivity isn't.We need other verticals open for our roadmap.
Support model. Tier-1 sits with you (you own the customer relationship); tier-2/3 sits with us on a defined SLA.Without this, our support load explodes the day you sign a customer.
Brand presence. Co-brand "Powered by LeedAB" in product UI and customer contracts.Full white-label removes our category-build; co-brand keeps both narratives intact.