Problem Statement

When I joined the project, it was clear from the start that the product had potential—but the adoption was low. Most users, especially business owners and finance personnel, preferred desktops but had no access to a web platform. The mobile app that existed was unintuitive, cluttered, and failed to accommodate the real needs of the users.

Key Challenges

• No centralized view of multiple projects

• Lack of finance health and company-level dashboards

• No existing web platform for management use

• Poor adoption due to unintuitive mobile UX

• Fragmented communication between site teams and office teams

• Errors caused by paper-based reporting

The design challenge wasn’t just about making something look better—it was about changing behavior and building confidence in digital tools among non-tech-savvy professionals.

Goals

• Build a scalable web application targeted at business owners, managers, and finance teams

• Improve usability of the existing mobile app

• Support multi-project visibility, reporting, and communication workflows

• Increase trust and adoption by simplifying the user journey and improving UI consistency

Research & Discovery

To design with confidence, I needed context. Who were we designing for? What were their constraints? Why had previous attempts failed? I explored these questions in-depth.

Stakeholder Interviews

• Connected with the founding team to understand their long-term vision

• Aligned on key metrics of success: usability, adoption, engagement

• Identified core frustrations business owners shared through the internal support team

Product Audit

• Reviewed current mobile app workflows—many features were present, but poorly organized

• Mapped user journeys to identify pain points, friction, and dropped engagement

Competitor & Market Research

• Analyzed tools like Powerplay, Buildcon, and Procore

• Noted opportunities in how collaboration, access control, and reporting were handled in modern construction tools

Personas and Pain Points

• Business Owners: Needed holistic visibility across projects and quick financial health snapshots

• Project Managers: Sought ease in updating material movement, tasks, and site status

• Finance Teams: Wanted structured, readable reports and seamless billing workflows

These findings helped guide every design decision I made throughout the project.

• Role-based structure: Owner, Manager, Accountant, Site Supervisor

• Simplified navigation and grouped actions by role for ease of use

Design Approach

Information Architecture

We started implementing our solutions, these were low Fidelity Wireframes to high fidelity. these were not final solutions, provided various solutions and Implemented/ Pick Solution after the Proper User Testing, We did User testing with Onsite Internal Team and Users. During this phase we started exploring the visuals, After N number of iterations these designs were finalise.​

Wireframes

High Fidelity wireframes

We started implementing our solutions, these were low Fidelity Wireframes to high fidelity. these were not final solutions, provided various solutions and Implemented/ Pick Solution after the Proper User Testing, We did User testing with Onsite Internal Team and Users. During this phase we started exploring the visuals, After N number of iterations these designs were finalise.​

Visual Design

• Our finance team now uses the web app daily without needing support.

• I can finally see what’s happening across projects without calling my site supervisors.

• Positive feedback from early adopters helped validate new IA and UI structure

Feedback & Validation

100K+

Results & Impact

construction businesses reached via Onsite's network

in projects tracked through the platform

₹5000 Cr+

$1.7M

in funding raised to scale post-launch

New user engagement increased due to improved usability and onboarding experience

• Working closely with founders accelerated iteration and feature alignment

• Designing for low-digital-literacy users requires micro-level empathy

• Testing early wireframes improved trust in the design process

• Founders appreciated transparent design documentation and reasoning

Learnings & Reflections