AI-native products
AI not just as a feature, but at the core of the product — starting with whether it pays off in production.
I build software that has to pay for itself.
For agencies that need build capacity, and for teams bringing something new to market.
In weeks, not quarters. Fixed scope, fixed price, fixed delivery date.
Book a 15-minute call
You'll come away knowing whether it's a fit — and what it costs.
After the click
Campaigns often die on the landing page rather than on the ads.
The ad makes the promise. The landing page has to deliver on it.
Ad
Landing page
Why me
3 years in online marketing.Then 6 years in software development.
01
Performance marketing at Smarketer
At a leading Google Ads agency, I managed Google and YouTube campaigns with six-figure monthly budgets — finishing my time there as team lead.
02
Software development at Finanzfluss
At one of the largest personal-finance platforms in the German-speaking market, I worked in a very small team and led the development of its ETF search — from the Rails API to the frontend.
How I work
AI-assisted from the first line to the last — and at no point without me.
Responsibility
Stays entirely with me. AI takes on tasks, not responsibility.
Cutting scope
AI helps me run through options and produce quick mock-ups. What belongs in version one and what comes after is my call — that is what keeps the promised delivery date realistic.
Writing and rebuilding
AI handles most of the execution here. That shortens implementation — not the agreed scope.
Reviewing
System checks wherever they make sense. Before anything ships, I review it personally.
What I build
The largest of them is an AI-native product.
Web applications
Frontends in React or Vue, and everything running behind them. Typically three to six weeks.
Backends, APIs and integrations
Data models, interfaces, connections to CRM and third-party systems, automation with n8n.
Landing pages and funnels
Fast, cleanly tracked, built for paid traffic. Typically one to two weeks.
Who I work with
Agencies
Build capacity when your calendar is full and your client is sticking to a fixed date. If you want, I work entirely in the background: under your name, in your design, with all communication running through you.
Startups and new products
From the first idea to a focused MVP that enables early feedback from real users — including the decision about what can wait.
Companies with one specific project
An application, an integration, a process that ought to be automated. Clearly bounded, with an end date.
How the work runs
No weeks of silence.
A 15-minute call
What needs building, by when, and what systems it has to talk to.
A quote, usually the next working day
Scope, fixed price, delivery date. In writing, before anything is agreed.
The build
A fixed weekly checkpoint.
Handover
The code is yours, the deployment is live, the documentation comes with it. Maintenance afterwards if you want it, or further work as it comes up.
Common questions
Including the one about price.
- What does a project cost?
- It depends on the scope, which is why there's no number here. After the call you get a fixed price and a delivery date — usually the next working day, once the scope is clear. No timesheets, and nothing billed on top for anything that was agreed beforehand.
- Do you work under the agency's name?
- Yes — white label is the normal case. If you want it, all communication runs through you and I don't appear in front of the client at all.
- What happens if the scope changes?
- Changes are quoted separately, with their own price and their own date. That's precisely what makes fixed prices work.
- Who owns the code?
- You do, in full, after the final payment — including every repository and every access credential.
- What do you work with?
- I'll pick up an existing stack where it holds up. Otherwise TypeScript: React or Vue on the front end, Node or Rails behind it, Postgres, Cloudflare or your own servers, automation with n8n.
Next step
Fifteen minutes is enough for scope, timing and systems.
I can currently start within a few days.
Prefer to write? felix@felixnagel.dev