Skip to content

Construction management platform

BuildAxis brings projects, documents, finances, equipment and communication into one platform: a web app for managers in the office and a mobile app for crews on site, with AI taking over the repetitive paperwork.

Client
B2B SaaS client
Role
Product Designer, end to end
Industry
Construction
Platform
Web app, Mobile app
Year
2026
Status
Delivered for development
BuildAxis project dashboard on a laptop, showing project progress, approval queues, defects and claims.

At a glance

Scope

  • User flows & IA
  • Web & mobile UI
  • Component library
  • Developer handoff
  1. Problem

    Updates, approvals, defects and payments were scattered across spreadsheets, apps, email and paper.

  2. Approach

    One layered system: critical information first, detail on demand, for managers and field crews alike.

  3. Delivered

    A ready-to-build web app, mobile app and component library, handed over and going into production.

01

Challenge

Construction teams run on too many tools: spreadsheets, separate apps, long email threads and paper documents. Work slows down and blind spots appear.

Decisions get delayed because the right information is hard to find. Updates, approvals, defect reports and payment status get lost between tools. The result is poor communication between the field and the office, expensive rework, and projects that run over time and over budget.

An RFI email thread in BuildAxis with an AI-generated summary, a panel of topics discussed, linked records and a voice recording widget.
Fig. 01RFI thread with an AI summary, linked records and voice capture for site meetings.

02

Solution

BuildAxis replaces the patchwork with one clear system.

Instead of switching between apps all day, teams manage projects, documents, finances, equipment and communication in one place.

AI handles the repetitive daily work: drafting documents, processing payments, routing messages to the right people and tracking machines on site. Field teams can focus on building; managers can focus on the decisions that matter.

Three phones showing the BuildAxis mobile app: a project dashboard, the blue launch screen and the sign-in screen.
Fig. 02The mobile app for site crews: dashboard, launch screen and sign-in.

03

What I delivered

I designed the full platform, web and mobile, from the first user flows to a ready-to-build Figma handoff.

That covered the web app for managers in the office and the mobile app for workers on site, designed as one experience so moving between them feels familiar.

Every screen shipped with developer notes and a reusable component system, so the team could move from design to code without guesswork.

BuildAxis document register table with an RFI creation form and a confirmation toast saying the RFI was submitted.
Fig. 03Document register and RFI creation. Dense data, kept calm and scannable.

04

Key design decisions

  1. 04.1

    One system for two very different users

    Managers need to see a lot at once: progress, approval queues, open claims and RFIs. Workers need the opposite: something simple and fast on a busy site. The answer was a layered structure: the dashboard leads with what matters most, and detail opens only when it's needed. Colour and status tags flag urgency without making screens noisy, and a modular component library lets new features land without breaking the design.

  2. 04.2

    Making safety steps easy to finish

    The first version of the safety induction was one long form, and workers gave up halfway through on their phones. I split it into short, clear steps with visible progress. Safety steps have to be completed, and the best way to get people to finish is to make the process feel easy.

  3. 04.3

    Money calculations people can trust

    Claims & Contracts is where the money is handled, so it has to be right. I built the real contract logic into the interface. Work value, retention and amounts tied to the defects liability period are calculated automatically instead of by hand in spreadsheets. The challenge wasn't visual: it was making complex financial information readable and trustworthy for people who aren't accountants.

BuildAxis defect record with a signed safety document, a quiz summary card and safety induction questions with the correct answers highlighted.
Fig. 04Safety induction, rebuilt as short steps with a clear quiz summary.
Claims table for a carpentry subcontract with claim statuses, a compliance card, respondent details and a contract value summary.
Fig. 05Claims & Contracts with contract values calculated in place.
The BuildAxis logo shown on white, black, dark navy and light grey backgrounds.
Fig. 06BuildAxis identity across light and dark surfaces.

05

Current status

The platform is designed end to end and handed over: the web app, the mobile app and a component library the team builds from. It's going into production now.

What the design settles is the structure. Six separate tools are replaced by one system, documentation sits inside the workflow instead of beside it, and both apps share a single component library. Whether that shows up as fewer errors or faster onboarding is something only real use on site will tell, and that data doesn't exist yet.

Next project

ProcuWise

Turning spreadsheet-driven procurement into a structured system, with an AI layer that compares vendors for you.

ProcuWise quote comparison open on a laptop placed outdoors on a stone surface.

Open to product roles & select freelance projects

Working on something similar?

Tell me about the product, the team and the timeline. I usually reply within 24 hours.