How to Start a Managed Service Provider Business

From 2016 to 2020 I was a partner and chief marketing officer at New York Capital Technologies, an emerging technology services company that we grew into an operational IT solutions provider serving businesses across multiple industries. My title said marketing. The work covered almost everything else: finding customers, shaping what we sold, negotiating with vendors, writing the procedures, answering the support calls and sending the invoices.

If you’re a technician thinking about starting a managed service provider (MSP) business, or you run a small IT shop that still lives project to project, this is what that experience taught me about building one from the ground up. It isn’t a business plan template. It’s the sequence of problems you’ll actually face, and what I’d do about each one.

Technical skill is the entry ticket, not the business

Most IT businesses are started by people who are good at fixing things. That’s necessary, and it isn’t enough. A technology services company needs a set of foundations that have nothing to do with how well you configure a firewall:

a digital identity that tells the right buyers what you do and why they should trust you
service offerings you can deliver the same way every time
a way to acquire customers that doesn’t depend on luck
internal processes for onboarding, support, billing and escalation
vendor partnerships and tooling that let a small team look after many clients
client relationships that outlast the first project

At NYCT I worked on every one of those, often in the same week. That breadth is the real job when a company is small. The sooner you accept that you’re building a business and not just a technical practice, the sooner it starts to behave like one.

Customers come first. The service catalog follows.

One of my most significant contributions was helping establish the company’s customer base. I identified prospective clients, built relationships, took part in negotiations and converted opportunities into contracted engagements. Over that period I personally originated more than one-third of the company’s customer relationships.

Those opportunities came from three places: direct outreach, digital marketing and professional networking. None of them works on its own for long. Outreach opens doors. Marketing makes you credible when someone looks you up after the meeting. Networking brings warm introductions you could never have bought.

The day-to-day work of business development was less glamorous than the word suggests:

writing client proposals, service agreements, contracts and pricing presentations
sitting in negotiations and shaping a solution around what the client actually needed
managing onboarding, ongoing communication and expectations once they signed

The lesson underneath it: don’t only sell the services you already have. Every sales conversation is research. Listen to what prospects keep asking for, and let that shape what you offer, how you present it and how you’ll deliver it profitably. At NYCT I helped shape all three, not just sell what already existed.

Recurring revenue changes everything

At the starting point, the company had essentially no recurring service revenue. Work came in as individual projects: set up a network, build a website, fix what broke. Every month started from zero.

Helping build a recurring revenue model was the turning point. The approach was simple to describe and took discipline to execute: treat every project as the start of a relationship. A finished website became website management. A network installation became ongoing support. A one-time fix became a managed service with defined responsibilities.

That shift does three things for a young IT business:

It makes cash flow predictable, so you can plan hires and tools instead of reacting to the month.
It aligns your incentives with the client’s. When you’re paid to keep systems healthy, preventing problems is profitable. When you’re paid by the hour, problems are.
It forces you to define the service. You can’t sell an ongoing agreement without spelling out what’s included, what isn’t and how fast you respond. That definition becomes the backbone of your operations.

Recurring relationships also depend on retention, which is earned in the unremarkable months: clear communication, kept promises and an account manager who notices problems before the client does.

Build the operating system before you need it

Selling recurring services is the easy half. Delivering them consistently is where small providers struggle, so a large part of my work was building the operational systems behind the service.

That started with tooling. I helped evaluate, negotiate and implement relationships with technology vendors and managed service platforms, including Kaseya, Datto and GMS. Platform choices like these decide how many clients a small team can realistically look after, so they deserve the same scrutiny as any major purchase: what they cost as you grow, what they lock you into and how well your team can actually run them.

Then came process. We built workflows for customer onboarding, service delivery, technical support, vendor coordination and account management, and documented them as standard operating procedures (SOPs). The work also included:

coordinating technical support and troubleshooting for business customers
desktop support, on-site visits and website maintenance
hosting environments, email administration and web infrastructure
onboarding, training and technical handoffs for new customers
administrative operations, billing workflows and accounts receivable

SOPs feel like overhead when there are three of you. They’re what let you serve clients beyond one-off engagements, and they’re what let anyone other than the founder answer a support call well. If you’re starting an IT services company, write the procedure the second time you do something, not the tenth.

Your own website is a sales asset

I led much of NYCT’s brand development and digital presence: designing and developing the company website, creating marketing materials and giving the company a more professional identity in the market. The goal was never just visibility. The site had to explain the value of the services, attract the right prospects and generate real opportunities.

That meant treating it as a business system: site architecture, WordPress, search engine optimization, content, social media, traffic analysis and lead generation, all working together. We applied the same thinking to the client websites and digital solutions we built. A website is a business asset, not a digital brochure, and it should be judged by usability, search visibility, performance and measurable results.

Sell outcomes, then design the solution around them

A core part of the role was translating business problems into practical technology. I worked directly with customers to assess requirements, develop proposals, recommend platforms and coordinate implementation. Depending on the client, that meant WordPress content management, scalable hosting, virtual servers, multilingual websites, analytics integrations, structured and searchable databases, or secure client-access workflows.

Every recommendation was a balance between technical feasibility, the client’s budget, usability, maintainability and their long-term goals. The technically best option is rarely the right one if the client can’t afford to run it or their staff can’t use it. The job is to connect the technology to the result the client wants, and to say so plainly when those two don’t match.

Stay close to the customer, even as you grow

I never stepped back entirely from client work. I regularly served as a point of contact for questions, technical issues, project coordination and support. I handled day-to-day communication, joined on-site engagements, coordinated deliverables and trained customers on new technology.

That hands-on involvement mattered. It’s where you learn how business development, service quality, customer satisfaction and operational efficiency pull against each other, and where you find out whether the processes you wrote actually work. It also made the proposals and documentation better, because they were written by someone who knew what the customer would struggle to understand.

What I’d tell someone starting an MSP today

Decide early that you’re building a business. Brand, sales, operations and finance are part of the job from day one.
Use projects as the front door to recurring relationships. Plan the ongoing service before the project ends, not after.
Let customers shape your offerings. Then package them so they can be delivered consistently and profitably.
Choose your platforms deliberately. Your RMM, backup and support tools set the limits on how far a small team can scale.
Document as you go. SOPs are what make service repeatable and let the business run without you in every conversation.
Treat your website as part of the sales team. It should attract, explain and convert, and you should be able to measure whether it does.

The lesson that stayed with me

NYCT taught me to look at technology from the business’s side: not only how a solution works, but why it matters, what it costs, how it supports growth and whether it creates lasting value. I wasn’t performing a single job function there. I was helping build the business itself: its systems, its customer relationships and the foundation its services ran on.

That experience shapes how I approach technology leadership today, and it’s why I founded Glavnos in 2020 to work as a fractional technology, systems and marketing partner for nonprofits, small businesses and professional firms.

If you’re building or restructuring a technology services operation, or you want a second opinion on how your own IT is delivered, start a conversation. You can also read more about my experience or how we approach IT service delivery at Glavnos.

Building a Technology Services Business From the Ground Up