Working across projects, risk and controls, you get used to seeing the same problem appear in different forms.
A project needs a change register. Another needs better contract tracking. Another needs an interface register. A business needs a risk, governance, safety or compliance process that does not quite fit the software already available.
The need is real, but the choice is often poor.
Buy a specialist system that is expensive and rigid, change the business process to fit the software, or build another spreadsheet.
For years, the spreadsheet usually won.
That experience is what eventually led to WorkMesh.
The gap between enterprise software and Excel
At Cost Time Risk, much of our work has involved helping organisations understand and control complex project information.
One thing became obvious over time: many processes are too important to live permanently in a spreadsheet, but too specific to justify a large specialist software implementation.
Excel remains useful because it is flexible and familiar. If a project team needs a new field tomorrow, they can add it tomorrow.
That flexibility is difficult to give up.
The trouble starts as the process becomes more important.
More people need access. Different people should see different information. Changes need to be traceable. Supporting evidence needs to stay with the record. Actions need owners. Due dates need to be visible. Management needs to know what is not happening, not simply receive another copy of the register.
At that point, a spreadsheet may still hold the information, but it is no longer enough to control the process.
A risk system helped crystallise the idea
Around four years ago, Gary was working with a risk system that handled the basic register but stopped short of several capabilities he wanted to see around it.
There was no straightforward combination of complete audit history, regular backup capability and the ability to extend the data into the analysis he needed, including Monte Carlo analysis.
The question was simple:
Why should this be so difficult?
The idea that followed was not to create another fixed risk product.
It was to create a foundation flexible enough to support risk and many other processes while retaining the controls expected from a genuine business system.
Keep the flexibility. Add the control.
The starting principle behind WorkMesh was deliberately simple.
Adding a field should not require a software project.
If a business can add a column in Excel, the equivalent change in WorkMesh should feel just as natural: create the field, name it, choose its type and use it.
But flexibility by itself is not enough.
WorkMesh was also designed around audit history, security, privacy, attachments, controlled record and field access, and workflow.
Most importantly, it was designed around Actions.
From years of working with project and business processes, our view is that a register should not simply describe what exists. It should help drive what happens next.
A process moves accountability between people. Something happens, a decision is required, evidence needs to be provided, an approval is needed or an issue must be closed.
If the system cannot turn that into a clear Action for the right person, there is a risk that the process becomes administration rather than management.
From an internal tool to a broader platform
WorkMesh began as an internal experiment: could we build something useful for our own business and solve some of the problems we had repeatedly encountered?
It did not take long to see that the same architecture could address a much wider range of use cases.
Risk was one example. Change, contracts, interface management, safety, governance, compliance and environmental processes all share a similar underlying need: configurable information, controlled access, evidence, workflow and accountable action.
That realisation changed WorkMesh from a small internal tool into a broader product direction.
There are still problems we have encountered over years of project and business work that WorkMesh does not yet solve. That is intentional. The platform has been built so additional modules can be added over time without abandoning the common foundation underneath them.
Built from the problem, not from a software category
WorkMesh is closely connected to Cost Time Risk because it came from the same practical experience.
It was not created because we decided the market needed another piece of enterprise software.
It was created because we kept seeing capable people trying to manage important processes with tools that were either too rigid, too expensive or not designed for what they actually needed to do.
The objective is straightforward: give businesses more control over their processes, focus people on the Actions that matter, improve the quality and security of the information behind those decisions, and do it without forcing the organisation into an oversized software model.
That is why we built WorkMesh.