A service enabled path can produce software leverage.
Human implementation is useful when each exception creates a reusable rule, mapping, test, schema extension, approval control, or interface for later clients.
Founder decision hub · Research updated July 10, 2026
Run one paid, standardized experiment with three independent STR managers. Scale only if recurring demand, delivery economics, and retention clear the gates.
Next founder decision
The external launch should test one bounded outcome, one supported stack, honest pricing, and recurring payment. It is not permission to build the full platform.
Do not add features to rescue the thesis. Reposition as a high margin project service, seek a PMS partnership or acquisition path, or stop external commercialization.
Research verdict
Human implementation is useful when each exception creates a reusable rule, mapping, test, schema extension, approval control, or interface for later clients.
No external case establishes that professional STR managers will pay monthly for canonical property facts, freshness monitoring, and governed exports.
Manual exception to reusable rule. Athenahealth is the strongest causal example.
Canonical master data plus stewardship. Veeva is the clearest target state.
Source traces to reusable objects. Celonis is the strongest technical architecture analogue.
One core with bounded configuration. ServiceTitan and Guidewire reject a separate product for every customer.
Expansion along the same data graph. AppFolio shows how a property record can support adjacent workflows.
Healthcare claims, payroll, insurance, and regulated life sciences have compulsory budgets and direct financial consequences.
Toast, AppFolio, and Shopify can recover expensive onboarding through payments or transaction revenue. The first STR offer cannot.
Palantir can lose heavily during acquisition because contract size, urgency, and capital are radically larger.
Client portability is a product promise. Retention must come from monitoring, provenance, approvals, receipts, and embedded workflow.
Failure cases identify controls, not one universal cause. External shocks mattered, but each company already carried a model that required continuing capital or near perfect execution.
First commercial offer
Create one approved property fact base, publish it to two verified destinations, monitor changes, preserve receipts, and give the client a complete exit export.
A repeated workflow earns engineering investment after it appears in at least three clients or 25 times, has stable inputs and failure states, consumes meaningful time or creates material risk, and will make later clients faster or safer to serve.
Interactive economics
Original 50 property Foundation monthly price: $750 + (50 × $12) = $1,350.
Direct recurring cost assumption: (14 hours × $38) + $180 infrastructure = $712.
Actual direct margin: ($1,350 − $712) ÷ $1,350 = 47.3%, not 73.6%.
The earlier 73.6% claim substituted $2,700 of monthly revenue that did not exist in the package.
Evidence gates
95% target coverage, provenance on every published fact, conflict handling, fail closed local workload, complete export, receipts, and every minute timed. This does not prove willingness to pay.
Three paid setups, at least two continue paying, common taxonomy covers at least 80%, routine review stays below 15 minutes per property monthly, and setup labor declines.
At least 60% fully loaded recurring margin, positive setup contribution, configuration driven onboarding, and Taylor is no longer required for routine delivery.
At least 70% fully loaded recurring margin, two renewal decisions, an implementer owns 80% of delivery, review stays below five minutes per property monthly, and no client has a core code fork.
Repeatable acquisition, latest cohort above 75% recurring margin, two retained workflows per customer, and the first same foundation expansion requested by three clients and purchased by at least two.
Comparable companies
Normalized master data, human stewardship, paid implementation, high subscription margin, and visible service economics map well. Regulated enterprise budgets do not.
Staff resolved claim exceptions, then encoded shared payer rules. Claims are compulsory, frequent, and tied directly to cash, unlike property fact governance.
Raw source traces become reusable transformations and canonical objects. Private economics do not prove service leverage.
A standard vertical core and strong retention preceded major institutional funding. Its payment and lifetime value engines can absorb onboarding losses that STR cannot.
A property record can support broad expansion. AppFolio also proves that an incumbent PMS can bundle adjacent parts of this wedge.
Menu mapping, setup, and training helped win the daily workflow. Hardware and services remain deeply loss making because subscriptions and payments repay the subsidy. We have no equivalent rail.
Kill criteria
Gated expansion
Canonical facts, provenance, approvals, portability, monitoring, versioned outputs, and receipts.
Additional website, listing, guidebook, or media workflows only after three requests and two signed orders.
Documented client API, limited partner certification, and one connector at a time after real integration demand.
These introduce new workflows, controls, liability, and labor. They are not scheduled products.
Require two independent clients, accepted pricing, and preserved 70% fully loaded recurring margin.
Long term product constitution
The intended system of record is reusable property knowledge. PMS and channel tools remain systems of transaction. Portability is a design goal to validate, not a guaranteed migration outcome.
Clients can view and export facts, observations, provenance, approvals, versions, mappings, receipts, and deletion state in documented formats from day one.
Build stable internal contracts now. Offer documented client interfaces only after the resources are stable and two clients or partners have a real integration use. Do not freeze an unproven public API.
Every first party or client built agent receives a tenant identity, narrow scopes, policy checks, approval rules, rate limits, kill switches, and durable action receipts. No direct database access.
Preserve canonical facts, history, mappings, and approvals so a move from Streamline to Guesty requires controlled mapping, reconciliation, testing, and cutover while reducing repeated data reconstruction.
Roam Free will prove one fail closed local workload. For that verified workload, protected data cannot reach an external model. Commercial client infrastructure remains deferred until paid demand proves it.
Internal Roam Free proof
Research library
Every report has a mobile table of contents, a founder takeaway, preserved inline citations, and an extracted source index.
Success mechanisms, failure patterns, economics, first ten operating model, stage gates, and red team critique.
Problem evidence, client hypotheses, pricing, SWOT, competition, GTM, and financial assumptions.
Existing products, implementation accelerators, client security, certifications, and safety requirements.
Read report →How trusted operating partners expanded around the client's core business without taking it over.
Read report →Client owned data, provenance, portability, extension contracts, agent controls, and private compute.
Read principles →Search filings, regulator records, product documentation, standards, company histories, and reporting across every report.
Explore sources →