Web design & web apps in IngolstadtWebsites and appsyou actually own.

I design and build the site, connect it to the tools you already use, and hand over the repo and the documentation — so you're never locked into the person who built it. Based in Ingolstadt, working with small businesses across Germany.

AnyonecangetawebsiteoutofanAIinanafternoon.Thehardpartiseverythingafter:whetheritranks,whetherit'ssecure,whetheritstilllookslikeitbelongstoaseriousbusinessinayear.Ibuildtheversionthatholdsup—thenteachyoutorunit.

03Services

What I build

Three ways in. Most people start with the first one.

  • Fast, secure, and built to rank — the kind of site that still looks like it belongs to a serious business in two years. Connected to the tools you already use, and built so you can keep it current yourself.

    • Built to rank
    • Secure by default
    • Yours to edit
    Websites: details and pricing
  • When a website isn't enough: customer portals, booking systems, internal tools. Logins, a database, and the integrations behind them, built around how your business actually works.

    • Logins and accounts
    • Your own data
    • iOS when you need it
    Web and mobile apps: details and pricing
  • Updates, security fixes, backups and small edits, for a fixed monthly price. So the site stays fast and current without you having to think about it.

    • Security updates
    • Small edits included
    • Cancel monthly
    Care plan: details and pricing

04Process

How I work

Four steps, around 40 hours for a typical project, and you're in the loop the whole way.

  1. Listen

    I ask more questions than you're expecting. A one-line brief almost always hides the real problem, and finding it is worth more than starting a week sooner.

  2. Decide together

    I come back with options and a recommendation. We agree what's in scope and what isn't before anything gets built.

  3. Build

    It gets built properly — search, security, and performance handled as part of the work rather than sold back to you afterwards.

  4. Hand over

    You get the repo, the documentation, and training for your team if you want it. Or I stay on a care plan and keep it current. Your call, not mine.

05Work

What I've built

Products I designed and built end to end. Client work is next — I'm taking on a small number of founding projects at a reduced rate.

ProductFull-stack

Feedlify

A feedback platform that collects customer requests from everywhere they land, uses AI to merge the duplicates, and tells people when their request ships. Designed and built solo — interface, database, auth, integrations, error tracking.

Launching 2026

Read the case study: Feedlify
WebsiteNext.js

pakarinen.de

This site. A WebGL hero, 3D scroll sections, a strict content security policy, and a CI pipeline that blocks its own merges on failing tests or new vulnerabilities. Built to be the proof rather than to describe it.

You're looking at it

iOSAI

Tools my family and friends use

iOS apps in daily use, and a tool I'm building to get my German to C1. This is where I try things and get them wrong, so that it doesn't happen on a client's project.

In daily use

06Handover

What you walk away with

The repo

In your account, under your name. Not held hostage in mine.

Documentation you'll actually read

Plain language, written for whoever inherits this after you.

A site that gets found

Search and AI-assistant visibility handled during the build, not sold back to you later.

Security handled quietly

Headers, dependencies, and access reviewed as part of the job rather than as an upsell.

A team that can run it

Training until they're comfortable doing it without me.

Me, still around

On a care plan if you'd rather not maintain it yourself. Optional, never assumed.

07About

About

I'm Johan — a Swede in Ingolstadt, Germany, building websites and apps for small businesses.

Seven years in tech, which started with a six-month coding bootcamp and a support desk at a B2B SaaS company. I was promoted to Product Owner there, and that turned out to be the most useful thing that could have happened to me: it taught me that the feature someone asks for is rarely the thing they actually need.

That's still how I work. I ask a lot of questions before I write anything, because the gold is almost never in the first sentence of the brief.

I've spent the last few years using AI in practice rather than reading about it — building things, breaking them, and learning where it genuinely helps and where it quietly creates problems later. I'd rather make those mistakes on my own projects than on yours.

Outside of work: a wife, three kids, padel, and more side projects than I can reasonably justify.

ClaudeClaude
Next.jsNext.js
ReactReact
shadcn/ui
Supabase
VercelVercel
Sentry

Let's find out whether this is worth doing.

Tell me what you need built, or what's wrong with the site you have. I'll reply by email, and if it's worth talking through, we'll set up a free 30-minute call. No charge and no obligation.

What do you need help with?

Your details are emailed to me through Resend and used only to reply to you. Privacy policy (in German)

I'm taking on a small number of founding projects at a reduced rate, in exchange for an honest case study at the end.