FEBRUARY 2025 — PRESENT
Unifying every stage of the home development lifecycle
I led design across the platform, defining how data and teams operate within the system.
In production with active users. Additional modules in ongoing development.
Teams were working across disconnected tools, making even simple tasks slow and error prone.
8+
tools used in a single project
4
handoffs to move a sold job into execution
The goal was to bring estimating, project management, procurement, scheduling, and financial tracking into one system.
In construction, workflows evolve across roles and timelines, not following a linear path. Most tools out there enforce structure too early, which breaks as projects become more defined.
THE SYSTEM
Five systems, one platform.
Instead of defining workflows upfront, we introduced five core pillars, establishing a foundation while allowing decisions to take shape over time.
01
Sales
capture demand
02
Preparation
define the work scope
03
Execution
operationalize the job
04
Field
execute + track delivery
05
Finances
manage cost + changes
FRICTION SHOWED UP IN THREE PLACES
01
Sales Conversion
Qualified work wasn't consistently turning into active projects.
02
Task Efficiency
Simple tasks took too many steps to complete.
03
Cross-Team Visibility
Information didn't carry cleanly between teams.
DESIGN CHALLENGE — 1 OF 3
How do you introduce structure without slowing teams down?
INSIGHT
Too much structure slowed teams down. Too little made the system hard to trust.
SOLUTION
We set global rules where consistency mattered, and left the tool flexible for teams to adapt.
Global financial markups exist in Admin Settings at the system level, versus dynamic adjustments at the project level.
OPERATIONS PROBLEM — 2 OF 3
As we brought more features into one place, the system became harder to navigate.
INSIGHT
Showing everything at once overwhelmed teams.
SOLUTION
Early stages were kept lightweight, introducing more complex features only as projects progressed.
DESIGN PRINCIPLE
Early stages show quick details only. Complex tools like estimating and selections appear as the project progresses and more information becomes available.
ASSUMPTION — 3 OF 3
We assumed that keeping all project details and history in one place would reduce manual handoffs.
INSIGHT
That assumption didn't hold. Project details accumulated across months of work, and stakeholders kept running into information they needed but couldn't find. Approvals got stuck, decisions got lost, and the “all in one place” vision was producing noise, not clarity.
SOLUTION
We introduced clear ownership at each step, with defined approvals and next actions to move work forward.
HANDOFF
A large platform couldn't rely on one-off screens.
I identified recurring patterns across the product (tables, status states, actions, approvals, summaries, and detail views) and translated them into reusable design logic so engineering could implement new workflows consistently instead of rebuilding each screen from scratch.
WHAT THE SYSTEM WAS BUILT TO DO.
01
Surface stalled and at-risk work
Inactivity, missed follow-ups, and operational drift become visible instead of accumulating silently.
02
Carry context between stages
Decisions and details flow from sales through execution without re-gathering information at each handoff.
03
Evolve after launch
The platform can absorb new workflows and modules without rebuilding existing surfaces.
04
Enable operational intelligence
The data model and pattern library create the foundation for future automation and reporting.
CHALLENGES ENCOUNTERED
Designing across interconnected workflows
Balancing governance with flexibility
Making complex processes feel clear in practice
LEARNINGS
Structure only works when teams understand and adopt it
Simplicity comes from intentional constraint
Handoffs only work when ownership and next steps are clear