I spent a Saturday walking into local businesses with Eldritch IT cards in my pocket.
Some doors were locked. Some conversations ended almost immediately. One business already had IT help. A few people politely took a card. Several were genuinely receptive. None of that produced an instant client.
It was still some of the most useful business development work I have done.
Until then, outreach was easy to over-engineer. I could tune the website, rewrite service descriptions, improve the CRM, research industries, and keep refining the pitch. All of that felt productive because it was measurable and comfortable.
Walking through a door removed the abstraction.
A real owner or employee does not care how complete my internal plan feels. I get a small window to explain why talking to me might be useful without wasting their time.
That changed how I think about selling IT.
The first objective was not closing a deal
I went in with business cards, not a forty-slide assessment deck.
That turned out to be appropriate.
For a cold introduction, asking somebody to make a major technology decision would have been absurd. They did not know me yet. I did not know their environment. I had no basis for claiming they needed a firewall replacement, a network redesign, managed support, or anything else.
The useful objective was smaller:
Make it clear what I do, establish that I am local and credible, and leave an easy path to contact me later.
That is a much healthier starting point than trying to manufacture urgency.
It also fits the standard I have been building into Eldritch IT from the beginning. Why I Started Eldritch IT was partly about building the kind of technical company I would want to hire. I would not want a stranger walking into my business and inventing problems before seeing the network.
Rejection was more informative than I expected
Cold outreach produces a lot of tiny failures.
A place is closed even though I expected it to be open. Someone is busy. Someone is not interested. A sign makes it obvious that soliciting is unwelcome. A business already has somebody handling IT.
At first those outcomes feel like a scoreboard.
They are not.
“We already have IT help” is useful information. So is a conversation that dies because the person cannot quickly understand what I am offering. So is discovering that a type of business has almost no appetite for a cold technical conversation on a Saturday.
The important question is not whether every stop says yes.
It is whether the next round gets better because of what this round taught me.
That is the same reason I keep technical retrospectives. In The Mistakes I Record After Every Project, the value of a mistake is the guardrail it creates afterward. Outreach deserves the same treatment.
I learned to respect the business before diagnosing the technology
When I look at a small office, I naturally start noticing technical possibilities.
How is the Wi-Fi laid out? Is that consumer networking gear? Are the cameras isolated? Is there a sensible backup path? How are the workstations managed?
That instinct is useful once I have permission to assess the environment.
Before that, it is just speculation.
A storefront can look technically messy and still have a perfectly reasonable arrangement I cannot see. An owner may already have a trusted provider. They may have constraints I know nothing about. They may simply have more important things to solve that week.
So I do not want Eldritch IT’s sales process to begin with pretending I have diagnosed a network from the parking lot.
The first conversation should establish fit. The assessment comes after permission.
That distinction protects trust and keeps the technical work honest.
A business card is a handoff, not a strategy
Several people happily took a card. That felt good, especially after the stops that went nowhere.
But handing somebody a card is not a completed sales process.
The card has one job: make the handoff easy.
If they remember a problem later, can they tell what I do? Can they reach me without hunting? If they hand the card to somebody else, does that person have enough context to understand why?
The rest belongs in the follow-up system.
That means recording where I went, whether the interaction was positive, whether somebody mentioned an existing provider, and whether there is a legitimate reason to follow up. It does not mean repeatedly contacting everyone who was polite enough to accept a card.
A CRM should preserve context, not turn courtesy into consent.
That is an important boundary for the way I want to grow this business.
The pitch got shorter when it became real
It is easy to write an impressive service list on a website.
In person, nobody wants the whole list.
The useful version is closer to:
I run a local IT company. I help small businesses with the network, Wi-Fi, security, Microsoft 365, and ongoing technical support. If you ever need another set of eyes on the environment, my information is here.
Then stop talking.
If they are interested, the conversation can expand naturally. If they are not, I have respected their time.
That short explanation also exposed something useful about positioning. If I cannot explain Eldritch IT without relying on industry shorthand, the positioning is not finished.
I do not need the person behind the counter to know what an MSP is. I need them to understand what problems I can help solve.
Local outreach changed how I think about trust
The website matters. Field Notes matters. Documentation matters. A professional email address and a coherent brand matter.
In person, though, those things become supporting evidence rather than the relationship itself.
The interaction comes first.
Was I respectful? Did I make the purpose clear? Did I avoid acting like their current setup was incompetent? Did I leave when the answer was no? Did I make it easy for an interested person to learn more afterward?
That is a more practical definition of trust than adding another badge or marketing claim to a homepage.
It connects directly to Order from Complexity as an Operating Standard. Reducing uncertainty is not only a technical job. A potential client should understand who I am, what I can do, and what happens next without decoding a pile of sales language.
The unsuccessful stops still moved the business forward
I did not come home with a stack of signed agreements.
I came home with something I needed first: evidence that I could actually walk into businesses, introduce Eldritch IT, hear no, keep going, and have normal conversations with people who might someday need the work.
That matters because planning can hide a very specific kind of fear. There is always one more page to improve before outreach. One more CRM feature. One more service description. One more pricing question to settle.
Eventually the business has to meet people.
The first outing made the next one less theoretical.
It also gave me a better standard for progress. A successful outreach day does not require every business to become a lead. It should produce cleaner messaging, better qualification, useful context, and a smaller gap between the company I designed and the company I am actually willing to represent in public.
That is real progress even before revenue appears.
What I will do differently next time
The next round should be more deliberate without becoming scripted.
I want a tighter geographic group of businesses, a simple record of each stop, and a clear rule for follow-up. I want to prioritize businesses where the kind of infrastructure Eldritch IT handles is actually relevant. I also want enough preparation to answer a serious question about scope or next steps without turning the introduction into a technical interrogation.
Most importantly, I want to keep the standard that emerged from the first round:
Do not manufacture a problem just to create a sales opportunity.
Introduce the capability. Listen. Ask permission before assessing. Document what matters. Follow up when there is a reason.
That is slower than aggressive selling.
It is also much closer to how I want Eldritch IT to operate.
Publication and privacy note
This article is based on real in-person outreach. The published version intentionally omits business names, employee names, addresses, exact locations, contact information, and details that could identify individual conversations. The outcomes matter here. The identities do not.
AI transparency
AI assisted with organizing and editing this article. The outreach, conversations, reactions, and conclusions are based on my own experience introducing Eldritch IT to local businesses.