Project progress and schedule state
Customers can see published progress percentages, schedule state, project updates, scope, and closeout information for that job.
Customer portal and e-signatures
Give each customer a clear view of one job
Publish customer-safe progress and customer-visible project data while internal job costs, private notes, and every other job stay out of the portal.
Customer-safe by design
A focused project view instead of a chain of update texts
Each active portal is tied to one job. The contractor controls which files, selections, change orders, and updates are customer-visible.
Customer-visible project data
Share customer-visible files, sent or approved change orders, selections, payment schedules, warranties, and signatures.
Sign and pay
A customer can review the selected item, written scope, amount, terms and consent statement, draw an electronic signature, and pay the invoice shown in the portal.
Portal boundary
One portal link, one job record
The public projection is deliberately narrower than the contractor workspace.
What the customer can see
- Customer-facing scope, exclusions, balance, payment schedule, and published project progress
- Files and selections explicitly marked customer-visible
- Sent, approved, or billed customer-visible change orders
- Electronic approvals, closeout, progress updates, and warranty records
What stays out
- Other customers and other jobs
- Internal-only files and rejected files
- Unpublished contractor notes and operating controls
- Labor rates, receipt details, internal cost calculations, and private workspace data
Synthetic example
A remodeling customer checks progress without calling the office
This scenario demonstrates the workflow and is not a testimonial.
Synthetic example
A customer opens the kitchen-remodel portal, reviews the latest published Project Pulse update and schedule state, views the published countertop selection, and electronically approves the selected change order. They cannot browse the contractor's other jobs, private notes, costs, or team records.
What Ardaro does — and what it does not
What it does
It creates a customer-safe projection for one job and records consent-backed electronic approvals from the portal.
What it does not do
It does not expose the full workspace, replace contractor review, decide what should be shared, or provide a universal legal determination that every electronic record is sufficient for every situation.
See the real workflow
Walk through the customer portal and e-signature flow
Watch actual Ardaro backend footage, choose a paid plan, or call Brent Scott directly if you want a human answer about how this fits your crew. Monthly billing is in USD. Verify your account and complete secure checkout; access starts after payment is verified. Creating an account does not charge you; review the final total before you confirm and pay. Founding, Enterprise, custom setup, and integrations are arranged separately and require reviewed terms.