AI Strategy
What AI does in the product
Harla uses AI across three layers of the property operations workflow. At the triage layer, AI classifies and routes inbound maintenance requests — interpreting unstructured tenant communications, assigning urgency, and matching to the right contractor or internal team without a human reading each ticket. At the intelligence layer, the system surfaces anomalies, predicts recurring issues, and recommends actions before they become problems. At the automation layer, AI drafts outbound communications, generates work orders, and populates compliance records, removing the administrative load that currently makes property management expensive to scale.
Together, these three layers mean a property manager using Harla handles more units with less manual effort — and does so with a higher quality of service record, which matters for regulatory compliance and tenant retention. [Edit this section to reflect the current scope of the product — be specific about what is live versus planned.]
Models and tools
| Function | Approach | Provider / Model | Build or Buy |
|---|---|---|---|
| Natural language triage | LLM prompt + classification | Anthropic Claude API | Buy |
| Document ingestion | OCR + extraction | [Provider TBD] | Buy |
| Maintenance categorisation | Fine-tuned classifier | [Internal / HuggingFace] | Build |
| Communication drafting | LLM with property context | Anthropic Claude API | Buy |
| Anomaly detection | Statistical model on ops data | Internal | Build |
Build vs. buy rationale
Where a capability is commodity — language understanding, document OCR, general text generation — Harla buys via API. Foundation model providers have invested billions building capabilities that no early-stage startup can replicate, and the marginal cost of API access is falling consistently.
Where defensibility comes from proprietary data, Harla builds. The knowledge of how a specific portfolio's maintenance patterns evolve over time, which contractors perform reliably for which issue categories, and how tenant communication behaviour signals forthcoming problems — none of that is available in a foundation model, and none of it can be purchased. It is accumulated through operational engagement with real properties.
The goal is a thin, fast API layer on top of foundation models, with a proprietary data and retrieval layer underneath that gets more valuable with every property managed. The model is the commodity; the data architecture is the product.
Data flywheel and defensibility
Each property onboarded adds structured operational data — maintenance histories, contractor performance records, tenant communication patterns, compliance timelines. This data trains and improves Harla's categorisation, routing, and prediction models in ways that become more precise and more specific to the UK private rented sector with every additional unit under management.
Over time this creates a proprietary dataset that a new entrant cannot replicate without acquiring a similar base of operational customers — and by that point, Harla's product will already be significantly more accurate for UK property portfolios than any general-purpose tool. The moat is not the model; it is the operational graph built on top of it, and the time it takes to build that graph is the barrier.
Risks and mitigations
| Risk | Mitigation |
|---|---|
| Model hallucination in operational context | Human-in-the-loop for all actions with financial or legal consequence. AI surfaces recommendations; a person approves them. |
| Cost at scale | Prompt optimisation, response caching, and model tier routing — simpler tasks routed to cheaper models; complex reasoning uses full capability. Margin improves as volume grows. |
| Vendor dependency | Abstraction layer across providers. Provider-specific logic is isolated; switching cost is bounded. Anthropic is preferred today but not required tomorrow. |
| Data privacy (tenant data) | UK GDPR-compliant data architecture. No personally identifiable information enters model training pipelines without explicit consent. Data processing agreements in place with all sub-processors. |