TradieArc keeps the current scope, quote, private handover, appointment, participant conversation, private photos, work state and completion history attached to one Job so a customer and tradie are not operating from different versions of reality.
Customer
Tradie
Shared lifecycle
Choose the trade, describe the work and use an approximate Job location. Exact address, contact and access details stay out of the lead.
An eligible trade workspace can submit one auditable quote. If the customer materially changes the Job, the old quote needs review before it can become acceptable again.
The customer prepares the exact site/contact/access handover. It is revealed through the authorised Job relationship instead of being placed in public scope.
The trade proposes the appointment. The customer confirms or asks for another time, and a replacement does not silently erase the current confirmed appointment.
Participant messaging, private site/progress/completion photos, appointment state and received activity remain attached to the work instead of scattering across separate tools.
The tradie completes the awarded work and the customer can review it. Completion/cancellation preserves the record rather than deleting the relationship context.
Next layers
These are part of the product direction, but the current interface keeps them labelled as gated until the required security, legal and operational systems exist.
Reuse relationship/site context for a fresh Job without copying stale private data into public scope.
In-app activity works now. Email/SMS should add monitored delivery and preferences rather than becoming a hidden source of truth.
Human-first provider profiles, search and reusable enquiry links are part of the marketplace north star but remain a public-launch gate.
The north star includes repeat work and human-first public profiles/direct enquiry links, so customers can choose a known tradie again and tradies can turn outside acquisition into the same organised Jobs workflow.
Yes in the controlled early-access workflow. A customer workspace can post a Job and eligible signed-in trade workspaces can receive matching operational leads, quote and continue the Job lifecycle.
A material pre-award change advances the Job version. Existing submitted quotes need trade review and cannot be accepted as if nothing changed. The conversation stays attached to the Job and any saved private handover must be reviewed for the current brief.
Those details belong to the private fulfilment handover, not the public lead. The accepted trade workspace gains access only through the authorised awarded-Job relationship.
Yes. After award, the trade proposes the time and the customer confirms it or requests another. Appointment changes and cancellations remain attached to the Job history.
Yes after award through the private Job-photo flow. Participants with the correct workspace access can view them; general documents and chat attachments are not being represented as live yet.
No. Current provider cards are clearly labelled visual samples. Open public discovery, public review aggregates and verification badges remain gated until their public-surface and operator controls are ready.
No. Card collection, subscriptions, trials, premium placement and paid ranking are not connected. Matching quality must not be distorted by future monetisation decisions.
Not currently. The appointment and received activity are stored in the Job, while outbound delivery and third-party calendar integrations remain separate gated enhancements.
That repeat-work continuity is part of the next product layer. The product direction is to start a fresh Job from the existing relationship while protecting old private details and preserving prior history.