Verified purchaser
UX feels illogical and key features are gated
It's hard to like Worklenz, as the UX design feels far from logical, especially during project setup.
The flow focuses on metadata like status, health, estimates, and categories before the purpose of the project is even defined. That’s the wrong order. A project should start with a clear goal and intent, then move into structure and execution, not the other way around.
Projects are driven by purpose, and different types of work (research, product, marketing) require different workflows. Here, everything is treated the same and pushed into configuration too early, which creates friction and breaks the natural way of working.
There are also structural gaps. File management lacks proper folder organization, making it harder to scale and manage assets inside projects.
On top of that, important features seem to be locked behind higher-tier plans without clear upfront visibility. Capabilities like client portals, finance tracking, and advanced scheduling are positioned as premium add-ons, even though they are core to real project workflows.
The UI looks clean, but the underlying UX logic is not aligned with how work actually happens. It feels built for tracking and reporting rather than thinking, planning, and building.
Overall: lacks a solid foundation. Needs a purpose-first setup flow, proper file structure, and clearer feature accessibility to be usable at scale.
A Project tools should help with a clear overview and control of the different process, what this is not!
kalinga_gunawardhane
Apr 30, 2026Thank you for taking the time to share such a detailed and thoughtful review — this kind of feedback is incredibly valuable for us as we continue improving Worklenz.
You’ve raised a very important point about the project setup flow being too configuration-heavy upfront, and we agree that this can feel counterintuitive. Projects should indeed start with a clear purpose and evolve naturally into structure. We’re currently working on refining this experience toward a more “purpose-first” approach, where users can define intent quickly and configure details progressively as needed.
Regarding workflows, you’re absolutely right — different types of work (research, product, marketing, etc.) require different approaches. We’re actively exploring project-type templates and flexible workflows to better support these variations without forcing a one-size-fits-all structure.
On file management, we acknowledge the limitation around folder organization. This is already on our roadmap, and we’re working toward introducing a more scalable and structured file system within projects.
About feature visibility and plan limitations, we understand how this can be frustrating. Our goal is to strike a balance between keeping the product sustainable and ensuring core workflows remain accessible. Based on feedback like yours, we’re currently revisiting what should be considered “core” vs “advanced” features, and improving how this is communicated upfront.
Lastly, your point about Worklenz feeling more geared toward tracking rather than thinking/planning is insightful. Our long-term vision is to support the full lifecycle — from idea → planning → execution → reporting, and feedback like this helps us close those gaps.
We truly appreciate your honesty. If you’re open to it, we’d love to involve you in early feedback on upcoming improvements — your perspective would be extremely valuable.
Thanks again for helping us build a better product 🙌