Product information and feedback
Help shape the workflows your trade needs.
Tell us which document or task you want to improve and how it fits into a real job. Specific examples help us understand the work behind a feature request.
Evaluate what you can use now.
Product pages, plan information and sample PDFs are available for all seven apps. The access page is the route for confirming access for your device. Review the actual features in the version you will use before making a buying decision.
Free starter options cover the family. Availability, document coverage and included features should be checked for the selected product and plan, not inferred from another app.
Make a feature request useful.
- Name the app and the document type.
- Describe the step that takes time or causes repeated work.
- Explain what a successful result would look like for your business.
- Include the device, relevant equipment or team arrangement.
- Use anonymised examples rather than confidential customer records.
If a current function is failing, use support so it is treated as an issue rather than a suggestion.
A request is not a release commitment.
Requests are considered alongside product and technical requirements. Submitting one does not confirm a release date or inclusion in a particular plan. If a missing feature is essential to your purchase, ask for its current status before subscribing.
For a larger team or a move from another system, share the practical requirement through the walkthrough request or team route.