To build an IT department, list the technology work your business already depends on, decide what the internal team will own and what stays with outside specialists, hire for the work you actually have, budget for tools and coverage as well as salary, and hand over responsibility in stages. One employee plus outside support is a valid starting department.
At first, someone in the office handles the laptops, a vendor looks after the network, and an outside provider helps when something breaks. As the company grows, those arrangements get harder to coordinate, and you want someone inside the business who knows your people and takes responsibility for IT. Hiring that person is only part of it. You also need to decide what they own, how requests reach them, and who handles the work beyond their experience or hours.
Key takeaways
- Start with an inventory of the work, including IT tasks that operations, finance, or an office manager handle informally today.
- An internal department does not have to own everything. Security monitoring, complex projects, and after-hours coverage can stay with specialists.
- Choose the first hire from the work you have, not from a generic job title.
- Budget for tools, security, coverage, and setup work, not only the salary.
- Hand over ownership when the new team has shown it can do the work, not on an arbitrary date.
What work will the IT department own?
List the technology work already happening in the business and who does it. Include recurring responsibilities as well as visible support requests: employee support, accounts and permissions, device setup, business applications, the network, backups, security, vendors, and planned projects. For each area, note how often it needs attention and what would happen if it stopped. Then ask department leaders about needs that never show up as a ticket, such as slow onboarding, unreliable applications, or manual work they want to automate.
This list becomes the department's starting scope. It also shows the work currently falling between providers and employees.
What should stay outside the department?
Building an internal team does not mean bringing every technical task in-house. Many companies keep specialists for security operations, complex projects, after-hours coverage, or applications that need particular expertise. Here is an example split for a small team. Adjust it to the people and providers you actually have.
| Responsibility | Internal IT | Outside support | Business leadership |
|---|---|---|---|
| Employee support | Routine requests and on-site issues | Escalations and agreed overflow | Sets service priorities |
| Accounts and access | Makes approved changes | Helps with complex configuration | Managers approve who gets access |
| Devices and systems | Inventory and day-to-day administration | Engineering and specialist changes | Approves spending and planned downtime |
| Security | Follows procedures and coordinates internally | Monitors and responds within an agreed scope | Approves policy and accepts business risk |
| Backup and recovery | Runs assigned checks and procedures | Supports backup operations and recovery tests | Sets recovery priorities |
| Planning | Reports needs and coordinates work | Provides options and estimates | Sets priorities and budget |
Be precise about the word "own." Doing a task, approving it, and accepting the business risk are three different responsibilities. Write down who does each, especially for incidents. Our post on co-managed IT explains how to split responsibilities with an outside partner.
Who should be your first IT hire?
Let the work decide. If most of the demand is employee support, device setup, and routine account changes, a support technician with experienced backup may be the right first role. If systems administration is the main need, you need a stronger administrator from day one. A senior first hire makes sense when the environment is complex, a major change is coming, or the company needs daily technical leadership.
Avoid a job description that combines help desk, infrastructure engineering, security leadership, purchasing, and strategy without saying what support the person will have. Good candidates want to know both the work and the limits of the role. Our guide on how to hire your first IT person includes a job description outline, interview scenarios, and an onboarding plan. If leadership is the main gap, read do you need an IT director, and to size the team, see how many IT staff your business needs.
What should an IT department budget include?
Separate one-time setup costs from recurring costs, so you can compare the first year with ongoing operation.
| Budget area | What to include |
|---|---|
| People | Salary, employer costs, benefits, recruiting, training, and equipment |
| Operating tools | Ticketing, device management, documentation, password and access management |
| Security and recovery | Monitoring, response, backup, and recovery testing |
| Setup work | Configuration, migration, documentation, integration, and training |
| Coverage | Vacations, after-hours support, escalation, and project help |
| Equipment lifecycle | Planned replacement of laptops, network gear, and servers |
Check what you already pay for. Some licenses and services will stay useful, and others may belong to a provider or duplicate something you own. When you compare internal IT with outsourcing, put the same responsibilities on both sides: a salary alone is not comparable to a service agreement that includes tools, coverage, and specialists. Our comparison of in-house IT, an MSP, and co-managed IT covers the options.
What tools and procedures does a new IT department need?
The new team needs a reliable way to receive work, manage devices and accounts, protect admin access, document the environment, and recover important systems. Review what you already have before buying more software, and give every tool a purpose and an owner. Decide where support history, the asset list, admin credentials, and procedures will live, and make sure the company, not a provider, controls them. Our guide to the internal IT tool stack goes into detail.
Before you hand anything over, test a few complete workflows:
- A new employee gets the approved accounts and equipment on day one.
- A support request reaches the right person and can be escalated.
- A departure triggers the approved access removal.
- A system alert reaches someone responsible for acting on it.
- A recovery procedure can be followed and the result recorded.
These tests show whether tools and responsibilities actually work together. A set of configured products does not prove the department can run them.
What should the first 90 days look like?
Treat this as an example sequence. Hiring timelines, inherited risks, and migrations can change it, and urgent issues get handled when you find them.
Days 1 to 30: define and prepare
Inventory the environment, document who does what today, agree on the first role, and confirm the company controls its admin accounts. Build the budget and decide which outside support stays in place during the transition. Prepare the core procedures and tools before the new hire starts, rather than expecting them to build everything while also running the help desk.
Days 31 to 60: start the operating process
Set up request intake, priorities, documentation, and escalation. Train the new employee on their assigned work and test common tasks with supervision before handing them over. Tell employees how to ask for help and what to expect, and make sure managers know their part in approvals and onboarding notice.
Days 61 to 90: hand over and review
Expand the internal team's ownership as it shows it is ready. Review support demand, open problems, documentation, and coverage, and confirm what still needs outside expertise. Give leadership a short roadmap: open risks, planned improvements, staffing needs, and decisions required. The milestone that matters is verified ownership, not a handoff date.
If you are leaving an MSP, the transition adds contracts, licenses, admin access, and records that need a plan of their own. Use our guide to moving from an MSP to internal IT and the MSP transition checklist, and do not end the old coverage until the new team can handle the critical tasks.
What this looks like in practice
A children's therapy center we support started as a two-person office, where technology was simple because the organization was simple. It grew to more than 70 employees across five locations in Westchester, Manalapan, New York City, Poughkeepsie, and Rockland County. Each new office added people, devices, and another place where technology had to work every day. Rather than adding a server at each site, we moved the organization to a standardized cloud environment with central management, so new employees and new locations could be set up the same way every time. Read the therapy center case study.
How Compass can help
Compass helps companies build their own IT department. Use it in any combination, one time or ongoing: an evaluation of what the department should own, help defining roles and choosing who to hire, tool selection and purchasing, ticketing and tool setup, escalation support at only the levels you need, after-hours coverage, or security monitoring.
If you are a New York or New Jersey business starting an internal IT team, talk with Spot On Tech. Start with the work you need covered, the people you already have, and what you want the department to own.
Frequently asked questions
How do you build an IT department from scratch?
List the technology work the business depends on, decide what the internal team will own and what stays with specialists, hire for the actual work, budget for tools and coverage as well as salary, set up core tools and procedures, and hand over responsibility in stages as the team proves ready.
Can one person be an IT department?
One person can be the internal owner and handle a defined set of tasks. The business still needs coverage for absences, advanced problems, and work beyond that person's skills, usually from an outside partner. Write down how each of those needs is met.
What should a new IT department do first?
Find out what systems and responsibilities exist, confirm the company controls its admin accounts and backups, and fix urgent gaps. Then set up support intake, ownership, escalation, and the procedures for everyday work.
How should a small IT department be structured?
Around responsibilities rather than titles: employee support, systems and devices, security, applications, and planning. In a small team one person may hold several of these, with outside specialists covering security monitoring, complex projects, or after-hours support.
Do we have to replace our existing IT tools?
No. Check whether current tools fit the new team's work, can be supported, and give the company the access and records it needs. Replace or reconfigure them only when there is a specific reason.
