About
An operations company that also builds
Metrixan exists because most business problems live between the org chart and the software - in workflows, responsibilities, suppliers, and reporting - and most providers only look at one side.
Why Metrixan exists
Businesses rarely fail for lack of tools. They stall because information scatters, follow-ups depend on memory, responsibilities blur, suppliers go unreviewed, and management loses sight of the operation. Software vendors sell software for that; consultants sell reports. Metrixan was built to do the whole job: understand the operation, fix the process, put the right systems behind it, and stay through implementation until the change is real.
Where the experience comes from
Metrixan has supported businesses and created operational systems across multiple industries and international markets - including health and care, IT and digital services, oil, gems, education, construction, real estate, and perfumery. During the first eight months of 2026, Metrixan supported three businesses from setup to launch across the UK, Jamaica, and Pakistan; those launches are recent examples of the work, not the limits of it.
Engagements have included launching new operations, helping long-established businesses begin improving after extended stagnation, reducing wasted team hours, identifying budget leakage, improving equipment selection and utilisation, connecting businesses directly with dependable suppliers, and reducing avoidable dependence on third parties.
- Health and care
- IT and digital services
- Oil
- Gems
- Education
- Construction
- Real estate
- Perfumery
How Metrixan works
Metrixan is led by Waseem Yahya, who is directly involved in every engagement from diagnosis through implementation, and works with carefully selected specialists where an engagement requires additional expertise. That structure is deliberate: clients get senior attention on every decision, with specialist depth brought in exactly where it earns its place.
Principles
How the work is held to account
Understand before recommending
No proposal arrives before the operation has been understood. The first conversations are questions, not slides.
Keep systems practical
A system the team actually uses beats an impressive one they work around. Simplicity is treated as an engineering achievement, not a compromise.
Protect confidentiality
Client operations, data, and identities stay private. That is why this site shows anonymised stories and synthetic interfaces instead of names and screenshots.
Avoid unnecessary complexity
The order of consideration is fixed: process change, better use of existing tools, then custom builds. Complexity must earn its place.
Document important decisions
Decisions that shape an operation get written down - what was decided, why, and who owns it - so the business is never dependent on memory, including Metrixan’s.
Measure whether changes work
Every change is checked against its intent. Adjusting or reversing a change quickly is part of the method, not an embarrassment.
Be honest about limitations
Where something falls outside Metrixan’s expertise, that is said plainly - and carefully selected specialists are brought in where an engagement genuinely needs them.
Talk to the person who would do the work
No handoffs to a sales team. Describe your situation and it lands with the person responsible for solving it.