
Databutton Launches Business Context to Eliminate Repeated Explanations in AI Development
Databutton is launching Business Context in Riff, a feature designed to create a shared knowledge layer that captures organizational rules, exceptions, and expertise as teams build AI agents. The update, announced in a LinkedIn post and set to go live March 4th at 11:00 AM CET, aims to solve a persistent problem in AI development: having to re-explain business logic and context for every new build.
The core innovation is accumulation. Each time a team builds something in Riff, the platform captures the underlying business context, including edge cases, approval workflows, compliance requirements, and institutional knowledge that typically lives only in the heads of experienced employees. That context becomes available to every subsequent build and every AI agent in the organization.
"No more starting from scratch. No more re-explaining everything to every new build," the company stated in its announcement.
How It Works
Business Context operates as a persistent layer beneath all Riff builds. When a developer or business user creates an application or agent, they naturally encode business rules, define processes, and handle exceptions specific to their organization. Riff captures this information and makes it accessible system-wide.
For example, if a finance team builds an expense approval agent that handles specific company policies around international travel, those rules become part of the shared context. When HR later builds a different agent for travel booking, it can read and apply the same approval logic without manual re-configuration.
This approach differs from traditional documentation or knowledge bases, which require separate maintenance and often fall out of sync with actual practice. Business Context is built through usage, not documentation effort.
Why It Matters for Organizations Scaling AI
The announcement positions Business Context as fundamental infrastructure for organizations deploying multiple AI agents. As companies move beyond pilot projects to enterprise-scale AI implementation, context fragmentation becomes a major bottleneck. Each new agent or application requires extensive setup, explanation of business rules, and integration of organizational knowledge.
Databutton CEO Martin Jonasson and team member Viral are hosting a livestream to introduce the feature, suggesting the company views this as a significant strategic move. The timing aligns with broader industry trends around AI governance and organizational memory, as enterprises seek ways to make AI deployments more efficient and consistent.
For Riff users, the immediate benefit is velocity. Teams can ship new agents faster because foundational context already exists. There's also a governance advantage: when business rules are captured in a shared layer, it's easier to ensure consistency and compliance across different AI implementations.
Positioning in the AI Development Stack
Databutton has positioned Riff as a platform where business teams can build AI agents with IT governance. Business Context extends this vision by making organizational knowledge a first-class system component rather than something recreated for each project.
The feature puts Databutton in competition with enterprise AI platforms that focus on knowledge management, as well as vibe coding tools like Bolt, Lovable, and Cursor that offer AI-assisted development but typically lack organizational context layers.
Databutton has been expanding its platform capabilities recently, including adding GPT-5 support and rolling out Gemini 2.5 Pro to all users. Business Context represents a shift from model access to structural improvements in how organizations use those models.
The feature goes live March 4th for all Riff users. Registration details for the livestream are available in the comments of Databutton's LinkedIn announcement.
Sources
1 checkedHow we cover tool news: Create With's tool desk drafts these reports with AI from the sources listed above and checks them against those sources before publishing.



