The Ennyn Thesis · v1

The two stacks — and the seams between them.

Every SMB runs on two parallel software worlds that don't talk to each other. The system-of-record vendors own the inside of each box and are racing to ship their own agents there. The territory between the boxes is the only place nobody owns — and it's where the company actually runs.

The operator runs on two disconnected worlds.

Everything an SMB touches falls into one of two stacks. The system-of-record vendors own the inside of each box. The lightning bolt between them is the only territory nobody owns.

Stack A · Operations

The unit of work AppFolio · Buildium · Jobber · ServiceTitan · Mindbody
Inbound leads & scheduling Calendly · Typeform · Yelp · Zillow
Service delivery & dispatch Housecall Pro · Vagaro · Square Appointments
Customer portals & billing Stripe · Square · Recurly
Reporting & analytics Google Sheets · QuickBooks reports · Metabase

⚡ The orchestration seam

Stack B · People & business

Payroll, HR, benefits Gusto · ADP · OnPay
Accounting QuickBooks · Xero
Email and docs Google · Microsoft 365
Hiring & ATS Indeed · LinkedIn
Marketing & brand LinkedIn · Instagram · Mailchimp
Lead generation Google Ads · Meta Ads · listing sites
Training and supervision ⚠ mostly none

Stack A resolves into a few repeating revenue loops.

The operations side isn't flat work — it concentrates onto a handful of repeating loops, each with a hard dollar value. This is where the operator's money and time both live. Three loops recur across nearly every SMB — acquisition, satisfaction, and the long middle of steady-state delivery.

Loop 01 · Acquisition

Win the customer.

A prospect raises a hand — paid ad, search, listing site, referral. The clock is opportunity lost per day. Metric: speed-to-close.

$ = days of revenue lost × daily margin

Loop 02 · Satisfaction

Earn the next engagement.

The relationship is the asset. Every save, every quietly-resolved issue, every NPS-9 conversation compounds. Highest-ROI loop in most SMBs. Metric: retention rate.

$ = re-acquisition cost saved + lifetime extended

Loop 03 · Steady state

Run the day-to-day.

The long middle. High volume, low judgment per event — but constant. Metric: cost-to-serve.

$ = labor hours per customer per month

The seams — where the handoffs break.

Each seam is a place where work has to jump between Stack A and Stack B (or between two tools in the same stack) and today gets done by a human copying data, remembering a step, or dropping it. This is the agentic target list.

New hire → fully provisioned operator Highest value

Stack B hired in Gusto ⚡ Stack A account, role, access, training plan

Broken today: someone manually creates the new rep in the ops system, sets permissions, assigns territory, emails credentials. Days of lag; steps get missed.

Operator performance → coaching Whitespace

Stack A outcomes (speed-to-close, conversion) ⚡ Stack B supervision (the loop with no incumbent)

Broken today: nobody connects how fast or well each operator works the acquisition loop to any coaching. Performance lives in the ops system; "management" lives nowhere.

Work order → vendor pay → books High value

Stack A work order completed ⚡ Stack B QuickBooks vendor bill, allocation, reconciliation

Broken today: work order closes in the ops system; someone re-keys the invoice into QuickBooks, allocates it to the right property/owner, and reconciles. Double entry, lag, errors.

Field hours → payroll reconciliation Medium

Stack A hours logged on jobs ⚡ Stack B Gusto payroll & PTO

Broken today: hourly crews log time against jobs in one place and get paid from another; reconciling and PTO is manual.

Documents → e-signature → record In-stack glue

Stack A document generated ⚡ DocuSign ⚡ Stack A filed + status updated

Broken today: the e-signature round-trip and refiling the executed doc + flipping status is manual chasing.

Customer-acquisition → onboarding Growth loop

Stack B marketing campaign ⚡ Stack A new customer record + initial setup

Broken today: winning a new customer means manually creating the record, configuring access, setting up reporting — the slowest part of growth.

These six are the canonical seam pattern across SMB verticals. The same shape extends naturally to every other Stack B surface:

Instagram tenant DMs landing as tour requests in the ops platform
LinkedIn B2B outreach feeding the new-owner pipeline with full attribution
Listing-site and Google Ads leads routed into the ops stack — spend tied directly to revenue outcomes
Brand-building content scheduled across channels, scored against the metrics that justify the spend

And one more: compliance and governance are seams too — sometimes the most expensive ones. Every Stack A ↔ Stack B handoff is also a governance event. Who authorized the charge? Who provisioned the access? Who signed off on the customer decision? Today the audit trail for "who did what, with what authority" is scattered across four vendors' logs — when those logs exist at all.

Single audit trail for cross-stack handoffs, not four scattered ones
Access provisioning on hire; clean revocation on departure
Approval signoffs for money-out actions above threshold, kept in one record
Industry-specific carve-outs (Fair Housing, HIPAA, GLBA, licensing) wired into the autonomy bands — see Section 04
Contractor classification and insurance verification tracked across vendors

The seams are universal — the carve-outs are local. Fair Housing in property management. HIPAA in healthcare. GLBA in finance. Food-safety and wage-and-hour across hospitality. OSHA in trades. See your vertical →

Different surfaces. Different stakes. Same seams.

Where to draw the human-in-the-loop line.

"Capable of anything" is a liability until constrained. Every seam step gets sorted into one of three columns. Early pilots keep the leash short — autonomy is earned, not granted.

● Autonomous

Retrieval, logging, drafting, reconciliation surfacing

Pull metrics & build digests
Detect expirations and triggers
Reconcile hours vs. pay, surface mismatches
Chase unsigned docs on cadence
Draft vendor bills coded to property

◐ Draft → approve

Anything client- or money-facing

Renewal offers & pricing
Coaching nudges to operators
Payroll run before submit
Owner kickoff sequences
Vendor payments over threshold

○ Human only

Legal exposure or irreversible

Customer/applicant decisions under protected-class logic (Fair Housing, ADA, fair hiring)
HIPAA / PHI disclosure and equivalents
Termination, eviction, or discipline decisions
Granting system access
Money-out actions above approval threshold
Final hire decisions

The strategic shape.

Inside each box, the system-of-record vendors are already shipping agents. Realm-X handles the PM silo. ServiceTitan IQ handles the trades silo. Toast, Mindbody, and every other vertical SoR are shipping their own in-silo AI. The all-in-one HR platforms automate the people stack. A frontal assault on either box loses.

The defensible position is the between — the cross-stack seams where each vendor sees only its own silo and none is incentivized to build the bridge. Plug into their marketplaces (AppFolio Stack, ServiceTitan Marketplace, Toast Marketplace — every SoR has a developer surface) as connective tissue. Don't replace the system of record.

That's Ennyn.

See it in your business.

Same orchestration shape, different tools and language. Pick a vertical and read the concrete shape.

Or see all five at a glance →