Frequently asked questions
Practical answers about the product, implementation, data hosting, AI and access—without replacing the Security page.
Product
InsightEasy is a managed platform that connects existing business systems, organisational knowledge and approved workflows so staff can ask questions and receive grounded, usable answers.
No. It works across existing systems rather than replacing them. Your CRM, ERP, finance and document tools stay in place.
It is currently focused on Australian SMEs, especially organisations with several disconnected systems and limited internal BI or integration resources—typically around 20–100 employees, without treating that as a hard exclusion.
No specialist prompt engineering should be required. InsightEasy is configured around agreed business questions, terminology and data sources.
It can generate approved outputs (such as PDF and Excel) and run configured workflows where those capabilities are enabled. It does not perform unrestricted autonomous actions.
Implementation
A focused first implementation may be delivered in weeks rather than months, but timing depends on source access, data quality, report complexity, SSO, permissions and the availability of business experts for validation.
Typically discovery, connecting agreed systems, mapping existing reports, adding organisational terminology and documentation, configuring access, testing with business users, training and handover.
Yes, where appropriate. InsightEasy can support APIs, read-only databases, secure extracts and approved data dumps depending on the source.
No. Existing reports can often be used as reference outputs or mapped into the initial implementation.
Trust and AI
InsightEasy is hosted in Australia, with our application and primary data stores located in Australian infrastructure. This helps keep your business information close to home while providing the performance, reliability and security expected from modern cloud platforms.
InsightEasy does not use customer data to train its own models. External model providers are used via API; whether a provider retains or uses API request data depends on the provider and contractual/API settings selected for your deployment. We confirm the applicable settings during implementation.
No. Organisational knowledge is indexed within the client’s InsightEasy environment. Relevant passages are retrieved when required and supplied as temporary context for that request.
RAG is an “open-book” approach. InsightEasy searches approved business documents for relevant passages before asking the language model to answer. The model is not permanently retrained on those documents.
Yes. Where supported, answers can show the systems, reports and exact document passages used so your team can verify information before acting.
The answer will identify that the source could not be checked rather than silently presenting an incomplete result as complete.
Yes. InsightEasy reduces risk through source grounding, permissions, validation and visible evidence, but important decisions should still follow your normal review processes.
Access and security
Google sign-in is available today. Microsoft Entra ID SSO and other identity providers can be configured as part of implementation. The application may be surfaced through Microsoft Teams where included in scope.
Yes. Access may be controlled by role, connector, report, field and knowledge source.
No. Information a user is not authorised to access must not be retrieved or sent to the language model merely because they ask for it.
Client users may manage permitted day-to-day features. Connector and knowledge configuration remains restricted to authorised administrative roles.
Commercial
InsightEasy is designed around organisation-based access rather than mandatory per-seat AI licensing. Usage budgets and optional user allowances can still apply.
Implementation and recurring platform costs are typically scoped separately unless your commercial agreement says otherwise.
Yes. A focused first implementation with agreed systems, reports and reference questions is the recommended starting point.
More detail on hosting, ownership and provenance is on the Security and trust page.
Ready to connect the dots?
Show us the systems, reports and questions your team depends on. We will help define a practical first implementation.