Solar is not a simple counter sale. A customer may discover a system online, ask for sizing, receive a quotation, pay in stages, wait for equipment, have an installer assigned and return for service months later. Treating each step as a separate spreadsheet or chat thread makes it difficult to know what has happened and who owns the next action.
Different tools, one customer journey
Joshville's public website and Solar AI apps help customers browse, plan and follow their relationship with the business. The staff platform handles products, stock, customers, quotations, orders, finance and fulfilment. The installer portal gives field teams the part of the job they need. These are separate interfaces, but they should never create separate versions of the same customer or order.
The backend is the operating record
The shared backend keeps the identity of a product, customer and order consistent across each surface. A catalogue change can reach the website and apps; an online order can enter staff operations; fulfilment and installation updates can return to the customer. That continuity matters more than making every screen look alike.
Solar workflows needed their own rules
- Products may be sourced for an order rather than limited to what is physically on a shelf.
- A quotation can include equipment, delivery, installation and site-specific work.
- Installers need assigned jobs and customer context without receiving unrestricted business access.
- Finance and audit records must follow an order through deposits, balances, expenses and fulfilment.
- After-sales service belongs to the same customer and installation record, not a new support spreadsheet.
Why the platform was built separately
This system was built with the team behind Suite.ng, but it is a separate Joshville Global client platform rather than a standard Suite.ng workspace. Solar sizing, installer coordination, customer apps and connected monitoring are central to Joshville's operation, so they required a product shaped around this business instead of features added to every Suite customer.
The goal was not to put every employee in one giant dashboard. It was to give each person the right view of one reliable operation.
What customers should feel
Customers should not need to understand the architecture. They should see accurate products, receive a coherent quotation, know what they paid for, follow an order and get support without repeating their entire history. The technology succeeds when that experience feels ordinary.