Services
Start with the reporting, data or workflow problem—not a service diagram.
You may need a trusted answer from several systems, a report that no longer depends on spreadsheet reconciliation, a place for a team to review and act on exceptions, or one recurring workflow taken out of manual operation.
Memory(One) helps choose the smallest credible route. You do not need to understand every service distinction before starting.
The primary journey: AI Data & Automation
Use this journey when the problem involves several systems, unreliable reporting, unclear readiness or a custom operating layer.
Assessment
When the next move is unclear: map the current workflow, systems, data, baseline, owners, risks and opportunities. Leave with a practical build, redesign, pause, no-build or approved alternative-route decision package.
Foundation
When systems do not agree: connect the selected sources, establish tested business definitions and build trusted reporting, dashboards or a first bounded capability in the client’s approved environment.
Operations
When dashboards are not enough: build the daily internal tools, review queues, approval paths, exception views and workflow controls that let a team act on reliable data.
How is Foundation different from Operations?
Foundation connects selected systems, establishes tested business definitions and reliable data flows, and delivers reports, dashboards or a first bounded capability. Operations is the custom daily action and control layer built on reliable data: review queues, approval screens, exception views and workflow-control surfaces. Operations is not a support plan, and Foundation is not merely a dashboard.
All prices are excl. VAT and third-party costs. Final scope and timing depend on access, systems, data quality, stakeholders, risk and operating requirements.
Are prices fixed, and what affects the final quote?
The public pages show the approved fixed price, starting price or typical timeframe for each route. The written scope controls the final quote. Access, systems, connector complexity, data quality, stakeholders, security, procurement, risk, operating requirements and third-party costs can affect scope, price or timing. Prices are excl. VAT and third-party costs unless stated otherwise.
A separate managed route
Managed Automation
Choose Managed Automation when one recurring workflow is already bounded, has a named owner, manageable exceptions and a manual fallback, and should run on the Memory(One)-managed platform under the agreed care or customer-raised incident-support arrangement.
This is not stage four of AI Data & Automation. It is one managed business capability rather than a client-owned data foundation or bespoke operating layer.
A focused alternative
Custom & Advisory Work
Choose Custom & Advisory Work when the requirement is already narrow, a production-readiness or architecture review is the right next step, or a focused build, advisory session or workshop is more appropriate than the primary journey.
Formats include focused builds, architecture and implementation reviews, advisory sessions, workshops and post-launch support.
Explore Custom & Advisory Work
Post-Launch Support & Improvement
Choose Post-Launch Support & Improvement for periodic monitoring review, fixes and agreed improvements after a client-owned project handoff. It remains distinct from Operations, which is a custom operating-layer build, and from Managed Automation care/support.
What sits underneath the route
Once the buyer problem and route are clear, the implementation may use five connected layers.
- Source — identify the systems and information needed for the business question.
- Ingest — move the selected data reliably and make failures visible.
- Model — turn source-shaped data into tested business definitions and useful views.
- Orchestration — run the right steps in the right order, with ownership and recovery paths.
- AI Interface — expose a bounded dashboard, report, assistant or controlled workflow that people can use.
Two disciplines cross every layer:
- Trust — freshness, quality, monitoring, alerts and visible failure states.
- Identity & Compliance — appropriate access, permissions, sensitive-data handling, auditability and human approval.
The exact implementation depends on the agreed environment and scope. The purpose is constant: useful outputs built on reliable data.
Which description sounds closest?
| Your current situation | Smallest credible route |
|---|---|
| Several systems, manual or disputed reporting, multiple possible use cases, or uncertainty about what is ready. | Start with Assessment; it may route to Foundation, Operations, Custom & Advisory or no build yet. |
| Selected systems need connected, tested and owned business data for reports, dashboards or a first bounded capability. | Foundation. |
| Reliable data exists, but people need custom daily review, approval, exception or workflow-control surfaces. | Operations. |
| One recurring workflow should be operated on the Memory(One)-managed platform with a named owner and fallback. | Managed Automation. |
| The need is already bounded, review-led or advisory. | Custom & Advisory Work. |
| A client-owned delivered capability needs periodic maintenance, fixes or agreed improvements. | Post-Launch Support & Improvement. |
Describe the problem
Bring the outcome you need, the systems involved, the current manual work and the person who will own the result.