Your users chase. Their clients search.
Professionals send questionnaires and chase documents. Their clients search, complete and return them by hand.
Established software providers
Connect your platform to your customers’ agents.
Your platform is the system of record. Your customers’ clients increasingly have an AI agent of their own. Nova connects the two: your known fields become agent-ready requests, and approved answers and documents return to the right record.
A co-building partner that builds the capability with you, on Nova Backbone.
Established software providers
Where the friction is
Agents arrive outside your platform.
Clients start to use personal AI agents. Without a connection, those agents work around your platform, not with it.
Building it alone takes a team.
Connectors, consent, validation and writeback are a product of their own. Most roadmaps have no room for it.
What has changed
Clients now bring their own agent. The platform that lets that agent work inside its workflow, with permission and review, keeps the relationship.
Established software providers
From a known field to a completed record
Connect
Nova connects to your platform through an agreed data contract and loads a versioned catalogue of supported fields.
Build the request
Your user selects known fields. Nova generates the form, the agent task and the mapping back to your platform.
Send
The request is linked to the right client and record, and sent as a secure link.
The client’s agent prepares
The client chooses an agent, grants scoped permission, resolves open questions and approves the exact response.
Return with a receipt
Nova validates the response, writes it to the right record and only marks it delivered once your platform confirms receipt.
Who does what
- Your platformStays the system of record. Provides the agreed data contract and receives answers and documents in the existing workflow.
- NovaBuilds and runs the connector, field catalogue, forms, agent adapters, consent, validation, delivery and status.
- Your usersSelect the client and the fields, send the request and review the returned record.
- Their clients and agentsThe client authorises the agent. The agent gathers and drafts within that scope. The client approves what is shared.
Rules that never bend
- No agent access before the client’s permission.
- Nothing is shared before the client approves.
- No request goes live with an unmapped field.
- Delivery only counts with a receipt from your platform.
- A retried submission never creates a duplicate record.
Use case: Accounting software
Tax documents, prepared by the client’s own agent.
An accountant selects the income statement, the pension certificate and the childcare question from the platform’s known fields. The client lets their agent collect the documents, confirms the open question and approves. The answers land in the right dossier, with a receipt.
A concept we are developing with an accounting software provider. Data access and agent capabilities are validated per platform.
Established software providers
How we work together
Demonstrate
Show the workflow and validate demand with one of your customers.
Co-build
Agree data access, integration scope and a funded pilot.
Commercialise
Offer it to your customers, embedded in your platform or under your brand.
Expand
Add use cases on the same connector, form and agent layer.
Start small: one environment, one questionnaire, a few known fields, one agent and a manual fallback.