What it is
AI Marketplace is ERM's internal home for discovering, scoping, building, and sharing focused AI and automation tools. It combines a catalogue of ready-to-use apps, the Requirements Agent for route assessment and PRD generation, and a governed app platform for AI Solutions builds, AI Solutions and consultant co-builds, and consultant-built solutions vetted by AI Solutions. Use what already exists first; build only when the workflow needs it.
| Aspect | Detail |
|---|---|
| Status | Experimental. Not an IT service. No SLAs or change management. |
| Audience | ERM staff only. Clients do not access Marketplace tools or use them for client work. |
| Access | ERM sign-in (Microsoft SSO) required on every tool |
| Hosting | ERM-managed AWS, single region (us-east-1) |
| AI | AWS Bedrock using the approved model configured for each environment |
| Cost | Absorbed centrally, not charged back to teams or projects |
Where it fits in ERM's strategy
AI Marketplace is one of three pillars in ERM's Client Delivery Evolution (CDE) automation and AI strategy. It is the "end users create software" pillar — helping consultants find existing capabilities, test ideas, shape requirements, and publish reusable tools with support that increases as complexity and risk increase.
| Pillar | What it means |
|---|---|
| Look to the market | Partnering with tech providers for joint go-to-market (e.g. Blumen, Upright Project). |
| End users create software | AI Marketplace. Consultants build and ship their own tools using AI and rapid prototyping. |
| Build where there are gaps | Custom software built via third-party developers where our needs require it. |
What is a micro-app?
A micro-app is a small digital tool that improves 1 agreed business task. It takes known information, follows an agreed method, and produces 1 clear result.
- Scope
- 1 agreed business task1 clearly defined workflow with 1 main result.
- Method
- Ready, or agreed within 2 weeksIf the method needs longer discovery, it is not yet ready for the micro-app build cycle.
- Build
- 3–5 weeksLed by 1 AI Solutions Engineer after the method is agreed.
- Adoption
- 5 named pilot usersTarget >20 people completing the main task each month, or an agreed equivalent for seasonal or specialist work.
- Value
- Measurable business benefitTime or cost savings, or a clear improvement in client delivery, quality, consistency, or risk.
- Total monthly cost
- Up to $500 per appApproved planning ceiling covering hosting, AI usage, and other services. Actual costs are assessed case by case.
These are planning guidelines, not rigid rules. We assess every request case by case, taking account of its context, expected value, users, risk, and delivery needs. Monthly active use means completing the app's main task, not simply opening it. Where discovery is needed, the full journey may take up to 7 weeks: no more than 2 weeks to agree the method, followed by a 3–5 week build.
Cost breakdown
| Cost | Planning expectation |
|---|---|
| Production (prod) hosting | About $15 per month while the live app is running. |
| Development (dev) hosting | About $15 per month while the development version is switched on for building and testing, normally for 1–2 months. |
| AI usage | Use $100 per month as the initial planning assumption. Actual charges depend on usage and are monitored through shared Marketplace controls. |
| Shared AI engineering accounts | A team-level programme cost included in the annual budget, not in the per-app total above. |
| Ongoing support | Internal team time for fixes and updates; separate from AWS and AI charges. |
| Higher usage and other services | Additional compute, AI usage, storage, file processing, licences, or specialist services may increase costs up to the $500 ceiling. |
When a request needs a broader solution
Some ideas begin with 1 task but become broader products when they combine several capabilities or create continuing operational responsibilities.
A broader product review is needed when the solution:
- combines several connected journeys, such as analysis, evidence review, follow-up questions, dashboards, saved work, or multiple outputs;
- depends on an expert method that will continue to evolve or requires ongoing specialist validation;
- stores records, histories, versions, or shared workspaces that users return to over time;
- needs multiple user roles, complex permissions, enterprise integrations, or direct client access;
- requires bespoke security, storage, infrastructure, or high and unpredictable AI usage; or
- needs more than 5 weeks to build, regular specialist support, or a continuing product roadmap.
The Requirements Agent will help determine whether a micro-app or another delivery route is the best fit.
Find the right route
Start in the Requirements Agent. It checks specialist handoffs and existing tools before assessing whether the next step is self-service, an AI Productivity solution, an internal AI Marketplace build, or broader delivery review.
One request, the right next step
Follow the branches, then zoom in to read any part of the chart.
This is not a request to rebuild. It records the current solution, intended users and usage, likely cost, ownership, governance, and expected value; it also gives GSL and CDE teams visibility where relevant. That evidence helps decide whether to keep the current hosting, move to AI Marketplace, or use another route.
Before committing: confirm ERM availability, licences, connectors, permissions, data controls, ownership, and ongoing cost. Sensitive or client-confidential data needs the relevant AI security review.
Why now
The technical bar for software development is lowering. ChatGPT, AI coding assistants, Lovable, and similar tools let end users with limited or no coding experience build real applications that solve their own business problems. Waiting for central IT to build everything is no longer the fastest path — the consultant closest to the problem is often the right person to build the tool.
Who it is for
ERM staff who want to use an existing capability, improve a repeatable workflow, or create a focused internal tool with a clear owner and measurable value. Marketplace tools are for internal productivity and efficiency — do not give clients access or use them for client work or deliverables. If your use case involves client confidential or sensitive data, review the AI security and client data guidance before proceeding.
Contact
| Role | Detail |
|---|---|
| Owner | ERM Digital Products — AI and Automation |
| ERM AI Solutions team | [email protected] |
| Governance | Decisions, open questions, and rules on the Governance page, including AI security guidance for client data |