- You have up to 150 employees and up to 3 locations
- You have one internal IT function, one managed service provider, or both
- You're not sure what IT services you actually need — whether an "IT guy" on call is enough
- Or you have an IT partner, and you're not confident you're getting what you pay for
- Something has forced the question: repeated incidents, a tender, a compliance requirement, a contract up for renewal
IT Service & Risk Assessment
Six weeks to know how your IT really works, where the risks are, and what to fix first.
- 5–6 weeks
- ~15–20 consulting days
- Fixed price from 2,600,000 HUF + VAT
- Hybrid, mostly onsite
The problem
Most companies don't have an IT problem they can name.
They have a feeling. Things keep breaking. The provider costs more than it seems to deliver. Nobody is quite sure which software licences are being paid for, or who has access to what. And every time a project gets complicated, the IT incidents start piling up alongside it.
That feeling is usually right, and it usually has the same structural cause: IT grew with the business without an operating model, an owner, or management processes to grow into. Nothing is written down, so nothing can be measured — and nobody inside has the spare capacity to stop and find out where the money, the risk and the friction actually sit.
Any untracked IT service is a risk. Untracked licences are a risk. No control over the devices and tools the company uses is a risk. No control over how data is handled is a critical one.
Who it's for
- CEOs, founders and operations managers — the people who carry the consequences
- Everyone in the organisation is affected by the outcome, so everyone in scope gets a voice in the interviews
- Larger or more complex organisations are quoted individually rather than turned away
What happens
Seven steps, five to six weeks.
- Initial discussion 3–4 hours onsite with your key people, to understand the pain points in their words and agree where to look first — including anything driven by a compliance or tender requirement.
- Data gathering and interviews One week. Questionnaires go out on Monday and are summarised by Friday, alongside interviews with the people who actually do the work.
- Requirement clarification 3–4 hours to walk the findings back to you and re-align on focus. This produces the Assessment Scope Statement — processes, stakeholders, systems, deliverables, criteria. From this point the scope is fixed and changes only by written change order, so the engagement can't quietly grow.
- Gap analysis Two to three weeks of comparing how your six agreed processes actually run against ITIL 4 and COBIT benchmarks, and mapping where value leaks out of them.
- Status meeting 1–2 hours, mid-flight, so the first time you hear a finding is not in the final report.
- Writing up One week to turn the analysis into the report, the risk register and the strategy.
- Presentation and hand-over 2–4 hours with all stakeholders present. Everything is handed over and the strategy is walked through against whatever compliance criteria started the conversation.
Six processes are assessed. The default set is request, incident, change, risk, data and asset management — swapped for others at the initial meeting if your pain sits elsewhere.
What you get
Six documents you own.
The current state from three angles: what the company knows, what the average employee experiences, and what we see from outside. Current status against target status, per area.
What we agreed to assess and against what criteria, signed off before the work starts. This is the scope baseline — it's what stops the project drifting.
Every agreed process against its benchmark, with the deviations and the observations behind them. A working spreadsheet, not a slide.
Every material IT risk found — known to you or not — with priority, impact, dependencies, recommended treatment and proposed ownership.
Prioritised actions against the material gaps, each with expected business value, the risk it addresses, dependencies and indicative effort. Financial ROI where it can honestly be quantified.
Your processes as they actually run today — policies, procedures, roles and responsibilities, escalation paths — with the gaps marked. For most clients this is the first time these exist in writing.
Packages
- Entry — IT health check A lighter look: the assessment and its findings, without the full strategy and register. Quoted individually.
- Standard — the full assessment Everything on this page: all six documents, the six processes, the presentation. 2,600,000 HUF + VAT, fixed price.
- Premium — assessment plus implementation support Standard, plus hands-on support closing the top three priorities the assessment identifies. Quoted individually.
- Custom More locations, more processes, more complexity, or a group of companies. Quoted individually.
Payment is 40% at signature, 30% when the scope is confirmed after discovery, and 30% on delivery of the final report and strategy. If you move to Premium within 60 days of the strategy hand-over, 25% of the Standard fee is credited against it.
- Access to whatever process documentation exists — however incomplete
- At least one named person per area involved, who can answer questions
- Requested information within five business days; delays move the milestones, they don't shrink the work
- Lists of your software, hardware, vendors and known data-handling processes — as they are, not tidied up
- A walk through the organisation's ordinary working day
- Not an implementation project — fixing the gaps is Premium, or the separate ITSM Tooling & Process Implementation engagement
- Not a compliance audit or certification — that's the readiness services under Compliance
- Not a total IT cost model; you get the risks, the gaps and ROI where it's genuinely quantifiable
- Not a report written for your MSP's benefit — Interpunct is independent of them and vendor-neutral
Next step
Start with the uncomfortable question.
If any of the above sounds like your organisation, the first conversation costs nothing and takes half an hour. If it turns out you don't need this, we'll say so.