We built different layers because not everybody needs the same relationship
Which IT layer do you need? It depends on how much of the risk and responsibility you want to hand off — from device care alone, to a full outsourced IT department, to governed compliance support.
One of the hardest things about explaining technology services is that people use the word “IT” to mean everything.
A person with one slow laptop needs IT help. A 25-person company with Microsoft 365, multiple locations, employee onboarding, backups, vendors, and security concerns also needs IT help. A tax practice that needs a real WISP, evidence, risk management, staff training, and ongoing review needs IT and compliance help. Those are three different levels of responsibility.
I do not think it is fair to push all three customers into the same package. I also do not think it is responsible to sell the smallest package to an environment that clearly needs more. That is why Truly Unlimited has distinct layers.
TU Essentials: take care of the device
TU Essentials is for individuals, home offices, self-employed professionals, and very small environments that want ongoing care for the computers they already own. The focus is the device:
- Keep it monitored
- Keep it updated
- Keep it protected
- Maintain the included backup
- Provide support within the defined plan
- Reduce the chance that small problems become larger ones
Think of TU Essentials as creating a minimum standard of care for the computer. It is not designed to become the complete technology department for a growing company. It does not automatically include responsibility for every employee, cloud service, vendor, network, policy, compliance obligation, or business system.
If you are one person with one or two computers and you want them maintained properly, Essentials may be exactly enough. It is also a great way to start seeing which tools you will need as your business grows.
TU IT Services: run the business technology environment
TU IT Services is for organizations that depend on technology and need somebody to take ongoing responsibility for it. This is the “dedicated IT department without the full in-house overhead” relationship. The focus expands from the device to the environment:
- Users and identities
- Computers and supported devices
- Microsoft 365 administration
- Help-desk support
- Network and connectivity coordination
- Security tools and monitoring
- Backup oversight
- Onboarding and offboarding
- Vendor coordination
- Documentation
- Technology standards
- Planning and budgeting
- Defined response and escalation
The objective is not merely to answer tickets. It is to help the business operate without unnecessary technology interruption. Our standard is:
Standardize → Monitor → Protect → Resolve early
When that work is done well, IT becomes less visible. New employees have what they need. Access is managed. Systems are understood. Problems are caught earlier. The owner is not the person trying to remember the Wi-Fi password, call the software company, reset the former employee’s account, and compare laptops between meetings.
TU Compliance: add governance, evidence, and accountability
Our compliance layer is built around recognized frameworks like the NIST Cybersecurity Framework, so the evidence you build up actually holds up to outside scrutiny.
TU Compliance is for organizations whose risks and obligations require more than ordinary technical support. The focus includes:
- Risk assessments
- Written security programs and policies
- WISP development and maintenance
- Control implementation
- Evidence and documentation
- Access reviews
- Security awareness and accountability
- Incident planning
- Vendor risk
- Compliance readiness
- Regular review and improvement
This can support organizations dealing with Massachusetts 201 CMR 17.00, the FTC Safeguards Rule, HIPAA where applicable, customer security requirements, cyber-insurance controls, or internal governance expectations. TU Compliance does not replace qualified legal advice or turn a document into a guarantee. It helps the business make its program real.
The distinction matters. IT makes the technology work. Security reduces technical risk. Compliance creates a governed, documented, and reviewable program around the obligations. Those areas overlap, but they are not identical.
You may need more than one layer
Answering which IT layer do you need is not always a single choice — plenty of businesses run two layers at once.
These services are not always three isolated boxes.
- A one-person consultant may use TU Essentials and purchase a defined project when something larger is needed.
- A growing company may use TU IT Services without requiring a full compliance engagement.
- A CPA firm may need TU IT Services and TU Compliance together, because daily operations and regulatory obligations are connected.
- A company with internal IT may need only TU Compliance support, a risk assessment, or a defined technology project.
The right answer depends on what responsibility already exists and what is missing.
A simple comparison
This table is the fastest way to see which IT layer do you need without reading the whole guide.
Choose TU Essentials when
- You are an individual, self-employed professional, or very small office.
- You mainly want care for one to three computers.
- You do not need a full outsourced IT department.
- You want predictable device monitoring, protection, maintenance, and support.
Choose TU IT Services when
- Multiple employees depend on shared technology.
- Technology downtime affects operations or revenue.
- Nobody internally owns IT.
- You need support across users, devices, Microsoft 365, vendors, networks, security, and planning.
- The owner or office manager has become the unofficial IT department.
Add or choose TU Compliance when
- You own or license regulated or sensitive information.
- A law, insurer, client, or contract requires security documentation or controls.
- You need a WISP, risk assessment, policies, evidence, or ongoing review.
- You want governance and accountability around the security program.
- Your existing documentation does not match the actual environment.
Where do projects fit?
Projects & Technology covers defined one-time work:
- Office moves
- Cloud migrations
- Network upgrades
- Security camera systems
- Cabling
- Large deployments
- Major remediation
- Equipment removal or recovery
- Specialized implementation
A managed client may still have projects. The monthly agreement supports the ongoing environment; the project changes or expands it. Again, the key is clarity — the proposal and agreement should say what belongs in each category.
I would love to care about everyone’s IT systems like they were my own. Sadly, that is not possible. A well-maintained business system has dozens of layers, documentation for every step, security precautions, compliance needs, and lots of investment along the way. As I build the business, I am also seeing the requirements of many businesses. Since the businesses I serve are not cookie-cutter, I have to find ways to help as many as possible without compromising our standard of care.
Some businesses simply do not care about implementing a standard for themselves, and that is absolutely okay — it just means we are not going to be a good fit. Technology is constantly moving, innovating, and demanding. That is why being clear on what we offer and what is acceptable keeps both parties protected.
Choosing the right layer
If you are still asking which IT layer do you need, start with the risk you are trying to reduce, not the technology.
If you are between two layers, do not choose based on the smallest monthly number. Choose based on the responsibility the business actually needs somebody to carry. Ask:
- 01If something breaks tomorrow, who owns the response?
- 02Who is currently managing employee access?
- 03Who knows what technology and vendors we have?
- 04Who checks that protection and backups are working?
- 05Who plans replacements and improvements?
- 06Do we have security or compliance requirements?
- 07Is our written program true in practice?
Your answers usually reveal the right layer. We want to serve people deeply, not indiscriminately — right values, mutual respect, a real need, and willingness to meet the standard all matter.
The purpose of the architecture is not to make the company look bigger. It is to make the relationship clearer before either side says yes.
