Start with the outcome.
Use a blueprint or your own idea. Define the team, systems, contracts and acceptance tests around the job.
Explore the build path →The Novagentica platform
Business Authority.
For the agents you choose.
Build new agents or improve existing ones around a clear business goal. Your business sets their authority. Novagentica supports testing, reviewed releases, action checks and result verification. Your chosen platforms execute the agents.
Freedom to choose.
Your agents. Your authority. Your systems.
- YOUR AGENTS
Propose the work
Agents run on the platforms you choose.
- YOUR SYSTEMS
Verify the result
Read back what was recorded and keep the evidence in Flight Recorder.
Runtime connections and the control flow
Agents · your chosen platforms
Copilot StudioMicrosoft
AgentforceSalesforce
Custom agentsYour runtime choice
Business AuthorityCheck the action.Systems of record
SAP / ERPOrders & operations
Salesforce / CRMCustomer records
Your systemsOther business records
Check the proposed action against the authority your business set. Authorized actions proceed; exceptions go to the responsible owner.
Two ways into the same process
A new business capability.
Or a better existing agent.
Start with the connected estate.
Review governance, applicable regulatory requirements and business value across the agents you already use. Prioritise gaps, review improvements and retest before redeployment.
Explore the assessment path →Both continue through the same Business Authority, release decisions and evidence in Flight Recorder.
Clear responsibilities
Everyone knows what they are responsible for.
Business teams set the goal and the rules. IT connects the systems. Your existing agent platforms keep running the work.
Sets the rules
Chooses the task, the limits and the person who handles an exception.
Purpose · Limits · Accountable owner
Checks actions and results
Assesses agents, checks proposed changes and keeps the records needed to review them.
Assessments · Action checks · Recorded results
Run the agents
Run the agents on your chosen platforms, with the agreed checks connected.
Your agent platforms · Your choice
Record what happened
Hold the order, case or transaction that gets checked after the action.
Purchasing · Customer records · Other systems
From either starting point to the next improvement
Give each agent a clear job
and a way to improve.
New and existing agents follow the same process. Agree what success means, test changes and retain the evidence. Your team approves each release and uses the results to decide what comes next.
- Describe the job
Give the work a goal, a baseline and an owner. Decision, Data and Interaction Contracts define permitted actions, access and human involvement.
- Test and release
Test the tasks and exceptions the agent should handle. Keep the results with the version your team approves.
- Check actions and results
Check who is acting and what they are allowed to do. After a change, read the system record back and keep the result.
- Measure and improve
Compare outcomes and costs with the baseline. Review proposed improvements, test the changes and approve the next version before redeployment.
From request to result
A critical action needs
more than system access.
An agent has access to your purchasing system. Your team still needs to decide which suppliers it may use, how much it may spend and who approves larger orders.
Create a purchase order
- Requested amount
- €24,000
- Supplier
- Approved supplier A
- Action
- Write to the ERP
The agent requests an order and provides the details needed to check it.
Check your purchasing rules
- Is this agent allowed to place orders?
- Is the supplier approved?
- Is the amount within the €25,000 limit?
- Is an approval required?
Allow the order within your rules, or hold it for the purchasing owner to review.
Check the actual ERP record
- Order amount
- €24,000
- Supplier
- Approved supplier A
- Result
- Matches the request
Check the recorded supplier and amount, and keep the result with the approval.
What if the amount is €32,000?
It exceeds the €25,000 limit in this example. The order waits for the purchasing owner’s decision.
Fit it to your environment
Start with one task and the system it changes.
Choose a task such as placing an order or updating a customer record. We’ll identify where the checks need to happen and how to confirm the change.
What we work through with your team
Agent & runtimeIdentity, version and the action it requests
Business ownerLimits, approval route and release decision
System connectionWhere the write happens and how to read it back
EvidenceWhich records the responsible team needs to review
Choose where the controls run.
We assess the deployment options your security and data requirements need, including cloud, on-premises and isolated environments. Availability and local enforcement are confirmed for the proposed setup.
Keep your existing agent platforms.
Use a supported connection or agree a custom integration. We test how your rules apply to the platforms and actions in scope.
Start by assessing existing agents ↗For your IT team
A closer look at how it works.
Do we need to replace our agent platforms?
No. Start with your existing agents and runtimes. We agree the integration and actions in scope, then establish the checks, approvals and evidence around that work.
Does every tool call have to pass through the Gateway?
Every action within the agreed governed scope must pass through the configured Gateway path. The contracts determine which checks, approvals and budgets apply. We confirm coverage for calls, data access, handoffs and responses during integration; activity inside an opaque external service is covered only at its exposed interfaces.
What if the business system records something different?
Novagentica compares the recorded result with the authorized action. A mismatch is flagged with the request, decision and business record for review. It does not imply that the original transaction has been automatically reversed.
Who remains responsible for approval and release?
Your designated business and platform owners. Novagentica supplies the controls, findings and evidence that support their decisions; it does not transfer accountability away from your team.
How does this work with controls in our existing platforms?
Keep the identity, security and runtime controls your platforms provide. Define where Novagentica adds the business rules, approval path and result verification for the process in scope. In an evaluation, test the same action across your selected runtimes and check whether the rule and evidence remain consistent.
What should our architecture team validate before an evaluation?
Confirm the runtime connection, enforcement coverage, permitted fields, evidence access and deployment location. Test what happens when a control or business system is unavailable, and measure the latency of the complete path. Agree these facts for your environment before expanding the rollout.
Talk to Novagentica
Let’s choose your starting point.
Bring a new business goal or an existing agent. We’ll work through responsibility, the systems involved and how to judge a useful result.