Work With Me

What I offer is closer to execution partnership than implementation labor alone. I help shape the product and then take responsibility for moving it toward something real. That also includes reviewing current technology shifts and applying AI to product features or internal workflows where it creates practical value.

Published products live on Services.

Ways We Can Work Together

There are two main ways to work together. Build Partnership means I take the product through planning, launch, and operating baseline as one continuous flow. Technical Advisory means I bring an outside perspective to decisions, structure, and technology choices when you already have an internal team or aren’t ready to commit to a full build. If you’re not sure which fits, we sort it out in the first conversation.

Build Partnership

Taking the product end to end — from planning through launch and operations. Closer to a partnership than to outsourced delivery; I share responsibility for execution and outcome.

Quick Bug Fixes & Short Dev Tasks

Small jobs that need hands on the keyboard right away, with no review or diagnostic phase. Bug fixes, small feature additions, operational hotfixes, or one-off debugging. (VAT excluded)

Best used when — your internal team is booked on other work, or you need a single short, well-defined task closed by an outside hand.

Typical deliverables

• Pull request or patch
• Summary of changes and impact area
• Brief follow-up notes for prevention (when relevant)

Anything that runs longer than about two hours is quoted separately.

0 to 1 Product Build Partnership

I support the full flow from early structure and implementation through launch and operating baseline.

Best used when — you want a partner-like build relationship instead of simple ticket delivery.

Typical deliverables

• Product structure design
• Web, mobile, and backend implementation
• Deployment and operating setup
• Post-launch improvement baseline

Service Redesign and Information Architecture

When an existing product has become hard to navigate or convert through, I help restructure it.

Best used when — teams know a redesign is needed but have not yet clarified where to begin.

Typical deliverables

• Current structure diagnosis
• Revised user flow and information architecture
• Screen and feature reprioritization
• Phased improvement plan

Technical Advisory

When you aren’t ready for a full build or already have an internal team, I work as an outside reviewer on product, structure, and technology decisions. Available as one-off reviews or recurring engagements.

Product Review

A close, outside-eye look at the user flow, UX, and information architecture of a product that has already shipped or is in production. I map where users drop off, where flows stretch too long, and how to prioritize the next round of fixes.

Best used when — the team has a vague sense that something is off in a live product, or wants an outside view to set the next quarter’s improvement priorities.

Typical deliverables

• Friction points in UX and user flow
• Information architecture and key path review
• Conversion and drop-off hypotheses with verification priorities
• Separation of quick wins vs. medium-term work

If you also want a technical view, pair it with Code Review so the technical root causes of product problems are connected as well.

Code Review

An outside-eye review of an existing codebase — quality, architecture, and operational risk. Not stylistic nitpicks, but the structural risks that will hold the team back long-term and the technical debt that should be paid down soon, prioritized.

Best used when — you want an objective read on a codebase that was shipped quickly or that you’ve inherited, or when an outside review is needed before the next big change.

Typical deliverables

• Code quality and architectural risk findings
• Performance, operations, and security review notes
• Test coverage and deployment pipeline review
• Prioritized list of improvement items

If you also want the user-facing view, pair it with Product Review so the user impact of technical debt is connected as well.

Product Strategy and Technical Architecture Review

I review what should be built first and how it should be implemented, including where new technology or AI may actually help.

Best used when — teams need product and technical decision-making evaluated together.

Typical deliverables

• Scope and priority review
• Architecture and operational risk review
• AI and automation opportunity review
• Implementation strategy notes
• Recommended next steps

MVP Planning and Product Structure

When the idea exists but the first version is still vague, I turn it into a workable product plan.

Best used when — founders and early teams need alignment on direction and scope before building.

Typical deliverables

• Problem framing and core user hypotheses
• Product structure and key user flows
• MVP scope and feature priorities
• Technical risk notes for implementation

How I Work

1. Reframe the problem first

I do not jump straight from request to build task. I start by aligning on the actual user problem and service goal.

2. Make the MVP boundary explicit

I separate what belongs in version one from what can wait, so the first release has focus.

3. Design structure and execution together

User flow, information structure, and technical structure are treated as parts of the same product.

4. Leave a useful decision baseline after launch

I want the product team to leave with operating points and a clear basis for the next decisions.

If you have a project in mind, reach out via Contact. To see what I’ve shipped, visit Services.