Technical Partner: IT leadership without a full-time IT director.
Most SMEs need IT director-level thinking, but not a full-time IT director. Technical Partner is an independent expert who keeps your IT situation under control: either through regular oversight, or an outside perspective when a project or decision calls for it.
See the services ↓What does technical partnership mean in practice?
A Technical Partner is an independent expert on your side of the table, not the vendor's. There are two ways I help, depending on the situation.
Regular IT oversight
A recurring review of your IT environment: current state, opportunities, risks, and a prioritized action list. Written report and personal walkthrough session.
€800 + VAT per session. Quarterly, monthly, or semi-annually.
Right for: staying informed proactively, not just reacting to problems. No active IT project underway.
Read more →An outside perspective when you need it
An independent set of eyes when you need them: project oversight, scope monitoring, budget tracking, translating technical language for management, or objective review of vendor work. It can be many things.
Case-by-case pricing. One-time review, ongoing monitoring, or a second opinion before a major decision.
Right for: an IT project or purchase underway with an external vendor, where you want an independent expert on your side.
Read more →Which fits your situation?
Regular IT oversight: for ongoing awareness
"We don't know what's happening in our IT environment. We want a regular report so we can make decisions based on facts." No active project running. You want to anticipate, not just react.
An outside perspective: when a project or decision calls for it
"We have an IT project running with a vendor. We're not sure we're getting value for money. We want someone on our side." Or: "We're making a major IT purchase. We want a second opinion before committing."
Both: during and after a project
An outside perspective monitors the active project. When the project ends, regular oversight continues to keep the overall picture in order. A natural combination after larger IT changes.
Regular IT oversight
Not a generic newsletter, and not an "industry trends" slide deck. Regular oversight is a recurring review of your IT environment, filtered through your specific devices, software, and business context. Each session produces a written report and a personal walkthrough: a person who knows your environment, not an automated tool.
What each session covers
Status check
A quick check-in, not a deep dive. Previous recommendations: done or not? License status and significant changes.
Opportunities
New features in software you're already paying for. AI tools that fit your work. Hardware recommendations before the old ones break.
Risks and actions
Security threats relevant to your industry. Regulatory changes you need to act on: NIS2, GDPR, privacy. Aging devices and licenses.
Prioritized action list
Every session ends with a concrete list: what to do first, what can wait, and what needs no action. Clear steps, not vague recommendations.
How a review is delivered
Written report
Clear, concrete, jargon-free. Same format as the IT Health Check reports.
2-hour walkthrough
On-site or remote. We go through the findings, answer questions, and train where needed.
Pricing for regular oversight
Fixed price per session: €800 + VAT. Choose the frequency that fits your situation.
All prices + VAT 25.5%.
€150,000 in unbilled service
Browsing a price list on a hunch, I found that a secure email service had been in use for two years without anyone billing for it. One afternoon of work. The finance department recovered the back fees including the previous year.
This is the kind of thing regular oversight catches.
See a sample report
This is what a regular review report looks like. Status check, opportunities, risks and a prioritized action list.
Open sample report (PDF) →An outside perspective when you need it
When you have an IT project or purchase underway with an external vendor, an outside perspective is an independent expert on your side. I'm on your side of the table: I make sure the project succeeds, stays on budget, and genuinely serves the business. It can be many things. Here are the most common.
What it can look like in practice
Review the IT project situation
Scope, schedule, budget, architecture, and risks. Know where you're starting from.
Identify problems before they materialize
Architecture and design mistakes are expensive to fix later. I spot them early.
Translate technical language for business
Leadership understands where things stand. No cryptic reports, just clear facts.
Make technical debt visible
What was built temporarily and stayed that way. It's expensive for the future.
Assess vendor work objectively
Does the billing match the work done? Is the hour usage sensible?
Example from practice
I jumped into an integration project where Confluence was a dumping ground. All the real knowledge lived in people's heads. Jira didn't reflect reality. Documentation was missing or scattered.
I built a new documentation model with clear structure, cleaned up Jira, and made sure all customer communication was saved in one place. At the same time, I audited the technical architecture and raised risks to management before they became problems.
I also found a missing scope gap: my partner's client's RFQ was missing key information, and the integration platform's underlying data was a mess (IDoc, XML, HR format, SFTP routing). I made the case that you don't build automation on top of an archaeological dig. The client paid for the platform cleanup separately.
The role is agreed case-by-case: a one-time assessment, ongoing monitoring during the project, or a second opinion before a big decision. No blind monthly contracts.
Who is Technical Partner for?
SMEs without an in-house IT director, who need that kind of thinking regularly or in project situations.
Accounting firms
Large amounts of client data, tightening regulation. IT decisions need to be made on facts.
Law firms
Confidentiality is non-negotiable. Vendor recommendations need to be evaluated independently.
Growing companies
IT hasn't kept up with growth. Someone needs to hold the overall picture together during change.
Procurement decision-makers
Planning a major IT purchase. You want a second opinion before committing.
Vendor proposed 150h. Reality was 15h
In an integration project, a vendor proposed two implementation options. Independent evaluation revealed that option B would take 15 hours. Option A would have required 150. Same result. Fraction of the cost.
This is why Technical Partner exists: someone at the table needs to ask the questions others avoid.
Why me?
I don't represent any vendor and I don't resell anything. I recommend what makes sense for you, whether that's a commercial product, an open-source solution, or no new solution at all.
Technical partnership only works if it's genuinely independent. My only interest is yours.
Why me
Independent
No commissions, no reselling. I recommend what works, not what I get paid for.
Direct
I tell you straight what's wrong and what to do about it. No technical smokescreens.
Experienced
M365 admin for 500+ environments. Project experience across multiple industries and organization sizes.
Consistent
The same person review to review. I know your environment. You don't have to explain everything again.
FAQ
What's the difference between regular oversight and project-specific support?
Regular oversight is proactive and recurring. It keeps you informed before problems arise. Project-specific support is situational. It activates when you have an IT project or decision underway that needs an independent outside perspective.
Can I have both?
Yes. If you have an IT project running AND want intelligence after it finishes, combining makes sense. An outside perspective during the project, regular oversight when it's done.
Doesn't our IT partner already handle this?
An IT partner reports on their own work. A Technical Partner looks at the whole picture independently, including things your partner won't tell you about. These roles complement each other.
Do we need an IT Health Check first?
Not necessarily. Regular oversight starts with a light assessment at the first session. Project-specific support activates based on your situation. An IT Health Check is a good starting point if the environment is unknown.
Do I have to commit to a year of regular reviews?
No. You can start with a single review and see if it's worth it. No contract obligation.
Can the review or support be done remotely?
Yes. The walkthrough works on-site or remote. In Kuopio I'm happy to visit in person.
Let's talk.
Tell me about your situation. I usually respond the same day.