MAKE ORDINARY01 / CATEGORY THESIS

Things that should have
become cheaper by now.

Technology costs have fallen dramatically. In many specialist corporate markets, the economics have not.

Make Ordinary finds those gaps and rebuilds the solution around today's economics.

A repeatable model for specialist corporate capability

Already working with us? Get support →
02

The economic gap

The technology changed.
The economics often didn't.

Software became easier to build. AI reduced the cost of analysis. Cloud infrastructure became standard. Sensors and connectivity became commodities. APIs made systems easier to connect.

Yet many specialist corporate capabilities still carry high licence costs, long implementations, recurring services and proprietary lock-in.

Some of it reflects an older market structure. We look for the second kind.
CONCEPTUAL / ILLUSTRATIVECost structure over time
Enabling technology costFALLING
Specialist solution costPERSISTENT

When the enabling technology changes faster than the market economics, a category can be rebuilt.

03

Inefficiency archetypes

Where the
economics break.

We look for repeatable problems where price, labour or complexity no longer matches the underlying capability.

01

Repeated corporate review

The same checks run every month across every business unit.

Finance, procurement, operations and compliance teams repeatedly extract data, reconcile systems, apply rules and investigate exceptions. Much of that work remains manual long after the underlying data, policies and decision logic became accessible enough to review continuously.

02

Specialist software

A narrow capability comes with a six-figure platform and implementation.

Specialist markets can retain pricing structures created when software was expensive to build, integration was difficult and distribution was limited. Customers may end up funding historical complexity, implementation overhead and weak competition—not only the genuinely difficult part of the problem.

03

Corporate knowledge

One change creates dozens of things to maintain.

A policy or authoritative requirement can become procedures, work instructions, training, checklists, audit controls, translations and AI guidance. When every output is maintained independently, they drift.One authoritative source. Every output stays aligned.

04

Enterprise software edges

The system can do it — after a project that costs more than the problem.

Large enterprise platforms contain enormous capability, but narrow requirements can still mean custom extensions, specialist modules, point solutions or critical spreadsheet workflows. Many of those edge cases should be focused reusable products rather than transformation projects.

05

Frontline workflows

Make existing enterprise systems mobile.

Many enterprise systems contain the right process and data, but are not designed around simple frontline smartphone use. A reusable mobile layer can provide role-based workflows, offline work, scanning, photos, voice, approvals, evidence capture and task execution while keeping the existing enterprise platform as the system of record.

06

Connected hardware

The device became cheap. The surrounding solution didn't.

Sensors and connectivity became commodities. Many industrial and building solutions still bundle inexpensive devices into proprietary gateways, software, service contracts and enterprise pricing. The opportunity increasingly sits in software, integration and intelligence around commodity hardware.

04

Product model

Build once. Use it everywhere.
Keep improving it.

If the same capability is needed across sites, functions or companies, it should not be designed, implemented and maintained independently every time.

Make Ordinary turns recurring requirements into reusable products that improve with every deployment.

05

Enterprise fit

Keep the systems
you already have.

The system of record is often not the problem.

Make Ordinary adds the missing capability around existing enterprise systems rather than forcing another replacement programme.

Integrate where the process and data already live; change only what needs to change.
06

Shared benefit

When we scale, customers
should benefit too.

Shared development and broader reuse should produce a better product and better economics for customers — not only better margins for the vendor.

MAKE ORDINARY07 / ACTION

Can we make
it ordinary?

We are looking for specialist capabilities whose cost, complexity or business model no longer makes sense.

Tell us a little about the inefficiency.
Enter a valid email address.
SUBMISSION DELIVERED

That sounds worth investigating.

Thank you. We have received your submission and will review it.