A public portfolio that looks like your business
Publish your services, sectors, locations, approved project stories, trust signals, and contact routes without exposing private ERP data.
Software, mobile, customers, suppliers, payments, learning, and community—connected for the trades. Explore the Network →
My Trade Site
Turn your best work into a public portfolio that brings the next job into your ERP.
My Trade Site is the public-facing layer for a trade business: a credible portfolio, clear service routes, and an enquiry form connected to the tenant workspace behind it.
The outcome
Make trust visible before the first call, then make every enquiry actionable.
A portfolio should do more than look polished. It should give customers a reason to contact you and give your team enough context to respond well.
Leads land in the right workspace
Every submitted enquiry is routed to the tenant and branch you choose, with source, contact details, job context, and consent captured for follow-up.
One proof layer for every channel
Use the same approved portfolio link from your website, quote emails, social profiles, directory listing, and customer conversations.
Human-approved publishing
Draft your public presence in the ERP, preview it, and publish only the pages, images, and claims your team has approved.
Customer conversations stay connected
Move from enquiry to qualification, survey, estimate, quote, job, invoice, and payment without starting the record again.
Built for multi-branch growth
Route enquiries to a default branch today, then add location pages and branch-specific ownership as your operation expands.
The customer journey
From public proof to an owned ERP lead.
The intended handoff is simple: customers see the right proof, submit a useful enquiry, and your team follows it through the same operational system as every other lead.
Connected platform overview
Every important relationship in trade work connected in one operating layer.
Office teams, field teams, customers, suppliers, mobile workflows, payments, and automation share context instead of living in separate tools.
ERPCRMMobileCustomer portalSupplier networkPaymentsAICommunity
Network relationships
Businesses
Commercial control, scheduling, finance, and oversight.
Tradespeople
Field execution, site context, notes, and completion.
Customers
Requests, approvals, documents, and payment touchpoints.
Suppliers
Pricing, availability, ordering, and goods movement.
Payments
Invoice collection and billing pathways tied to real work.
Community
Trust, support, learning, and long-term trade relationships.
1. Configure
Choose your public name, service areas, trade categories, contact route, approved media, and lead-routing branch.
2. Preview
Review the public profile as a customer would see it. Private ERP records, financial data, and internal notes remain out of scope.
3. Publish
Use a shareable portfolio URL and embed it into your existing website, email signatures, social profiles, and directory presence.
4. Convert
New enquiries become Leads in the tenant workspace, ready for qualification and the connected lead-to-payment workflow.
Publishing guardrails
Public by design. Private by default.
The public site should expose only approved business information. Tenant data, customer records, job margins, internal notes, and operational controls stay behind the authenticated ERP boundary.
Review security principlesApproved profile content only
Tenant and branch-aware lead routing
Source and consent captured at submission
No public access to private ERP records
FAQ
My Trade Site questions
Is My Trade Site separate from the ERP?
It is the public-facing layer connected to the tenant ERP. The portfolio is designed for publishing approved business content; lead capture hands new enquiries into the tenant workspace.
Can each branch have its own profile?
The first rollout should use a tenant-level profile with a default branch for routing. Branch-specific pages and routing can be added once the publishing model is validated.
Will customers see private jobs or prices?
No. Private ERP records, internal notes, margins, and customer data must remain behind the authenticated ERP boundary. Only approved portfolio content is public.
Can I use my existing domain?
The intended rollout supports a shareable portfolio URL first, followed by custom-domain mapping once publishing, DNS, and tenant verification controls are in place.