Asana plans portfolios. Trello is a wall. We wanted the hour on the card.

Asana wins cross-functional planning. ClickUp wins breadth. Trello wins the afternoon. Tides keeps the calm of a board and adds the three things client work actually has: a client, a document, and an hour someone bills.

Asana is what people recommend when the work is not only software. Marketing, ops, a launch. It is good at that. It is just not a ledger. I do not run a portfolio review. I run delivery for one client at a time, and at the end of the month someone has to invoice the hours behind every card.

I left Asana out of the Linear-versus-Jira table because it lives in a third building. It is neither a code tracker nor an enterprise process engine. It is the cross-functional planner, and it is genuinely good at showing a whole portfolio at once. None of that tells me what to bill.

What Asana gets right

Portfolios, timelines and dependencies across many teams. If your job is to see everything at once, that is the product. Tides is deliberately narrower: one client, one board, one set of columns.

What we kept simple

Statuses you name. Board, list and calendar. Assign, comment, attach, move on. No workflow engine, no certification. If adding a column needs a meeting, the tool already lost.

What we kept detailed

• The project belongs to a workspace and usually a client, from the shared directory.
• Time can live on the card, and it is the same hour the timer invoices.
• A wiki page can hang off the task, and the task shows Open in Tides from the page.
• Shelly lands in an agent inbox column, and a human can throw the card back.

What is actually wired

• Time on a task feeds the shared hour record; the timer reports it, and the card stays a board card.
• A “Track with the timer” shortcut carries the task, so you never retype the project name.
• Board, list and calendar on the same project, with rich text, tags, templates, relations and attachments stored privately.
• Connected-app rules can turn an assigned issue into a task, checked once so nothing doubles up.

A portfolio tells you where the work is. A ledger tells you what it earned. A studio needs both.

If you run a portfolio across ten teams, use Asana. If the work is the code, use Linear. Tides is for the studio that has a board, a clock and a client who does not care which framework you like.

Use Tides when the board is how you deliver and the hour on the card is how you get paid. Use Asana when the portfolio is the product.