WeLaunch journal / 2026

Notes from the execution layer.

What we're learning building AI-native operating companies inside industries that never got software that does the work.

Field notesNov 14, 2026

Why AI Pilots Fail and How to Get to Production

Why AI pilots fail and what AI pilot to production really takes: an owner, live data, integration and a scoreboard. See the full checklist.

Field notesNov 14, 2026

Palantir Alternatives for Midsize Companies

Palantir alternatives for midsize companies compared: build in house, integrators, agent platforms or applied AI partners. See which one fits.

Field notesNov 12, 2026

Cost to Deploy an AI Agent: What Drives the Price

What drives the cost to deploy an AI agent? See the real cost drivers, hidden costs, pricing models, and how to judge payback before you buy.

Field notesNov 12, 2026

AI Back Office: What It Runs and What It Replaces

An AI back office runs intake, scheduling, billing, payroll and reporting. See what agents take over and where the hidden admin cost goes.

Field notesNov 11, 2026

Forward Deployed Engineer: What It Is and Why AI Needs One

A forward deployed engineer gets AI working inside your business. Learn the role, the team around it, and how to judge a vendor's deployment team.

Field notesNov 11, 2026

AI Operating System for Business: What It Is and Does

An AI operating system for business runs the work, not just records it. See the layers, what it runs daily, and the signs you need one.

Field notes

A Compliance Deadline Is Only Useful If Something Is Watching It Two Months Out

Inspection businesses log cure windows into software but rarely automate the lookback, leaving expiring certifications and failed reinspection triggers unmonitored until a penalty or audit forces the issue.

Field notes

The Compliance Deadline Is Only Useful If Something Is Watching It Two Months Out

Inspection businesses track cure windows manually until they miss one. An orchestration layer watching deadlines across a fleet converts compliance from a calendar risk into an automated escalation sequence.

Field notes

How to Start a Service Business With Zero Employees and One Brain

The orchestration layer handles lead capture, booking, dispatch, invoicing, and collection. A founder contributes the domain judgment. The system compounds the rest.

Field notes

Windshield Time Is a Payroll Problem Before It Is a Fuel Problem

Routing software optimizes distance but ignores production value per technician per hour, leaving the costliest idle time buried in payroll rather than visible on a fuel or mileage report.

Field notes

What Active Subscription Means Depends on Who You Ask

Billing, CRM, and ops teams each maintain a separate definition of the same customer status. That vocabulary gap is where reconciliation fails and automation projects stall before they start.

Field notes

What One Recovered Churn Dollar Is Worth at a Twelve Times Exit Multiple

Back office orchestration priced against payroll rather than software spend produces a ten to one ROI case before touching margins, and each retained customer compounds that multiple at exit.

Field notes

Building a Trucking Fleet Business With an AI Back Office and No Staff

UpKeep logs the maintenance ticket. An AI back office routes the truck, triggers the invoice, and queues the next job before a dispatcher would have read the first alert.

Field notes

The Roll Up Thesis Only Works If the Margins Compound Across Companies Not Inside One

A PE buyer deploying capital across home services acquisitions needs one orchestration brain that redeploys to each portfolio company, not a bespoke build that restarts at every new platform.

Field notes

Windshield Time Is a Cost Your Routing Software Measures but Never Actually Reduces

Field service routing tools surface drive-time data but stop before acting on it. The gap between a mapped route and an optimized one lives in dispatch logic no software currently owns.

Field notes

Vertical AI Agents as a Portfolio Layer, Not a Point Solution

Capital-first roll-ups buy the business then scramble for the AI. One portable orchestration brain, already live, redeploys across every portfolio company from day one.

Field notes

One Orchestration Brain Redeployed Across Every Portfolio Company

Capital-first AI roll-ups buy the business and then scramble to build the system. WeLaunch built the brain first, proven in production, and walks it into the capital.

Field notes

Your Automation Stalled Because Two Systems Define Active Customer Differently

Before any orchestration layer can run, conflicting field definitions across billing, CRM, and dispatch must be resolved. Clean data alone does not fix a vocabulary problem baked into operations.

Field notes

Three People in the Same Company Cannot Agree on What Active Subscription Means

Before any automation project can run, conflicting internal definitions of core terms like active, lapsed, and cancelled create two data universes that reconciliation tools alone cannot collapse.

Field notes

The EBITDA Multiple Hidden Inside Your Cancel Reasons

Every unrecovered cancellation shrinks exit valuation by its churn dollar times the acquisition multiple. Back office orchestration priced against payroll, not software, changes that math directly.

Field notes

The Recovered Churn Dollar Is Worth More Than the New Sale at Exit

At a twelve times EBITDA multiple, one recovered annual contract adds twelve dollars of enterprise value. Back office orchestration priced against payroll, not software, makes that math routine.

Field notes

Eight Agents Run a Twenty Truck Facility Fleet Without a Dispatcher

Where UpKeep and Fiix log the work order and wait, a shared-state orchestration brain dispatches, routes compliance checks, and closes the shift automatically across every truck.

Field notes

Non-Payment Is the Largest Cancel Reason in Home Services and Almost Nobody Tracks It Correctly

Most field service businesses log cancellations by category but never separate involuntary churn from voluntary churn, leaving the most recoverable revenue bucket unmeasured and unworked.

Field notes

What a Home Services Private Equity Buyer Should Ask Before Trusting the Pitch

Two live deployments on one runtime answer diligence questions that a hundred slides of modelled projections cannot. The transfer test is whether the system runs without the founder in the room.

Field notes

Facility Management Software Records the Work Order. This System Closes It.

UpKeep and Fiix surface the ticket and wait for a human. Eight agents and one orchestration brain handle dispatch, compliance checks, and invoicing across a twenty-truck fleet without a coordinator in the loop.

Field notes

Field Service Automation That Dispatches, Invoices, and Collects Without Staff

Eight agents and one orchestration brain run a twenty-truck facility fleet end to end. No software dashboard to interpret. The system closes the loop itself.

Field notes

The Cure Window Every Inspection Business Tracks and Almost Never Automates

Compliance deadlines in facility and inspection businesses are logged manually and reviewed late. An agent watching a cure window sixty days out converts a liability into a scheduled job before a violation is written.

Field notes

Two Departments, Two Definitions of Active, One Broken Automation

Before any orchestration system can act on customer data, someone must settle what the word active means. Conflicting definitions create dual data universes that no reconciliation script resolves on its own.

Field notes

A Compliance Deadline Is Useless If Nothing Is Watching It Two Months Out

Inspection businesses track cure windows manually, which means deadlines surface after the violation, not before. This article maps how an automated compliance layer catches the window early and creates an auditable log without adding headcount.

Field notes

Two Live Deployments on One Runtime Beat a Hundred Slides of Projections

PE buyers evaluating AI back office automation should ask one question: does the system run at a new portfolio company without the selling founder in the room. Modelled projections cannot answer that. A shared runtime already in production can.

Field notes

How a Pest Control Company Starts With Zero Employees and One Brain

An AI holding company model built for founders: automated lead, book, dispatch, invoice, and winback across a 64,000-customer lifecycle before the first hire.

Field notes

A Pest Control Dunning Sequence and a Legal Intake Flow Are the Same Back Office Problem

Legal, medical, and field service businesses each collect customer data, schedule work, and chase payment on a recurring cycle, meaning one orchestration brain covers all three without vertical-specific rebuilds.

Field notes

What Facility Management Software Skips and Ten Legal Agents Do Not

Clio logs the intake. Ten on-premise agents handle it: billing triggers, draft routing, and conflict checks run without a paralegal queuing tasks in a dashboard.

Field notes

Two Departments Have Two Different Lists of Your Best Customers

Before any automation project can run, someone has to reconcile which definition of active, VIP, or at-risk is the operating truth. Most businesses never do. Agents cannot run on contested data.

Field notes

Non-Payment Is Your Biggest Cancel Reason and Your Dashboard Hides It

Most field service operators conflate non-payment churn with voluntary cancels, obscuring a recoverable revenue bucket that costs a fraction of new acquisition to reclaim through automated dunning sequences.

Field notes

Why Two Departments Define Active Subscription Differently and What It Costs You

When billing and operations run separate definitions of active, every automation project inherits the conflict. The vocabulary problem precedes the data problem and no home services software resolves it at the source.

Field notes

Pest Control Software Records the Route. One Brain Runs the Business.

Funds acquiring pest control operators inherit a software stack that logs work. A portable orchestration brain already running a 64,000-customer lifecycle redeploys across every acquisition instead.

Field notes

Non-Payment Is Not a Billing Problem, It Is Your Largest Churn Bucket

In recurring-revenue home services, involuntary churn from failed payments outpaces voluntary cancels. The fix is automated dunning sequenced before the anniversary cliff, not manual follow-up after.

Field notes

What Pest Control Software Cannot Do With 64,000 Customers in the System

Traditional pest control software stores the customer record. A connected orchestration brain runs the dunning, renewal, and winback cycle across all 64,000 automatically.

Field notes

One Orchestration Brain Across Every Portfolio Company

Field service automation stops at data. The Facility19 control tower runs eight agents across a twenty-truck fleet, live today, portable to the next acquisition tomorrow.

Field notes

The EBITDA Multiple Hidden Inside Your Cancel Reason Data

A recovered churn dollar at a twelve times exit multiple is worth twelve dollars, not one. Most operators never separate cancel reasons, so the compounding value of fixing non-payment stays invisible until diligence.

Field notes

What PE Buyers Should Ask Before Believing Any AI Vendor Pitch

The transfer test is simple: does the system run at a new portfolio company without the founder present. Two live deployments on one runtime answer that question. A hundred slides of modelled projections do not.

Field notes

Ten Agents Running Law Firm Automation Across Billing Intake and Drafting

Clio and its category store the matter. A ten-agent orchestration brain runs intake, drafts documents, and closes the billing loop without a paralegal touching the queue.

Field notes

The Roll Up Thesis Only Works If the Margins Compound Across Companies

Buying ten businesses and applying AI inside each one separately is not a compounding system. This article defines the transfer test: whether one orchestration brain redeploys across a portfolio without rebuilding from scratch at each acquisition.

Field notes

The Eleven-Month Anniversary Cliff Most Home Services Operators Never See Coming

Subscription churn spikes at eleven months before annual renewal, not at cancel. This article maps the specific trigger window, why standard dashboards miss it, and what automated intervention at that moment recovers in revenue.

Field notes

Two Live Deployments on One Runtime Beats a Hundred Slides of AI Roll-Up Projections

PE buyers evaluating AI roll-up theses should ask one question before the pitch deck closes: does the system run at a new portfolio company without the founder in the room, or does it require rebuilding every time.

Field notes

Windshield Time Is the Metric Your Fleet Management Report Buries

Drive time between jobs appears as a routing footnote, not a payroll and fuel line item. Eight agents running a twenty-truck fleet surface it as a dispatch decision, not a post-route report.

Field notes

What Active Subscription Means Depends on Who in Your Company You Ask

Before any orchestration system can act on customer data, it has to resolve conflicting internal definitions. Two departments running different counts of the same metric is a vocabulary problem, not a data problem.

Field notes

An AI Native Business in Home Services Needs No Ops Headcount to Launch

Housecall Pro and Jobber assume a dispatcher, a biller, and a scheduler exist. A founder who starts with an orchestration brain instead routes, invoices, and reactivates 64,000 customers without hiring any of them.

Field notes

The Four Kinds of Churn No Home Services Dashboard Separates

Involuntary, voluntary, never-served, and reactivation-gap churn each require a different fix. Bundling them into one cancellation number hides the highest-margin recovery opportunity.

Field notes

Legal Intake Automation Lets One Founder Run a Firm Without Staff

Ten custom agents handle intake, billing, and drafting from day one. A founder building a legal services business today does not hire an office. The brain runs it.

Field notes

What a Home Services CRM Tracks Versus What the System Actually Runs

Housecall Pro stores the 64,000-customer record. The orchestration layer books the follow-up, routes the tech, collects the invoice, and seeds the next job on the same street.

Field notes

Windshield Time Is the Dispatch Metric Your Routing Report Hides

Every routing tool shows a map. Few measure unproductive drive time per technician per day, the number that directly sets production value and determines whether a twenty-truck fleet runs at margin or at break-even.

Field notes

Field Service Automation That Dispatches, Invoices, and Closes the Loop

Most field service platforms surface a work order and wait. A single orchestration brain running eight agents handles dispatch, compliance, and collection across a twenty-truck fleet without a coordinator.

Field notes

AI Agents for Private Equity Acquiring Fire Protection Companies

Capital-first funds close the acquisition then build the operating layer. One brain already running dispatch, compliance, and invoicing redeploys the day the deal closes.

Field notes

Ten Legal Agents Handle Intake Billing and Drafting With Zero Staff

A founder entering legal services can run intake, billing, and document drafting through ten purpose-built agents on one orchestration brain, before hiring a single person.

Field notes

Two Departments Define Active Customer Differently and That Is Where Automation Breaks

Before a data problem, there is a vocabulary problem. This piece maps how conflicting definitions of active, lapsed, and churned across ops and billing create dual data universes that no clean dataset alone resolves.

Field notes

Vertical AI Agents Let One Founder Run a Pest Control Business

A dunning agent chases payment, a renewal agent books the next visit, a winback agent recovers churned customers. A founder with zero employees runs the full 64,000-customer lifecycle.

Field notes

The Back Office Cost You Are Paying in Payroll, Not Software

Orchestration priced against a coordinator's fully loaded salary changes the ROI math entirely. This article builds the ten-to-one case using facility management headcount, not software licensing fees, as the cost baseline.

Field notes

The One Question PE Buyers Should Ask Every AI Vendor Before the LOI

Does the system run at a new company without the founder present. This piece defines the transfer test, explains why modelled projections fail it, and shows what two live deployments on one runtime actually prove.

Field notes

What Field Service Automation Looks Like When the Brain Actually Runs

Eight agents, one brain, twenty trucks: the Facility19 control tower handles dispatch, compliance, and overtime without a coordinator, closing the loop software only records.

Field notes

What a PE Buyer Should Verify Before Trusting Any AI Vendor Pitch

Modelled projections and live deployments are not the same thing. Two systems running on one runtime across different companies is the only evidence that margins will compound at the portfolio level.

Field notes

The Cure Window Every Inspection Business Tracks Manually and No One Has Automated

Compliance deadlines in facility and inspection management are logged but not watched. This piece examines what an orchestration layer does differently when it owns the calendar two months ahead of the violation, not the day of.

Field notes

How to Start a Home Services Company With Zero Employees

Service business automation now handles the full loop: lead, book, dispatch, invoice, collect. A founder with one brain and no staff can run 64,000 customers.

Field notes

The EBITDA Multiple Hidden Inside Your Cancel Reason Codes

Cancel reasons are recorded as operational notes but almost never mapped to exit value. Each recovered churn dollar compounds at whatever multiple a buyer applies to trailing EBITDA, making retention math identical to acquisition math.

Field notes

What a Home Services Private Equity Buyer Should Ask Before Believing the AI Pitch

The transfer test is simple: does the system run at a new company without the founder present. Modelled projections cannot answer it. Two live deployments on one runtime can.

Field notes

Windshield Time Is the Metric Your Routing Software Collects but Never Acts On

Routing tools optimize the sequence before the truck rolls. They rarely measure idle time per technician after the day closes or feed that figure back into the next morning's dispatch logic.

Field notes

Non-Payment Is the Largest Cancel Reason and the Easiest One to Fix

Involuntary churn from failed billing typically outpaces voluntary cancels in recurring service businesses, yet most operators treat it as a finance problem rather than an automated recovery sequence.

Field notes

Non-Payment Is Your Largest Cancel Reason and the Easiest One to Fix

Most churn dashboards collapse voluntary and involuntary cancels into one number. Non-payment sits inside involuntary, fully recoverable, and almost never touched by traditional field service software.

Field notes

One Set of Vertical AI Agents Redeployed Across Every Portfolio Company

Capital-first roll-ups buy the business before the AI exists. A portable orchestration brain already running in production means a fund deploys the same agents into each new acquisition from day one.

Field notes

What a Pest Control Company and a Law Firm Have in Common Operationally

Both run intake, assign work, bill on completion, and manage a recurring client lifecycle. The back office structure is nearly identical, which means one orchestration brain handles both without rebuilding from scratch.

Field notes

Non-Payment Is Your Largest Cancel Reason and No Dashboard Names It That

Most churn reports label lost customers as voluntary cancels. The ones who stopped paying before canceling represent a fixable revenue leak that sits between billing and operations, invisible to standard dashboards.

Field notes

Fire Protection Software Records the Inspection. The Orchestration Brain Runs What Comes Next.

A PE firm acquiring fire protection companies gets one redeployable brain that handles dispatch, compliance follow-through, and invoicing, the layer every field service platform stops short of.

Field notes

Windshield Time Is the Metric Routing Software Shows You but Never Fixes

Field service routing tools map the drive but do not adjust the schedule when a job runs long. Production value per technician stays buried until an orchestration layer acts on the gap in real time.

Field notes

Two Departments, Two Definitions of Active, One Data Universe That Never Reconciles

Before any automation project can run, operators must resolve what counts as an active customer. Conflicting definitions across billing, dispatch, and CRM create a reconciliation problem that clean data alone cannot close.

Field notes

Field Service Automation That Runs Dispatch Without a Dispatcher

Eight agents and one orchestration brain run a twenty-truck facility fleet: dispatch, compliance, overtime. The work completes. No coordinator required.

Field notes

Field Service Automation That Runs Dispatch, Not Just Records It

Eight agents and one brain manage a twenty-truck facility fleet: dispatch, compliance, and overtime routing handled without a coordinator watching a screen.

Field notes

A Founder Can Launch a Fleet Operation With Vertical AI Agents and Zero Employees

Vertical agents handling dispatch, compliance, and overtime routing mean a first-time founder can operate a fleet business from day one on one brain, with no operations staff behind them.

Field notes

What the AI Roll Up Thesis Requires That No Pitch Deck Shows

The roll up thesis compounds only if the operating system transfers to each new acquisition without rebuilding. Two live deployments on one runtime answer that question. A hundred projected slides do not.

Field notes

What a Medical Billing Back Office and a Pest Control Company Share

Both run on recurring schedules, compliance checkpoints, and collection cycles. The back office problem is structurally identical. An orchestration brain built for one vertical redeploys across the other without rebuilding the core logic.

Field notes

The AI Roll Up Model Has the Capital and Needs the Brain

Capital-first roll ups buy the business, then build the AI. WeLaunch inverts that: one live orchestration brain, redeployed across every portfolio company from day one.

Field notes

Clean Data Does Not Fix a Vocabulary Problem

When two systems disagree on what counts as an active customer, the issue precedes the data layer. Conflicting definitions inside one business produce two parallel operating realities that reconciliation software cannot resolve.

Field notes

Why Non-Payment Is Your Largest Churn Bucket in Home Services

Involuntary churn from failed billing outpaces voluntary cancels in most home service businesses, yet most dashboards never separate the two, burying the cheapest recovery lever.