Help now
Something is broken, or people cannot work.
You need technical help with a computer, application, login, printer, or another business system. You do not need a Managed IT agreement first. Get Support is the right door.
How We Work
Start with the situation you actually have.
You do not need to choose the right IT service before you talk to RPM Computers. Tell us what is happening and we will work out the technical path from there. We work with businesses in Barrie and the surrounding area.
Different ways in
People contact us for different reasons. That is expected.
Those starting points lead to different next steps, but they share the same RPMC approach: understand the business, learn enough about the environment, and recommend the work or relationship that actually fits.
A defined piece of work
You have a project, purchase, or technology change.
A new office, new equipment, a system change, or a specific piece of IT work. That can stand on its own. You do not have to become a Managed IT customer to get a project done.
Ongoing responsibility
You want RPMC looking after IT over time.
Fully Managed IT is for businesses that want ongoing technical responsibility. Co-Managed IT is for organizations that already have internal IT and need additional capacity, escalation, or a clearer division of work.
Not sure yet
You have a technology question, and the service category is not obvious.
That is a normal starting point. Contact Us or a discovery conversation is enough. Figuring out which service fits is part of our job, not homework you have to finish first.
How we think
The same judgment, whatever door you used.
Whatever brought you to us, we work the same way: understand enough to recommend well, make responsibilities clear, then carry that context forward when there is an ongoing relationship.
01
Understand the business need
What are you trying to accomplish, what is happening today, and why it matters to the people doing the work.
02
Learn enough about the environment
People, computers, important software, locations, vendors, and how technology fits into a normal day. Only as much as the situation requires.
03
Determine the technical path
Support, a project, equipment, Fully Managed IT, Co-Managed IT, or another defined piece of work. The technically ideal answer is not automatically the right business answer.
04
Make responsibility clear
What is included, what sits outside normal scope, commercial terms, and how additional work will be approved.
05
Do the work and keep context
Then maintain that understanding where there is an ongoing relationship, so you are not starting from zero every time you call.
Discovery
Bring what you know. We will ask the rest.
Technical knowledge is not a requirement for asking for technical help. You do not need a prepared inventory before the first conversation. Discovery is not a quiz. It is how we learn enough to recommend what should happen next.
Some people know a lot
You may already have a clear picture.
How many servers you have, whether they are physical or virtual, which applications matter, and how the network is arranged. That is a useful starting point. We still listen first, then fill in what is missing.
Some people know very little
You may only know how the business feels.
Twenty employees, everybody uses computers, accounting cannot stop, there is a server somewhere, and something keeps causing problems. That is also a reasonable starting point. Discovering the technical picture is part of our job.
Employees and computers
Shared or dedicated workstations
Servers and cloud systems
Important business software
Locations and vendors
Backup and security context
How a normal day actually works
As simple as the situation allows
Discovery should fit the conversation and the situation.
The first conversation
Sometimes that conversation provides almost everything we need. If the environment is reasonably clear, we can move toward a proposal.
More discovery when needed
If important questions remain, discovery continues. That might be another conversation, remote access where appropriate, or an onsite visit to understand the environment more clearly.
The format follows the work
Phone, virtual, or face to face. A customer who prefers a virtual meeting can meet virtually. If an onsite meeting is useful technically, or you simply prefer to meet in person, we can work that way too.
Recommendation
We understand first, then recommend.
A useful recommendation connects technical reality back to the business. Cost, risk, downtime, existing systems, timing, and the way employees actually work all matter. A system that could technically be replaced may have a good reason to remain for now. A small-looking problem may create enough operational risk that dealing with it sooner makes sense.
What deserves attention?
What should happen now?
What can wait?
What are the realistic options?
What does RPMC recommend?
Why that path, for this business?
Fully Managed IT
Co-Managed IT
IT Support
A project or defined piece of work
Equipment or a purchase
Agreement first
Larger work starts after both sides know what they are agreeing to.
Once discovery gives us enough information, we prepare the proposal or quote and make sure the scope, responsibilities, and terms are clear before larger work begins.
Ongoing Managed IT
The relationship is defined before onboarding begins.
Once discovery is complete enough, we prepare the appropriate proposal and agreement. That covers what the relationship includes, who is responsible for what, the commercial terms, and how work outside the normal scope will be handled.
1 Discovery until the picture is clear enough
2 Proposal and agreement
3 Agreement finalized
4 Onboarding and managed work
Projects and purchases
A standalone project has its own path.
We can take on a project, equipment purchase, or other larger billable engagement for a business that does not have an ongoing managed relationship. That work is scoped, quoted, and approved on its own terms.
1 Discovery for that piece of work
2 Plan and scope
3 Quote or proposal
4 Approval, then the work
Managed onboarding
Onboarding turns an unfamiliar environment into one we can support.
This stage belongs to a Fully Managed relationship after it has been agreed. The goal is to build visibility, establish a managed baseline, and document how the business actually uses its technology.
Systems start reporting what they can
We deploy management agents to the appropriate endpoints. Together with our automation, scripts, reports, and technician review, they help establish the current state of devices, software, updates, patching, versions, and performance. That gives us a faster, more consistent baseline so technicians can focus on what the information means and what needs attention. Routine updates and corrections can begin from there where appropriate.
We also learn what a report cannot show
Every business has particulars. Line-of-business software that has to be handled a certain way. Printers used for specific tasks. A department process that looks unusual from the outside but matters. Special vendors, equipment, workflows, and dependencies. Those details become part of the company's documentation, so another RPMC technician can work on the environment without starting from zero.
We review what you already have and what it needs
Networking equipment, computers, servers, security systems, backup systems, and other important technology may already be suitable to keep. Other equipment may need updates, changes, replacement, or a different management approach. We assess what is there, whether it can be supported properly, and what should be discussed with you. Some improvements may make sense now. Others belong in a longer-term plan.
Continuity
A technical point of contact keeps the relationship from resetting.
An ongoing customer should have a consistent technical point of contact. That does not mean one person personally performs every ticket or every technical task. Different technicians may work on different issues based on availability, experience, or the type of work involved.
The technical point of contact provides continuity around that work. They understand the customer, know the environment, understand what has been happening, and remain familiar with what the business is trying to accomplish. Internally, we can involve the appropriate technicians and specialists while you still have someone who understands the larger picture. You should not have to build the relationship again with a different person every time you contact us.
Someone already knows the environment.
That continuity becomes more valuable over time. Support later in the relationship starts with context instead of a blank page.
After onboarding
Managed IT continues between support tickets.
After onboarding, we keep reviewing the managed environment at different levels so emerging problems, maintenance needs, capacity limits, aging hardware, and opportunities for improvement can be identified over time.
Close-in checks
Some checks happen continuously or very frequently. They help identify immediate problems, failed processes, security concerns, update issues, and other conditions that need attention.
Longer-view review
Other reviews look at patterns: a computer that regularly runs short of storage, a machine that consistently uses nearly all of its memory, unusual performance, recurring errors, aging equipment, or a process that no longer works as well as it should.
The business question
Over time the question becomes more than whether a computer is currently working. Is the environment still appropriate? Is equipment becoming a limitation? Has the business changed in a way the technology needs to catch up with?
Employees still need somewhere to ask for help, and technology still fails. With Managed IT, those support requests arrive inside an existing relationship with documentation, previous work, important systems, and business context already in place. You should not have to explain the entire business again. How support requests are handled is covered on the IT Support page.
When the need is larger
Bring the technical need to us. We will say clearly what sits outside the normal relationship.
Businesses change, and some future technology needs will sit outside the normal managed fee. We establish how additional billable work will be handled so you know when a project, purchase, specialist engagement, or other work needs separate approval.
Projects, purchases, and specialists
A support request may uncover separate project work. New equipment may need to be purchased. A specialist may need to be involved. Larger projects, purchases, and special engagements are normally scoped and approved before we proceed.
Smaller out-of-scope work
For smaller hourly work outside the agreement, the process depends on the arrangement with that customer. Some businesses are comfortable authorizing ordinary out-of-scope work under their agreed terms. Others want designated people to approve that work first. We can accommodate an approval process when you want one.
Vendors and specialists
Sometimes the final solution belongs partly or entirely with another provider: Microsoft, an internet provider, a software company, a copier company, a hardware manufacturer, or another specialist. You can still start with us. We can investigate, gather information, explain the environment, work with the other provider, and help determine what happens next. Specialist resources extend the RPMC department while we stay involved in understanding the need, coordinating the technical work, and keeping you informed.
Communication
You explain the business. We handle the technical translation.
Throughout the relationship, we explain technology in language you can use. You explain what the business needs. We turn that into the technical requirement. When technical work produces findings, those findings come back the other way: what is happening, why it matters, what the options are, what we recommend, and what happens next.
You do not need to become the technical person for that relationship to work. A good RPMC relationship should feel straightforward from your side. You can explain what you need. We understand what you mean. We understand how the business works. We know what to do next. And you do not have to keep teaching your IT company who you are every time you call.
Choose the door that fits
Tell us what is happening. We will take it from there.
Use the path that matches the situation. We will not make you pick the perfect service category first.
An ongoing relationship
Book a Free Discovery Call
For exploring Fully Managed IT, Co-Managed IT, or whether an ongoing relationship is the right next step.
Book a Free Discovery CallSomething needs help
Get Support
For a current technical problem, a user who cannot work, or a system that is not behaving.
Get SupportA question or general enquiry
Contact Us
For a technology question, a project idea, or when you are not sure which service fits yet.
Contact Us