The problem
A project is a named piece of work with an owner, a status, and a pile of tasks that should finish. That is it. Then the tool arrives.
Asana wants a structure: portfolios, sections, rules, a status that is also a custom field. Trello is a board that starts simple and dies as a graveyard of cards. Monday is a spreadsheet with colours, sold as a platform. A wiki projects board is a database plus a view you will rebuild after every process change.
You spend more time maintaining the project tool than running the project. The customer lives in another system. The tickets live in another. The deadline is in someone’s calendar. Standup is “what’s the status?” because the board is stale.
How Thogits is that system
You describe the projects you actually run. Thogits stores projects and their work as records and builds pages on them: a project list, a project page, a board of tasks. That board is not a built-in kanban engine. It is a screen over the same records you can search, link, and talk about.
A project can point at a customer, a set of tickets, a doc, and the people on it. You are not gluing Asana to a CRM to a wiki. The objects are in one workspace.
Invite the team. Everyone sees the same projects. There are no per-record permissions. Fine when the company is a handful of people who already know the work. Wrong if you need Monday-style column-level access.
An assistant can update a project in chat, by email, or on a phone call. “What’s at risk this week?” “Mark website rebuild as blocked — waiting on copy.” It does not send SMS.
A scheduled job can send a weekly status list. It does not fire the instant a task moves columns.
Projects sync across web and iOS. There is no offline mode. MCP, if you use it, reads and writes records only.
What you actually use
A project tracker in Thogits is usually three objects and a few pages.
- Project — name, status (planned, active, blocked, done), owner, due date, summary.
- Task or ticket — work on the project, assignee, status.
- Milestone (if you use them) — a date that matters, linked to the project.
- Links — customer, docs, people.
Pages you open:
- All projects — filter by status or owner.
- Project detail — status, owner, dates, related customer, open work.
- Board of work — tasks on that project by status. A generated screen, not a product inside a product.
- My work — what you own across projects.
Example: project “Website rebuild,” active, owner Priya, due 30 May, linked to the paying customer. Open work: “homepage copy” in progress, “redirects” blocked. The customer page shows the same project. The copy doc is linked.
Ask the assistant: “List active projects and what’s blocked” or “Add a task to website rebuild: confirm SSL, assign Sam, due Friday.” Same records the project page shows.
Why this instead of Asana, Trello, or Monday
Asana is strong when a PMO wants a standard way to run many teams. If you are not that company, you will use 20% of it and still feel behind.
Trello is a visual board with almost no setup. It does not want to be your customer list and your wiki.
Monday is strong at charts and making a sheet look like software. You still have a sheet.
A projects database with two board views still becomes the project. Here the board is a screen over the records.
Projects as records, screens generated on those records, and an assistant that can report and update them. The project list is the same system as the people and the tickets.
Try it
Sign up. An account is free. A new organisation starts a 30-day trial, no card required. See features, comparisons, and pricing.