Interfaces
How your teams work with agents
Your teams and your agents work in the same place: shared views built around orders, suppliers, projects and claims, where everyone sees the same state of the work.
An order view brings together status, exceptions, customer messages, what agents have done and what they recommend next.
Custom apps
New working tools for humans and agents, built on top of your ERP and other systems. In some cases they replace ERP screens that were never designed for the work; in others they create tools that never existed. Pre-built for each vertical, and yours to change.
Dashboards
Live operational views of how the team is performing, what needs attention, and how agents and processes are going: throughput, exception rates, autonomy levels, business outcomes.
Working side by side
Agents and people act on the same orders, projects and claims. Agents handle what they can and bring decisions to the right people, with full context, when they need them. People can pick up any item, redirect it or override a decision. The work moves on whichever side is best placed to move it.
Build interfaces by chatting with AI
The people who know the work rarely have a developer to hand. So the builder takes plain language. Describe the tool your team needs and it creates the working view on your data: connected to the ERP and the systems around it, drawing on the shared context, showing what agents have already done. The same builder adjusts how agents behave and creates new ones. Everything it produces is real code, a React frontend on a FastAPI backend, versioned and deployed like the rest of the platform, with full code access the moment someone wants to go further.
- 01
Describe it
A claims desk for the service team, sorted by SLA risk, with what the agent has done on each case. A project overview for the site manager. A customer page for sales.
- 02
It arrives connected
It knows your entities, your procedures and your integrations, so the first version is already on live records, with what the agents have done in place.
- 03
You iterate by chatting
Another column, a different sort, a filter for your own region: ask and it changes while you are looking at it. The team that uses the view is the team shaping it, with no ticket and no release to wait for.
- 04
Real code, in your stack
A React frontend and a FastAPI backend, deployed alongside the pre-built views and versioned and promoted like everything else. Adapt it by hand when needed. Your domain experts own how it runs.
What Riff is not
- Not an ERP replacementRiff sits on top of your systems of record.
- Not a general-purpose assistantAgents have specific operational roles.
- Not a workflow toolAgents have judgment and context, not just trigger-action rules.
- Not an analytics platformThe context layer serves operations, and your BI tools plug into it.
We leave capability, not dependency
Our forward-deployed team works as part of your organisation from day one, deploys the first agents, and stays as the backstop until your own capability exists. Your builders learn on real use cases with our team alongside, the platform carries the standards, and your domain experts end up owning, extending and building agents around your own strategic goals.