Marcus Biel.

Custom process automation

Automate the work your team does by hand

Copying data from emails into spreadsheets, entering the same order in several systems and chasing approvals all take time.

I connect the systems, build in your business rules, and show each person what needs their attention.

I start with a single workflow. Your team can try it on real cases and see where it saves time or avoids rework.

Which tasks are worth automating?

Look for tasks your team repeats frequently.

  • Entering data more than once. Customer, order or project data is entered by hand in several applications.
  • Gathering information. Staff check emails, spreadsheets and business applications before they can continue.
  • Chasing approvals. A case waits for a decision because it’s hard to see whose approval it needs or where it stands.
  • Organizing handovers. One department must inform another, pass on documents or re-explain tasks.
  • Keeping lists up to date. People track progress in Excel, then reconcile it with other systems.

I follow a case from start to finish with the people who handle it. That shows me where automation can help and where someone needs to make a decision.

From confirmed order to project kickoff

Follow a confirmed order from sales to project setup and accounting. At each handoff, someone needs to know what’s ready, what’s missing, and whether the next system received it.

How it might work today

Sales enters a confirmed order in the CRM and emails the project lead. The lead copies customer details and scope into a project spreadsheet, sets up the project in the planning system and sends the information to accounting.

When details are missing, someone chases them by email and updates a separate tracking sheet.

What changes with automation

  1. A confirmed order starts the process

    Once sales confirms the order, the workflow picks up the customer and order details already in the CRM.

  2. Check for missing details

    If the order is missing a contact, an account code, or a start date, the application assigns someone to fill in that specific detail.

  3. The project lead reviews and approves

    The lead checks the prepared information, adds internal details and approves creation of the project.

  4. Create the project and assign the work

    An integration creates the project. Other systems receive the information they need and staff receive their assigned tasks.

  5. Everyone can see progress

    A shared view shows completed steps, missing information, work waiting for action and transfers that failed.

The way your team handles orders today determines which steps are worth automating.

Responsibilities, approvals and exceptions

A workflow also needs a way to handle questions, changes, and decisions that need a person’s judgment.

For each step, I ask the people doing the work a few questions.

  • Who is responsible?
  • What information should be available?
  • What review or approval does the step require?
  • What if a required detail is missing or two records disagree?
  • How should a change be handled after approval?
  • Who steps in if an automated step fails?

I build these rules into the workflow and its screens. Staff can see what has happened and what they need to do next.

The right technology for your process

Connecting existing systems

I connect the applications so they can exchange the agreed data and confirm receipt.

I identify which system owns each piece of information and how to handle changes.

More about APIs and system integration

Developing internal tools

Where existing tools fall short, I build a screen for the work. That might mean recording a case, approving it or seeing a shared list of open tasks.

I design those screens with the people who will use them every day.

Web applications for employees

When a spreadsheet has become the workflow

If one spreadsheet serves as your order register, task list and approval process, I can bring that workflow into a custom application.

The new application keeps the fields, calculations, and rules people rely on and adds the permissions, statuses and integrations the process needs.

Improve one workflow from start to finish

  1. 1. Understand the current workflow

    I ask the people doing the work to walk me through a recent case, from the event that started it to the final result.

    I identify systems, data, manual steps, waiting times and common exceptions. A finished specification isn’t needed at this stage.

  2. 2. Choose the first improvement

    I map the intended workflow with your team so you can choose one improvement to build first.

    You’ll know what the software will handle, which decisions stay with staff, and how to tell whether the change is helping.

  3. 3. Build and test the solution

    I implement the applications, integrations and rules. You see the working version early and can give feedback.

    I test a typical case alongside incomplete orders, changes after approval, and transfers that get interrupted.

  4. 4. Put the workflow into use

    Before rollout, we agree on who will run the software and how staff will switch to the new workflow.

    Once it’s in use, we look at what still slows people down and decide what to improve next.

You receive the agreed workflow, working software and a handover for the people who will use and run it.

Discuss a first process improvement

How much time could your team save?

I look at how often the work comes up, how long it takes, and where people wait for a decision or have to do the same work twice.

After rollout, you can compare the old and new workflows.

  • How often do you still need to transfer data manually?
  • How much staff time does each case take?
  • Where are processes still waiting for information or decisions?
  • Which mistakes still need fixing, and what do people still have to chase?

I compare the benefits with development effort, operating costs and support.

To estimate the work, I look at the systems involved, the quality of the data, and how many exceptions the rules need to handle. I can then quote for a first release.

Who leads the project from planning to rollout?

I’m Marcus Biel, a software developer and architect. I’ve worked with Java since 2001.

I’ll map out the workflow with the people who do the work and help build the software. I can join your team or bring in specialists when you need them.

I’ll help you pin down who owns each step, what passes between systems, and what someone should see when a case needs attention.

More about working with Marcus
Marcus Biel
Marcus BielSoftware developer and architect

Which recurring process takes up your team’s time?

Tell me what triggers it, which people and systems are involved and where the manual work happens.

I’ll help you find a first improvement you can try with your own team.

Prefer to talk first? Call +49 171 1151013 or message me on LinkedIn.

Discuss your business process