Automation Showroom as an app: sparring, cookbook, and bottleneck diagnosis offline on iPhone and iPad

Anyone who wants to automate processes today ends up stitching together three to fifteen SaaS dashboards — tool comparisons, ROI calculators, "AI Bottleneck Diagnostics", newsletter funnels. All in the browser, all on servers that aren't yours. Every keystroke travels across the internet, gets logged, analyzed, retargeted.

We deliberately chose a different path.

The Automation Showroom app is a native iOS and Android application. It contains three tools that let operations leaders reach a first automation hypothesis in ten minutes — and everything stays on the device. No account, no tracking, no data in the cloud.

Download on the App Store →

>

Google Play (coming soon) →

→ Full screenshots and details on the product page

What the app gives you

1. Sparring engine — bottleneck diagnosis in 7 questions

A sparring session starts with seven short questions about industry, function, volume, and constraints. The engine matches your answers against curated architecture patterns — no LLM generation, no hallucination. After about 90 seconds you get:

• A diagnosis with confidence level (low/medium/high) — honest about what the engine doesn't know
• 1–3 hypotheses about where the actual bottleneck sits — often not where you first looked
• An ROI estimate with ±25 % range
• Concrete next steps instead of "let's book a meeting"

Per hypothesis the app gives you a concrete lever, common pitfalls, and a suggestion for what to do first — no generic coaching platitudes. You can share the result as a PDF or use it as a discussion document in your team — PDF generation happens on-device too.

← horizontal scrollen, um alle Screenshots zu sehen

2. 12 cookbooks — proven automation architectures across 12 industries

The cookbook section contains 12 real automation setups — healthcare, project management, customer service, data processing, e-commerce, and more. Each cookbook describes:

• The trigger
• The architecture with concrete tool stacks (n8n, FHIR R4, Slack, SAP IS-H API, …)
• Realistic timelines (e.g., "10–12 weeks", not "2 days")
• Typical pitfalls and escalation paths

In the detail view you get the stack, KPI targets, and an explicit note that this is a curated demo architecture rather than a verified client case. No hype, no made-up ROI numbers. The cookbooks are the condensed form of what we've seen in real client projects — comparable to the showcases on this site, only deeper and searchable.

3. Mini course — learn to read automation architectures

Three short lessons on tools, architectures, and AI — translated into a language that isn't shaped by vendor marketing. Before you build, you learn what an architecture diagram actually says and what vendors typically hide. For a deeper entry point, our process automation guide complements this on the web.

Why an app and not a web app?

It would have been easier to put everything in the browser. We decided against it for three reasons — and they matter if you want to understand why this app is fundamentally different from most "automation assistants" out there.

Your data never leaves the device

When you type into the sparring wizard "We have an order-routing bottleneck at 8 000 orders per month, B2B, German mid-market", that's competitively sensitive information. In a SaaS solution it runs through someone else's servers, through analytics pipelines, through backups, often through third-party tools (Segment, Mixpanel, Heap, …). In worst-case scenarios, it ends up in the training set of an LLM provider.

In the app, the tag-matching logic runs entirely locally on your device. We don't see what you type. We can't.

That's not a privacy policy — it's an architectural decision: the app contains no backend call for the sparring engine. There simply is no server endpoint your answers could be sent to. If you want to go deeper on GDPR-compliant automation, our piece on what process automation actually is lays the groundwork.

It works offline

Cookbooks, sparring engine, and lessons are bundled inside the app. On-site at a client without Wi-Fi, on a train between Munich and Berlin, on a plane, in a plant with patchy coverage — the app works without internet. That may sound nostalgic in 2026, but for mobile operations roles it's simply reality.

No account, no friction

You install the app and can use it immediately. No email verification, no "trial ends in 13 days", no drip sequence, no "verify your phone number". This is deliberate: the app is a tool, not a lead funnel.

Who is this built for?

If you're in one of these roles and occasionally think about automation, the app is built for you:

• Operations leaders in owner-led mid-market companies (10–250 employees) who prioritize themselves rather than delegating
• CTOs and tech leads weighing a Make vs. n8n vs. in-house build decision
• Founders with a technical background who want to sense whether a bottleneck is automatable before calling consultants
• Consultants and solo operators who need a fast sparring tool before client conversations

If you have to automate rather than want to (compliance pressure, acute staffing gap, failed prior project), skip the app and go straight to our 6-week method.

Privacy posture in detail

For the skeptical — and it's right to be skeptical — here are the architectural facts:

This isn't a marketing promise — it's verifiable, because the permissions are documented publicly in the store listing, and npm ls --all of the build artifacts shows no tracking library.

How the app fits with our consulting

The app does not replace a diagnosis session. It's the low-friction first form: ten minutes, no account, no sales pitch. If the result is interesting, there are two ways forward:

Both are legitimate. We don't sell the app download.

Frequently asked questions

No. It's free in both stores, no in-app purchases, no subscription.

iOS 14+ and Android 8+ are supported (on Android 7 the variable font falls back to the nearest static weight, no other limitations).

Yes. Cookbook updates ship via App Store releases — typically every 4–6 weeks, depending on which new architectural patterns surface in real projects.

Yes, as a PDF via the standard share sheet. The PDF is generated on-device — nothing leaves the device unless you actively share it.

Not currently, and not planned for now. The architectural decision (on-device, no backend) is intentional and part of the product's DNA.

The app processes no personal data — all inputs stay local, there's no processor agreement to sign, no third-country transfer. This is the strictest possible GDPR posture: don't collect data in the first place.

Download

Download on the App Store →

>

Google Play (coming soon) →

The Android version is currently in review with Google Play and will follow shortly.

For more context, screenshots in DE and EN, privacy details, and the Apple Store badges, see the product page for the app.