Pretending to Be Our Own Customer

When you are building a business, it is easy to stay focused on delivery and assume your internal processes are working well. We decided to step back and test that assumption.

Rather than refining individual tasks, we mapped our entire workflow from end to end to understand how our business actually operates.

Mapping the full workflow

We looked at everything from marketing and lead generation through to delivery and ongoing customer support.

The aim was simple. Identify where time is lost, where information breaks down, and where our processes could be simplified or strengthened.

To guide this, we drew on established process mapping approaches used by automation and AI agencies and best practices from software development. These provided us with a reference point without forcing us into a rigid structure.

What we learned

Some of our findings were not what we expected.

We found that:

• several assumptions about what our systems needed to work were incorrect,
• our existing processes were already reliable and not over-engineered,
• there were clear gaps where better data capture and more consistent handovers would improve outcomes.

The most important issue was timing and quality of information. Getting the right data from customers at the right point in the process has a direct impact on our delivery.

When that information is incomplete or arrives too late, it increases rework, slows progress, and introduces risk.

Where improvements were needed

The gaps were not in major structural failures, but in smaller points of friction.

In particular:

• expanding existing systems to capture more useful data,
• improving how information moves between stages,
• standardising how work is carried out across similar tasks.

These changes are expected to make our workflow more predictable and reduce variation in output.

The role of measurement

As part of this work, we began using basic internal time tracking tools.

This highlighted something easy to overlook. Small inefficiencies add up. For example, switching between systems and repeated logins were taking more time than expected.

Without measuring this, it would have remained hidden inside our normal flow of work.

The challenge of stepping back

There is often resistance to reviewing processes that appear to work.

Changing them introduces risk. If a process breaks, it can disrupt delivery. This often leads to a mindset of leaving things as they are.

In practice, avoiding review carries its own risk. Inefficiencies become embedded, and small issues scale as a business grows.

Taking time to map and question our processes creates a clearer understanding of how work actually happens.

What this means for us

We are still working through what these changes look like in practice.

The expectation is not a complete overhaul, but a more stable and consistent way of operating: better flow, clearer structure, and fewer unnecessary steps.

This exercise has also influenced how we think about the systems we build for clients. Reinforcing the importance of focusing on improving how work is done, rather than adding technology for its own sake.

In short, pretending to be our own customer has helped us see where our efforts are well spent and where more value is still to be derived from them.