PMS, pricing, operations, guest messaging, finance, CRM, documents, spreadsheets, media, email, Slack, and future tools.
The company thesis
Sit in the middle. Make every system more useful.
There will not be one permanent software winner in property management. The stack changes too quickly. The durable position is the independent data and acceleration layer that lets clients adopt the best tools without rebuilding their business every time.
Our positionTrusted operating data
Identity, history, evidence, decisions, permissions, APIs, agents, exports, and beautiful information surfaces.
Owner intelligence, onboarding, content, websites, social, CRM, compliance administration, bookkeeping support, and capabilities not invented yet.
NeutralIntegrate the winners. Replace a tool only when the market leaves a real gap.
Client controlledThe client can always view, export, transform, repoint, or build on their data.
AI readyAPIs, webhooks, events, service identities, and agent tools are core infrastructure.
Service enabledHigh touch work becomes reusable mappings, controls, interfaces, and software.
The promise If a client wants to move from Streamline to Guesty tomorrow, their information layer, workflows, history, and accelerators should not need to be rebuilt.
Business model
A barbell. Nothing in the mushy middle.
What the corrected pricing research changed
The original premium price was based too heavily on delivery cost and consulting analogues. The corrected model counts only value that can reach client cash flow. A typical 75 property manager is usually too small. Healthy operators near 250 to 300 properties are the practical center unless a smaller company has a major migration, hiring, acquisition, or risk trigger. Lake Tahoe Accommodations is a design partner candidate, not proof of the final market.
The first wedge
Property Knowledge Reliability
Before dashboards or AI accelerators can be trusted, the company needs one reliable property knowledge layer. The first product proves that scattered facts can be captured, reconciled, certified, surfaced, and exported without losing history.
Standardize onboarding
Map every client's unique sources and terminology into a wide, extensible data model.
Maintain continual sync
Keep business information current across PMS, pricing, operations, AI, documents, and human managed sources.
Surface operating intelligence
Combine Streamline, PriceLabs, RevA, Conduit AI, Breezeway, Slack, and other systems into a real time owner view.
Unlock accelerators
Reuse governed data for listings, captions, social content, websites, CRM, bookkeeping support, and later workflows.
Test tenantRoam FreeProve function safely on our own portfolio first.
→
First external design partnerLake Tahoe Accommodations120 plus units, existing Conduit AI, complex source history, strict forensic preservation.
→
Repeatable marketQualified operatorsOnly after the common model, delivery economics, and willingness to pay are proven.
LTA constraint Current production data is not assumed correct. Original snapshots, later changes, mistakes, corrections, evidence, approvals, and published outputs must remain independently reconstructable.
Approved architecture
A wide base with a small, stable kernel.
The commercial wedge stays narrow. The underlying data foundation must be wide enough to support new clients, sources, verticals, AI models, and services without redesigning the platform.
1Immutable raw versionsWhat each source actually said
→2Fact candidatesPreserved claims, never silent overwrites
→3Canonical decisionsExplicit authority, evidence, time, and approver
→4Derived artifactsDashboards, content, exports, and agent context
No last write wins A source update creates a new claim. It does not silently replace truth. Corrections supersede prior decisions and trigger impact review across downstream outputs.
Core primitives
Clients, resources, identities, source objects, evidence, claims, decisions, relationships, artifacts, policies, approvals, receipts, and audit events.
Versioned definitions
Clients and verticals add typed resources, fields, relationships, units, validation, sensitivity, authority, and namespaces without redesigning the database.
Wide does not mean unstructured Raw payloads remain lossless. The canonical layer stays typed, governed, versioned, and testable.
PeopleRole and attribute based access by client, property, field, purpose, and time.
IntegrationsSeparate service identities with least privilege and explicit directional permissions.
AI agentsPurpose bound tools, minimized context, policy checks, approval gates, and complete activity receipts.
SupportExplicit, temporary, audited access controlled by the client administrator.
1
Permanent client owned IDs. Vendor IDs are mappings, never the identity of the business.
2
Complete exports. Facts, evidence, history, relationships, artifacts, permissions, and receipts leave with the client.
3
Open surfaces. Stable APIs, events, webhooks, agent tools, and connector contracts support whatever the client builds next.
4
Controlled repointing. New destinations receive explicit commands, diffs, approvals, readbacks, and rollback receipts.
Per client isolationShared code and control tooling, separate client data planes and credentials.
Point in time recoveryEncrypted backups, versioned objects, integrity checks, and durable checkpoints.
Restore drillsRecovery is independently tested, not inferred from the existence of backups.
Fail closed resumeWritebacks stop during uncertainty and require reconciliation before resuming.
AI safety and private compute
Enable agents without surrendering control.
The platform should encourage clients to build with their own or our AI agents, while making safe behavior the default. For the most sensitive workloads, local models can operate inside the client's controlled environment so frontier labs never receive the data.
Approved public facts and published content.
Operational context with purpose and user checks.
Minimized, redacted, or routed to client controlled compute.
Local models and purpose bound access only.
Separate facts from inferenceAI guesses retain model, confidence, evidence, expiration, and uncertainty.
Certify by audience and purposeA fact approved for an owner dashboard is not automatically safe for a guest message.
Fail closed on riskStale or uncertain safety, access, policy, and identity facts block high risk outputs.
Never turn secrets into knowledgeCodes and credentials are purpose bound retrievals, not reusable prompt or search content.
Competition and moat
The competitors are layers, not one company.
Systems of recordStreamline, Guesty, Hostaway, OwnerRez
They own core workflows and can expand into analytics or integrations. We win by remaining portable across them and making migration less dangerous.
Data and integrationSnowflake, Fivetran, Hightouch, iPaaS tools
They provide infrastructure but usually do not deliver the STR specific canonical model, evidence, stewardship, operating controls, and acceleration partnership.
AI and automationConduit AI, HostBuddy, point agents, internal builds
They consume or create operational information. We make that information governed, safe, portable, and reusable across agents.
ServicesConsultancies, virtual assistants, agencies, fractional teams
They can solve workflows manually. We must turn repeated work into a reusable client controlled foundation instead of accumulating labor.
WeakMore features
UsefulConnector coverage
StrongCanonical decisions and provenance
StrongerClient trust, embedded controls, and historical graph
DurableFaster safe adoption of whatever comes next
Nvidia is the closer strategic analogy Enable the ecosystem, stay beneath fast moving applications, make switching and building easier, and enter an application layer only when the market leaves an important gap.
Execution sequence
Wrap, shadow, compare, repoint, retire.
Phase 0Discover every Roam Free source
Inventory OwnerRez, Breezeway, Google Drive, Docs, Sheets, Supabase, Notion, Conduit, Airbnb, Vrbo, the direct site, onboarding files, guidebooks, manuals, email, Slack, local files, and every forgotten source. Unknown and unconnected sources remain visible.
Phase 1Build the isolated Roam Free foundation
Create permanent identities, immutable capture, the evidence vault, policies, decision history, and complete export without production writeback.
Phase 2Wrap what already works
Reuse the proven fact engine, dossiers, claim tracing, approvals, write guards, readback verification, and receipts. Wrap vendor specific code as adapters.
Phase 3Shadow and reconcile
Run the new canonical model beside current systems, compare every fact and artifact, preserve disagreements, and time the human work.
Phase 4Launch the read only audit
Show sources, freshness, evidence, conflicts, unknowns, inferences, certifications, published diffs, and a complete export in a beautiful owner ready surface.
Phase 5Govern Roam Free outputs
Use certified facts for listings, captions, Conduit knowledge, and the operating dashboard. Add controlled writes only after explicit approval, canary scope, readback, receipts, and rollback.
Phase 6Deploy LTA in forensic read only mode
Certify baselines and reconstruct history before any new system writeback. Repoint one consumer at a time only after parity and correctness are proven.
Roam Free acceptance gates
Function must be proven before commercialization.
01
Every known source inventoried. Unconnected sources remain visible.
02
Every active property has a permanent ID and verified external mappings.
03
Selected source captures are immutable, hashed, and replayable.
04
At least 95% of the target fact catalog is populated or explicitly unknown or conflicted.
05
Every displayed or exported value traces to evidence and a decision.
06
Authority, sensitivity, audience, freshness, and retention are defined for every target field.
07
Restricted data egress to external models fails closed.
08
No unresolved critical safety, access, policy, or identity conflicts.
09
A complete export and independent restore both succeed.
10
All setup, review, correction, and maintenance time is measured.
Important distinctionRoam Free proves technical function and operating safety. It does not prove external willingness to pay.
Evidence room
Read the analysis behind every major decision.
Managed Business Acceleration Infrastructure
The governing technical blueprint, data lifecycle, safety model, migration path, and MVP gates.
Explore blueprintLTA workflow and data shape audit
What to reuse, generalize, wrap, retire, and build without rewriting proven code.
Read auditBusiness plan research
Product fit, competition, SWOT, target clients, moat, risks, and validation roadmap.
Read reportCorrected pricing strategy
Buyer value, delivery economics, Standard scope, qualification, and kill criteria.
Read reportService enabled platform cases
Veeva, Athenahealth, Celonis, ServiceTitan, failure patterns, and first ten client gates.
Read reportProducts, tools, security, and certifications
Market alternatives, implementation accelerators, standards, safety, and client readiness.
Read reportOperating partner analogues
What worked in healthcare, restaurants, trades, construction, employment, finance, and ecommerce.
Read reportSearch the source library
Go directly from the analysis to original filings, documentation, standards, company material, and reporting.
Browse sourcesNext move
Complete Roam Free source discovery.
The architecture decision phase is complete. The next step is not another product decision. It is to inventory the real Roam Free information environment before choosing connector order or building the canonical schema.