A super in the Bronx has a tenant with no hot water on a Sunday morning, and he's standing in a cold boiler room thumbing through his phone. He calls three guys before he gets to your name. By the time he reaches you, two of them have already said yes, and you're stuck being the backup for a job you'd have loved to take.
You did solid work for that same super back in March. He wasn't unhappy with you. He just forgot you existed until he was four contacts deep, because you went quiet for two months and slid down his mental list.
That's the real game with building supers and property managers. Most of your repeat work comes from a handful of them, and they only think of you when something's already breaking. The fix isn't fancy. It's a light text every few weeks that keeps your name near the top, so you're the first thumb-tap instead of the guy they have to scroll to find.
Build the short list before you send a thing
Don't blast every number in your phone. The people who matter here are the supers and property managers who've actually paid you more than once, or who run enough buildings to send steady work. For most borough contractors that's eight to twelve names, not fifty.
Write them down somewhere you'll actually look. A notes app, a cheap spreadsheet, the back of a clipboard, whatever you'll keep open. For each one, jot the basics so a check-in takes ten seconds to personalize:
- Name and building. Mike at the six-family on Grand, not just "Mike."
- What they manage. One walk-up, or a portfolio of thirty units across the borough.
- Last job you did. Gives your text a hook and reminds them you're the one who fixed it right.
- Best way to reach them. Some supers only answer texts, some only pick up the phone. Match how they work.
What to send so it reads like a human
Keep it short and specific. A super reads texts standing in a hallway with a leak behind him, so a wall of words gets ignored. Two lines does the job: remind him you're around, tell him when you're free, ask what's on his list.
Something in this shape works:
- "Hey Mike, it's Danny from the plumbing crew. Slow week coming up, I've got Thursday and Friday open. Anything on your list at the building I can knock out?"
- "Morning Rosa. Boiler season's almost here. Want me to swing by and look at the units on Grand before it gets cold? Free most of next week."
Those land because they stay in their lane. You're a reliable pro naming a window of time and asking one easy question, which is about the amount of effort a busy super will actually answer.
How often, without becoming the guy they mute
Every three or four weeks is about right during a quiet stretch. Often enough that you stay top of mind, rare enough that you're not noise. If a super just handed you a big job, back off and let the work speak for a while.
Timing beats frequency. A check-in hits harder when it's tied to something real on their calendar:
- Before boiler season (late September into October), when the heat complaints start.
- After the first hard freeze, when pipes let go.
- Spring, when roofs, facades, and winter water damage all show up at once.
- Right before a holiday weekend, when their usual guy might be out of town.
One rule worth holding: don't text at 9 PM on a Sunday unless the building's on fire. A pest at the wrong hour gets muted, and a muted number never gets the boiler call.
Log every reply so small jobs turn into a standing account
Here's where most contractors leave money sitting. A super texts back "nothing right now, check with me in a couple weeks," and that reply vanishes into a scroll of green bubbles. Two weeks later you've forgotten, and so has he.
Write down what they say the second they say it. You don't need software for this. A line in your notes with the date and the next step is plenty:
- "Not now, try October." Set a reminder for the first week of October and move on.
- "Got a leak on the third floor, come Tuesday." Log the building and the job so you can follow up after it's done.
- "Who is this again?" That one needs a real visit, not a text. Note it and go shake a hand.
Over a few months that little log turns a scattered handful of emergency calls into a pattern you can see. You start to know which buildings run hot in July, which manager always has a punch list in spring, and which one pays in three days versus thirty. That's the difference between catching jobs and running an account.
Where a little automation helps, and where it doesn't
The nudging part is easy to systemize. A reminder automation, which is just a scheduled alert to yourself, can ping you every few weeks with the supers due for a check-in and even draft the text so you tweak one word and hit send. That saves you the mental load of remembering, which is usually the part that falls apart.
Be careful what you hand off, though. Software that auto-texts a batch of supers on a timer reads as a blast, and supers can smell a mass message from across the boiler room. The relationship is the asset here. Keep the actual sending human, even when a tool lines up the reminders and the draft.
Wiring up that reminder-and-draft setup is the kind of small, cheap thing we put in for NYC shops, though you can run the whole loop from your phone's notes and calendar for free if you'd rather.
Worth doing this week
You don't need a system yet. You need to send the first few texts and write down what comes back.
- Make the list. Pull the eight to twelve supers and managers who've paid you more than once. Names and buildings, ten minutes.
- Write one message. Draft a two-line check-in you can reuse: who you are, when you're free, what's on their list.
- Send three today. Start with the supers you haven't heard from in a month and see what bounces back.
- Log the replies. Every answer gets a date and a next step in your notes, even the "not now" ones.
- Set the next round. Put a repeating reminder three weeks out so the loop doesn't die after week one.
Do that, and next time the hot water quits on a Sunday, you're the first name he thumbs, not the fourth.