Selected work

Engagements, anonymised

Client operations are confidential, so no names, logos, or screenshots appear here. The situations, the work, and the outcomes are real.

New health and care provider

Health and care startup taken from setup to launch

Situation
A founding team preparing to open a regulated care service, with sector experience but no operational infrastructure - no processes, no systems, and launch obligations arriving on a fixed timetable.
Operational challenge
Everything had to exist at once: an operating structure, customer and referral handling, staff documentation, supplier arrangements, and the reporting a regulated service is expected to produce from day one.
Metrixan's role
Metrixan worked alongside the founders from initial setup planning through to launch, designing the operation before building the systems to run it.
Outcome
The service opened on schedule with its core operations working from the first week: enquiries handled through a structured pipeline, documentation organised and findable, and management able to see the state of the service without asking around.

The engagement began with the operating model: who does what, how an enquiry becomes an assessment and then a service user, which documents exist, and what management needs to see each week. Only then were systems put in place - a structured enquiry and referral pipeline, staff and service documentation with clear ownership, supplier arrangements set up directly rather than through intermediaries, and a simple reporting rhythm the team could sustain.

Because the foundations were designed before launch rather than patched afterwards, the team spent its first months serving customers rather than untangling its own operation.

Details are anonymised to protect client confidentiality. The organisation type, situation, and nature of the work are described accurately.

New digital services company

Digital services business launched with its operations already working

Situation
A founder launching a digital services business with strong technical capability but no structure for handling customers, projects, suppliers, or money once real work arrived.
Operational challenge
Service businesses fail quietly on operations: enquiries answered late, projects with unclear status, invoicing that lags delivery. The founder wanted those problems designed out before the first client, not discovered afterwards.
Metrixan's role
Metrixan defined the operating structure and customer journey, set up the CRM and lead handling, established project and delivery workflows, and delivered the public website through which enquiries arrive.
Outcome
The business launched with a working enquiry-to-delivery pipeline. New enquiries are captured and followed up systematically, project status is visible without meetings, and the founder can see commitments and cash position in one place.

The work ran in a deliberate order: customer journey first, then the CRM configured around that journey rather than the other way round, then delivery workflows, then the public website as the front door to an operation that was already ready to receive work.

Details are anonymised to protect client confidentiality. The organisation type, situation, and nature of the work are described accurately.

New perfumery and consumer products business

Consumer products launch with suppliers connected directly

Situation
A new consumer products venture needed sourcing, production arrangements, stock handling, and sales operations established before its first product could reach a customer.
Operational challenge
Early-stage product businesses often inherit expensive habits: intermediaries inside the supply route, informal stock records, and no clear picture of what each unit actually costs. The founders wanted a clean start instead.
Metrixan's role
Metrixan established the supplier arrangements - connecting the business directly with dependable suppliers rather than through middle layers - and set up the operational basics: stock and order handling, cost visibility, and the sales and enquiry workflow.
Outcome
The business launched with direct supplier relationships, a known cost base, and order handling that does not depend on any one person's memory. Avoidable third-party costs were designed out before they could become normal.

Sourcing came first: identifying dependable suppliers and establishing direct relationships, so the business would not build its economics on top of intermediary margins. Operational basics followed - stock and order records with clear ownership, simple cost visibility per product line, and a sales workflow that captures every enquiry.

Details are anonymised to protect client confidentiality. The organisation type, situation, and nature of the work are described accurately.

Established multi-site business

Long-established business restarted its improvement after years of drift

Situation
A business trading successfully for many years had stopped improving. Processes ran on habit and memory, the owners were involved in routine decisions, and performance had begun to slip in ways nobody could quite locate.
Operational challenge
Nothing was visibly broken, which is exactly why nothing was being fixed. Wasted staff hours, budget leakage, and under-used equipment were spread thinly across the operation rather than concentrated in one obvious place.
Metrixan's role
Metrixan carried out a structured operational review - workflows, responsibilities, supplier and third-party arrangements, equipment utilisation, and reporting - then prioritised and implemented improvements with the management team.
Outcome
The review made the drift visible and gave it owners. Wasted hours were reduced by removing duplicated and unnecessary work, budget leakage was identified and closed at its sources, equipment decisions became evidence-based, and management gained a reporting rhythm that shows problems while they are still small.

The diagnosis deliberately separated symptoms from causes. Slow reporting traced back to duplicated data entry; recurring mistakes traced back to process steps with two owners or none; costs traced back to arrangements that had never been reviewed since they were first made.

Improvements were then implemented in priority order - not as a single disruptive programme, but as a managed sequence the business could absorb while trading.

Details are anonymised to protect client confidentiality. The organisation type, situation, and nature of the work are described accurately.

Established service business

Management visibility system replacing month-end spreadsheet assembly

Situation
Directors of a service business received their performance picture weeks late, assembled by hand from spreadsheets held by different people, with numbers that changed depending on who compiled them.
Operational challenge
Decisions were being made on stale or contested information. The reporting burden consumed skilled staff time every month, and problems surfaced only after they had already cost money.
Metrixan's role
Metrixan defined the small set of figures management actually uses, traced where each one originates, removed the manual bridges between systems, and implemented a reporting structure that stays current without a monthly assembly effort.
Outcome
Management now works from one agreed, current view of the operation. The monthly assembly effort was eliminated, definitions are consistent, and issues appear while there is still time to act on them.

The critical step was not the dashboard - it was the definitions. Before anything was built, each figure was given one agreed meaning and one source. The reporting layer then simply presented data that was already trustworthy.

Details are anonymised to protect client confidentiality. The organisation type, situation, and nature of the work are described accurately.

Established sales and service organisation

CRM rebuilt around the team that had stopped using it

Situation
A CRM had been in place for years, but records were incomplete, staff kept private lists, and management reports from the system were quietly ignored because nobody trusted the data.
Operational challenge
The tool was not the problem. The CRM demanded work from the team without giving anything back, so the team worked around it - and every workaround made the data less trustworthy.
Metrixan's role
Metrixan mapped how enquiries and customers actually flow through the business, redesigned the CRM structure around that real flow, removed fields and stages that existed only for the software's sake, and introduced follow-up and ownership rules the team helped define.
Outcome
The team returned to the system because it now saves them time instead of costing it. Follow-ups no longer depend on memory, private lists have retired, and management reporting from the CRM is trusted enough to run meetings from.

Adoption was treated as the design goal, not an afterthought. Every field the team is asked to fill either drives a follow-up, a handover, or a report that management genuinely reads - anything that failed that test was removed.

Details are anonymised to protect client confidentiality. The organisation type, situation, and nature of the work are described accurately.

Your engagement would be treated with the same discretion.

Discuss Your Business