Participant management should not live in scattered spreadsheets.

Rosella exists because participant operations are often treated like admin glue, even though this is where a lot of the study actually happens: recruitment, screening, scheduling, forms, reminders, messages, follow-up, compensation, and completion.

We are not a large organisation with a huge team. Rosella is being built close to the problem, with research context and software craft sitting side by side.

Research teams end up running that work across tools that were never designed to work together: spreadsheets, email threads, survey links, booking calendars, messaging notes, shared drives, and institutional systems. Each tool may be fine on its own, but the participant journey gets fragmented.

That creates hidden work. Teams have to remember which list is current, who was contacted, whether a participant is approved, which activity unlocks next, whether someone needs compensation, and which version of the protocol applies.

Rosella gives that work a home. The product direction is simple: one workspace where research teams can see what has happened, what is required, what is blocked, and what needs review.