Approved user roles
Customer, contractor, company, crew, and platform-admin paths stay separated.
How it works
ezProject.ai is designed around the full contractor/project lifecycle, not just lead generation. The detailed marketplace overview and workflow process now live here instead of repeating on the landing page.
Start with a projectA private demo of the full contractor marketplace path: from safe project intake to contractor discovery, structured estimates, project execution, warranty, and external PayTrack coordination.
Customer, contractor, company, crew, and platform-admin paths stay separated.
The private demo follows the approved build plan instead of improvised feature claims.
PayTrack coordinates external payment status only; it does not hold, transfer, or process funds.
Synthetic data, controlled preview, no public onboarding or production marketing.
Workflow image direction
The layout follows your Figma direction: large clean cards, numbered steps, compact timing labels, and simple connector lines. The copy is adjusted to match ezProject.ai policy boundaries.
5 mins
Customer submits scope, timing, and broad service area without exposing private contact or exact address.
Privacy-safe
Eligible contractors discover matching opportunities by service, category, and configurable location.
24-48 hours
Contractors submit structured estimates with scope, assumptions, timeline, and preserved terms.
1-3 days
Customer compares offers and selects one contractor or company when the verified workflow allows it.
External only
Track due dates and external payment status without holding, transferring, processing, or escrowing funds.
Ongoing
Milestones, schedules, crews, materials, messages, progress, and warranty stay connected.
Audit-ready
Important workflow states preserve records for completion, reporting, and future support context.
For contractors
Contractor signup is separate from customer signup, but both use the same pop-up account flow so users do not lose their place while browsing.
Private demo boundary
Open the private demo lab for implementation evidence through M9.1. Public launch, payment processing, escrow, subscription billing, and M9.2+ payment-proof workflows remain outside this demo scope.