Ruby · Vertical research · Paused — design only

The call gets answered. Properly.

In real estate the first call decides the deal, and it usually arrives outside office hours. Ruby picks up, works out what the client actually wants, searches what is available, and books a viewing in the calendar. It remembers the last conversation, so a returning client does not start from the beginning again.

Ruby
01

Why voice, and not another chat widget

The channel is not a style choice. It is where this particular business is won or lost.

TIMING

Enquiries do not keep hours

People look at listings in the evening and on weekends. A call that goes to voicemail is usually a client who has already called someone else by the morning.

SPEECH

Speech in, speech out

The agent hears and answers directly, without transcribing to text and back. That is what keeps the reply quick enough to feel like a conversation instead of a queue.

MEMORY

It remembers the client

Budget, area, what they disliked last time. A second call continues where the first stopped — the part that makes a good human agent feel like a good human agent.

02

What it does on the call

Not a menu tree. The agent has tools and uses them while you are talking.

Qualify
Works out budget, area, timing and what the client is really optimizing for.
Search
Looks through available property against those criteria, instead of reading out a fixed list.
Explain
Answers questions about a specific property from its own records, with the source available.
Book
Puts a viewing in the calendar and confirms it, rather than promising a call back.
Hand over
Passes to a human when the client asks or when the situation needs one, with the context attached.
Record
Leaves a written summary of the call, so the agency has the conversation and not just a number.
03

Where it stands

Ruby is designed but not built, and it is paused behind the products that have users. This section says what that means concretely, because "coming soon" tells you nothing.

BUILT

The engine it would run on exists

The agent graph, memory and control layer are already deployed for our other products. What Ruby would add is the trade-specific part — property tools and the voice persona — not the foundation.

PAUSED

Designed, not built

The trade side is worked out on paper — what it does on a call, how it is distributed, what it costs. No code has been written for it yet, and it waits behind the products that have users.

NO DATE

We are not announcing a launch date

Telling you a month we cannot defend would be the easy move. It ships when the call quality is good enough that we would put our own business on it.

BOUNDARY

It does not negotiate or advise

Ruby qualifies, informs and schedules. Price negotiation, contracts and legal questions go to a licensed human — and the agent says so on the call.

04

Interested early

If you run an agency and the after-hours calls are the problem, that is exactly the conversation we want.

05

Questions about Ruby

Asked by the agencies we have shown it to.

What can it actually do on a call?
It works out budget, area and timing, searches available property against those criteria, answers questions about a specific listing from its own records, and puts a viewing in the calendar. Tools during the conversation, not a menu tree.
Is the technology unproven?
The engine is not new. The graph, the control layer, memory and voice are the same ones running the other products; Ruby is that engine pointed at one trade, built with a single agency rather than for a market.
Does it negotiate or give advice?
No. It qualifies, informs and books. Anything that commits a client or a price stays with the person who is accountable for it.
When does it launch?
There is no date, and it would be dishonest to invent one: the build has not started. Ruby is designed and paused behind the products that have users. Saying that costs us less than a month we would later have to explain.