Updates on Requirements Agent, new apps, guidance, platform changes, and fixes.
Newest first ยท Last updated 17 Aug 2026
Featured
Latest high-signal updates
AppsGuidancePlatform
AI Marketplace expands delivery for targeted micro-apps
What changed. We are now a team of three supporting AI Marketplace work, helping ERM teams scope ideas and build focused internal tools.
What this means. ERM teams can start with Requirements Agent, then route the work as a platform build, consultant build, or co-build with the right subject matter review, data checks, and support path.
Recent Requirements Agent work tightened the route guidance, PRD preview, Word export, and admin review views so requesters and reviewers see a more consistent package.
Routing diagram is available as a static in-app reference.
PRD preview and Word export are better aligned.
All requests is easier to scan for impact, budget, status, and AI team notes.
Audience and governance checks are clearer for client-facing or externally shared use.
AI security guidance for client work is easier to find
The Governance page now calls out when client confidential, personal, financial, regulated, or otherwise sensitive data needs AI risk assessment or AI Security input before using an AI tool.
AI Marketplace expands delivery for targeted micro-apps
The AI Marketplace is ERM's internal route for identifying, assessing, and building focused applications that support client work. We are now a team of three helping ERM teams scope use cases, find the right delivery route, and build focused internal tools.
What changed now?
We are now a team of three supporting AI Marketplace work. We can help teams shape their use cases and progress selected opportunities through request review, build, launch, and handover.
What is the AI Marketplace?
The Marketplace is a practical route for turning well-defined internal use cases into supported tools. It helps teams move selected ideas through requirements capture, governance review, build, launch, and handover.
It is also the place to find existing applications before creating something new, and to make useful team-built tools easier to reuse across ERM when they meet the right quality, ownership, and governance expectations.
What is a micro-app?
A micro-app is a small, focused internal tool built for one specific workflow, task, or decision point. It is not a broad product or open-ended system; it should have known users, known inputs, an agreed method reviewed by a subject matter expert, and a clear output that can be reused by a team.
Good micro-apps help teams work faster or more consistently, reduce delivery cost, improve quality, reduce risk, or make a repeatable client-delivery step easier to run.
Start with Requirements Agent
Requirements Agent is the starting point for scoping a use case. It helps teams describe the need, check whether an existing tool already fits, and assess whether a new build is justified.
Not every request should become an AI Marketplace build. If another route is a better fit, such as an existing ERM tool, enterprise platform, analytics solution, automation route, or broader product effort, the request can be directed there instead. The route guidance explains how that decision is made.
How delivery can work
The new delivery capacity creates more than one path. The right path depends on complexity, ownership, data sensitivity, service-line urgency, and whether a team already has someone able to build with Marketplace standards.
Platform buildAI Solutions leads priority use cases that need stronger platform ownership, shared reuse, or more structured governance.
Consultant buildA service team builds the tool using the Developer Guide and Marketplace standards.
Co-buildAI Solutions and the service team build together when the method sits with consultants but the app needs platform support.
What makes a strong candidate
A defined client-delivery or internal workflow, not a general request to "make an app".
An agreed method, or a method that can be confirmed quickly with subject matter experts.
Named pilot users and a realistic path to adoption after launch.
Clear value, such as time saved, lower delivery cost, better quality, reduced risk, or faster turnaround.
Known data inputs, expected outputs, and a practical owner for review, support, and future changes.
How quality and data use will be checked
Selected builds will need subject matter expert review so the workflow, method, assumptions, and output are fit for purpose. Any use of client confidential, personal, financial, regulated, restricted, or otherwise sensitive data will also need the right AI security and governance checks before build or use.
What may need another route
Broad products with multiple unresolved workflows or unclear ownership.
Client-facing tools, external sharing, or use in front of clients.
Client confidential, personal, financial, regulated, restricted, or otherwise sensitive data without the right AI security review.
Large integrations, complex permission models, or enterprise-platform work better handled by an existing ERM technology route.