Spring 2026

Trellis

Agents that run short-term rental operations end-to-end

Visit website

What they do

agents that run short-term rental operations from messages to cleaners

How close to us

5, very close

agents run ops for one small-firm type with $500k ARR; closest to W5, though it is a full stack

Wedges

  • W5 One layer for one type of small firm direct
  • W2 Seeing whether your AI agents actually produce adjacent
  • W8 The other 90% of an AI skill adjacent
L1 Company brain (knows the organisation) 2, clear
L2 Agent team (runs agents, tools, approvals) 2, clear
L3 Does and learns (finishes, checks, measures, updates the brain) 2, clear

Who buys

Firm size
sme
Buyer type
business
Role
owner or operations head of a short-term rental management company (20+ units)
UK
yes
Their own description (from YC)

Trellis is building toward a new hospitality platform: one that does not just help guests find homes, but actually operates them with agents.

Our first wedge is short-term rental property managers, replacing their fragmented stack across guest messages, tasks, cleaners, maintenance, vendors, and owner updates with agents that run operations end-to-end.

In two months, we’ve grown to $500k ARR across 35 customers and 3000 listings, growing around 15% week over week, with one customer already running day-to-day operations with no human involved.

Full teardown

Trellis (YC Spring 2026): teardown vs XMarts

In one line: Trellis sells AI agents that run the daily work of short-term rental (holiday let) property managers: guest messages, cleaners, repairs, owner updates [site] [yc]. Threat: 2, because it is the clearest live example of W5 (one layer for one type of small firm) and it claims real revenue, but it sits in one vertical and the company is five people [yc] [site]. A YC partner who likes vertical agents will name it.

1. Fact file

Item Finding Source
What they say Site: "Vacation rentals ran on chaos. Now they run on agents." YC line: "Agents that run short-term rental operations end-to-end." [site] [yc]
Founded, team, funding Founded 2026, San Francisco, 5 people [yc]. Backers named on their site: Y Combinator and Entrepreneurs First [site]. Round size UNVERIFIED: outside listings disagree ($125k seed, $500k pre-seed, or no amount) and the $500k looks mixed up with revenue [press]. [yc] [site] [press]
Traction (they claim) YC page: $500k ARR, 35 customers, 3,000 listings, about 15% weekly growth "in two months" [yc]. Their site, dated 24 Aug 2026: 50+ companies, 6,500+ listings [site]. No outside check found. [yc] [site]
Founders Lodovico Benvenuti (CEO): founding AI engineer at Conduit (YC W24), earlier built a Milan rental firm (Xenia) to 150 listings [yc] [blog]. Jan Sahagun (COO): sales, says he closed $2M in under two years in rental tech and runs a rental-tech media site [yc]. What YC likely saw: a founder who ran the operation himself and built the AI for it, plus a seller who knows the industry (inference). [yc] [blog]
Customers Named on site: Grand Welcome, Leisr Stays, Haven Vacation Rentals (260+ units, CEO quote), Halo Hospitality, HatchRent, Xenia Milano, Xenia Living, Vesta Domus, Heart Milan Apartments, Cortivo House, Hamaca Homes, Host Me Tender, Alpeon, Momentum [site]. Xenia is the CEO's own earlier firm [blog], so it is not an independent customer (inference on the two Xenia logos). [site] [blog]
Price Public: one plan "starting at $749.99/month", rising with property count; one-time onboarding fee quoted on a call; no charge until the agents reach 70% "autopilot accuracy" on the customer's channels [site]. Fit stated: about 20+ units with a PMS (property management system) [site]. Job ads: none posted [jobs]. [site] [jobs]
Path No renames found. Launch post on YC (about April 2026) [yc]. Trellis page figures dated 24 Aug 2026 [site]. Guesty and Hostaway list it as a certified partner [site] [docs]. [yc] [site] [docs]

2. Their proposition, reverse engineered

Part What they do
Who buys Owners and ops heads of short-term rental management firms with about 20+ units and a PMS. The YC post says most are stuck between 10 and 50 listings [site] [press].
The pain Work is spread over "5 to 10 disconnected tools", so things slip, reviews fall, growth stalls [yc].
The promise Agents own each job from first message to the closing report, and the firm runs with fewer people [yc] [site].
How it works Plugs into the PMS (Guesty, Hostaway and others), inbox channels and field tools. Agents answer guests on Airbnb, Vrbo, WhatsApp, email and voice, escalate what needs a person, and schedule cleaners and repairs from live bookings [site] [docs]. Autopilot is switched on per channel after accuracy is checked [site] [blog].
The output A guest reply sent, a task created and dispatched, an owner update, a claim filed [yc] [docs]. Plus a field-team app, owner portal and dashboards [site].
Proof style Counts of customers, listings and a weekly growth rate [yc]. A dashboard mock-up shows "84.5% AI automation rate", which looks like illustration, not a result [site] (inference). One quote from a customer CEO. No before/after money or hours number from a named customer on the pages read.
Who sells it Founder-led sales plus industry events and the Guesty and Hostaway marketplaces [yc] [docs]. Demo-led ("Book a demo") [site].
Price model Per-property subscription from $749.99/month, billing starts after 70% accuracy is reached [site].
The story Enemy: a pile of single-purpose tools and marketplaces that own the guest. Belief: give "control of the guest experience" back to operators [yc]. CEO line: sell "AI that builds your software", not software with AI [yc].

3. Positioning

  • Category they claim: "AI property management software for short-term rentals"; "a digital copy of a property management company that runs itself" [site] [docs].
  • Category a YC partner would put them in: vertical AI operations layer for one type of small firm (inference).
  • What they want to be known for: the AI that runs a rental business end to end, not another inbox bot.
  • Where they sit on the map: L1/L2/L3 = 2/2/2, buyer = sme, business (20+ unit rental managers).

4. Three layers vs ours

Layer Them (score + evidence) Us (Marton's logs show)
L1 Company brain 2. Agents "maintain full operational context" on guest, property, issue and past attempts [yc]. CEO says the system "learns how each operator works" [yc]. Operator knowledge base and documented processes feed agents [site]. Depth of the lasting memory is a claim; no public detail (inference). A vault of 1,396 pages, 112 call transcripts and 8,763 customer quotes, searchable by meaning. Built on his own business.
L2 Agent orchestration 2. Several agents across messaging, tasks, workforce and owner updates, with escalation to people and approval boundaries [site] [blog]. Field staff are handed work in a mobile app [site]. Not run as a general team builder. About 5,600 jobs run by agents from three makers (Codex 4,756, Claude 839, Gemini 46), each checked by a different AI.
L3 Execution and learning 2. Does the work (replies, dispatch, claims) [yc]. Checks it: billing waits for 70% autopilot accuracy and a "weekly accuracy check" is advised [site] [blog]. No public proof that measured results rewrite the next run, so not 3. Every failure gets a record and an automatic check (about 160). Offer feedback lines fell from 44 to 18 as 22 lint rules were added. Only about 15% of jobs reached the main code.

5. Same and different

Topic Same or different Them Us
Core belief Same Agents fail without full operating context; one agent should own the job to the end [yc]. Same idea (brief).
Autonomy goal Same One customer already runs day to day "with no human involved" [yc]. That is probably the CEO's own old firm (inference). Marton's logs show agents run his own business around the clock.
Buyer Different One vertical: rental managers with a PMS [site]. SMEs and scale-ups across types; not chosen yet (brief). No customer yet.
Kind of work Different Guest, field and owner work; the output is a message or a dispatched task [yc]. Build, check, publish work: code, content, offers (inventory).
Where agents get their rules Different Operator's processes and prior data, set up by Trellis with a human check before autopilot [site] [blog]. Rules added from every failure and every piece of rejected feedback (inventory).
Owner of the result Same The operator owns the result; Trellis runs on top of their PMS [site]. Customer owns it (brief), unproven.
Delivery Different Software plus onboarding, 200+ integrations, marketplace listings [site] [docs]. The system plus two founders. Mac-bound today (inventory).
Proof Different $500k ARR claimed, 35 to 50+ customers claimed [yc] [site]. Internal counts only. No customer number.
Price Different From $749.99/month, pay after 70% accuracy [site]. Not set.

6. Wedge overlap

Wedge Fit Why
W5 One layer for one type of small firm direct Same shape: one small-firm type, one operating layer. Trellis is the full stack for rental managers [site] [yc]. It is a proof the pattern sells, and a warning that the vertical needs deep data.
W2 Seeing whether agents actually produce adjacent They measure autopilot accuracy per channel and gate billing on it [site]. This is an inside-the-product check, not a separate tool for other people's agents (inference).
W8 The other 90% of an AI skill adjacent "AI that builds your software" and documented workflows [yc] [site] suggest upkeep of how agents work per operator. No public claim of skill retirement or freshness checks (UNVERIFIED that none exists).

7. Whitespace (where they stop)

  • Layer gap: they run the operations of one trade; they do not sell a general brain-plus-agent system for any firm [site]. To own it we need the same loop shown on a customer's workflow, not only on our own business.
  • Buyer gap: firms under about 20 units, firms without a PMS, long-term rentals, and every other trade are out of scope [site]. To own it we need a non-rental SME that says it has the pain and will run a workflow.
  • Number gap: pages read show customer counts and a mock-up rate, no named customer before/after number in hours or money [site]. To own it we need one number a finance person would sign.
  • Price gap: not true. A price from $749.99/month is within SME reach [site]. Speed gap: not shown. First value is gated by accuracy, no days given [site].

8. For the YC application

  • Proven today: Marton's logs show his system already runs agents that do and check work: about 5,600 jobs, each checked by a different AI, with about 160 failure records that each added an automatic check. Trellis claims $500k ARR in one trade [yc]; we have no customer revenue.
  • Draft answer to "how are you different from Trellis?": DRAFT. "Trellis is a strong example of agents running one trade, rental managers. Our system is built across trades, with a company brain that learns from checked results, and it already runs our own business." Founders say it their own way.
  • Future claim (needs proof): "We bring the same loop to SMEs in trades Trellis does not serve, with one number owned." Needs one customer workflow run for 4+ weeks with a before/after number.
  • What we understand that they don't: a general brain that learns from checked results can serve many trades without rebuilding each one. needs proof on a customer; they may well reach the same idea inside rentals.
  • Copyability (M3): medium. Their team already builds agents with a check step [site] [blog], so adding learning from results is within reach. A horizontal product would pull five people off a vertical that is growing fast and fits their data and partner channels [yc] [docs] (inference). Not hard, so M3 can not score above 3 against Trellis alone.
  • Why now (M4): None found in this teardown. Do not use "agents can now do the work": that is general AI progress.
  • Do not claim: "no one runs operations end to end with agents" (Trellis claims it). "Vertical agents don't work" (they claim 35 to 50+ customers). That our loop beats theirs (their learning depth is unknown). Anything built on their traction being false (UNVERIFIED either way).

9. Ideas worth taking

  1. Charge only after the agent reaches an agreed accuracy on the buyer's own channels [site]. It removes the buyer's risk and gives a clear first-value test.
  2. Turn autopilot on per channel, not all at once, and keep a short escalation list [blog]. Trust grows in steps.
  3. Sell through the marketplace of the tool the buyer already uses (Guesty, Hostaway) [docs]. A cheap way to reach many small firms.

10. Unknowns

  • Real funding and who invested. Look for a Trellis announcement or a YC Demo Day deck.
  • Whether the $500k ARR and the "no human" customer are independent of the CEO's own firm. Ask a named customer.
  • Whether results feed back and change agent rules. Read their documentation and changelog (the changelog page returned 404).
  • Which customers pay and at what price per property. Ask an operator who saw a quote.
  • Whether the UK or wider Europe is a target beyond Italian customers. Check careers and customer pages later.

Sources

Technical detail
Slug
trellistech
Lens hash
179096c479
Pass
deep
Stale
no