Solutions Architect
I have been the account exec and the engineer in the same room for 160+ projects. Architecture I owned, agentic systems I built and run, and the pre-sales half most architects have never done.
Why Solutions Architect, why now
12 years building, the last few freelance, including 4 years owning the architecture and product roadmap as part-time CTO at National Auto Service. Solutions Architect work is the part I have been doing in fragments my whole career: scoping a customer's actual problem, defending the proposal against the alternatives, and staying with the build until it is a system that survives the renewal.
Concretely, that means partnering with an account executive to translate a customer's goals into an architecture they'll commit to - serving as the technical advisor across the whole adoption journey, from discovery and evaluation through to deployment, keeping business objectives and technical implementation pointed at the same target the entire way.
An SA turns a customer's messy reality into a system that ships and then survives. I have spent my career doing the three parts of that separately: designing the system, leading the build, and selling the value.
I run one in production every day: a self-hosted MCP server on a box I administer, with skills and workflows that hold state, scoped tools, guardrails and version-controlled definitions. I have published tooling as well, a Claude Code skill that runs my delivery method and a prompt builder for Lovable. That is the difference between demoing a product and having built one.
Part-time CTO for 4 years at National Auto Service, spear-headed three admin panels and a delta ingestion rebuild that stopped it rewriting every row on every run at SAVR, and was the backend engineer on the integration that put crypto trading into a Stockholm fintech. I have owned the call, not only the diff.
Ran a digital agency for six years and freelanced after it. 160+ projects across about 40 clients, and 1.6M+ SEK billed freelance since 2022. I was the account exec and the engineer in the same room: I defended proposals against bigger competitors, talked customers out of bad ideas, and then had to build whatever I had promised.
Production work across Laravel, Vue, React, Astro, HubSpot CMS, WordPress, FilamentPHP, and the SEO and performance plumbing around them. I co-built a HubSpot developer tool that HubSpot's own core team referenced in their documentation.
Five years as a professional coach before I was a developer, then years of agency selling. I can run an architecture deep-dive with the engineering team and an hour later put the same solution to a CFO as a business case, with both ending up pointed at the same thing.
What translates from freelance & agency work
- Owning solutions end-to-end as a freelancer → owning the architecture call, not just the diff.
- Defending technical proposals against bigger competitors → pre-sales conversations against alternatives.
- Multi-stack delivery across 160+ projects → solution-shaping that isn't married to a single technology.
- Part-time CTO at NAS → understanding how solutions actually land in a team's workflow, not just on the architecture diagram.
- Five years coaching + agency selling → translating between technical and non-technical stakeholders.
This page is curated for the Solutions Architect role specifically.
Please note, this is only a summarised version of my full CV. For the full picture, the complete CV is one click away.
What I bring → What this role needs
Each line connects something I have done to something this role asks for.
A production agentic system I run daily. MCP server, scheduled unattended runs, scoped tools and guardrails, which are the concerns an AI-product engagement raises.
Turned my own delivery method into a skill anyone can run, and shipped tools that help others build with AI.
Drove tech strategy, security and delivery for an internal asset-management platform now used across ~90% of Australia.
Built operability tools for a regulated Stockholm fintech, and rebuilt ingestion so it stopped rewriting every row on every run.
Built a developer tool inside another vendor's platform that they ended up referencing in their own docs.
Qualified the real problem, sized the solution, defended it against bigger competitors, and then had to build what I had promised.
Engagements, start to finish
The problem, what I did about it, and what came of it.
SAVR - Operability Tools
- Problem
- Operability gaps for the data and customer-service teams - no usable internal tooling for managing platform data, leaving non-engineering teams blocked on routine workflows.
- Solution
- Three admin panels, two of them FilamentPHP, for the data service, customer service and analyst teams.
- Build
- Spear-headed admin panel work from a paired exploration in my first month at SAVR into three production tools across the engagement.
- Outcome
- Three production operability tools shipped. Non-engineering teams (data, customer service, analytics) unblocked on workflows that previously required engineering involvement.
SAVR - Delta Ingestion System
- Problem
- Every run pulled the whole source and then overwrote the whole database, rewriting every row whether anything about it had changed or not. The run took about three hours.
- Solution
- Keep the pull, cache it, and compare it against what is already stored, so only the writes that are a real change are applied.
- Build
- Designed and built end-to-end as the closing project of my SAVR engagement - owned the architecture call, the implementation, and the cutover.
- Outcome
- The pipeline stopped rewriting rows nothing had changed about, on the platform's key data path.
National Auto Service
- Problem
- Asset management workflows ran on paper and spreadsheets, forcing manual coordination between the internal team, contractors, and customers - and slowing cashflow.
- Solution
- A purpose-built internal platform with customer + contractor interaction layers, replacing the legacy workflow.
- Build
- Designed, built, and operated the system as part-time CTO since 2022 - full ownership of architecture, security, sprint delivery, and product strategy. Brought in a small temporary dev team for larger features.
- Outcome
- Cashflow improved, in the CEO's words. Customer relationship maintained over the full engagement.
HubSpot FieldsJS
- Problem
- Building HubSpot CMS modules required developers to author module field configuration as raw JSON - a slow, error-prone, repetitive process across customer projects.
- Solution
- A JavaScript-authored workflow that compiles to the JSON HubSpot expects, dropping cleanly into existing build pipelines.
- Build
- Co-built and open-sourced as
@iGoMoon/hubspot-fields-js. Refined the developer experience based on actual customer-project usage at iGoMoon. - Outcome
- Adopted by the HubSpot core team and referenced from their official Fields.JS documentation. Cross-vendor / partner-ecosystem credibility - a developer tool inside another vendor's platform that they ended up endorsing.
What carries over from everything else
The half of the job that is not code, and where I learnt it.
- Customer
- Customer-facing and pre-sales
- Architecture
- Owning the architecture
- Enterprise
- Architecture at enterprise scale
- Agentic AI
- Agentic AI in production
- Hands-on
- Hands-on engineering
- Leading
- Leading and coaching engineers
- Project Management
Goal-based delivery on time and budget - clear goals, accurate estimates, agile iteration, reusable foundations.
- Ability to Lead
Bridging cross-functional teams and motivating people to do their best work, informed by years of coaching.
- Sales and Business development
Self-employed mastery of B2B/B2C sales - 90%+ revenue from referrals; scaled to 160+ projects via freelancers.
- Languages
English (Native) · Swedish (Elementary)
- Team Player
Adaptability, trust and shared goals - leading developers while collaborating with sales and design under deadline pressure.
National Auto Service
An internal asset-management platform for vehicle lifecycle tracking - customer portals, contractor coordination, and cashflow workflow automation. Built with Laravel and VueJS.
HubSpot FieldsJS
Open-source dev tool for HubSpot modules - adopted by the HubSpot core team into their official docs.
Frankenverse: A Self-Hosted Agentic System
A production agentic system I built and run every day. My own knowledge base wired to Claude through a self-hosted MCP server, with custom skills and workflows that do the everyday work and run unattended on a schedule.
SAVR - Delta Ingestion System
Re-architecture of the ingestion pipeline at SAVR (Stockholm fintech). It had rewritten every row on every run; it now writes only the rows that changed.
SAVR - Operability Tools
Three production admin panels at SAVR (Stockholm fintech), two of them FilamentPHP, for the data service, customer service and analyst teams.
AI Skill: Create MVP
Productized my consulting methodology as a Claude Code skill - discovery → planning → implementation, resumable across sessions.
TestDome· Top 10%- TestDome· Top 10%
- TestDome· Top 10%
- TestDome· Top 10%
- TestDome· Top 10%
- TestDome· Top 10%
The technologies this role names
Cut down from the full list to what the job ads for this role ask for.
- Laravel
- PHP
- VueJS
- AstroJS
- TypeScript
- React/JSX
- AWS
- Docker
- Claude
- REST API
- PostgreSQL
- FilamentPHP