A rent number for a brick two-family has to be defended, not emailed
The rent estimate is the moment an owner decides whether you know their market, and sending it as an attachment hands the decision to a spreadsheet.
Comparable rents for a brick two-family in Tower Grove and for a subdivision house in Ballwin are built from different logic. Unit mix, parking, laundry, basement condition and heating all move the number, and none of that survives a PDF.
Deliver it live, on a call or standing at the property. Walk through how you priced it, what you adjusted for and what would change it. The owner is buying judgment, and judgment cannot be attached to an email.
Send the written version afterward, so it becomes a record of a conversation rather than a bid to be shopped. Firms that lead with the document tend to be compared on the number alone.
If the owner's expectation is well above what you would list at, say so on the call. Losing that one early is cheaper than a vacancy argument in month two.
Promise a leasing timeline only after you know which municipality inspects the unit
Time to lease is the promise owners hold you to, and the administrative step between an approved application and handing over keys varies from one small municipality to the next.
Your intake has to capture the municipality, not just the city name on the mailing address. In St. Louis County that field changes who you deal with and how long the step usually takes. The City of St. Louis is separate again, and Illinois is separate from both.
Build the estimate from what you have seen in that specific place, give it as a range, and say plainly that you confirm current practice with the municipality before committing to a date. Practice and fees change without much notice.
Owners forgive a range. They do not forgive a specific date that slipped, because the difference shows up in their bank account. A blown promise in the first month is the most common reason a second property never arrives.
Track the actual elapsed time by municipality. After a year that internal record is better than anything you can find published, and it makes your quotes defensible.
Two states means two intake paths, and your answering service needs both
An owner calling from Edwardsville and an owner calling from Kirkwood should not be reading from the same script.
Write two versions. The Missouri path establishes whether the property is in the city, the county or St. Charles County. The Illinois path establishes whether it is in Madison County or St. Clair County and whether you serve it at all.
Whoever answers should capture the same fields every time: address, municipality, property type, occupancy, and whether there is a current management agreement. Anything less and your pipeline data describes nothing.
Keep maintenance and tenant calls out of the new business queue. They are more frequent, more urgent sounding, and they train whoever answers to treat every call as a problem rather than a sale.
Listen to recordings weekly for a month. The gap between what your team thinks the script is and what it actually sounds like is usually the single largest conversion problem in the business.
The first repair approval is a conversion event nobody instruments
An owner decides whether to give you a second property based on how the first meaningful repair request was handled, not on your onboarding packet.
Send approvals in a consistent format. Photographs, a plain description of the scope, competing bids where practical, what happens if it waits, and a clear recommendation. Owners approve quickly when they are not being asked to make a decision blind.
Masonry and structural questions deserve extra care here. Freeze-thaw damage to brick can look cosmetic and not be, so for anything load bearing recommend a licensed structural engineer rather than offering an opinion in a message thread.
Measure approval turnaround. Slow approvals usually mean unclear messages rather than difficult owners, and the fix is in your template, not in your client list.
Note which owners went quiet after a repair. Silence after the first significant bill is the earliest warning that the door is leaving.
Renewal offers are the one thing you send often enough to test
Owner inquiries in a single metro cannot support small effect experiments, but lease renewals arrive in real numbers and they move owner revenue directly.
Renewals give you a repeatable message with volume behind it. Test send timing, how increases are framed, whether offering a longer term changes acceptance, and how a reminder sequence performs against a single letter.
Timing matters more here than in mild climates. Generally, a unit that turns in the middle of a St. Louis winter is a harder lease than the same unit in June, so shifting renewal outreach earlier in the fall is worth measuring rather than assuming.
Applications are a second surface with volume. Where applicants abandon, which document request stops them, whether the co-applicant step is the drop off. Every day saved there is a vacancy day the owner does not pay for.
On the owner side, run something different. Structured loss reasons, recorded calls, and one deliberate change at a time held across a full lease cycle. Counting reasons beats a test that will never reach significance.
The addresses you decline are a list worth keeping
Every inquiry you turn down carries information about where your marketing money is landing wrong.
Log four fields on every decline: address, municipality, property type and reason. Too far for the maintenance schedule. Too small to be worth managing. Condition you did not want. An owner whose price expectations were unworkable.
Read it quarterly. Patterns show up fast. A stream of declines from one direction usually means your paid geography or a service area page is drawing from ground you cannot serve.
Feed it back into both channels. Exclude the municipalities producing unusable inquiries, and write pages for the ones producing good ones. The list is also the argument for expanding coverage when the same good address keeps arriving from a place you do not currently reach.
Keep a matching list of the ones you accepted and regret. It is less comfortable reading, and it is usually more instructive.
Questions we actually get
- We only get a handful of owner inquiries a month. Is conversion work worth it?
- That is precisely when it is worth it, because every inquiry carries a large share of your growth. The work looks different at low volume. Instead of split tests, it means fixing the intake script, the rent conversation and the follow up sequence, and instrumenting where inquiries stall so you can see the pattern across a quarter.
- What should we measure first?
- Response time to a new owner inquiry, the fields your intake actually captures, and a loss reason on every deal that did not close. Those three cost nothing to start and usually expose the biggest leak within a month. Rank and traffic reports tell you nothing about any of it.
- How long should we wait before judging a change?
- Long enough to see a full lease cycle, because seasonality and turnover drive so much of this business. Judging an intake change over three weeks in February will mislead you. Change one thing at a time and hold it, rather than running several adjustments at once and losing the ability to attribute anything.
- Should we publish our fees to reduce wasted calls?
- In most cases yes. Owners compare price whether or not you participate, and the calls you lose to a published fee page were mostly going to be lost anyway. Where pricing varies by property type or municipality, publish the structure and the variables rather than one number you will have to walk back.
- Can you improve our tenant application completion rate too?
- That surface usually has enough volume to test properly, unlike the owner funnel. The common leaks are document upload requirements, fee timing and the co-applicant step. Improvements there reduce vacancy days, which is the number your owners are actually watching.
