Skip to content
Martin DückMD-Advisory
Book an intro call

Understand first. Then automate.

I map your department, put its workflows in order and automate routine work. You can see what I am working on at any time.

Book an intro callHow I work

30 minutes, free of charge, by video.

Martin DückWeekly status · Friday, 16:30
Week 6
Goal
Nobody in purchasing compares quotes by hand anymore.
Done
Quote comparison runs automatically, 14 suppliers connected.
Ongoing
Automatic supplier reminders
Open
Your decision: above which amount does an order need approval?
Automated4 of 6
Example: this is what your weekly status looks like.
10+Years of process optimization
17Client projects in 9 industries
5Leadership roles in projects
12,000+Employees at the largest client

From my projects since 2015

Where departments lose time today

Five examples. If your situation looks different, tell me about it.

  • Project management

    Your project managers write status reports instead of steering projects.

    Afterwards

    Completed tasks, effort and open items flow into the report every week. Project management reviews and decides.

    Weekly report, built for a machine manufacturer

  • Knowledge & development

    Knowledge about your systems sits in a few heads and in old code.

    Afterwards

    Legacy code and documents are analyzed; specifications and documentation are written in your team's format. Your developers review instead of writing.

    Knowledge secured from legacy code, accepted by the client

  • HR & administration

    Every new approval process needs IT and takes days.

    Afterwards

    Requests are pre-checked, decisions prepared, data handed over to payroll. The business department sets up new workflows itself.

    New approval workflow in 2–3 hours instead of 10 days

  • IT & system migration

    Moving to a new system takes years and ties up an entire team.

    Afterwards

    Logic, data and workflows move from the old system to the new one: the same logic in new code. Your team checks the results.

    Sub-project lead: 10 SAP systems merged into one

  • Purchasing

    Your purchasing team compares quotes, chases suppliers and retypes orders.

    Afterwards

    Quotes are requested and compared, suppliers reminded, orders prepared for approval. Your buyers negotiate and decide.

From organically grown workflows to a clean structure

What working with me looks like, from the first conversation to the support afterwards.

  1. Organically grown workflows

    Excel lists, emails, knowledge in a few heads. Everyone knows it could be better. Nobody has time for it.

  2. Intro call

    30 minutes by video. You tell me where things get stuck. I tell you honestly whether and how I can help.

    Pick a time

  3. Collecting data

    I look at how your department really works: workflows, systems, volumes, exceptions. Who does what, how often, how long.

  4. Proposal

    You receive a proposal with goal, scope and a price per milestone. No off-the-shelf package.

  5. Implementation

    I build, your team tests along the way. Every week you know the goal, what I am working on and what is open.

  6. Clean structure

    Routine work runs automatically, your team checks and decides. I think ahead with you and don't stop at what the proposal lists.

  7. Ongoing support

    I stay available, adjust and extend the setup when your department changes.

What runs by itself afterwards

Five building blocks that run in my own business. For your department, I build them to fit your systems.

Inbox

Code + AI

Sorted before you read. What you need stays. The rest is filed as soon as you give the go-ahead.

Time & budget

Code

Every hour is tied to a task. You see budget and status at any time.

Knowledge

Code + AI

Ask your policies, manuals and legacy code. Every answer names its source.

Status report

Code

Every week, time entries, tasks and open items turn into the report as a PDF. Nobody has to write it; project management only reviews it.

Night shift

Code + AI

At night the system reviews the day and suggests improvements. In the morning you decide what gets adopted.

AI is a tool, not a cure-all. It only becomes powerful with the right concept, applied by someone with experience.

All building blocks show example data.

From my projects

I name clients in a call, where they have agreed to it.

  • 2–3 hinstead of 10 days for a new approval workflow

    Energy utility

    approx. 2,200 employees · project lead

    A configurable approval framework, from requirements to go-live. Since then, new approval processes have been set up without development work.

  • 10 → 1SAP systems merged into one

    Social insurance, public sector

    over 12,000 employees · sub-project lead, 2.5 years

    One of the largest SAP migration projects in the German-speaking region, in agile sprints. Today one system with self-service for employees and managers.

  • AcceptedFollow-up project commissioned

    Machine manufacturer

    approx. 400 employees

    Secured the knowledge in the existing machine software before it is redeveloped. Specification and documentation in the developer's format; the developer only reviews.

See all SAP projects →
Portrait of Martin Dück

Martin Dück

For more than 10 years I have been optimizing processes in companies, from the energy sector to the public sector.

As project and sub-project lead, I bring business departments, IT, management and external providers to a common understanding.

I say openly what does not work, and I build every solution so that your team understands it.

More about me →

Tell me where things get stuck.

30 minutes, free of charge, by video. Afterwards you'll know whether and how I can help.

Book an intro callor by email: info@md-advisory.com