THE BUSINESS REBUILD

Your business should not have to work around its software.

I help established businesses understand the systems, processes and knowledge they have accumulated — then simplify, rebuild and modernise what is actually holding them back.

See how the rebuild works →Business first. Technology second. AI where it genuinely earns its place.

Businesses accumulate complexity quietly.

An ERP becomes surrounded by spreadsheets. A manual workaround becomes policy. Email becomes a workflow. A staff member remembers the exception. The owner remembers why it matters. Years later, nobody wants to touch anything because nobody fully knows what will break.

Core ERP / legacy softwarestill valuable?
Spreadsheets + Access + SQLcritical knowledge
Email + manual processeshidden workflow
Staff + owner knowledgesingle points of failure

The answer is not automatically to replace everything.
First, understand it.

Understand first. Change second.

The sequence matters. The fastest way to automate the wrong process is to start with the technology.

Observe

See how work actually happens — applications, people, exceptions, hand-offs, reports and the real sequence of a task rather than the process people imagine exists.

01 — SOFTWARE / PROCESS RENEWAL

Keep the business knowledge. Lose the unnecessary friction.

Understand the existing ERP and software environment, capture real workflows, identify unnecessary work and rebuild only the parts that deserve rebuilding.

Explore the Business Rebuild →
02 — BUSINESS / ERP TRANSFORMATION

Modernise without pretending everything old is worthless.

Use SQL, Python, APIs, integrations and targeted applications to connect and simplify what already exists. Sometimes the ERP stays. Sometimes part of it goes. The architecture follows the business requirement — not a software sales target.

See the transformation approach →
03 — BUSINESS CONTINUITY

Make important knowledge belong to the business — not one person.

Capture operating knowledge, recurring decisions, exceptions and management signals so the company becomes progressively less dependent on the owner or a key employee remembering everything.

Explore Owner Independence →

I come at systems from the side of the person who has to run the business.

That means customers, staff, purchasing, stock, invoicing, email, ecommerce, printing, management information and the awkward exceptions that do not appear in a clean software diagram.

I am not presenting HubertKuzel.com as a giant consultancy. The value is practical operating-business experience combined with hands-on systems work.

SAP Business OneSQL ServerMicrosoft AccessPythonAPIsPOS + inventoryPurchasing + salesE-commerceWorkflow systemsAutomation

No technology prescription before the diagnosis.

01

Observe the business

Understand the systems, people, data and actual day-to-day work.

02

Capture how work really happens

Document workflows, business rules, exceptions, hand-offs and dependencies.

03

Identify friction

Find duplicated work, unnecessary steps, fragile knowledge and avoidable complexity.

04

Decide what stays and what changes

Keep useful systems. Remove waste. Rebuild only where it earns its place.

05

Build, test and document

Create controlled improvements and leave the organisation understanding its new environment.

06

Then automate and AI-enable

Only after the underlying process makes sense.

Technical depth when you want it.

Existing environments

SAP, Dynamics/Navision, MYOB, Access, SQL Server, spreadsheets, custom applications and combinations that evolved over many years.

Improvement tools

Python, SQL, APIs, targeted applications, integration layers, workflow tools, reporting and conventional automation.

The modern layer

AI-assisted development, document intelligence, workflow analysis and business knowledge systems — used after the process underneath is understood.

Show me the process you wish worked better.

Tell me about one process that frustrates you. We can start there — no software decision, no transformation programme and no commitment. Just a practical conversation about what is getting in the way.

Start with one process →