What you can commission here
Three offers. Each one states who it is for, how it runs, and which completed project evidences it. Where there is no evidence, none is claimed — that is deliberate.
Website & findability
Your website exists but customers don't find it. I look for the cause first — it usually sits in the technology, not the marketing — and fix it verifiably: load time, structure, local visibility, and a machine-readable description for Google and AI search.
Who it's for
Local businesses and independent professionals with an existing website, usually WordPress, who rank behind their competitors and don't know why.
How it runs
- Audit: name the causes before any work is commissioned, with scope and effort
- Repair the foundation: plugin conflicts, load time, duplicates, crawl hygiene
- Content and structure: distinct text per landing page, not swapped place names
- Make it machine-readable: Schema.org markup for Google and answer engines
- Hand over documentation complete enough to run the site without me
Frequently asked
- What does it cost to make a website findable?
- It depends on how much legacy sits in the system, and that can only be answered honestly after an audit. One completed project of this kind took roughly 50 hours across twelve stages. That is why the audit always comes first and states the scope before you commission any work.
- Why is my SEO plugin not doing anything?
- The most common cause in practice: a second plugin is working against it. When two SEO plugins are active at once, one controls robots.txt, the sitemap and the meta tags while the other emits nothing — so everything you maintain in the backend never reaches the page. Other frequent causes are bloated markup from page builders and subpages that are copies of one another.
- What is GEO and do I need it?
- GEO refers to being found by answer engines such as ChatGPT, Perplexity and Gemini. They preferentially cite pages that are clearly structured, answer concrete questions up front, and describe in machine-readable form who you are. The work largely overlaps with classic SEO — so it comes along anyway when the job is done properly.
- Do you maintain the site afterwards?
- If you want me to, yes. A clean handover is just as explicitly available: you receive documentation with a technical reference for every setting and separate task lists. A website only its developer understands is a dependency, not a result.
Custom software, built and operated
A web application for your problem — and no abandonment afterwards. I build from concept through to production: payments, user accounts, protected content, integrations. Deployment, TLS, backups and monitoring are part of it, not a separate offer.
Who it's for
Independent professionals and small businesses whose requirement no off-the-shelf product covers, and who don't want to hire a second contractor just to keep it running.
How it runs
- Scope it: test the riskiest assumption first, not the biggest feature first
- Record decisions in writing, with the alternatives and the reasoning
- Ship in stages, each one runnable and acceptable on its own
- Take it live: deployment pipeline, TLS, backups, monitoring
- Keep running it or hand it over cleanly — your call, not mine
Evidenced by
Frequently asked
- What does a custom web application cost?
- That can only be answered honestly once the scope is set. The real lever is elsewhere anyway: the most expensive mistake is not a high hourly rate but six months of work in the wrong direction. So the first question is which assumption is riskiest — and that one gets tested first.
- Why not use an existing platform or a site builder?
- If an off-the-shelf product covers your requirement, you should use it — and I will tell you so. Custom development pays off when the fit is what matters: your own workflows, your own data ownership, integrations a builder cannot offer, or per-user running costs that become uncomfortable as you grow.
- Who runs the application after launch?
- By default I do. Four systems currently run in production under my responsibility, with Docker, TLS, automated deployments, backups and uptime monitoring. If you want to take operations in-house, that is planned for and documented — there is no lock-in.
- How do you handle GDPR and payments?
- As part of the build, not as an afterthought. Concretely: deletion paths for user data from the start, data processing agreements with the providers actually used, EU hosting where possible, and payment handling through an established provider rather than something home-grown.
Mobile app development
Native Android and cross-platform apps with Flutter — from first idea to the Play Store. Including the parts that get underestimated: store submission, privacy declarations, permission rationales, and what happens when the network drops.
Who it's for
Businesses and independent professionals who need an app as a product in its own right, or as mobile access to an existing system.
How it runs
- Settle the platform question: does this really need an app, or will the web do?
- Interaction concept before code — an HCI background rather than gut feel
- Build with tests for the logic and screenshot comparison for the interface
- Store submission including privacy declarations and permission rationales
- Updates and maintenance after release
Frequently asked
- Do I even need an app?
- Often not. If your users should reach the application through a link without installing anything, the web is almost always the better route — instantly reachable, no store review, no second codebase. An app pays off with genuine offline needs, hardware access such as camera or sensors, push notifications, or when an icon on the home screen is part of the product. I ask this before quoting, not after.
- Flutter or native?
- Flutter when both platforms need serving and the interface is the bulk of the work — one codebase instead of two. Native when deep platform integration or maximum performance in specific cases matters. I decide based on your case and write down the reasoning.
- Do you take over existing apps?
- Yes, starting with an honest assessment. Sometimes continuing is right, sometimes a rebuild is — and I will say the latter even when it is inconvenient. I have made that call against my own codebase.