AI Automation in a Service Business: What Changed at Fussbally

What the 70% office-automation estimate actually means

Lobmeyr estimates that roughly 70% of the office work the company had been doing six months earlier was automated by the time of the interview. The reference point matters. He is describing a portion of administrative work previously performed, not 70% of every task across Fussbally.

That denominator excludes any inference that the company automated 70% of coaching, employed 70% fewer people, or achieved a measured 70% reduction in expenses. The conversation does not establish those outcomes. It also does not supply time logs, a cost model, or a before-and-after error rate.

The useful signal is narrower and still substantial: a local operator says routine office work changed enough to alter what employees could spend their time on. For founders evaluating their own operations, that suggests starting with an inventory of repeated tasks instead of a target percentage copied from someone else's business.

The concrete example: removing 16 manual registration steps

His clearest example is registration. Lobmeyr describes a process that previously required 16 manual steps after a customer signed up and says those manual steps were eliminated. He also describes earlier reliance on spreadsheets and work helping parents through the signup process.

The interview does not enumerate all 16 steps or identify every application, integration, and control involved. It would be misleading to turn that account into an illustrated software diagram or claim each task is now performed by a particular AI agent. AI-assisted development and automated workflows can be part of the same story without every workflow action being an AI decision.

What another operator can reasonably take away is the unit of analysis: one repeatable process with a recognizable trigger and outcome. Registration is more specific than a broad ambition to automate the office. It creates a manageable place to examine handoffs, repeated entry, exceptions, and the customer's experience.

Removing manual steps is only one way to evaluate such a change. A founder would also want to know whether registrations reach the right place, whether families receive accurate information, and how unusual cases reach a person. Those are our evaluation questions, not claims about controls verified inside Fussbally.

The reported result was different work, not fewer employees

Lobmeyr explicitly connects the changes to reallocating existing employees' effort. In his account, the same people continue working, with more attention available for work he considers higher impact. This is a different operating objective from cutting staffing to match the number of removed tasks.

That distinction is especially relevant in a service business. Eliminating an administrative burden does not automatically improve the experience a customer receives. Management still has to decide what deserves the recovered attention and make that priority clear.

For a business trying a similar approach, a useful planning question is: what will the team do differently if this workflow succeeds? The answer should be more concrete than being productive. It might be addressing unresolved customer questions or improving staff development. These are illustrative possibilities for other operators, not a list of verified Fussbally assignments.

A faster website experiment is not the whole business

Lobmeyr also recounts his team spending about a week rebuilding a website using ChatGPT, then seeing a friend use Lovable to produce something he thought looked better in roughly five minutes. It is his comparison of two building experiences, not an independently timed test or a finding that a production-ready website takes five minutes.

The anecdote illustrates how quickly the effort required for a particular digital task can change. It does not verify the security, accessibility, reliability, or completeness of either result. Nor does the interview establish a tool recommendation that every small business should copy.

Lobmeyr's more interesting point is competitive: if software becomes easier for everyone to create, having software alone may become less distinctive. The hosts discuss the ability of small companies to move quickly; he also expects competitors to adapt. Those are perspectives about competition, not a guaranteed forecast.

The advantage still has to show up on the field

The conversation returns to communication, motivation, coaching, and relationships. Lobmeyr emphasizes the difficulty of building an organization that delivers consistently. An easier registration process cannot, by itself, give a coach the judgment to teach a child or earn a family's trust.

His account of building Fussbally across locations makes that operational challenge concrete: staff, suitable groups, and workable schedules have to come together. Our parent's guide to training quality considers the visible experience at the other end of those decisions.

This is why office automation and service quality should be evaluated separately and then connected. Faster administration is valuable, but customer outcomes remain a question to investigate, not an automatic benefit to claim from adopting a tool.

Five questions before automating a service-business workflow

These questions are our editorial synthesis of the case, not a description of Fussbally's technical implementation:

1. What repeats? Name a specific process, its trigger, and the outcome a person needs.
2. What is the baseline? Record the current steps, time, rework, and exceptions before claiming savings.
3. Where does judgment belong? Decide which unusual cases need a person and who owns that decision.
4. What must be protected? Review data access, permissions, and customer information before connecting tools.
5. What will the team do next? Assign a useful purpose to the capacity the change is intended to create.

The case is compelling without inflating its numbers: a Colorado founder reports changing a repetitive process and redirecting employees' time while remaining focused on a people-intensive service. Watch the full interview for his account, then explore more Mile High Makers conversations about how businesses actually operate. Subscribe to keep following that work beyond the latest technology headline.