Navigation
Guided dropdowns
Every search and setup area should start with clear choices: role, need, location, project type, scope, material, and visibility.
Ease of use system
The platform should feel like it already knows what the user needs next.
This page defines the user-friendly structure: dropdown-first movement, guided setup, plain language, protected private areas, clear next steps, and role-based pathways.
Universal user path finder
Instead of making users understand the whole platform first, give them simple dropdowns that lead them to the right task.
- 1
Ask who the user is
Built to keep the user moving without confusion, dead ends, or unnecessary form fatigue.
- 2
Ask what they need to do
Built to keep the user moving without confusion, dead ends, or unnecessary form fatigue.
- 3
Show only the most relevant fields
Built to keep the user moving without confusion, dead ends, or unnecessary form fatigue.
- 4
Let them skip what they do not have
Built to keep the user moving without confusion, dead ends, or unnecessary form fatigue.
- 5
Suggest profile improvements later
Built to keep the user moving without confusion, dead ends, or unnecessary form fatigue.
- 6
Connect them to jobs, bids, people, suppliers, or training
Built to keep the user moving without confusion, dead ends, or unnecessary form fatigue.
No overwhelm ruleHide complexity until the user needs it.+
Short sections
Expandable details
Save and continue later
Progress bar
Plain labels
Examples inside forms
No dead end ruleEvery screen should have a useful next step.+
Continue
Save draft
Invite teammate
Add project
Find match
View profile preview
No local-only ruleThe platform should feel global while staying easy.+
Country first
Region/state/province
County
City
Service radius
International product origin
No lost work ruleA person's project history should survive job changes.+
Project resume
Role history
Reference request
Training record
Photo proof
Public/private controls
Forms
Plain-English forms
Use labels that real construction people understand. Avoid tech language and explain what each field does.
Clarity
Progressive detail
Show the basics first, then let users expand deeper sections for certifications, product lines, project history, or cost-sensitive notes.
Trust
Profile previews
Users should see what their public profile looks like before anything goes live.
Privacy
Private by default for sensitive items
Bid notes, pricing, relationship notes, internal team updates, and drafts should not accidentally become public.
Mobile
Mobile-first movement
Every core action should work from the field: add a project, upload a photo, save a note, apply, message, or search.