How Workapp Used Useberry to Validate Its Core Flow

When you are building an early-stage product, it is easy to feel like the next step is to keep designing, keep adding features, or keep moving toward development. But before investing more time into building, there is one important question worth asking:

Can users actually understand and complete the core flow?

That was the question behind Workapp, a task management product designed for freelancers and small agencies. The project was led by Denitsa Ivanova, co-founder of Workapp, with guidance from Magdalena Chavdarova-Linkova, a senior UX designer and mentor through the Mentor the Young program.

As part of the mentorship, the team used Useberry to test Workapp’s main product flow, gather feedback from real users, and move forward with more confidence.

You can watch the full conversation below or keep reading for the key lessons from their testing process:

From product idea to user validation

Workapp started as an early-stage product idea for helping freelancers and small agencies manage projects, tasks, clients, and workflows in one place. At first, the process seemed straightforward. But as the product moved from idea to design, Denitsa quickly realized that building a useful product required more than a good concept and a polished interface.

Through the mentorship process, the team defined key features, explored user needs, ran competitor analysis, created wireframes, and designed the main product flow. Once the prototype was ready, the next step was to validate whether users could actually move through that flow.

That is where Useberry came in.

Magdalena had used Useberry before and suggested it as a simple way to run a quick validation test with real users. The goal was not to create a complex research setup. The goal was to get useful feedback early enough to make better product decisions.

What they tested

The team tested a responsive Figma prototype of Workapp using Useberry. The study focused on the main freelancer journey, including:

• logging in

• creating a project

• adding members

• creating a task list

• creating and managing a task

• changing task views

• marking a task as complete

• finding and deleting a completed task

Instead of asking users to freely explore the product, the team broke the experience into smaller steps. Each task represented one part of the journey, making it easier to see where users moved smoothly and where they slowed down. This helped the team validate the full flow while still keeping the study lightweight and easy to follow.

For teams testing a prototype for the first time, this kind of structure can be especially useful. It turns a broad question like “Can people use this?” into smaller, clearer moments that can be observed, measured, and improved.

A lightweight test with practical feedback

Workapp ran the test with 10 participants from different backgrounds, including small agency owners, people from marketing, design, and development, as well as users outside the design and IT space.

This helped the team see how the flow worked for different levels of familiarity. Denitsa also observed some participants in person, which made it easier to catch small moments of hesitation that may not show up from the prototype alone. The goal was simple: understand where users moved smoothly, where they slowed down, and which parts of the experience needed more clarity.

What the team learned

The results gave the team confidence that the core flow was working. Users were able to complete the main journey, but the test also revealed a few areas that needed refinement.

One example was the action for marking a task as complete. Some users missed the original path, so the team added another way to change the status from the task details. Another finding was related to the board columns. Some users did not notice the column headings and icons clearly enough, showing that the visual hierarchy needed to be stronger.

These were not major structural issues, but they were useful signals. The test helped the team catch small friction points before they turned into bigger product problems.

Confidence before moving forward

For Workapp, the biggest outcome was not a full redesign. The test helped the team confirm that users could complete the core flow, identify small usability issues, and continue development with fewer assumptions. For an early-stage product, that kind of validation matters. It helps teams avoid unnecessary rework and make clearer decisions before investing more time into building.

A practical lesson for early-stage teams

Workapp’s story is a reminder that useful research does not always need to be complex. A small test with a clear objective can still show what users understand, where they hesitate, and what needs to be improved before launch. For founders, designers, and small teams, the takeaway is simple:

Test the core flow early. Watch where people pause. Fix what creates friction. Then move forward with more confidence. Ready to test your own product idea? Start validating your prototypes with Useberry.