Founders and product owners
AI Product Discovery
I turn a rough idea into a clear product plan: what to build, what to skip, and how to start safely.
View service: AI Product DiscoveryAI Product Engineer
I turn product ideas, manual workflows, and online store problems into planned, launched, and supported web products, coordinating extra specialists only when truly needed.
- Plan → build → launch
- Products and workflows
- AI and specialists when needed
Direct technical ownership
One responsible partner keeps scope, code, launch, support, and any needed specialists connected.
Services
Choose the kind of help you need now.
Start with a clear plan, a build sprint, automation, an eCommerce improvement, or ongoing technical support.
Founders and small businesses
MVP Build Sprint
I build a focused working product slice that users or your team can actually try.
View service: MVP Build SprintSmall businesses
AI Business Automation
I help reduce repetitive manual work with simple internal tools, automation, and AI where it is useful.
View service: AI Business AutomationOnline store owners and teams
eCommerce Platform Support
I help improve online stores, admin workflows, integrations, speed, and product content processes across legacy and modern stacks.
View service: eCommerce Platform SupportOwners and agencies
Support Retainer
I provide ongoing technical support for launched products, online stores, internal tools, and automations.
View service: Support RetainerProcess
A simple path from unclear idea to working product.
First we narrow the useful next step. Then I build, stabilize, and decide what to ship, skip, or hand to a specialist.
01
Clarify
I understand the business goal, who will use the product, what problem it solves, and what the smallest useful next step should be.
02
Scope
I turn uncertainty into a clear scope, technical direction, task list, and success criteria.
03
Build
I build the interface, logic, integrations, AI-supported parts, and launch path needed for a useful release.
04
Stabilize
I add checks, documentation, handover notes, support options, and a realistic plan for the next improvements.
A leaner way to build focused products
Why work with one technical partner instead of a large delivery setup?
For many early products, internal tools, and AI-assisted workflows, the expensive part is not only writing code. It is coordination, handoffs, meetings, review loops, launch queues, and rework. A smaller delivery model keeps the business goal, decisions, and implementation closer together.
01
Typical agency delivery
- Multiple roles between the client and the code.
- Context moves between people, tickets, meetings and handoffs.
- Senior expertise may appear in planning, while execution can be delegated.
- AI tools may still be used, but accountability can be distributed across the chain.
02
Direct technical ownership
- One accountable person owns discovery, architecture, implementation and delivery.
- Fewer handoffs and less context loss.
- AI agents are used openly as acceleration tools, with senior review and quality gates.
- Testing, launch work, documentation and support stay close to implementation.
Agencies can be the right choice for large enterprise programs or projects that need many parallel specialists. This model is built for focused products where speed, clarity and direct ownership matter more than a large delivery structure.
Less overhead. More technical ownership.
01
One accountable builder
The person planning the system stays close to the code, launch, and support. Context does not travel through a long chain before work happens.
02
Lower coordination overhead
Less time is spent translating business intent through tickets, meetings and handoffs. More effort goes into implementation, validation and useful product decisions.
03
AI-assisted, but not AI-blind
AI agents speed up code drafts, refactoring, tests and documentation. Engineering judgment still controls architecture, security, edge cases and launch readiness.
04
Faster feedback loops
When discovery, development, testing and deployment are close together, small corrections do not need to travel through a long delivery chain.
05
Built for focused product economics
Focused products should validate value before carrying the cost structure of a large team. The goal is a working, maintainable product path, not process for the sake of process.
How I work
- Clear scope before implementation.
- Small deliverable milestones.
- Transparent trade-offs.
- Automated tests where they protect business-critical behavior.
- No fake certainty: risks and unknowns are called out early.
Need a compact technical partner for your product, workflow, or internal tool?
Send the idea. I will help clarify the scope, risks and useful next step before writing unnecessary code.
No vague sales call. First step: understand what should be built, what should be skipped and what can be validated first.
AI with responsibility
AI should shorten the work, not blur accountability.
I use AI for research, code drafts, refactoring, tests, and documentation while keeping scope, architecture, quality, and launch decisions explicit.
Controlled acceleration01-04
01
Research
options, risks
02
Draft
code, content
03
Review
architecture, edge cases
04
Ship
tests, docs, support
Direct technical ownership
You work with the person who plans and builds the product.
The value is not just writing code faster. The value is keeping the product goal, budget, technical choices, launch, and support under one responsible owner.
ScopeBuildLaunchSupport
Experience before the AI wave
12+ years across CMS, eCommerce, Magento modernization, teaching, and AI products.
My advantage is not one narrow stack. I have seen many stages of the web in production: early CMS builds, high-volume store support, platform migrations, frontend teaching, and newer AI-assisted products built from zero.
50+
WordPress projects across business sites, catalogs, landing pages, and custom themes
20+
OpenCart projects, store fixes, catalog work, integrations, and eCommerce improvements
5+
years with large Magento eCommerce projects on the DE and NL markets
4 AI
AI product projects started from zero, from product framing to working implementation
Platform breadth without platform bias
WordPress, OpenCart, Joomla, Drupal, Magento, WooCommerce, and custom PHP work help me read existing systems quickly. I can support or modernize them without treating legacy choices as the default for new products.
Magento depth in real commerce
My recent background includes 5+ years of feature development and continuous support for large Magento stores in European eCommerce, including 6 Luma to Hyva migrations.
Teaching sharpens communication
2+ years teaching frontend courses trained me to explain complex technical choices clearly. That matters when clients need practical business decisions, not hidden implementation jargon.
Modern product builds
Next.jsReactTypeScriptTailwind CSSNode.js
CMS and eCommerce platforms
WordPressWooCommerceMagentoHyvaOpenCartDrupalJoomla
Magento modernization
Luma to HyvaFeature developmentStore supportPerformance fixesEU eCommerce
AI-assisted work
AI products from zeroAI agentsContent workflowsDocument processingTests
This background is useful because it combines production reality with modern product judgment: I know how older platforms fail, when they still make business sense, and when a leaner stack is the better path.
Stack
Modern build stack for product delivery.
Build stack
Current tools for new web products, automation, and support.
These are the tools I prefer for new work. WordPress, Magento, OpenCart, Drupal, Joomla, and PHP remain platform experience for audits, support, and migrations, not the modern default.
Next.js/FrontendReact/FrontendTypeScript/LanguageTailwind CSS/Design systemZod/Content validationVitest/TestingPlaywright/E2ENode.js/RuntimeAI agents/Development workflow
Start with scope
Have a product idea, manual process, or online store problem?
Send the context. I will help define the next useful step before you spend money building the wrong thing.