- frank.fava@gmail.com
- 0729 183 764
- github.com/frankfava
- linkedin.com/in/frankfava
- Stockholm Sweden, SECurrent Location
- Australian + EUCitizenships
Solutions Architect
Why Solutions Architect, why now
After 18 years building - the last few freelance, including nearly 4 years owning the architecture and product roadmap as part-time CTO at National Auto Service - I'm moving deliberately into Solutions Architect work. The pull isn't away from engineering; it's toward the part of the work I've been doing in fragments my whole career: scoping a customer's actual problem, defending the proposal against alternatives, and shepherding the build through to 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's job is to translate a customer's messy reality into a system that ships, scales, and survives. That sits at the intersection of three things I've spent my career doing: designing systems, leading the build, and selling the value.
Part-time CTO for nearly 4 years at National Auto Service, spear-headed three admin panels and a high-throughput data-ingestion delta system at SAVR, and led the integration that put crypto trading into a Stockholm fintech. I've owned the call, not just the diff.
Ran a digital agency for ~6 years (160+ projects, 1.1M+ SEK billed via Cool Company on a single recent stretch) where I was both the account exec and the engineer in the room. I've defended technical proposals against bigger competitors, talked customers out of bad ideas, and stood by what I shipped - exactly the technical air-cover an AE needs to move a deal.
Production work across Laravel, Vue, React, Astro, HubSpot CMS, WordPress, FilamentPHP, Streamlit, and the SEO/perf plumbing around them. I co-built a HubSpot dev tool that the core HubSpot team adopted into their own docs - that's the kind of cross-vendor depth a good SA needs.
Five years as a professional coach before I was a developer, plus years of agency selling. I can run an architecture deep-dive with the eng team and, an hour later, frame the same solution as business value for a CFO - leaving both pointed at the same target.
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.
- Laravel
- PHP
- VueJS
- AstroJS
- TypeScript
- React/JSX
- AWS
- Docker
- Claude
- REST API
- PostgreSQL
- FilamentPHP
Lovable Output Analyser
A web tool created with Lovable that allows users to analyse a GitHub repository's codebase and rank it for maintainability and complexity.
AI Skill: Create MVP
Productized my consulting methodology as a Claude Code skill - discovery → planning → implementation, resumable across sessions.
SAVR - Operability Tools
Three production operability tools at SAVR (Stockholm fintech) - FilamentPHP admin panels for the data and customer-service teams, plus a Streamlit data-analysis tool for the analyst team.
Lovable Prompt Builder
A web tool helping Lovable users craft better prompts - built using my own Create MVP methodology skill, demonstrating the enablement-first approach.
SAVR - Delta Ingestion System
Delta-based re-architecture of the ingestion pipeline at SAVR (Stockholm fintech) - replaced full-source pulls and significantly improved performance.
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.
-
TestDome · Top 10% - TestDome · Top 10%
- TestDome · Top 10%
- TestDome · Top 10%
- TestDome · Top 10%
- TestDome · Top 10%
- 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.
What I bring → What this role needs
Specific examples - each line connects something I've done to something this role calls for.
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 re-architected ingestion to significantly improve performance.
Built a developer tool inside another vendor's platform that they ended up referencing in their own docs.
Sold technical work to skeptical SMB owners against larger competitors.
Qualified the real problem, sized the solution, and carried the technical conversation alongside the commercial one.
Discovery, evaluation, PoC and deployment - owned end-to-end rather than thrown over a wall.
Case Studies
End-to-end engagements: problem → solution → build → outcome.
End-to-end ownership: read the actual problem, agree the solution, build it, ship the outcome.
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 operability tools - two FilamentPHP admin panels (data service + customer service) and a Streamlit data-analysis tool for the analyst team.
- 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
- The platform's ingestion pipeline from the key data source was a performance bottleneck - full-source pulls were costly and didn't scale with platform growth.
- Solution
- A delta-based re-architecture that fetched and applied only changed records, replacing the full-source pull approach.
- 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
- Ingestion performance significantly improved. The delta approach replaced full-source pulls on the 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 across nearly 4 years - full ownership of architecture, security, sprint delivery, and product strategy. Brought in a small temporary dev team for larger features.
- Outcome
- Now used across ~90% of Australia. Cashflow workflow significantly improved. 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.