Software & AI studio
We build websites, portals, integrations and AI for companies, and run them if you want us to. Two people, from the first sketch to the running system.
You do not have to pick a technology. Start at the sentence that fits you.
People find us, but too few of the right enquiries come in.
Presence, content and the way to an enquiry are built as one path, not as three parts.
Presence, content and the way to an enquiry from one team.
Portals and internal tools for exactly your workflow.
The complete conversation
“I would like to buy a rented apartment.”
14 September · 10:30
“Which other documents do you need from me?”
Enquiry, appointment, email and internal note belong to one client record. The next action is right there.
Interactive project excerpt with fictional data. Changes stay in this preview.
What stays gets connected. What is replaced, we build as a module inside your own system.
One system. Yours.
An assistant for the documents you have released, with a source for every answer.
§ 4 Warranty. Spare parts: 24 months from delivery. Wear parts: 12 months.
Chapter 9, downtime: note the error code, call the service line. Callback within 4 hours.
Recurring feeder downtime since commissioning. We request a prompt service visit.
Series 4, base module: €48,900 net. Feeder: €6,250. Lead time Series 4: 6 weeks from order.
114-021 conveyor belt 1,200 mm, stock 2. 114-034 inductive sensor, stock 8. 114-051 drive belt, stock 0.
Series 4 line with feeder and PLC control: €64,950 net. Lead time six weeks from order.
Belt 114-051 replaced, sensor calibrated. Follow-up check agreed in four weeks.
3.2 Approvals. Orders above €9,000 net: approval by the head of purchasing. Above €50,000, management approval as well.
§ 4 Warranty. Spare parts: 24 months from delivery. Wear parts: 12 months.
3.2 Approvals. Orders above €9,000 net: approval by the head of purchasing. Above €50,000, management approval as well.
Series 4, base module: €48,900 net. Feeder: €6,250. Lead time Series 4: 6 weeks from order.
Chapter 9, downtime: note the error code, call the service line. Callback within 4 hours.
The feeder has stopped. What now?
Note the error code and call the service line. Callback within 4 hours.Maintenance manual S4 · ch. 9
Your environment · privately runNothing leaves your environment.
Hosting, updates, backups and incidents from one team, with a report every month.
Backups run. Updates follow.
A backup counts when it can be restored.
We find the cause and test delivery again.
What is done. What stays open. What comes next.
It runs. And you know why.
Your data lives where you say, and no service sees it without your approval.
Where does your data live?
Your data lives in Germany.
Who may access it?
Your data lives in Germany. 2 of 3 services approved
Source code, data, access and documentation are yours from the start. Whether we keep running it or your team takes over is your call.
Current project state · fully traceable
Deliverables, source code, configuration, and documentation are handed over in an organised form rather than hidden with individuals.
Roles and handover points for approval, delivery, operations, and escalation are named together.
Four websites we built, each on the device it was designed for first. Each one leads to its case study.
From the first conversation you talk to the two people who build your system. We are based in Frankfurt am Main.
After every step there is something on the table that you can review.
Step 1
You tell us what should change and how things work today. We ask questions and say openly whether and how we can help.
From youAbout 30 minutes, by phone or video. You need no documents.
AfterwardsAn honest recommendation
Step 2
Before anything is built, we clarify scope, workflow and open questions. This is a separate, bounded engagement. What it covers is agreed in writing beforehand.
From youOne person who knows today’s workflow and answers our questions.
AfterwardsConcept & proposal
Step 3
We build stage by stage. After each stage you try a working version, not slides.
From youYour feedback on each version.
AfterwardsA version to try
Step 4
Your system goes live. Code, data and access belong to you. So you can choose: we run it for you, or we hand it over completely to your team or another provider.
From youOne person who gives approvals, for example for larger updates.
AfterwardsOperations plan and monthly report
One call, thirty minutes. Afterwards you know whether and how we can help.
You talk to
Patrick HofbauerInterface design, full-stack, mobileLuc ThieryAutomation, AI & RAG, backend
