What happens at the first meeting with an IT company?
The first meeting is a conversation, not a sales pitch or a technical audit. Expect about half an hour on the phone or a video call: headcount, devices, what software runs the business, what keeps breaking, and who currently holds the admin accounts. No passwords are needed and none should be asked for. Afterwards you should get a written quote, not a verbal number.
Answered by Anthony Omini, Cross River Tech, Dallas
Key takeaways
- Expect about half an hour of questions, no charge, and no obligation; a first conversation that feels like a pitch is a warning sign.
- The questions are about people, devices, software, what breaks and who holds admin, not about technical detail you are not expected to know.
- No provider should ask for a password on a first call. Handing over credentials belongs to onboarding, after you have signed something.
- You should leave with a written quote listing what is included and what is not, plus a plain-language summary of what needs fixing first.
- Come with your own questions: who does the work, what happens when they are unavailable, and what you own if you leave.
What happens at the first meeting with an IT company?
Someone asks you questions for about half an hour, writes down the answers, and goes away to price it. That is genuinely the whole thing. It should cost you nothing, commit you to nothing, and involve no access to your systems whatsoever.
With me it is normally a phone call or a video call, because that is the fastest way to get to a useful answer and it saves you a trip across Dallas. If there is a server, a wiring closet, an office being built out or anything physical to look at, I will arrange to come by afterwards. Onsite visits are by appointment; I come out myself, so I plan them rather than pretending I can drop in unannounced.
What the meeting is for, on my side, is understanding your business well enough to quote honestly. What it is for on your side is finding out whether you want to deal with this person. Both of those are done through the same conversation, so treat the questions I ask as a sample of how I will work, and treat the questions you ask the same way. If you want the full list of things worth asking any provider, questions to ask before hiring a managed service provider covers the red flags too.
What will an IT company ask me?
Five areas, in roughly this order. None of them require you to know anything technical.
- People. How many work here now, how many a year from now, how many are in the office versus remote, and are there contractors or part-timers with company email.
- Devices. Roughly how many laptops and desktops, how old they are, whether they are Windows or Mac, whether there is a server, and what network equipment exists. "There is a box from the internet company and another box" is a perfectly acceptable answer.
- Software. Email on Microsoft 365 or Google Workspace, and then the systems the business cannot operate without: the practice management system, the case management system, the agency management system, the design suite, the accounting package. Naming these matters more than anything else on the call.
- Pain. What breaks, how often, who fixes it now, and how long the office loses when it happens. This is where the real information is.
- Control. Who holds the domain, who is the administrator of your email tenant, and whether a previous provider still has access. Not the passwords, just who has them.
I will also ask two questions that people find unexpected. First: when was the last time a backup was actually restored, as opposed to reported as successful. Second: is there anyone who left the company whose account might still work. The answers to those two tell me more about the state of an office than a full inventory would.
What should I prepare before talking to an IT provider?
Nothing is required, and I would rather have the call than have you postpone it while you assemble paperwork. But if you want the quote to be accurate the first time, these help:
| Have ready | Why it changes the quote |
|---|---|
| Headcount now and in a year | Managed IT is priced per user or per device, so this is the main driver |
| A rough device count and age | Old machines mean more support hours and a replacement plan |
| Names of business-critical software | Some systems need specific handling, hosting or vendor coordination |
| Whether there is a server, and what it does | A server changes backup, maintenance and risk substantially |
| Your internet provider and rough speed | Determines what is realistic and whether the circuit is the bottleneck |
| Last year's IT invoices, if any | Shows what you have actually been spending, not what you think |
| Any security questionnaire you have been sent | Turns vague requirements into a specific list of things to fix |
| Your lease end date, if a move is possible | Cabling and internet have long lead times and must be sequenced early |
What you do not need to prepare: a network diagram, an asset list, a budget figure, or any understanding of the jargon. If a provider makes you feel unprepared for not having those, that is a preview of the working relationship.
What should an IT provider never ask for at a first meeting?
Passwords. Not the email administrator password, not the Wi-Fi password, not the password to your practice software. There is no legitimate reason to need credentials before there is an agreement, and a provider who asks casually on a first call has told you how they will handle your credentials later.
Also on the list of things that should not happen at a first meeting:
- Installing anything. No remote access agent, no monitoring tool, no "quick scan" software. That belongs to onboarding, after you have signed.
- Asking you to sign that day. Discounts that expire at the end of the call are a sales technique, not a price.
- A free assessment that requires deep access. A genuine assessment is fine, but be clear what is being connected to what, and get it in writing.
- Scaring you. An honest provider will tell you what is genuinely wrong, plainly, and let the facts do their own work. Nobody needs a slideshow about hackers.
- Refusing to talk price. "It depends" is a reasonable answer to what a plan costs before the questions are answered. "No pricing discussion until the audit is done" is not.
What access a provider legitimately needs, and when, is a whole subject of its own; I covered it in what access an IT company needs to your systems. The short version is that it comes after the paperwork, it is granted through named accounts rather than shared passwords, and you keep the ability to revoke it.
What questions should you ask back?
The meeting works in both directions, and the answers you get to these will separate providers faster than any price comparison. Ask all of them, and listen for whether the answer is specific.
- Who will actually do the work? With me the answer is simple: I plan the work and stay your contact, I come onsite myself, and my team handles the routine monitoring and updates behind me. With a larger company, ask whether you get a named engineer or whoever picks up the ticket.
- What happens when you are unavailable? Vacation, illness, two problems at once. Any honest provider has a real answer to this, and a small company owes you a particularly clear one. Mine: support keeps running, my team covers the routine work, I stay reachable for decisions, and planned onsite work is scheduled around it.
- How do I reach you, and what happens after hours? Ask what after-hours work costs before you need it, not during an outage.
- What is not included? Ask for the exclusion list, in writing, before the inclusion list.
- Who owns the accounts, licenses and documentation? The answer should be "you do", without hesitation.
- How does the agreement end? Notice period, what gets handed over, and in what format.
- Can I speak to a current client? How to use the answer is in how to check an IT provider's references and reviews.
My own answers, so you can hold anyone else's against them: you deal with me directly and I plan the work, my team handles the day-to-day monitoring and updates while I stay your point of contact, I am remote-first because it is faster and cheaper for you, onsite across the metroplex by appointment, and the plan is month to month so leaving is a matter of notice rather than negotiation.
How long does it take and what does it cost?
The conversation itself is about half an hour, sometimes a bit longer if the business is complicated or a move is involved. It costs nothing. There is no charge for a quote, a walkthrough of your office, or the follow-up questions afterwards.
If a site visit is needed, that is usually another hour on a separate day. I will use it to look at the wiring closet, the network equipment, the server if there is one, and the physical layout of the space, because Wi-Fi problems in particular are usually explained by walls rather than by settings. That visit is also free when it is part of quoting.
Where charging starts is the moment I am fixing something rather than looking at it. If you want a problem solved during the assessment, that is hourly break/fix work at published rates: $100 an hour remote and $150 onsite in business hours, $150 and $225 after hours, one-hour minimum. I will say clearly when that line is being crossed, and you can always say no. Everything I publish is on the pricing page.
What do you get after the meeting?
A written quote, and a plain-language summary of what I found. Not a verbal number, not a figure in the body of an email that changes later.
What should be in it:
- The price and how it is calculated. Per user or per device, how many of each, and what happens to the number when you add or remove a person.
- What is included. Named, itemised, not "full IT support".
- What is not included, and how that is billed. Projects, hardware, third-party licenses, cabling, after-hours work.
- Term and notice. Mine is month to month, cancel any time. If someone else's runs a year with automatic renewal, that belongs in the comparison as much as the price does.
- Anything urgent, separated out. If your backup has not run for months or a former employee's account still works, that goes at the top with a cost to fix it, whether or not you hire me.
That last point matters. A first meeting should leave you better informed even if you hire somebody else, and the urgent list is yours to keep. When you are putting two or three quotes side by side, how to compare IT support quotes shows how to normalise them so you are comparing the same thing.
How do you set the meeting up?
Send me a couple of sentences: how many people, what the business does, and what prompted you to look for IT help now. That last part shapes everything, because a business reacting to an incident needs a different first conversation from a business planning a move.
I will suggest a time for a call. If a visit makes sense, I will say so on the call rather than insisting on one first. Then you get the written quote. There is no follow-up sequence and no pressure; if the timing is wrong, tell me and I will leave you alone until it is right.
Get in touch when you are ready. If you are still working out whether you need a plan at all, start with on-call IT versus a managed plan, and if you already have a provider you are unhappy with, how to switch IT companies without downtime covers the handover.
Questions people ask
What happens at the first meeting with an IT company?
A conversation of about half an hour, usually by phone or video, covering headcount, devices, the software the business depends on, what keeps breaking and who holds the administrator accounts. Nothing is installed and no system access is given. If there is a server, a wiring closet or a build-out, a site visit follows. Afterwards you should receive a written quote with inclusions and exclusions listed.
What should I prepare before talking to an IT provider?
Nothing is required, but a few things make the quote accurate first time: headcount now and in a year, a rough count and age of computers, the names of the software the business cannot run without, whether there is a server, your internet provider, last year's IT invoices, and any security questionnaire you have been sent. You do not need a network diagram or any technical vocabulary.
What will an IT company ask me?
People, devices, software, pain and control. How many staff and how that will change, roughly how many machines and how old, which systems the business depends on, what breaks and who fixes it now, and who holds the domain and email administrator accounts. Expect two extra questions worth answering honestly: when a backup was last actually restored, and whether any former employee's account still works.
Should I give an IT provider passwords at the first meeting?
No, and a provider should not ask. There is no legitimate reason to need credentials before an agreement exists. Access belongs to onboarding, granted through named administrator accounts rather than shared passwords, with the business retaining the ability to revoke it. A casual request for a password on a first call is a reliable preview of how that provider will handle your credentials later.
Does a first meeting or site visit cost anything?
Not with me. The conversation is free, the follow-up questions are free, and a site visit to look at your wiring closet, network equipment and layout as part of quoting is free. Charging starts only when I am fixing something rather than assessing it, at my published hourly rates, and I will say clearly when that line is being crossed so you can decline.
What should I receive after the meeting?
A written quote showing the price and how it is calculated, an itemised list of what is included, an explicit list of what is not and how that is billed, the term and notice period, and any urgent problems separated out with a cost to fix them. That urgent list is yours regardless of whether you hire the provider who found it.
