Measure industrial and office separately, or the healthier desk hides the leak
A single blended conversion rate across asset classes tells you nothing you can act on.
Industrial and flex inquiries convert differently from office inquiries, which convert differently from land and investment sales. Averaged together, a strong industrial desk can mask a retail pipeline that is losing every requirement at the first reply.
Split the reporting the same way you split the business. Asset class first, county second. Travis, Williamson and Hays behave differently enough that a Round Rock warehouse inquiry and a South Congress retail inquiry should never sit in the same bucket.
Set the segments before you start optimizing anything. Retrofitting them later means rebuilding history you no longer have.
Keep the number of segments small enough to stay readable. Four or five is useful. Twenty means every cell has two inquiries in it and no conclusion is safe.
Time to first reply is the one number that moves every other one
Nothing else you change will matter as much as how long an inquiry waits.
Measure it properly. Not the automated acknowledgment, which nobody counts, but the first message from a human who read the requirement.
Then set a rule the team can actually keep. Every inquiry gets a named owner within an agreed window, and every inquiry has a second owner in case the first one is in a car near Georgetown. A shared inbox with no owner is where requirements go to age.
The first reply should carry something specific: a building or two that fits what they described, and one question that moves the deal. Generic acknowledgments buy you nothing, because the tenant sent the same message to two other firms.
Watch the after hours pattern. Relocating operators frequently send inquiries from other time zones, and a message that arrives at eight in the evening is competing against whoever answers first thing tomorrow.
Owner users go quiet when nobody answers what the lot will allow
The silent deal killer in this market is usually a site question that never got a straight answer.
A buyer looking at land or a small owner occupied building has a question underneath the one they asked. What can I actually build here, and what will the site work cost me.
Local rules on tree protection and impervious cover are unusually strict, and they add a review step that surprises people who have developed elsewhere in Texas. Shallow limestone, karst and slope make excavation a real variable west of the city. Those two things together produce a lot of unanswered emails.
Nobody expects a broker to give a code opinion, and you should not offer one. What converts is naming the question, saying that requirements vary by lot and are generally worth confirming with the city and your own counsel before design, and offering to bring in the people who can answer it properly.
Build the answer into intake. If land and owner user inquiries get a standard first reply that acknowledges the site question and proposes a next step, the thread stays alive instead of dying politely.
Count the calls that ring out while brokers are driving between Buda and Georgetown
A large share of commercial inquiries never touch a form, and most firms are not measuring the ones that do not.
Instrument the phone. Call tracking with a proper record of missed and abandoned calls will usually surface a bigger leak than anything on the website.
Then look at the times. Calls that ring out cluster around exactly the hours your team is in the field, and the caller does not leave a message because they are already dialing the next firm.
The fix is boring and it works. A backup answering path during field hours, a same day callback rule, and a shared log so nothing depends on one person remembering.
Do the same audit on email. Count how many inquiries got no human reply at all in the last quarter. The number is usually higher than anyone in the room expects.
Put every requirement on a lease expiration clock and write follow ups worth opening
A requirement that is not ready today is not dead, it is dated, and most firms lose it by treating those as the same thing.
Capture the lease expiration or the target date on every inquiry, then let it drive the follow up schedule instead of a generic drip.
A follow up should carry something the reader wants. A note on what has traded in their submarket, a new availability that matches their size, a change in the corridor they cared about. Checking in is not a message, it is an apology for having nothing to say.
Do the same on the owner side. Anyone who asked what a building is worth belongs on a list that gets a short, honest market note, not a newsletter.
Track reactivations as their own metric. A requirement that goes quiet for months and comes back is a real outcome, and firms that do not count it end up cutting the follow up that produced it.
A quarter of Central Texas inquiries will not settle a headline argument
Split testing needs volume that a single metro commercial firm does not have, so change big things and judge them on outcomes.
Statistical testing on a page with a few dozen inquiries a quarter cannot detect the small effects that testing tools are designed to find. Running it anyway produces confident nonsense.
Change one substantial thing at a time instead. Replace the entire intake flow, or rewrite the whole first reply, or rebuild the availability template. Then hold it for long enough to see whether booked tours moved.
Keep a written log of what changed and when, with dates. Without it, nobody in six months can tell whether the improvement came from the new form or from a good quarter.
Judge on the outcome that costs money. Booked tours and signed agreements, not form fills. A change that produces more inquiries and fewer tours has made the business worse and will look like a win on the dashboard.
Questions we actually get
- We only get a handful of inquiries a month. Is conversion work even worth it?
- Usually more than traffic work, because the fixes are cheap and the leaks are large. Response time, routing and follow up cost nothing but discipline. Low volume rules out split testing, not improvement. It just means you judge changes on booked tours over a quarter rather than on a statistical result in a week.
- Should we add live chat to the site?
- Only if a real person will answer it during the hours brokers are unavailable. An unanswered chat widget is worse than none, because it advertises availability you do not have. If nobody can staff it, a clearly displayed direct number and a same day callback promise you actually keep will do more.
- Is a shorter form always better?
- No. The right length is whatever routes the inquiry correctly in one hop. For a commercial firm that generally means county or submarket, size, use, timing and contact details, plus a free text box. Cutting below that saves the visitor ten seconds and costs your broker a phone call to find out what you already should have asked.
- What should we track in the CRM?
- Four stages, agreed with the brokers before you start: inquiry received, qualified requirement, tour booked, agreement signed. Add the source and the lease expiration date. Anything beyond that tends to go unfilled, and a stage nobody updates is worse than no stage at all.
- How do we know whether a change actually helped?
- Write down what you changed and the date, then compare cohorts of inquiries before and after over a long enough window to include a full decision cycle. Look at booked tours rather than form submissions. If a single large deal is doing all the work in the numbers, say so out loud rather than claiming credit for it.
