An IT Support Client's First 90 Days: Journey Stages and What Your Website Should Do at Each
Short answer: A small business that buys IT support moves through six stages: noticing a problem, shortlisting providers, getting a proposal, signing up, going through onboarding, and judging the first quarter. Your website should have a different job at each stage. Early on it must prove you are local and credible; in the middle it must make a conversation easy to start; after signing it must reduce confusion; and by day 90 it should make renewal feel obvious. This article sets out each stage and the page, message or automation that serves it.
Stage 1: The trigger (before day 0)
Nobody searches for "managed services" for fun. Something has happened: the office server failed, a staff member clicked a bad link, the person who "looked after the computers" left, or an insurer asked a question about backups.
What the visitor needs: reassurance that the problem is a normal one and that you deal with it. Write pages in the language of the trigger, such as "Our only IT person has left", "We had an email scam last month" or "Our server is out of support". Each page should say what typically happens next and who to call.
What to avoid: leading with acronyms. A small business owner is not searching for a product tier, they are searching for relief.
Include your service area and opening hours prominently. Local business structured data helps search engines understand your name, address and hours, though it does not guarantee a particular display.
Stage 2: The shortlist
The visitor has opened three tabs. They compare what you do, whether you serve companies their size and whether you sound competent without being superior.
What they need from your site:
- A plain statement of who you serve (for example, offices of 5 to 50 people) and who you do not.
- A description of what is in the standard service and what costs extra.
- A sample of what a monthly report looks like, with fictional data clearly marked as an example.
- Contact details that do not hide behind a form.
- A way to reach a person quickly: phone number that works from a mobile tap, plus a short form.
Publishing a price is your decision. If you do not publish fixed prices, explain what drives them (number of users, devices, hours covered) so the visitor can judge scale.
Stage 3: The first conversation and proposal
This is where many small providers lose the lead through slow follow-up. Decide a response target and measure it. A form entry should create a record, tell your team instantly and send the visitor a message that confirms receipt and what happens next.
For the discovery call, send a pre-call checklist: number of staff, main systems, who handles IT now, biggest worry. Keep it to five questions. It makes the call more productive and signals organisation.
The proposal itself should be readable in ten minutes. Include scope, what is not included, a start date, a notice period and the first 90 days plan, which is the core of this article. A proposal that shows the first three months in outline reassures a nervous buyer more than a long list of features.
Track the source of each enquiry using campaign labels in links so you know which pages bring these leads.
Stage 4: Signing and day 0
The moment of signature is when doubts return: "Have we made a mistake?" Send a welcome message within an hour containing the name of their contact, what happens in week one and what you need from them.
What they need: a short, friendly page or email that lists the access items you require, such as admin accounts, a list of staff, supplier contacts for internet and phone, and the location of any licence information. Give a secure way to share these rather than asking for passwords by email.
Stage 5: Onboarding (days 1 to 30)
This stage decides whether the client trusts you. A simple plan shown to the client works well:
- Week 1: inventory of devices, users and accounts; confirmation of backups.
- Week 2: monitoring and security basics in place; first list of recommendations.
- Week 3: staff briefing on how to ask for help; test of the support route.
- Week 4: review meeting to agree priorities for the next two months.
Send a short update at the end of each week, even when little changed. Silence at this stage is the biggest cause of early doubts.
Your website's role is the "how to get help" page. It should show the phone number, the email route, the web form and what to say in an emergency, in one place with large type. Print it as a one-page card for the office wall.
Stage 6: Days 31 to 90 and the first review
The client now judges whether the service is working. They notice small things: how fast a password reset was done, whether a staff member was treated politely, whether anything broke.
What helps:
- A brief monthly report that lists tickets resolved, outstanding items and one recommendation, written in plain English.
- A day 60 check-in call that asks two questions: what has been annoying, and what has been better.
- A day 90 review that summarises the first quarter and restates the agreed plan for the year.
Ask for a review or referral only after a good moment, such as a resolved outage, and make the request easy with a direct link. Avoid sending a satisfaction survey every month. Once after onboarding and again at the 90 day mark is enough.
Putting it together
| Stage | Visitor's question | Your page or message |
|---|---|---|
| Trigger | Is this a common problem? | Situation pages written around the trigger |
| Shortlist | Do they suit a business like ours? | Who we serve, scope, sample report |
| Proposal | What happens next? | Confirmation message, pre-call checklist, proposal |
| Day 0 | Was this the right choice? | Welcome message, access checklist |
| Days 1 to 30 | Are they doing anything? | Weekly updates, how to get help page |
| Days 31 to 90 | Is it working? | Monthly report, review call |
FAQ
Do we need a separate page for each stage?
Not always. Stages one to three need public pages. Stages four to six are mostly emails, documents and a client help page. Build the public pages first.
Should we publish our response times?
Only if you consistently meet them. Publish the target for urgent problems and explain how you measure it.
How do we handle clients who are unhappy by day 30?
Contact them before they contact you. Ask what went wrong, agree an action and record it. An early honest conversation usually protects the relationship better than a polished report.
What should we track from the website?
Track which pages lead to enquiries, how long a form takes to answer and which source brings clients who stay beyond the first quarter.
If you want your site and follow-up messages mapped to this journey, talk to us about your IT support business.