We built the thing we kept asking other hosts for

The problem we started with

Every short-term rental accumulates a body of knowledge that lives nowhere. The Wi-Fi password is in a text message from 2023. The trick to the dishwasher is in the host’s head. Parking is explained in a paragraph pasted into the last eleven booking threads. The guest who arrives at 11pm and cannot find the light switch does not have access to any of it, so they message the host, and the host answers the same question they answered a week ago.

Hosts already carry a hard clock on that. Airbnb asks hosts to reply to reservation requests, inquiries and guest messages within 24 hours, counts anything slower as a late response, and says response rate can affect where a listing sits in search results. Superhost status requires replying to 90% of new messages on top of a 4.8 rating and a cancellation rate under 1%. The work is not optional, and it does not scale with the number of properties.

What we decided to build instead of a chatbot

The obvious product is a bot bolted onto a messaging inbox. We did not build that, because the failure mode of a bot is that it is confidently wrong in front of a paying guest, and a single invented answer about a lockbox code costs more trust than a hundred correct ones earn.

So the product is the knowledge base first and the chat second. Each property gets a Property Brain: the manual, the quirks, the check-in instructions, the house rules, the appliance notes, all in one structured place that the host owns and approves. Guest answers are drawn from that and can cite which document they came from. When confidence is low, the question escalates to the host instead of being guessed at.

It is also deliberately platform-agnostic. There is no Airbnb login to connect, no Vrbo integration, and no property management system requirement. Guests reach the portal by a link or QR code for their stay. That decision costs us some convenience features. It buys hosts the guarantee that their property knowledge is not held inside somebody else’s API. How it works covers the mechanics in full.

How we operate

• Independent and founder-led. Moche-AI is a small independent team, not a venture-scaled organisation with a sales floor. When you email support, the reply comes from someone who works on the product.
• Built in Somerville, MA. One place, one legal entity, published in our legal center.
• Host approves, machine proposes. The assistant can suggest an update to a property’s knowledge base. It cannot publish one to guests. A human accepts it first.
• Your data leaves with you. Property Brain documents and the structured profile export on request, and account deletion is a real two-step flow rather than a support ticket. Both are documented in the support policy.

Where we are right now

Moche-AI is pre-launch. General availability is January 1, 2027. Accounts created before then are free until launch and no card is charged before that date. After launch the pricing is per property and published openly on the homepage rather than hidden behind a call.

We are telling you this on the page that exists to earn your trust because the alternative is worse: a product that implies scale it does not have is a product that will disappoint you in month two.

What we will not claim

A short list, kept here on purpose so it can be held against us:

• No customer counts, review counts, or “trusted by thousands of hosts” line until there is a number we can show you.
• No claim that the assistant is always right. It answers from your material, cites it, and escalates when it is unsure. That is the honest ceiling.
• No security certification we do not hold. Our trust and safety page states the controls that are actually in place and names the ones that are not.
• No pretending a guest assistant replaces you in an emergency. Safety and urgent maintenance route to a human every time.

Talk to us

If something on this page reads as marketing rather than fact, say so and we will either substantiate it or remove it. Support has the ways to reach us, including for security reports and data rights requests.