01Existing foundation
Ask Your Data
Find the records behind the answer. Ask about invoices, purchasing and expenses in your authorised workspace.
“Which supplier invoices are on hold?”
YOUR BUSINESS. AUGMENTED.
Make the systems you have
work smarter together.
The direction is simple: a conversation that connects questions, evidence and work. Start with the existing workspace foundation; shape the next step around your real business processes.
02Existing foundation
Resolve Exceptions
Bring the evidence into focus, identify the next step and keep controlled decisions with an authorised person.
“Why is this invoice blocked?”
03Planned capability
Build Workflows
Describe a recurring task. The planned experience will turn it into a proposed workflow for your team to review.
“Notify the owner when an approval is overdue.”
04Planned capability
Build Apps
Describe the view your team needs. The planned experience will help create focused apps around your business processes.
“Build an invoice exceptions dashboard.”
CAPABILITY BOUNDARIES
What’s here. What comes next.
“Existing foundation” means implemented in the current business workspace source, subject to your organisation’s configuration, permissions and deployment. It is not a claim that every customer has every module enabled.
| Capability | Current boundary | Availability |
|---|---|---|
| Ask Your Data | Questions about authorised Syntriva AI finance, procurement and expense records. Accounts receivable depends on the organisation’s deployed configuration. | Existing foundation |
| Resolve Exceptions | Recorded invoice analysis, status context and recommended next steps. Authorised people perform controlled actions in the business workflow; the assistant does not execute them. | Existing foundation |
| Build Workflows | Existing structured approval workflows remain available. Creating a new workflow through conversation is a planned capability. | Conversational builder planned |
| Build Apps | Generating new internal applications from a conversation is planned. The marketing demo displays an illustrative dashboard only. | Planned |
| External connections | Connections to existing ERP, finance, CRM, files and APIs require discovery. No live universal connector catalogue or confirmed vendor compatibility is offered. | Planned / subject to scope |
No release dates are promised. Pricing for planned capabilities will be agreed separately when scope and availability are confirmed.
ILLUSTRATIVE CONNECTION DESIGN · PLANNED
Talk to data where it already lives.
Your existing systems
Example targets: Xero, Microsoft Dynamics, a CRM or a business spreadsheet.
A permission-aware conversation
“Which supplier invoices are blocked, and what evidence is missing?”
A reviewed next step
Inspect source records. Propose a workflow. Keep approval with the responsible team.
This is a proposed architecture, not a live integration. Vendor support, data access, security review and any write permissions must be confirmed during discovery.
GOVERNANCE IN THE EXISTING FOUNDATION
People stay responsible.
Organisation boundaries
Current business-data queries use the authenticated organisation and existing role permissions.
Controlled action boundaries
The current assistant identifies approval, payment and record-change requests and requires an authorised human to act.
Evidence and traceability
Responses use persisted workspace records. Existing workflows record business activity; proposed external integrations will need their own agreed audit design.
Honest limits
Unsupported queries are identified. Conversation-built automation and apps are shown as planned, not as released features.