Custom & Advisory Work
Let’s talk about what you are actually trying to build.
Not every problem needs a full Assessment, Foundation or Operations build. Custom & Advisory Work covers focused implementation, production-readiness reviews, decision support, team workshops and support for delivered project capability.
The format stays bounded: understand the problem, choose the smallest useful engagement, write the scope, fix the price and either start the work or say there is no fit.
Formats and starting prices
| Format | Public price | Best for |
|---|---|---|
| Custom Build | From 30.000 DKK | A narrow, known implementation with a clear handoff. |
| Architecture Review | From 10.000 DKK | Production-readiness, system, integration or operating-risk review. |
| Advisory Sessions | From 1.500 DKK/hour | Focused guidance without a build commitment. |
| Implementation Review | From 10.000 DKK/sprint | Review of workflows, payloads, prompts, data handling and observability. |
| Intro Session | From 5.000 DKK | A 1–2 hour alignment, education or triage conversation. |
| AI Data & Automation Workshop | From 10.000 DKK | Team alignment, opportunity mapping and an execution-oriented plan. |
| Post-Launch Support & Improvement | From 2.000 DKK/month | Monitoring and support for capability delivered through a project. |
All prices are excl. VAT and third-party costs. Final scope depends on access, integrations, risk, documentation, stakeholders, security and operating requirements.
Custom Build
Use Custom Build when the requirement is well-defined and reliability matters: a single integration, focused dashboard, one-off data migration, hardening an automation that already creates value, or a bounded AI-assisted workflow.
A focused build can include:
- one integration or dashboard built to the agreed production standard;
- a checked one-off data migration;
- retries, idempotency, alerting and observability for an existing workflow;
- documentation and handoff notes;
- engagement-specific source code and infrastructure in the client’s approved environment where scoped.
Simple point-to-point work is suitable only when the trigger and output are clear, existing connectors or straightforward APIs are available, risk is low, no custom data model is required and a human fallback exists. Custom connectors, ERP or accounting complexity, sensitive workflows, production AI judgement and broad reporting normally require a larger scope.
Architecture Review
A written teardown of an automation, AI workflow, internal tool or data pipeline: what may break in production, what is missing and what needs to change before release.
Depending on scope, the output can include a risk list, reliability fixes, access and ownership gaps, an architecture sketch, a concrete backlog and a production-readiness recommendation.
An Architecture Review can be the right route when an AI-assisted workflow is approaching production and the team needs a decision on whether to release, redesign, narrow or pause it. It reviews the system and operating model; it is not generic AI governance, cybersecurity certification or legal/compliance advice.
Advisory and Implementation Review
Advisory Sessions provide senior technical and business decision support on architecture, data contracts, failure modes and rollout plans. Implementation Review examines workflows, payloads, prompts, data handling and observability so an internal or supplier team can ship with explicit guardrails.
The work can cover retries, idempotency, alerts, audit trails, structured outputs, human approval, prompt or model evaluation, data boundaries and operating ownership where relevant.
For an AI workflow production-readiness review, buyer questions can include:
| Review area | Buyer question |
|---|---|
| Identity | Which user, service or agent is acting? |
| Permissions | What data and systems can it access? |
| Allowed actions | What may it do automatically, and what must it never do? |
| Human review | Which uncertain or consequential actions pause for a person? |
| Logs and evidence | Can material inputs, decisions, approvals and outcomes be traced at the agreed level? |
| Cost | Who sees usage and cost, and what limit or escalation applies? |
| Monitoring | How will stale inputs, failures, quality problems and missing outcomes become visible? |
| Fallback | How does work continue safely if the AI or workflow is unavailable or unreliable? |
| Revocation | How can access, credentials, tools or deployment be stopped when needed? |
The resulting backlog and recommendation remain bounded to the reviewed workflow and the written scope.
Intro Session and Workshop
An Intro Session is a 1–2 hour alignment, education or triage conversation around one business area or question. It does not include a full system map, detailed roadmap or SOW-ready implementation plan.
An AI Data & Automation Workshop brings the relevant people together to map business goals, systems, data sources, use cases, risks, owners and next steps. Half-day, full-day and workshop-plus-roadmap formats are available according to scope.
Post-Launch Support & Improvement
Post-Launch Support maintains capability delivered through a project. It may cover monitoring review, connector maintenance, dashboard fixes, issue handling, runbook updates and agreed small improvements.
What is included after launch?
The written scope defines any included stabilisation or hypercare. Periodic monitoring review, fixes and agreed improvements are separately scoped through Post-Launch Support & Improvement. Managed Automation uses its active Care or Managed Support arrangement, while Operations is a custom build rather than monthly support. No route includes unlimited changes or an unstated service-level commitment.
Every support agreement defines the covered systems, monitoring cadence, included fixes, excluded changes, response expectations, cost review, access review and escalation path. Large connectors, new dashboards, new automations, major redesigns, custom applications and special SLAs are separately scoped.
This is not Operations, which is a custom build of daily operating surfaces within the AI Data & Automation family. It is also not Managed Automation care, which operates one bounded workflow through the Memory(One)-managed platform.
Process
- 30-minute scoping call — clarify the problem, desired outcome, current systems, ownership, risk and likely range.
- Fit check and written scope — where there is fit, Memory(One) provides phases, deliverables, handoff plan and price within 48 hours; where there is not, Memory(One) says so.
- Fixed quote and start — the work begins in the agreed window after the written scope is accepted.
What to bring
- The problem in one sentence and the outcome that would make the work useful.
- The current systems, data sources, workflows and known failure points.
- The people who understand and will own the result.
- Existing diagrams, code, workflows, payloads, prompts or reports when the engagement is a review.
- Timeline, access, security, privacy, procurement and compliance constraints.
- The handoff or support model expected after the work.
Illustrative example
A team already has an automation moving submitted information into a work system, but duplicate records, silent failures and unclear ownership make it unsafe to expand. A Custom Build could harden the workflow with idempotency, alerts, explicit failure handling and documentation. If the team only needs an independent diagnosis and backlog, an Architecture Review may be the smaller route.
Fit boundary
Custom & Advisory is appropriate when the requirement is bounded or the team needs a decision, review or workshop. It is not a substitute for Foundation when several systems need a trusted shared data layer, or for Operations when the goal is a substantial daily operating surface.
Choose Managed Automation when one bounded workflow should remain hosted, monitored and maintained by Memory(One) through active care. Choose Custom Build when independent deployment, project-specific ownership, bespoke infrastructure or broader implementation is required.
Commercial questions
We'll match a comparable written offer.
Got a lower comparable written offer? Send it to us. Where the scope, systems, delivery standard, ownership, monitoring and support assumptions are comparable, we'll match the price and scope. If the offers are not comparable, we'll show you the difference before you decide.
Do you offer reduced rates for non-profit work?
Reduced rates may be available for qualifying NGOs, charities and non-profit organisations. We review eligibility, fit, scope and capacity case by case.
If you have the ideas but lack a clear direction, start with an assessment.
When several systems are involved or the smallest credible build is not yet clear, start with an Assessment.
Discuss the right format
Bring the problem, current systems, desired outcome, constraints and internal owner. Memory(One) will recommend a build, review, session, workshop, support route or no-build next step.