Projects
Run work from kickoff to delivery: phases, tasks, files and team on one board everyone can see.
Three phases from discovery to delivery, a team of five, final handover on Ramadan 30.
All of these tools belong to the project,
and the project belongs to its client.
Details, tasks, chat, files, finance, team and meetings — tabs of one project, not seven apps, and the head of the chain is the client: open their record and you see their projects, and inside a project everything that happened in it. Switch tabs to see.
A full visual identity for Riyadh Press: logo, colour system and typeface, then applied to the Ramadan campaign. Every figure here comes from the work itself — no report to assemble.
Drag any card to another column and the counters move with it (or use the move button on mobile), and Open shows the task itself — twelve of twenty tasks done, and the percentage comes from the tasks, not from anyone's estimate.
The project chat is not another app: tasks are created from it with #, the call is recorded there with its summary, and the assistant reads it along with the rest of the project — and all of it stays under the name of Riyadh Press.
Whatever is uploaded on a task appears here automatically — with its preview, size and owner, and no second folder to update by hand.
Finance is not a side file: the quote and the invoices are tied to the project and its client, so you know its profit, not just its revenue.
Hover over any avatar to see that person's card — so you assign work to whoever has capacity, not to whoever comes to mind first.
Project meetings sit in the team's own calendar — and a recorded meeting keeps its summary inside the project.
A client's record is scattered across five places,
and you reassemble it by hand every time.
The quote is in email, the approval on WhatsApp, the files in Drive, the tasks in an app and the invoice in an accounting program. So when the client asks two months later what did we agree?, the hunt begins — the answer exists, but it is connected to nothing.
Five places that know nothing of each other. Every question starts with a search, and every employee who leaves takes half the story with them.
One connected chain: open the client record and you see their projects, and inside each project everything that happened in it — with no searching and no reliance on anyone's memory.
Nine areas all roll up into one project, and the project into one client. That is why following a client's details stays a single question rather than a search — press any area to see its page.
Four habits that let a project run itself.
Before any work: pick the client on the project, and put every task inside its project with/. That hierarchy — client, then project, then task, then file, invoice and call — is what preserves the information and makes finding it months later a single question.
A milestone date reveals slippage early; a task date alone hides it until the final week.
When the invoice lives inside the project you know its profit, not just its revenue — income against spend in one place.
A colleague's card shows what is on their plate right now, so the task goes to whoever has room, not to whoever you think of first.
Put Projects to work
Try it with your team and judge after the first hour.