Website for IT support companies: selling reliability to a technical buyer
A website for an IT support company is a step 03 business website: EUR 1.500-3.500 for four to seven pages, a CMS, service pages and a contact or booking flow. A client portal with a login, ticket status or a connection into the systems you already run is step 04, EUR 3.500-7.500.
The difference for this trade is not the price. It is that part of your audience can read the page and the page source. The office manager who lands on your site can forward it to whoever will judge it, and that person can check your claims without asking you anything.
The site is a work sample, whether you meant it that way or not
Every supplier in your market can write the word reliable. You are selling the thing your own website either demonstrates or fails at in front of the buyer. A page that throws console errors, a subdomain serving an expired certificate, a contact form that accepts a message and never delivers it: each one is an argument against hiring you, made on your own domain.
It cuts the other way too. A site that is fast on a phone, correct on every URL and honest about scope does a piece of selling no testimonial does, because the reader verified it instead of believing it.
Seven things a technical reader can check without asking you
| What they look at | What it tells them |
|---|---|
| HTTPS on every URL, www and non-www, with the redirects behaving | Whether you get certificates and DNS right on the one domain you fully control. |
| How the site behaves on a phone on a weak connection | Whether you ship what you would recommend to a client. |
| Whether the contact form confirms, and whether the message actually arrives | Whether anyone monitors the single thing on the site that earns money. |
| Broken links, dead pages, a footer year that stopped updating | Whether the site is maintained or simply still online. |
| Whether the service pages say what is out of scope | Whether the scope argument happens now or after the contract is signed. |
| SPF, DKIM and DMARC on the domain your mail comes from | Whether you apply to yourself the advice you sell. |
| A real address, a registration number, named people | Whether there is a company behind the logo or a reseller behind a template. |
Make the reliability claim checkable
- Publish the response target you actually hold, not the one that reads best, and say which of your plans it applies to.
- Write down what is included and what is billed separately. Hardware, projects, out-of-hours callouts and third-party licences are the four to spell out.
- Name the platforms you standardise on. A technical buyer can rule you in or out on stack before looking at price, and being ruled out early is cheaper for both of you.
- If you run a status page, link it from the header rather than burying it. A supplier who shows their own incidents is making a claim that cannot be faked.
What moves the price
- How many services get a page of their own: helpdesk, managed backup, Microsoft 365, networking, procurement, compliance support. Each one you sell properly is a page.
- A pricing page. Publishing a per-seat range or a starting monthly figure is a page and a decision, and it is the page a technical buyer will look for.
- Location pages, if you support businesses across a region rather than one city.
- A client portal with login, ticket status or a dashboard, which is step 04 at EUR 3.500-7.500.
- Paying invoices on the site. Payments belong to step 04 too: a provider, refunds, receipts and a record that reconciles with your accounting.
The prices in full
| Step | What it covers | Price | Timeline |
|---|---|---|---|
| 01 Single-page landing | One page, form, analytics, responsive | EUR 600-900 | 1-2 weeks |
| 02 Mini-site | Two to three pages, contact flow, basic CMS | EUR 900-1.500 | 2-3 weeks |
| 03 Business website | Four to seven pages, CMS, service pages, booking or contact | EUR 1.500-3.500 | 3-6 weeks |
| 04 Advanced site or web app | Login, dashboard, API, CRM, payments, chatbot | EUR 3.500-7.500 | 6-12 weeks |
| 05 Custom SaaS platform | Scope, auth, billing, admin, deployment | from EUR 7.500 | After discovery |
Care is EUR 100-300 a month and covers updates, monitoring, backups and small fixes. It is not a redesign and it does not pay for new features. SEO foundation is a one-off at EUR 450-750: Search Console, analytics, indexation, technical hygiene, titles, internal links and a three to six month plan. SEO growth, which is technical and on-page work, service, location and content pages, internal links and authority, and monthly reporting, is EUR 500-800 a month. The same figures sit on the packages page, and a fixed quote always follows scoping.
How the build runs
Scoping first: the services you want on the page, what you are willing to publish about scope and price, and whether anything has to talk to a system you already run. A fixed quote follows that. Then design, build, content and launch, at 1-2 weeks for step 01, 2-3 weeks for step 02, 3-6 weeks for step 03 and 6-12 weeks for step 04. Step 05, a custom platform from EUR 7.500, is scoped in discovery first.
The part that waits on you is the decision about what you publish. Response targets, inclusions, exclusions and a price range are things only you can sign off, and a site cannot be clearer about them than the business behind it. The engineering side is set out under design and engineering, and the stack in more detail on the Next.js development page.
When to spend less
If your work arrives by referral and you are at capacity, a rebuild is not the purchase. Fix the pages people are actually sent to, confirm the form delivers, and stop there.
If the site reads well but nothing finds it, the problem is not the design. SEO foundation at EUR 450-750 one-off, as listed above, will tell you whether SEO growth at EUR 500-800 a month is worth starting.
Do not buy a client portal before anyone has asked for one. An inbox that gets answered is a better experience than a login nobody signs into, and when a client does ask, a login is an add-on at EUR 1.500-4.000, confirmed by the quote.
Questions to settle before you commit
Can you build a client portal that shows ticket status?
Yes, at step 04, EUR 3.500-7.500. It needs a login, a permissions model, a connection into whatever holds your tickets, and an agreed answer for what the portal shows when that system is unreachable. If it also takes payment for invoices, that sits inside the same step rather than adding another one.
Do we own the code, and can we host it ourselves?
You own the code, the repository and the database. Hosting is agreed per project: the studio can host, and where the site runs is settled during scoping and reflected in the fixed quote. If you run infrastructure for a living and have a view on where it should live, raise it at the start.
Should we publish prices?
Publishing a range answers the question the visitor opened the page with, and it screens out the enquiry you would have declined anyway. If your pricing depends on what a client already has, publish the range and name the things that move it, which is exactly what this page does.
We already have a site. Is a rebuild the answer?
Not always. If the pages read well and the site is found, the fix may be a list of repairs plus SEO foundation at EUR 450-750 rather than a new build. Ask for those repairs to be written down and priced before anyone proposes starting again.
Send us your current site and the question you hear before a prospect signs, and you will get a number rather than a brochure: get in touch.
Building something?
JP Studio designs and builds websites, storefronts and product interfaces.