When product teams bring me in
The roadmap is moving faster than the team
The priorities are clear, but internal capacity is already committed. I join the existing workflow, become productive quickly, and take ownership of a meaningful part of the backlog — without forcing the team to reorganize around me.
A complex initiative needs senior depth
An upgrade, integration, inherited platform or architectural decision carries more risk than an ordinary feature. I clarify the requirements, identify the technical tradeoffs, and carry the work through implementation, testing and release.
Technical ownership across teams
A workstream crosses product, engineering and commercial stakeholders and needs someone senior enough to clarify requirements, make decisions and carry it through testing and release.
How I work inside your team
I work as an embedded member of the team rather than as an isolated external supplier. I join the planning, stand-ups and reviews that help delivery, work within your repositories and tooling, and collaborate directly with developers, product managers, designers and commercial stakeholders.
I work within your repositories, tooling and delivery process.
I contribute to requirements and technical decisions instead of merely accepting tickets.
I take ownership of agreed outcomes and surface risks early.
I deliver in reviewable increments rather than disappearing until a large release.
I document decisions and implementation details where they matter.
You work directly with me — there is no account-management layer and no junior team operating behind the scenes.
What I can own
Every engagement is different. I can take responsibility for a defined workstream or bring specialist depth to a broader product initiative—from technical discovery and architecture through implementation, release and handover. Typical areas include:
.NET and Umbraco development — new functionality, reusable components, editorial tooling.
Upgrades and platform modernization, including Umbraco 13–17 migrations.
APIs and system integrations — CRM, product data, analytics, email automation and customer journeys.
Technical discovery and architecture, turning a loosely defined requirement into a practical technical approach.
Performance, accessibility and technical SEO.
Stabilizing inherited platforms without proposing an unnecessary rebuild.
Modernizing code base
When the work touches CRM, analytics, email automation or lead capture, I can work directly with the commercial stakeholders instead of requiring someone else to translate the requirement into technical language.
Technical depth with commercial context
Product development is rarely just a technical exercise. Priorities come from customers, operations, sales and marketing, and the strongest implementation is useless if it solves the wrong problem or creates more work elsewhere in the organization.
Over the last eight years, I have worked directly with senior sales and marketing stakeholders on websites, CRM processes, analytics, automated communications, free-trial journeys and customer-facing integrations. That experience helps me understand why something is being built—not only what the technical specification says.
I can discuss architecture with developers, customer journeys with product managers and commercial consequences with management. The result is less translation, fewer assumptions and a shorter path from objective to working software.
Proven where technical and commercial priorities meet
Product ownership from architecture to production — KindbergCo Platform, 2025 - 2026
Designed, built and continue to maintain my own production-ready Umbraco Platform. The work covers architecture, reusable components, multilingual content, performance, accessibility, technical SEO, security, editorial tooling, documentation and commercial packaging.
It is both a product and the foundation running this website—so I remain responsible for the decisions long after the first release.
Five years of continuous platform development — Infront, 2018–2023
At Infront, I spent five years taking direct responsibility for the company’s web platform while working closely with its Global Head of Sales and Global Head of Marketing.
The engagement included a complete rebrand, ongoing CMS development, campaign requirements, free-trial journeys, CRM integrations, analytics and connections between the website and the company’s financial technology platform.
This was not a website handed over after launch. It was a business platform developed continuously as the company, its positioning and its commercial requirements evolved.
That is the kind of relationship I am best suited to: close enough to understand the business, senior enough to work independently and accountable for what is delivered.
Product architecture from the ground up — Epteca, 2011–2013
Built the foundational architecture for a travel-related data and communications platform, working closely with the CEO to translate the company vision into a practical technical direction. The work included complex data integrations, personalized customer communications and coordination of outsourced development.
How we work together
Full-time embedded capacity
I join your product or engineering team at full-time capacity, working within the same processes, tooling and expectations as your permanent developers. The engagement is open-ended and continues for as long as the capacity is needed, typically with one month's notice on either side.
This gives you stable senior capacity without committing to permanent headcount or having to predict an exact end date upfront.
Defined product initiative
I take ownership of a clearly scoped initiative—such as an upgrade, platform modernization, custom integration or inherited-system stabilization—and carry it from discovery through implementation, release and handover.
This works well when you need concentrated senior ownership for a specific outcome without adding another developer across the wider roadmap.
Interim technical ownership
I take responsibility for a platform or workstream during recruitment, organizational change, parental leave or another transition, keeping technical decisions and delivery moving while the permanent team changes around it.
This works well when the product cannot pause while you search for the right long-term person or restructure internal ownership.
Pricing depends on scope, capacity and duration — I’ll quote based on the specifics of the engagement once we’ve talked it through.
Tell me about the gap in your team
Send me your current stack, the outcome you need, where delivery is blocked and your expected start date. I’ll respond within one business day, tell you honestly whether I’m a strong fit, and what I’d need to get started. Client details can stay confidential at this stage, and NDAs are welcome.