Question 1

What do we get at the end of the first engagement?

Accepted Answer

A process map of how the work is done today, a scored and sequenced roadmap with rough effort per phase, the integration points to your existing systems, and a baseline measurement to judge results against. All of it is yours to keep, and it is specific enough that another supplier could execute from it if you preferred.

Question 2

How long does this take?

Accepted Answer

The mapping and roadmap phase is typically two to four weeks depending on how many departments are involved. The first workflow in production usually follows within four to eight weeks after that. We deliberately avoid multi-year programmes — if a phase cannot show a result inside a quarter, it is scoped too large.

Question 3

What does it cost?

Accepted Answer

The discovery and roadmap phase is a fixed fee quoted after a free review call, and each build phase is quoted separately once its scope is clear. Splitting it this way means you can stop after the roadmap with something useful in hand, and you are never asked to approve a budget for work that has not been scoped.

Question 4

Do you also build the software, or only advise?

Accepted Answer

We build it. The mapping exists to decide what to build, and the same senior people carry the work through into production, which is why our estimates account for data migration and edge cases rather than the demo path. If you would rather build in-house, the roadmap is written to be executable by another team.

Question 5

Do we have to replace our accounting or ERP system?

Accepted Answer

No, and we usually advise against it. Your accounting system is where the legally meaningful records live and it should stay the system of record; new workflows integrate with it so data is entered once. Replacing a working finance system at the same time as changing operational processes is how transformation programmes stall.

Question 6

Our staff resist new systems. How is this handled?

Accepted Answer

By involving the people who do the work from the first interview and by piloting with a small group before any wide rollout. Most resistance is rational — the new tool adds steps, or it was designed by someone who has never done the job. We would rather find that in a pilot of five people than after a company-wide launch.

Question 7

What if some of our processes should not be digitised?

Accepted Answer

Then the roadmap says so. A process that runs four times a year and takes an hour does not justify software, and some exception handling genuinely works better as a phone call between two people who know the customer. Removing weak candidates from the list is part of the value of the mapping phase.

Question 8

What about our data in spreadsheets — is it usable?

Accepted Answer

Usually yes, after cleaning. Expect duplicates, inconsistent naming, free-text fields holding structured data and records that only make sense to the person who maintains the file. We treat migration and cleanup as explicit scope in the phase, because underestimating it is the most common reason a rollout slips.

Question 9

How do we know whether it actually worked?

Accepted Answer

Because we measured before. The baseline captures hours per week on the process, error and rework rates and the queue at each handoff, and the same measurements are repeated four to six weeks after rollout. We do not publish target percentages up front — the honest promise is measurement, not a number chosen before the work started.

Question 10

How does this relate to Digital Strategy and Process Digitization?

Accepted Answer

This page is the umbrella. Digital Strategy is the direction-setting work — priorities, sequencing, budget shape and what to leave alone. Process Digitization is the delivery of individual workflows into production. Most clients begin with a review call here and are routed to whichever of the two matches where they actually are.

How can we help?

Digital Transformation
FAQ

Helpful
information

Getting Started

Timeline

Pricing

Support

Still have questions?

Digital TransformationFAQ

Helpfulinformation