The new pfisterer.digital: a website you use like a phone
pfisterer.digital is now an AI boutique built as a phone: lock screen, apps, a lab of in-house tools, and every AI image labelled one by one. A look inside.
Open pfisterer.digital on your phone and the first thing you see is a lock screen: the time, the date, a few notifications. Swipe up and the home screen with its apps appears. Since 26 October 2026 this is the new version of my second website.

From local agency to AI boutique
Until now pfisterer.digital stood for websites and digital basics for small businesses in the Hunsrück region. The rebuild changes the positioning. The site now describes a boutique practice: few engagements, deep work, one person accountable. One of the notes on the site gives the reason. Most projects hinge on details, and you only see those up close.
The scope matches what I offer on pfisterer.xyz: AI automation and in-house tools sit next to ERP migration, e-invoicing with DATEV, reporting as well as compliance. pfisterer.digital tells it in fewer words and shows more of the workshop.
How the site works
On a smartphone you get a phone with a lock screen and a home screen. On a desktop the apps open as windows, with a dock along the bottom. Each app answers a question a prospect would otherwise ask in a first call:
- The Lab lists in-house tools with an honest status. E-invoicing is marked “in use”, the DATEV bridge “in development”, pre-coding and the KPI board “prototype”, the deadline watcher “idea”.
- Haltung (principles) holds four rules I want to be measured by: standard software first, no autopilot, measurable or gone, one person accountable.
- The calendar has a month view and a button to request a meeting.
- In Notizen (notes) visitors can leave a message. The latest one shows up at the top of the lock screen.
- Rechtliches (legal) collects the imprint and privacy policy, plus the AI transparency notice.
Behind the home screen runs a custom 3D scene built with three.js. Everything is plain JavaScript without a framework. The endpoint for notes and meeting requests is a small PHP script at the hosting provider. The 3D view of the screenshots above also runs on three.js, loaded from this server with no external CDN.
The model: studied, not copied
The phone idea is not mine. It comes from frvky.online, a portfolio site that works the same way. I looked closely at how it is built: how the lock screen reacts, how windows and dock behave, which data goes where. From that I wrote my own specification, and I built against that specification from scratch.
Code and copy are my own, as are icons and images. I did not take over any third-party files. The same order of work, understand first, specify second, build third, is how I approach client projects that replace an existing system.
Every AI image labelled on its own
AI tools sit in many corners of pfisterer.digital. Images come from Google Gemini, copy was drafted with Claude, code was written with OpenCode and Claude Code. That is why every image carries its own label, either “AI-generated, not a real photo” or “real photo, edited with AI”. The same information is machine-readable in ai.txt, in llms.txt and as metadata in the image files themselves.
Behind it is an internal process with a checklist and an asset register. Before anything is published, each image and text gets a note on how much AI went into it, and it only goes live after sign-off. Public photo uploads through the camera app stay closed until a human review step is in place. How I handle this on pfisterer.xyz is described in the AI transparency notice.
The case against a phone-style website
The obvious objection: it is a gimmick. Part of that is fair. The content is rendered by JavaScript, and a classic site with subpages is easier for search engines to read. If you want to win visitors through Google, a conventional structure serves you better.
That is exactly why pfisterer.xyz stays as it is. The articles, whitepapers and service pages that need to be found live here. pfisterer.digital has a different job. It is the page someone opens after a conversation or from a link, and it shows in two minutes how I work. For AI search systems there is also an llms.txt that describes the content in plain text.
What you can take away for your own projects
A good model is a requirements document, not a copy order. If you want to rebuild or replace an existing system, first write down what it does, then build on your own terms. That holds for a website as much as for an ERP interface.
Labelling is a process, not a banner. A line in the footer is not enough once a site carries dozens of images with different degrees of AI involvement. A register per asset and a sign-off before publishing cost little and stand up to scrutiny.
I described how a rebuild with AI works in practice once before, using this site as the example: Website relaunch with AI instead of an agency. If the goal is not a website but a tool of your own, that is a case for custom solutions and apps.
Frequently asked questions
What is pfisterer.digital?
pfisterer.digital is my second website. Since 26 October 2026 it presents an AI boutique: few engagements, deep work, one person accountable. Services, principles and in-house tools appear as apps on a recreated phone.
Was the site copied from another website?
No. The idea of a phone as the interface comes from frvky.online. I studied how that site is built, wrote my own specification from it and built everything from scratch. Code and copy are my own, as are icons and images. No third-party files were taken over.
How are AI images labelled on pfisterer.digital?
Every image carries its own label: either “AI-generated, not a real photo” or “real photo, edited with AI”. On top of that there is an AI page listing each image, machine-readable notes in ai.txt and llms.txt, and metadata inside the image files.
Does pfisterer.digital replace pfisterer.xyz?
No. pfisterer.xyz stays the main site with all services, the articles and the whitepapers. pfisterer.digital is the shop window for the boutique work and links back to pfisterer.xyz.
Next step
You want to build a tool of your own, or replace an existing system cleanly without cloning it blindly? In a first call we look together at whether standard software is enough or whether a custom solution pays off.
→ Or read more first: AI automation for mid-sized companies