← Insights

Article · 6 min read

What a Balloon Store's Quoting Bot Teaches CRE About Governed Deal Intake

Vantrow · Oct 17, 2026

Quick answer

Automate the capture, not the commit. A balloon store's quoting bot structured each bespoke inquiry and drafted an estimate — but the owner still approved every price. CRE teams should do the same: turn a vague broker inquiry into a structured deal record with a grounded draft estimate, then keep a human on the quote or LOI.

What did the balloon store actually automate?

A one-person balloon store automated the slowest part of its business: turning vague customer inquiries into an accurate quote. Every arrangement was bespoke — different colors, sizes, quantities, event dates — so quoting meant endless back-and-forth. The owner built an intake automation that structured the request and drafted an estimate. She still reviewed and approved every price.

The story, shared by builder /u/jacobgc75 on Reddit's r/automation, is small. The pattern is not. Any operating company whose product is priced per-job — a balloon store, a florist, a commercial real estate (CRE) leasing team — hits the same wall: intake is slow because nothing is standard, and the person who prices the work is the bottleneck.

The interesting part isn't the balloons. It's what the owner did not automate: the commit. The system proposed a price. A human sent it. That is the whole lesson.

Why does bespoke quoting sound exactly like CRE deal intake?

CRE deals are bespoke the way balloon arrangements are bespoke — only the variables are bigger. There's no standard price for a lease, and no two inquiries arrive the same way. Every prospect brings a different mix of space, term, and terms, and the person who can price it is usually the busiest person in the shop.

Swap the balloon variables for CRE ones and the shape is identical:

  • RSF (rentable square feet) instead of arrangement size
  • Lease term and renewal options instead of event date
  • NNN (triple-net — tenant pays taxes, insurance, and maintenance on top of base rent) vs. gross, instead of delivery vs. pickup
  • TI (tenant improvement allowance — dollars the landlord contributes to build-out) instead of custom design work
  • Use, buildout condition, and free rent instead of colors and styles

A broker inquiry — "got a tenant looking for ~4,000 RSF, flex use, wants to be in by Q2" — is the balloon store's vague in. It needs the same treatment: capture the variables, structure the request, draft an estimate from comparable prior deals, and route it to a human who owns the number.

What made the automation safe — not just fast?

It was safe because the automation stopped before the irreversible step. It gathered requirements, drafted an estimate from prior jobs, and sent the owner a clean summary to review. It never quoted the customer directly. That boundary — draft everything, send nothing — is the difference between a helpful desk and a liability.

At Vantrow we call this propose, never commit: software stages an action, a human approves it, and the decision lands on an audit trail. The balloon owner followed it by instinct. She let the system do the tedious part — the fifth round of "what colors, what date, how many" — and kept the judgment call for herself.

For CRE, the irreversible steps are obvious once you name them: sending a quote or LOI (letter of intent — the non-binding term sheet that opens a deal), committing a rent number to a broker, promising a delivery date. Those are commits. Everything before them — capturing the ask, matching it to your rent roll and comps, drafting the terms — is safe to stage.

What would this look like on a CRE leasing desk?

It looks like a structured intake that turns a broker's text or email into a reviewable deal record — with the price still waiting on a human. The system handles the repetitive capture; the operator handles the number and the send.

A governed version of the balloon workflow, translated:

  1. Capture the inquiry wherever it lands — a broker's voice note, an email, a form — instead of retyping it into a spreadsheet.
  2. Structure the variables: RSF, use, target occupancy, term, TI expectations, contact.
  3. Draft an estimate from your own prior deals and current asking rents — not a made-up market number.
  4. Stage a clean summary for the leasing lead to review, edit, or reject.
  5. Human approves the quote or LOI; the send and the change land on an audit trail.

According to a JLL survey cited across its 2024 CRE technology reporting, the large majority of real estate firms are experimenting with AI while far fewer have put it into production. The gap is rarely capability. It's trust — nobody wants a system emailing rent numbers unsupervised. Structured intake with a human on the commit closes that gap without asking anyone to gamble the deal.

Where does the balloon analogy break down?

It breaks down on stakes and on the source of the price. A wrong balloon quote costs an afternoon. A wrong rent number, TI figure, or lease-expiration date can cost a tenant or a renewal. And CRE estimates can't be invented — they have to come from your actual rent roll, comps, and stacking plan, not a plausible-sounding guess.

That raises the bar on two things:

  • Grounding. The draft estimate must cite where the number came from — comparable deals, current asking rent — so the reviewer can check it, not just trust it.
  • The record. Every proposed quote, edit, and approval should be traceable. When a broker asks why the number moved, "the system suggested it and I approved it on Tuesday" is an answer. "The AI sent it" is not.

The balloon store got away with informal review because it's one person who knows every price. A leasing team with multiple brokers and hundreds of expirations needs the review step built in, not improvised.

FAQ

FAQ

Can AI send quotes or LOIs to brokers automatically?

It can, but for CRE it shouldn't. A quote or LOI is a commit — hard to walk back once a broker sees a number. The safer design lets the system draft the estimate and structure the request, then routes it to a human who approves the send. Draft everything; commit nothing without a person.

How is this different from a chatbot on my website?

A chatbot answers questions in a conversation and often disappears afterward. A governed intake automation produces an artifact: a structured deal record with RSF, term, contact, and a drafted estimate your leasing lead can review, edit, and approve. The output is a reviewable request, not a chat log.

Where does the estimated rent number come from?

From your own data — prior comparable deals, current asking rents, your rent roll — not an invented market figure. A grounded estimate cites its source so the reviewer can verify it. If the system can't show where a number came from, treat the number as a guess.

Isn't reviewing every quote just as slow as doing it manually?

No. The slow part of quoting is the repeated back-and-forth to capture requirements. The automation removes that and hands you a complete, structured request. Reviewing and approving a drafted number takes minutes; chasing a broker through five emails for the details takes days.

Does this only work for simple businesses like a balloon store?

The opposite. The more bespoke and higher-stakes the pricing, the more the pattern pays off — which is why it fits CRE. What scales up is the discipline: structured capture, a grounded draft, and a human on the commit, all on an audit trail.

See what this looks like for your firm.

Governed software, configured to how you actually work — built embedded, shipped as something you own and can audit.