AI product delivery & team collaboration
Give a useful AI feature a place in your product.
I work with founders and product teams to find a useful role for AI and build it into the experience. We can test a first idea, take a feature through integration or define ongoing involvement alongside your team.
01 / Ways to work together
A clear goal. The right involvement.
Deliver a project
Choose one customer or internal task, test a working feature and decide what deserves integration. We agree how to judge usefulness before expanding the build.
- A focused use case and evaluation criteria
- A working feature with representative data
- Interaction, review and fallback behavior
- An integration and operating plan for the agreed stage
Join your team
Bring product thinking, interaction design and AI integration into your team's work. I can take a defined feature area from opportunity through implementation while sharing decisions with your product and engineering leads.
- An agreed feature area and delivery responsibilities
- Prototypes and implementation in your product context
- Quality, failure-case and cost reviews
- Documented decisions and an agreed maintenance owner
02 / The first milestone
Something concrete to review together.
Put one useful interaction in someone's hands. Review output quality, how people steer it and what happens when it fails, then decide the next integration step.
What we need from you
- A product walkthrough and the people who understand its users.
- Examples of the task and representative data we are permitted to use.
- A product and technical contact to agree integration, access and evaluation.
03 / Relevant experience
Work in its actual context.
RoadTrippin – Collaborative Road Trip Planner ↗
FUERST.ONE, Hobby
Product screenshot
Editable itinerary and route map
Automatically generated image description
This is a screenshot of a travel route planning application showing a Balkan trip itinerary with 9 stops. The left panel lists stops with dates, distances, durations, and estimated costs, including Würzburg, Linz, Vienna, Budapest, Siófok, Belgrade, and Sarajevo. The main section displays a map of Central and Southeast Europe with a red route line connecting these cities, marked by numbered circles. The top bar includes options like Share, Export, and Settings. An AI Assistant panel on the right offers trip modification and route optimization features. The interface uses white, orange, and gray colors.
Konfig – Product Design Configurator ↗
Arider · Konfig
Product screenshot
Decal editor and product parts
Automatically generated image description
This is a screenshot of a graphic design application interface for customizing motorcycle decals. The central area shows two symmetrical black and neon yellow decal designs with sharp angular patterns and text elements like 'SMCR' and a logo. The left sidebar lists decal parts such as 'Frontfender,' 'Gabelprotektoren,' and 'Heck,' each with a small preview and 'HINZUGEFÜGT' status. The right sidebar displays layer controls labeled 'Pfad' and color editing options with a neon yellow background color selected. The top bar includes a search box and language selector, while the bottom bar shows options for help, design, sharing, saving, and a shopping cart button with a price and delivery date.
04 / Practical questions
Before we work together.
Do we need to start with a review or assessment?
No. If the goal and starting point are clear, we can agree a delivery milestone or team involvement directly. A review or assessment helps when you first need an independent basis for the decision.
How much involvement do you need from us?
We need a contact who can make product decisions and access to the relevant technical knowledge. We plan the walkthrough, access, feedback and acceptance together, agreeing a review rhythm that fits your scope.
What determines effort, fee and start date?
Effort depends on the task, data access, quality requirements and integration depth. We also consider model costs and evaluation needs before agreeing scope, fee and schedule.
What does the handover include?
We agree the handover before implementation: relevant designs and code, setup and operating notes, open issues and a walkthrough with the people continuing the work. Your existing tools and process shape the format.
Who handles operation and maintenance afterward?
We establish responsibility for operation, monitoring, changes and fixes before handover. Your team can take over, or we can agree further involvement. Ongoing maintenance scope and availability are explicitly agreed.
What needs to work next?
A short introduction to your product, task and team is enough to start. We establish responsibilities, scope and fee together.