Existing shareholders outnumber prospects on your site, and the layout shows it
Traffic from your own buildings is the loudest signal in your analytics and the least valuable, and design tends to follow the loudest signal.
Look at the top pages in your analytics. Portal login, contact, maintenance request. Every one of those is a resident of a building you already manage, and giving them a fast path off the homepage is genuinely good service.
Serving them is not the same as designing for them. When resident tasks own the header, the hero and the first two scrolls, a board member evaluating agents lands on a site that appears to be an account services desk and leaves without ever seeing what you do.
Separate the paths in the first screen. A short, obvious resident lane on one side, and a new business lane that speaks to boards and owners on the other. The resident lane can be plain text links. It does not need a hero image, it needs to be findable in one second.
Measure the two separately from then on. Sessions and pages per session across a blended site will tell you nothing, because the two audiences behave nothing alike.
The first screen has to prove you run prewar buildings, not a listings feed
A board member decides in seconds whether your firm resembles buildings like theirs, and stock photography answers that question badly.
Say what you run and where, in words, above the fold. Co-ops and condos from ten units, across Brooklyn, Queens and upper Manhattan. Prewar walk-ups and elevator buildings. Rental portfolios of a certain size. Naming the boundary is more persuasive than claiming to serve everyone, and it saves you the inquiries you would decline anyway.
Follow it with proof a board recognizes. Building types and unit ranges you manage, the size of your accounting team, how often financial reports go out, how emergency calls are handled after hours and by whom. Concrete operational facts do work that adjectives cannot.
Cut the listings feed from the front page if new business is the goal. Rental listings serve apartment hunters, they are the slowest thing on most management sites, and no board member has ever chosen an agent because of a vacancy grid.
If you can name a building type you have run for a decade, say so. Specificity about what you do beats a claim of full service every time.
The most valuable field on the inquiry form is when their current contract ends
One field turns a vague inquiry into a dated opportunity you can work backward from.
Ask the practical things, in the order that matters to you rather than the order a template suggests. Building address. Approximate unit count. Co-op, condo or rental. Elevator or walk-up. Whether the building is self-managed today or has an agent. And when the current agreement ends or renews.
The contract date field changes how you follow up. A board eight months from renewal needs a slow, useful sequence. A board two weeks past a notice deadline needs a call today. Without the date, both get the same email and one of them is wasted.
Keep the form short enough to finish on a phone. Six or seven fields, no captcha wall, and a clear statement of what happens next, including who will call and roughly when. A vague thank you page loses momentum you paid for.
Route by answer. A two family house in Bay Ridge and a hundred unit prewar co-op on the Upper West Side should not land in the same inbox with the same autoresponder.
Show the transition plan, because the handoff is what the board is afraid of
Boards do not fear hiring you, they fear the ninety days when the old agent has left and the records have not arrived.
Every board that has switched agents has a story about a lost key set, a bank account that took six weeks, an unpaid invoice that surfaced in March, or a super who did not know who to call. Fear of the transition keeps more buildings with an agent they dislike than loyalty ever has.
Put the answer on the site. What happens in week one, what you need from the outgoing agent, how bank accounts and records generally move, when the first financial package arrives, how residents are told, what the super needs to know. A page that walks through the handoff is worth more than a services list.
Be careful with specifics. Timelines for account transfers and record handovers depend on the building, the outgoing agent and the bank, so describe your process while saying plainly that dates vary and that the building's own counsel should review the outgoing agreement and its notice terms.
A board reading that page is being told something no competitor's site is telling them: that you have done this before and it did not go badly.
Your portal lives on someone else's domain, and the scripts live on yours
The two biggest speed problems on a management site are usually a hosted portal you do not control and third party code you chose to add.
Most agents run resident and owner portals on a vendor platform under a different domain. You cannot rebuild it, but you can control the handoff: a fast, obvious link, no interstitial page, and a consistent look so residents do not think they clicked something suspicious.
On the pages you do control, the weight is usually self inflicted. Chat widgets, review carousels, embedded maps, a hero video, three font families and an analytics stack that loads before the text. Strip them in that order and measure after each removal rather than trusting a redesign to fix it.
Speed matters here for an unglamorous reason. A superintendent standing in a basement, a resident in a stairwell and a board member on a train are all working with an intermittent connection, and a page that needs four seconds and full signal simply does not open.
Set a page weight budget in kilobytes before the design starts. Retrofitting speed onto a finished site costs more and usually fails.
Board members read on an iPad with the text zoomed, so design for that
A meaningful share of the people choosing your firm are older volunteers reading at night on a tablet, and small gray type loses to a competitor with plain black text.
Set body text at a size that is comfortable without pinching, hold real contrast rather than fashionable gray on white, and make sure the layout survives a browser zoom of two hundred percent without collapsing. Test it on an actual tablet rather than in a desktop browser window resized by hand.
Give links and buttons real tap targets, label them with what they do, and keep phone numbers tappable everywhere they appear. A board president who has to pinch to find your number is being told something about how you handle details.
Long documents deserve care too. Proposals, fee explanations and the transition page will be read at length, so give them generous line spacing, short paragraphs and headings a skimmer can use.
Accessibility work here is not a compliance exercise, it is straightforwardly the same as designing for your actual buyer.
Questions we actually get
- Should the resident portal login be in the main navigation?
- Yes, and near the top. Hiding it does not push residents toward your marketing pages, it produces phone calls to your office asking where the login went. Give it a plain, obvious link and then design the rest of the page for prospective clients.
- Do we need a separate site for new business?
- Rarely. A separate site splits your search authority and doubles maintenance. What you usually need is a clear new business path within the same site, with its own landing pages by borough or building type, and a homepage that does not bury it under resident tasks.
- Can we publish the list of buildings we manage?
- Some agents do and some management agreements or board preferences restrict it, so check your agreements and ask the boards before publishing addresses. A common middle path is describing buildings without naming them: a hundred and twenty unit prewar co-op in upper Manhattan, a twenty two unit walk-up in Astoria. It gives the proof without the exposure.
- How fast does the site actually need to be?
- Fast enough to be readable on a poor connection, which in practice means keeping the page light and letting the text render first. Set a weight budget before the design starts, cut third party scripts aggressively, and test on a phone with the connection throttled rather than on office wifi.
- Is a chat widget worth adding?
- Usually not, unless a person is genuinely staffing it during business hours. In this trade an unstaffed widget mostly collects maintenance complaints from existing residents, adds weight to every page, and trains prospects to expect a response speed you are not providing. A visible phone number and a short form outperform it.
