Jonas ForshellSenior Product Owner
jonas@jforshell.seEmail me

Fourteen examples

Everything, with what it was worth written next to it

Six of these shipped while I held a product role. Six I built on my own time. Two I did just for practice.

The fraud investigation solutionRead more →King · Product and operations · 2015 to 2018 · QlikViewThe signals were already in the data. No developer resources were available to build against them, so I designed the investigation view and a QlikView specialist implemented it.40%less player-account fraudaround 50 support hours a month freed
Payout handling, three clicks to oneKing · Payout operations · 2016Approved withdrawals still needed three repeated actions after the safety checks were done. The checking stayed exactly as it was. The repetition went.3 → 1repeated actions per withdrawalroughly 600 to 1,000 clicks a day removed
Decision support for fraud escalationsKing · Support and fraud operations · 2017First line support decided case by case whether something needed fraud review. The same case could come back with a different answer depending on who picked it up.Same answerwhoever picks up the case45% less processing time, errors and needless escalations
Direct debit, two fields to oneRead more →Lendo · Insurance · 2023 to 2025Insurance customers who set up direct debit at signup kept their insurance far more often. The form asked for the account number in two fields, and Swedish bank apps hand over one.~10%more completed direct-debit signupsno integration built, on purposeStatistics dashboard, repackaged for handoverRead more →Clearon · Digital Platform · 2026A dashboard of pie charts nobody could read a trend from, and no spare design or frontend capacity to fix it. I prototyped the replacement from the backend API contract.1 speca working package, not a wishno discovery slot needed
Gift card shipment calculatorClearon · Customer Success · 2026I saw Customer Success splitting large gift card orders by hand on an onboarding tour in week three. Every envelope had to stay under the 5,000 kronor insured value, and the arithmetic was theirs to do.0 mathsdone by hand per shipmentnothing over the limit by accident

AI builds. Claude and Codex wrote essentially all the code. The scope, the decisions and the testing are mine.

Archive LensRead more →Historical photograph catalogue · 2026 · React, FastAPI, Supabase, Cloud RunA searchable catalogue for a friend's photograph collection. Originals stay in Google Drive. OCR suggests, a person approves, and only approved records reach the catalogue.Working buildUser testingIn user testing with the person I built it for.Feedback goes straight back inResume BuilderRead more →CV document tool · 2026A structured CV editor that keeps reusable content separate from layout, with fast previews while editing and a rendered PDF check before export.LiveIn production. I use it myself,and a few select friendsVard CRMRead more →CRM for a freelance photographer · 2026A narrow CRM built around one freelance photographer's actual workflow rather than a general feature set.Never usedFinished for a friend.He got employed before he needed itNews AgentRead more →AI news curation agent · 2026 · Python, FastAPI, PostgreSQL, OpenAIAI agents wrote the code. I set the spending caps, made the decisions, and checked the AI's news judgement against my own. Closed once I had learned what I set out to learn.ClosedA handful of sessions, closed on purpose.The learning stayed, the product wentJob MatcherRead more →AI job-ad scorer · 2026 · Next.js, OpenRouterAI agents built it, and I taught it what I want. A scorer that reads job ads and predicts my interest, tuned against 188 of my own ratings. The job boards, not the AI, turned out to be the hard part.ClosedTwo days, closed on purpose.The rulebook and the eval lessons keep the valueThis websiteRead more →Personal site · 2026Built from scratch as a working product rather than a brochure, and used to test tone, structure and delivery thinking on something I own.LiveStill changing whileI use it for my own job search

A note on this list

Three of these were never used by anyone and two were closed on purpose. They stay because a portfolio that only shows the wins is an advert. The useful question is what each one was for and what it changed.

Building them has also grown my respect for developers, because the parts I cannot check myself, architecture and security and what the code will cost to change, are exactly where their judgement lives.