Consulting
I take a small number of engagements through my Finnish consultancy, focused on software and infrastructure for ports, logistics firms, and other businesses that move physical things. I also work on applied AI, email, and websites.
I’ve written software since the mid-1990s, served ~50 client businesses through GoSoft, written an ISO 27001-aligned ISMS, and spent ~1,000 hours operating the port machinery that terminal operating systems schedule.
Infrastructure & operational systems
Fractional infrastructure leadership
Standing up or running IT for organisations too small for a department but too critical to improvise: identity, networking, servers, backups, vendor management.
Architecture review
Operational and logistics systems, terminal operating systems included: integration boundaries, build-versus-buy, multi-tenancy, the parts that are expensive to get wrong.
Network design
Routing, wireless, and segmentation for industrial and logistics environments.
ISO 27001
Writing an ISMS - scope, risk assessment, policies, controls, and the records that show they run - as the person who writes them and configures them, not one who hands over a template pack. Certification itself is audited by an accredited body: I work as the implementer preparing for that, not as a substitute for it.
AI, email & web
Applied AI - advice and integration
Finding which internal processes and procedures a company can benefit from automating, and which aren’t worth it, then building useful integrations for the ones that are. The AI process review below is a fixed-scope way to start.
I connect AI to a company’s documents, data, and existing systems. I’ve built this in production, solo. The case study covers the implementation, latency, and load-test numbers.
Email & web for small businesses
For companies that need email that reaches the inbox and a website that loads fast and stays up - without a stack of subscriptions to babysit. Domain, DNS, mail authentication and a site served from infrastructure you own, set up and documented so it can be handed over. This site and the mail behind it are the working example.
Self-hosted email
Corporate email on servers you own: migration off the big providers or alongside them, deliverability (SPF, DKIM, DMARC, reputation), transport security (DNSSEC, MTA-STS, DANE), spam filtering, archiving and retention. The mail behind this domain runs exactly this way, and every one of those records can be checked from outside; the hardening is written up in the essays.
How engagements are shaped
Five shapes cover most of what I take on. All of them end in something written down: a verbal handover is not a deliverable.
Fractional retainer
A retainer with a stated monthly hour band, for organisations that need someone accountable for infrastructure decisions without hiring for it. Ongoing, and documented as it goes so the role can be handed over.
Infrastructure assessment
A fixed-length review of what you are actually running - network, servers, identity, backups, and the operational habits around them. The deliverable is a written findings document: what is exposed, what is fragile, what to do first, and what each fix depends on. No retainer attached; you can hand it to someone else to execute.
ISO 27001 gap analysis
Fixed scope: your current state measured against the standard (the clause 4 to 10 management system as well as the Annex A controls, because that is where the findings come from), delivered as a gap report and a remediation list ordered by dependency, including what producing a Statement of Applicability would take. Worth doing whether or not you go on to certify.
AI process review
Time with the people who do the work, walking through how it actually runs. You get a short written list: where AI would save real time, where it does not belong, and what each would take - data, cost, privacy, and whether it can run on your own infrastructure. Whether to build a pilot afterwards is your decision.
Email & web setup
Fixed scope, for small businesses: the email and web setup described above, closed out with a handover document. Ongoing care after that is optional, not assumed.
How I work
I work directly, document as I go, and prefer owning an outcome to billing hours against someone else’s plan. Remote-first from Finland; on-site when the work is physical. Current availability is on the now page.
Written references from earlier employers exist - one is quoted on the CV; references from current work sit under NDA. The engagements I can talk about publicly are written up under Work.
If your problem lives where operations meet software, write to me.