Choose another country or region.
One day, while managing a design and build project, a simple question came up.
“Did the client approve this?”
Everyone was certain the approval had been discussed.
But no one could find it.
The conversation had happened somewhere — perhaps on WhatsApp, perhaps on a call — but by the time the issue resurfaced, the message was buried in weeks of chat.
That moment felt familiar.
For many years I worked as an interior designer and project manager in the AEC industry, managing complex design and construction projects involving architects, contractors, vendors, consultants, and clients.
Almost every instruction, update, and decision moved through messaging.
Drawings were shared on chat.
Vendors confirmed deliveries through messages.
Teams discussed site issues through conversation threads.
Client approvals were often requested on WhatsApp, and sometimes given verbally on calls.
Later those approvals would either get buried in chat threads or be forgotten altogether.
When delays happened, the pattern was predictable.
Someone searched through hundreds of messages.
Different teams blamed each other.
And the real issue was rarely clear.
As a project manager, I often felt I was spending more time chasing conversations than managing projects.
Naturally, I tried solving the problem with traditional tools.
I implemented the cloud version of Microsoft Project and even created a Project Management Office to bring structure to project tracking.
On paper it looked like the right solution.
In reality, it didn’t work.
Teams continued coordinating work in chat while the project management system remained underused. Eventually managing the tool itself required dedicated people, which increased project costs without solving the underlying problem.
That’s when a different thought began to take shape.
The work was already happening in chat.
But the chat itself had no way of tracking the work behind those conversations.
I began asking myself a simple question:
If work already happens through chat, why can’t chat track the work?
Project management tools required teams to leave their conversations and manually enter tasks.
Messaging apps were easy to use but were never designed to organise work.
What seemed missing was something entirely different.
Not another project management tool.
But a messaging app where conversations themselves could become trackable work.
That idea eventually became Arkchat.
Arkchat represents a new category — the Work Tracking Messaging App.
Once Arkchat was built, the first place I used it was in managing Arkchat’s own product development.
Software development, much like construction projects, involves constant collaboration — discussions, bug reports, feature requests, testing feedback, and approvals.
Very quickly, something interesting began to happen.
Important discussions were linked directly to tasks and approvals.
Bug reports stayed connected to the conversations that created them.
Repeat issues became easier to track.
Decisions were clearer because approvals were visible.
Even more interesting, team performance began surfacing naturally through the work itself rather than through monitoring or reporting.
For the first time, the system was not forcing people to change how they communicate.
Instead, communication itself was organising the work.
That experience confirmed what I had long suspected after years of managing projects.
When conversations become trackable, work becomes easier to manage.
Arkchat was built around that simple idea.
