Purpose: What is this for, in this business?
The reason the system exists (often everyone in the room has a different answer). Settle this and you know what's worth building, and what isn't.
Every system a business runs on is asked the same three questions.
These questions let a system work better alongside people, not merely exist because it was brought in.
“Complexity is not a badge of honor.”
The answers change with the business. The questions don't.
Technical: What has to be true underneath for that to hold?
The conditions the purpose depends on. The tools follow from the answer here; they don't lead it (the most common answer to this question is a product name, which isn't one).
Operational: Who keeps this running when no one is looking?
What decides whether a system keeps working on its own, or quietly comes to depend on one person (best answered from the start, not discovered at handover).
The map
Your whole business in one view: the systems it runs on, grouped into four areas — the same four whether you sell products or services. The difference starts one level down — the website, the inventory, the time tracking. I check every system on this map against the same three questions: Purpose, Technical, Operational. Open Attract or any other area, then one of its parts for the three questions.
In practice
The same three questions, asked of a different business each time, and where the answers land on the map. Hover or focus a card to see its areas on the ring.
Every customer's fix becomes the next customer's tool.
Behind every separate customer system sits one shared toolkit: migrations, automations, backups, test runs.
Built together with Markus Wals, who owns and leads the practice.
Show on the map
A publishing pipeline where writing the note is the whole job.
Write in Notion, or just talk to an agent: the site rebuilds and publishes itself.
Show on the map
Time logged, approved, invoiced — built for enterprise requirements.
A team member logs their time, the team lead approves it or sends it back, and the client confirms on one of four paths — from a click in an email to a signed PDF with a second factor. The system then checks which order is ready to bill and what is still missing, and produces the invoices with German or Swiss VAT per client.
In progressCompliant electronic invoicing (XRechnung and ZUGFeRD), the piece finishing now.
Show on the map
An assistant that may write into the ERP without being able to break anything.
Every change is shown first and executed only against a single-use approval. The gateway teaches the assistant the weclapp API — which fields a query has to carry along, how an update runs, what to do when a call fails instead of blindly retrying. And every write stays on the record.
In the wals.pro team: from customer feedback to release.
Show on the map
Log time without clicking through projects first.
A focused week view rather than a full ERP screen: your own entries, or the team's where the role allows it. Customer, order and task come from weclapp, and the logged time goes back there. Signing in uses the company account people already have.
A wals.pro product, built with the team.
Show on the map
A shared foundation the next app already stands on.
What the existing applications can already do becomes one shared kit: components, interaction patterns and the brand in one place, under test and documented. Time tracking, fulfillment and the assistant gateway draw from it.
In the wals.pro team: design and the interface layer.
Show on the map
The deliveries are ready at the packing table each morning.
The autopilot drives orders through to a finished document by the rules of each sales channel — printed or paperless. What it is meant to leave alone, it leaves alone: the B2B routes run as before, and any single document can be held back. The same mechanism connects the brand shop's till to weclapp.
Delivered with the wals.pro team.
Show on the map
A property catalog they own outright, instead of renting space in someone else's.
Filterable listings under their own domain, with upkeep in one place instead of an external portal.
Show on the map
Keeping the site current takes nothing technical.
Marketing and editorial build on-brand pages themselves, out of reusable components. The pattern held, and now carries the company's other sites as well.
Show on the map
A few fields filled in, and the finished document comes back.
One kit of form, rule set and document generation, assembled for the purpose at hand: a checklist, a self-assessment, a cost calculator. The prospect sees their result as a picture instead of having to imagine it, and the business gets an answer it can work with rather than a form mail.
Show on the map
Members find their own answers instead of guessing where to look.
One searchable, transcribed video library, wired straight into the client's existing email system.
Show on the map
Measure first, rebuild second.
A partly automated pass reads a site down to the server, the cache and the database: through the hosting API, over SSH, plus crawlers and ranking data. What comes out is ordered by weight — what is costing load time, what is costing discoverability, in search engines as much as in AI answers, and which of it pays off first.
Show on the map
Shifts are requested, approved, and everyone knows where they stand.
The real rules — a weekend is one unit, each house staffed on its own — live in the website that was already there. Requests, approvals and refusals notify everyone involved on their own, instead of starting a phone chain.
In progressConfirmation by text message, the piece finishing now.
Show on the map
What clients say
Arne is a great person to do business with. Easy, transparent communication, reliable — highly recommended.
Aurelio VolleCo-Founder & CEO, WP Umbrella
Arne has supported us reliably for years, and his knowledge of processes and infrastructure has taken us well beyond building a good website.
Enrico BuschekCEO, Spreevital GmbH
Arne has been an incredibly fortunate addition to my team, delivering clarity and strategic insight across IT, strategy, and design.
Kerstin HackCoach
About
I work with business owners and their teams on the systems their business runs on. I build nothing that only I can operate.
A standing part of the wals.pro team — weclapp and ERP consulting run there. A solo practice of my own. Based in Germany.