Skip to main content

[01] / Audit

A decision-first answer to:
should we keep, improve, or replace this?

Modernization decisions stall when the workflow, operating risks, and economics are not clear. Discovery creates a decision artifact before a replacement scope is proposed. If the right answer is to retain or improve the current system, the recommendation should say so.

scopeAgreed in discovery
timingAgreed with the decision owner
deliverableDecision record + readout
termsAgreed before a build

Discovery approach by solution: NetSuite & ERP Scope, timing, and commercial terms agreed in discovery · WordPress Scope, timing, and commercial terms agreed in discovery · Salesforce & CRM Scope, timing, and commercial terms agreed in discovery · BI & Dashboards Scope, timing, and commercial terms agreed in discovery

[02]
§ Deliverable

What you can inspect before a build decision.

Discovery produces a documented decision artifact rather than a generic sales pitch. The final format follows the agreed scope and evidence available.

  1. [01]

    SaaS spend map

    The subscriptions, renewal context, owners, costs, and assumptions relevant to the decision, documented at the level supported by the available information.

  2. [02]

    Workflow inventory

    The workflows, systems, dependencies, owners, and control requirements that affect a keep, improve, or replace decision.

  3. [03]

    Replicate-vs-stay verdict

    A recommendation for each scoped workflow: retain it, improve it in place, consider phased replacement, or defer action. A replacement is not assumed to be the right answer.

  4. [04]

    Scoped replacement plan

    For any proposed work: the intended scope, assumptions, delivery phases, migration approach, acceptance checks, ownership model, and commercial terms requiring agreement.

  5. [05]

    Risk + continuity review

    Data, continuity, integration, access, operating, and migration risks, with the mitigations or unresolved decisions that need to be addressed before production change.

[03]
§ Process

A practical path to a decision.

The timing, access, people, and deliverable are set against the workflow risk and evidence available.

  1. Start

    Align

    Agree the decision to be made, the relevant people, the available evidence, and the access boundaries for discovery.

  2. Discovery

    Map the operating work

    Review the scoped workflows, systems, costs, dependencies, controls, and ownership requirements with the relevant stakeholders.

  3. Model

    Assess options

    Document assumptions, retained systems, operating costs, risks, and the alternatives that merit consideration.

  4. Decision

    Define the proposed path

    Set out the recommendation, acceptance checks, migration approach, operating model, and commercial terms that require agreement.

  5. Readout

    Review the artifact

    Walk through the decision record, open questions, owners, and next steps. The format and timing are agreed for the scoped engagement.

[04]
§ Fit check

When the audit is the right move.

→ probably yes

  • A critical workflow no longer fits the business or is costly to change
  • A renewal, operating, control, or ownership decision needs better evidence
  • The team needs to know which systems should stay before replacing anything
  • The business has an internal owner who can assess the future operating model

× probably no

  • There is no decision owner or willingness to review the operating model
  • The team only needs an immediate feature with no discovery or change planning
  • A specialist platform, regulatory control, or vendor ecosystem is the better fit

Preparing the consultation form…

Optional context: offer, company, spend, or renewal timing
We review every request before replying.

[→] Start with a consultation request

Start with the workflow that needs a clearer decision.

Tell us what is expensive, hard to change, or risky to operate. A request starts a conversation; it does not create an appointment automatically.

Get in touch →