Contributor Platform

Evaratus
In production

Team

Naman Bhalla ( PM )
Shreyansh S ( Manager )

Note : To comply with my NDA, I have omitted and obfuscated confidential information in this case study. All information presented is my own and does not necessarily reflect the views of Scaler.

Note: To protect confidential information, all product data and identifiers have been modified. This case study reflects my work during my time at Scaler.

Background

Evaratus, an initiative by Scaler, connects specialists with AI training projects for frontier labs and enterprise teams. Contributors earn payouts by completing tasks like data creation and response evaluation.

Contributors

The platform serves professionals from a wide range of backgrounds - including software engineers, healthcare professionals, researchers, writers, and many others - bringing the expertise required across different project domains.

Context

As adoption grew, the product expanded across new project domains, payout structures, and account requirements. What had started as a system for the early rollout now had to support a broader set of workflows and operational requirements.

Context

As adoption grew, the product expanded across new project domains, payout structures, and account requirements. What had started as a system for the early rollout now had to support a broader set of workflows and operational requirements.

Explore(1) and Payouts(2) before the redesign.

The development of the next release marked a major shift in product strategy: it was hyper-focused on the type of power user that opened a growth opportunity for the business, moving beyond the platform's internal operating model — specialists gaining direct access. As one of the early product designers on the team, I collaborated closely with the PM and engineers from ideation through execution.

The development of the next release marked a major shift in product strategy: it was hyper-focused on the type of power user that opened a growth opportunity for the business, moving beyond the platform's internal operating model — specialists gaining direct access. As one of the early product designers on the team, I collaborated closely with the PM and engineers from ideation through execution.

Project Exploration

Explore was the starting point for finding new work. With projects varying in requirements, choosing where to apply meant understanding how each one differed.

Project Exploration

Explore was the starting point for finding new work. With projects varying in requirements, choosing where to apply meant understanding how each one differed.

Contributor Journey

Interview requirements and difficulty were revealed only after opening a project, so comparing several opportunities meant moving back and forth between the list and their individual details.

Interview requirements and difficulty were revealed only after opening a project, so comparing several opportunities meant moving back and forth between the list and their individual details.

New Project Listing

The listing needed to present enough information upfront to help evaluate options before committing to one. This made it easier to identify what was worth exploring further.

Explore Section

Payouts

Work could now span multiple projects within the same payout cycle, with each project containing hundreds - or even thousands - of individual tasks. While earnings accumulated task by task, payouts were ultimately received as a single bi-weekly settlement. The original payout history no longer reflected this. Understanding what had been paid, when, and which projects contributed to each payment became increasingly difficult as activity grew.

Payouts

Work could now span multiple projects within the same payout cycle, with each project containing hundreds — or even thousands — of individual tasks. While earnings accumulated task by task, payouts were ultimately received as a single bi-weekly settlement. The original payout history no longer reflected this. Understanding what had been paid, when, and which projects contributed to each payment became increasingly difficult as activity grew.


We worked backwards from the moment a payout was received to identify the information needed to understand each payment with confidence.

Usage Scenarios

Every completed task appeared as its own row in the payout history, regardless of which project or period it belonged to. At low volume, this was readable. At scale, a single payout period produced hundreds of ungrouped line items without subtotals or cycle boundaries, making payment tracking tedious.

Defining Succcess

A payout is the culmination of work completed across projects and tasks. The final amount brought together total earnings while preserving the specific details pertaining to each.

Payouts Section

Financial history shouldn’t require downloading a separate statement to verify earnings. A core transaction summary belongs directly in context, with deep breakdowns available on demand for reconciliation and compliance.

The challenge was striking the right information density: omitting critical context obscured payment origins, while displaying every raw record rendered the view unreadable. Refining the hierarchy across each phase of payout allowed us to balance high-level status with granular proof.

Financial history shouldn’t require downloading a separate statement to verify earnings. A core transaction summary belongs directly in context, with deep breakdowns available on demand for reconciliation and compliance.

The challenge was striking the right information density: omitting critical context obscured payment origins, while displaying every raw record rendered the view unreadable. Refining the hierarchy across each phase of payout allowed us to balance high-level status with granular proof.

Settlement breakdown shown in context.

Not all work completed during a payout cycle was immediately eligible for payment. Tasks could remain "In review" while the cycle continued, creating a clear distinction between what had been completed and what would actually be paid.

Project contents in review

For work built around paid expertise, keeping the connection between them clear is fundamental to the experience.

Account Settings

Over time, configurations had grown organically into isolated silos. Payout setup sat inside payouts, conflating account management with financial history tracking.

Original Account Section

To fix this, we decoupled operational settings from earnings data. Establishing a clear functional boundary allowed earnings history to serve as a dedicated space for tracking income, while account settings became the centralized hub for preferences, identity, and payout destinations.

Unifying component behaviors across surfaces ensured new UI patterns felt like natural extensions of the platform while streamlining overall navigation.

Bank transfer setup is a high-anxiety moment. A single mistyped routing number doesn't just trigger an error message - it misdirects earnings or delays payouts indefinitely. Treating data entry as an immediate success state created a dangerous blind spot, leaving users to assume their account was ready while unaware of the silent verification process happening behind the scenes.

Bank Transfer

Mitigating risk required restructuring the setup around two deliberate checkpoints. First, a pre-submission review step requires users to confirm their inputs, catching manual typos before they reach the backend. Second, an explicit "Verifying" status bridges the gap between submission and activation. Exposing this background process directly in the UI replaces an ambiguous waiting period with explicit feedback—signaling that validation is underway while indicating payout readiness.

Details being sensitive, defining a clear boundary between legitimate communication and requests that should never come from the team was essential. Building trust relied on offering contributors clarity at the right moment, without raising concerns.

To accommodate third-party integrations, the system relied on external OAuth flows- making the return journey a critical touchpoint for maintaining user momentum.

Paypal Setup

Beyond immediate 2FA and preference management, this clear structure opened up space for seamless integration of advanced security and identity controls.

Final thoughts

Designing for a growing system meant looking beyond individual screens to build a structure that scales. By establishing distinct functional boundaries and predictable data patterns, this effort provided a unified foundation—enabling the product to expand without requiring underlying flows to be reinvented with every release.

As of June 2026, Evaratus remains in active beta with capabilities continuing to roll out in phases. Early qualitative feedback from initial specialist cohorts showed marked reductions in payout status inquiries and higher confidence during financial setup. Related coverage: Economic Times ↗

Thankyou :)

Back

Create a free website with Framer, the website builder loved by startups, designers and agencies.