Skip to content
Comparison

Two conversational AI products, and one difference that matters.

Structurely is one of the longest-standing conversational AI products in real estate. If you are comparing it with Lewis, the question to hold onto is not “which one writes better sentences”: it is who approves a message, and what neither will send.

Same category, different default

Both products belong to the same category: AI that converses with real-estate leads over text, qualifies them, and hands the warm ones to a person. Anybody comparing them is comparing two credible answers to the same question.

What differs is the default posture. Lewis starts every account at “nothing sends without your yes”, and the autonomous mode is something you grant in words and can take back the same way. Products in this category more commonly start from the other end: the assistant converses, and the agent is notified when something is worth their time.

Neither default is wrong. They suit different appetites, and the one you want depends on whether “it answered before I saw it” reads to you as the feature or as the risk.

Side by side

One row per thing an agent actually asks about.

How Lewis and Conversational AI, generally differ
LewisConversational AI, generally
Default postureEvery draft held for the agent’s yes; autonomy is granted in wordsTypically autonomous conversation with escalation to the agent
Can the agent write the message themselvesYes, the draft stays and your words go out verbatimVaries by product
What is refused outrightFair-housing language, unsourced property facts, unsourced travel times, listing-agent contact detailsVaries. Read the vendor’s own documentation
Where the rule livesCode, checked on the output of every message at every autonomy levelVaries
Record of refusalsAppend-only event log, with the rule that firedVaries
ChannelText, over iMessageUsually SMS, sometimes email
Priced byAgent per monthRead the vendor’s current pricing
CRM integrationNone needed, it reads a CSV exportUsually direct integrations

Everything below about Lewis is checkable in this product. Everything about the other side is a description of the CATEGORY it belongs to, not a claim about its internals. For anything specific, and for current pricing, read their own documentation. If something here is out of date or unfair, tell us and it gets fixed.

What Lewis is deliberately narrower about

Lewis has no MLS behind it, and it is built so that having one would not change the rule: it will not assert a fact about a property. Not “will try to be accurate”: will not assert. Square footage, price, taxes, availability, and any travel time it cannot get from a provider that traced streets are refused on the way out.

That is a real limitation, and it is chosen. The alternative is a system that occasionally tells somebody a home has a new roof, and a commute is one of the two or three things people actually decide on.

What direct CRM integration buys, and what it costs

A direct integration writes back. That is genuinely convenient, and it is also a permission to change your CRM, which some brokerages will not grant and most take a while to approve.

Lewis reads a CSV export and writes nothing back. That is less convenient and it is why there is nothing to set up, nothing to authorise, and no CRM it does not support.

How to actually compare them

Ask both for the same thing: show me a message you refused to send, and the rule that refused it. The answer to that question tells you more than any feature list.

Other comparisons

Your book is already full of people who meant it.

Point Lewis at the export and he works it over text, every draft still waiting on your yes.