Software nobody was trained on is software half the company avoids.
Every field service platform has screens most of the team never learns. The knowledge lives with two or three people, gets asked for by text message, and disappears entirely when those people are out. Training documents help right up until a screen gets reworded and the document quietly becomes wrong.
SolarProjeX ships a written manual and an in-app assistant that read from the same source. Over a hundred documented topics cover what each screen does and where it stops. The manual renders them filtered to the person reading — a technician's manual has no payroll pages in it — and the assistant answers questions from the same material.
The freshness check is mechanical, not aspirational. Each topic is fingerprinted against the actual labels on the screens it describes. Reword a button and the topic is flagged for review; rename it entirely and the assistant drops that topic rather than answering from a document that names a control which no longer exists. An assistant that confidently describes a button nobody can find is worse than no assistant.
What it does, point by point
- Answers drawn from your own documented procedures, not general web knowledge
- Also reads the trade knowledge base and the notes on the job being asked about
- One source of truth behind both the written manual and the assistant
- Manual filtered by role and access — people see the pages that apply to them
- Topics fingerprinted against real screen labels, so stale documentation is flagged automatically
- A topic naming a control that no longer exists is withdrawn rather than served
- Per-person on and off switch, plus a company-level usage ceiling
- Printable manual generated from the same corpus for onboarding and handouts
