Routing should read the jurisdiction before it reads the asset class
The first sorting question for a DMV inquiry is which jurisdiction it belongs to, because that decides whether it is yours at all.
Most routing rules are built around asset class, so an office inquiry goes to the office desk regardless of where the building is. In a market split three ways that produces a broker in the District working an inquiry for a Rockville building nobody at the firm is licensed to handle.
Build the rule the other way. Jurisdiction first, then asset class, then submarket. An inquiry that names Northern Virginia should land with a Virginia broker before anyone considers whether it is retail or office.
Give the unroutable inquiries a home too. If a requirement falls outside your coverage, it should go immediately to whoever owns referral relationships rather than sitting until someone notices it. A fast referral is a relationship. A slow one is nothing.
Audit the routing quarterly by pulling twenty recent inquiries and tracing where each one went and how long it took. The results are usually worse than anyone expects and the fixes are usually configuration rather than strategy.
Say in the first reply which side of the Potomac you can act on
The first response should establish coverage and next steps, not open with questions the visitor has already answered.
A visitor who has just told you they need 8,000 square feet in Alexandria by the second quarter does not want a reply asking what they are looking for. They want to know that you work Alexandria, who will handle it, and what happens next.
Write the first reply as a short template with three parts: confirmation of the jurisdiction and requirement, the name and direct line of the broker who covers it, and one specific next step with a time.
Where the requirement is outside your footprint, say so plainly in that first reply and make the introduction in the same message. Confirm your own licensing position with counsel, then let the template reflect it honestly.
Speed matters more than polish. A brief accurate reply within the hour outperforms a considered one the next afternoon, particularly with a prospect who is contacting several firms at once.
One metro, three funnels: measure them apart or learn nothing
A blended conversion rate across the District, Maryland and Virginia averages three different businesses into one meaningless number.
Inquiry volume, response time, tour rate and win rate all differ by jurisdiction, because the inventory, the competition and the client mix differ. Reporting them together hides which one is broken.
Instrument the stages that exist rather than the ones a template suggests. Inquiry received, first response sent, requirement qualified, tour booked, tour completed, agreement signed. Attach jurisdiction to each record at the point of entry.
Tour booked is the metric to steer on. It happens inside a reporting cycle, it correlates with revenue, and unlike form fills it cannot be inflated by loosening a form.
Agree the definitions in writing before anyone builds a report. Two brokers will define a qualified requirement differently, and a dashboard built on an undefined term will be argued about rather than acted on.
You will not get a sample for a two percent lift, so test the big swings
Commercial inquiry volume in a single metro cannot resolve small differences, which changes what is worth testing.
Button colors, headline variants and layout tweaks require traffic that a brokerage site in one metro does not have. Running those tests produces numbers that look like results and are noise.
Test changes large enough to show up anyway. Cutting a nine field form to four. Adding a required jurisdiction field. Moving availability above the fold. Replacing a gated document with an open one. Those move rates by amounts a small sample can detect.
Where volume is genuinely thin, switch from split testing to before and after measurement with a long enough window, and be honest that seasonality and market conditions are in the number. A tour booking rate measured through a February of snow closures is not comparable to one measured in September.
Sequence the changes so you can attribute them. One significant change at a time, held for a full cycle, beats four changes shipped together and an argument about which one worked.
A ten o'clock Tysons tour and a noon Navy Yard tour is one canceled tour
Scheduling across the Beltway is where confirmed tours quietly turn into rescheduled ones.
Cross jurisdiction travel in the middle of the day is slow and unpredictable. A booking system that treats a Tysons appointment and a Navy Yard appointment as an hour apart will produce a late broker and an unimpressed prospect.
Build realistic travel buffers into whatever scheduling tool you use, set by jurisdiction pair rather than by a single default. It costs slots and saves tours.
Send a confirmation that includes the practical detail: where to park, whether access is through an alley, which entrance, who to call on arrival. Access in the core is genuinely confusing and a confused visitor calls to reschedule.
Winter deserves an explicit policy. Snow and ice move tours here every year, and having a stated rule about what happens and who calls whom keeps a weather week from becoming a pipeline gap.
A procurement minded tenant wants your process written down before the call
A large share of buyers in this metro evaluate firms the way they evaluate vendors, and documentation converts them better than conversation.
Federal and contractor organizations run structured selection processes. A prospect from that world is often assembling a comparison before anyone speaks, and what they can find in writing determines whether you make the shortlist.
Publish the unglamorous material: how your engagement works, what your fee structure is and when it applies, what the timeline for a typical requirement looks like, which jurisdictions you are licensed in. Hedge anything legal and point readers to their own counsel.
Gating that material is usually a mistake with this audience. A form in front of a fee schedule reads as evasive to someone whose job is comparing vendors, and it screens out principals more effectively than it screens out competitors.
Track whether those pages are read before an inquiry arrives. Where they are, the first call tends to be shorter and further along, which is a conversion improvement even though no rate on a dashboard changed.
Questions we actually get
- We do not get enough inquiries to run split tests. What should we do instead?
- Focus on changes large enough to show up without a formal test, and measure before and after across a full cycle. Cutting form length, adding required jurisdiction routing, publishing a fee structure that was previously gated, and shortening first response time all produce effects big enough to read in a small sample. Save split testing for the rare page with genuine volume, and be honest when the sample cannot support a conclusion.
- What is the most common place inquiries leak?
- Between arrival and first response, usually because the inquiry landed in a shared inbox rather than with a named person. The second most common is routing to a broker who covers a different jurisdiction, who then has to hand it off. Both are configuration problems rather than marketing problems, and both are fixable in days rather than months.
- Should we gate the offering memorandum or the availability list?
- Generally not the availability list. Gating a document that a competitor can obtain anyway mostly obstructs principals and lenders who are not going to fill in a form to browse. Confidential material on a specific transaction is a different matter and there are good reasons to control it, which is a question for your own counsel rather than a marketing decision.
- How fast does the first reply need to be?
- Faster than the firm currently thinks, and consistent more than heroic. A short accurate reply that names the covering broker and a next step, sent within the hour during business hours, does more than a detailed response the following day. What matters most is that every inquiry gets one, which is a matter of ownership rather than effort.
- What should we report to the partners each month?
- Inquiries, first response time, tours booked and tours completed, each split by jurisdiction, plus a short note on what changed and what it appeared to do. Avoid blended metro wide rates, which average three different businesses together. Avoid reporting activity such as pages published or emails sent, which tells a partner nothing about whether the pipeline improved.
