Designing a management site for two states, two audiences and one phone

Name Kentucky and Indiana in the first line of copy, not on the contact page

An owner reading your homepage is answering one question before any other: do you take property where mine is.

Put the answer in words, at the top, in the same sentence as what you do. Managing single family homes and small multifamily across Jefferson County, Oldham and Bullitt, and in Clark and Floyd Counties across the river, is a headline. A stock photograph of a house is not.

If you take only one side of the river, say that plainly. Owners in Southern Indiana have learned to assume Louisville firms mean Kentucky, and being told directly saves everybody a call. Licensing and registration differ by state and are worth confirming with the relevant agency or your own counsel before the site implies wider coverage.

List the places you serve as text, not as an embedded map. A map graphic communicates nothing to somebody scrolling on a phone and nothing to a search engine either.

Say what you do not take. Firms that name their limits read as more credible than firms that imply they take everything.

Two fields decide the conversation: county and heat source

The owner inquiry form is a qualification tool, and most of them are built as a mailing list signup instead.

Ask for the property address or at minimum the county, first. A door in New Albany and a door in Middletown are different jobs before anything else is discussed, and the answer decides who calls back.

Ask what kind of property it is and how many units. A shotgun double in Germantown, a Crescent Hill house cut into apartments and a Fern Creek ranch produce different maintenance loads and different rent conversations.

Ask about the heating setup and whether there is central air. Winters here are real, and heat is the single largest source of emergency calls in the cold months. Knowing whether a property runs on gas or electric, and whether the LG&E account is in the owner's name or the tenant's, changes the first conversation.

Ask when the current lease ends and whether the property is occupied. Timing is the field that tells you whether this is a call for today or a note for the calendar.

Keep it to those, plus a name and a phone number. Every additional field costs completions, and the fields above are the ones that earn their cost.

The listing feed from your management software is an iframe pretending to be a website

The vacancy pages most firms are proudest of are frequently the slowest and least visible thing they publish.

Feeds embedded from management software often load in a frame, arrive after everything else on the page, and cannot be read properly by search engines. Renters get a slow experience and owners get a homepage that stalls.

Decide what those pages are for. As a leasing tool, a fast, simple list with real photographs and a clear application path is enough. As a search asset, listings are short lived and will not carry the site.

Keep the feed off pages where it does not belong. An owner reading about management fees does not need a grid of available units loading underneath.

If the software supports a properly rendered listing page rather than an embed, use it. If not, accept the limitation and put your search effort into the durable pages instead.

The first of the month is your busiest hour, and no owner is involved

Tenants use the site as infrastructure, and their traffic peaks are predictable enough to design around.

Rent payment, maintenance requests and application status make up most of your sessions. Put the portal link in the main navigation, in the same place on every page, and stop treating it as an afterthought in the footer.

Design the maintenance request path for somebody standing in a cold house with one hand free. Short form, plain language, a clear emergency path, and an honest statement of what counts as an emergency after hours.

Heavy tenant traffic on the first of the month is a load question as much as a design one. A site that slows to a crawl on payment day generates phone calls that eat the same staff hours you were trying to protect.

Keep the two audiences apart without hiding either. Owners should never have to scroll past a tenant portal to find out what you charge.

Turn the owner statement and the inspection report into pages, not gated PDFs

The material that actually convinces an owner is the boring operational evidence, and most firms bury it behind a form.

Show a sample owner statement, a sample inspection report and a plain description of how maintenance approvals work. Owners are trying to picture what the next twelve months will feel like, and a page beats a promise.

Publish the fee structure with what each fee covers. If pricing varies by door count and property type, show the structure and the range rather than a single number.

Explain the process in order: rental analysis, marketing, screening, lease, maintenance, statements, renewal. Six short pages beat one long one, and each is a page that can answer a search.

Put a photograph of a property you actually manage next to it. A brick shotgun on a narrow lot is more persuasive to a local owner than any stock image of a skyline.

If publishing a vacancy needs a developer, the site rots by spring

A management site is an operational tool, and one that only an agency can update becomes stale within a season.

Somebody on your staff should be able to add a neighborhood page, correct a fee, or update the after-hours message without a support ticket. Build for that from the start.

Keep the templates few and simple. Sites in this trade decay because twenty one-off page layouts were built and nobody remembers how to edit any of them.

Watch the third party clutter. Chat widgets, review carousels, map embeds and tracking scripts accumulate, and each one costs load time on the phones your tenants actually use.

Plan for the seasonal edits before winter. Freeze guidance, after-hours procedures and holiday coverage all need updating on a schedule, and a site nobody can edit will simply run last year's version.