Skip to main content
    Proof
    Impress Blinds — cost per recorded Google Ads conversion down 62.63%SLS Solicitors — cost per recorded Google Ads conversion down 58.48%FixCare Property — cost per enquiry down 56.36%Rubbish Removal WA — cost per enquiry down 53.18%Floral Cakery — cost per enquiry down 49.82%ILLUMINATE Laser Emporium — cost per enquiry down 48.54%Aussie Plumbing — cost per enquiry down 41.96%Sydney Fence Painting — cost per enquiry down 33.68%Alliance Plumbing — cost per enquiry down 29.6%Gridless Build Solutions — cost per enquiry down 29.16%FacilityWorx — cost per enquiry down 23.62%Cornerstone Roofing — cost per enquiry down 20.47%Council finance — budgeting and workforce designCouncil planning — clearer approvals and reportingCultural audiences — media strategy and creative conceptsCommunity participation — surveys, maps and project pagesPublic-sector research — survey design and analysisPublic art — site studies and visual conceptsRegional identity — visitor guides and wayfinding conceptsCouncil systems — integration and migration planningA pressure washing business — service-led search campaignsA pressure washing business — a clear enquiry journeyA carpet cleaner — Google Ads built around cleaning servicesA roofing company — campaigns for repairs and restorationA CCTV installer — campaigns for security enquiriesA fence painter — search campaigns for specific surfacesA maintenance business — live in 8 weeks, 3 stacks gone41 numbered clauses, published in full5.0 across every Google review$120M+ in media under management250+ active engagements across five countries
    SoudCoh
    Government & Public Sector

    Map your applications before planning a replacement

    An application inventory is useful when it helps a team make a decision. A list of product names is only a starting point. The important questions are what each system supports, who is responsible for it, how it connects with other work and what needs attention next.

    • 23 September 2026
    • 3 min read
    Application inventories and modernisation planning: map the current work, then connect the information, then support the decision.
    An example approach for a distributed service organisation.

    The steps

    Map the service before replacing its applications

    InventoryRecord what people actually useValidateCheck the important connectionsSequenceChoose a workable order of change

    Inventory

    Combine existing registers with staff review. Identify the applications supporting the service and the people responsible for maintaining them.

    Ready for the next stepA shared application register

    Validate

    Confirm dependencies with the teams involved. Mark uncertain information and lifecycle gaps so they can be resolved before major decisions.

    Ready for the next stepA reviewed dependency map

    Sequence

    Use the service priorities and dependencies to arrange the next actions. Assign responsibility for keeping the inventory and roadmap current.

    Ready for the next stepA prioritised improvement roadmap

    Begin with the service, not the software list

    Choose an important service and ask the people running it which applications they use. Include specialist tools and the informal spreadsheets that carry essential work. Record what each system contributes, rather than relying only on a product category.

    For a distributed organisation, the same product may be used differently by several teams. Conversely, different products may support nearly identical tasks. Looking at the service makes those relationships easier to understand and gives the inventory a purpose beyond collecting technical names.

    Find the person who can verify the record

    A register needs owners as well as entries. Identify who understands the application’s use, who maintains it and who can confirm important information. These may be different people.

    Start with existing records, then ask the appropriate staff to review gaps and inconsistencies. Mark an unknown value clearly instead of guessing. A useful inventory can show where knowledge is missing. That is more valuable than an apparently complete spreadsheet filled with assumptions that no one is prepared to stand behind.

    Draw the connections that affect decisions

    Show which systems exchange information and which services depend on them. Keep the first diagram understandable to the people making the decision. Detailed supporting information can sit behind it where necessary.

    A proposed replacement may affect a report, another application or a manual step that is not obvious from the product list. Ask staff to test the map against a normal working day. The diagram should help someone explain the effect of a change before that change becomes an implementation problem.

    Prioritise using an agreed basis

    Possible concerns include ageing products, unclear ownership, duplicated functions and difficult handovers. Agree which factors matter to the organisation and how they will be assessed. Avoid treating every overlap as waste or every old application as an immediate replacement candidate.

    Combine the findings into a practical sequence. Some issues may need better documentation or a small process change. Others may justify a detailed replacement assessment. The roadmap should explain why an item appears early or late and what further evidence is needed before committing to it.

    Keep the inventory alive

    Decide when records will be reviewed and what changes trigger an update. A new application, a different owner or a major service change should have a clear path back into the inventory. Train the responsible team using real examples.

    The outputs can include application and infrastructure registers, dependency maps, a lifecycle review and a prioritised roadmap. Their value depends on continued use. Build the maintenance routine around the organisation’s normal decisions so the inventory remains a working reference rather than a document left behind after an initial review.

    Explore our Application inventories and modernisation planning, related services and Choose business systems around the decisions people make.

    What to do next

    Talk to SoudCoh about the service question, the people involved and the outputs your team needs.
    Talk to SoudCoh
    Read next

    Three more from the index.

    Filed under the same desk first. The full index is searchable and filters by reader.

    If you would rather we just did it.

    The briefing above is the reasoning. These are the pages that describe what it looks like as a piece of paid work, including what it costs and what gets reported.

    All 86 briefings

    Apply it to your account

    Reading it is the easy half. Thirty minutes with someone who runs accounts and you leave with a written list of what is leaking on yours — yours to keep either way.

    Get that list for your accountSee real client wins

    No pitch deck. No upsell. A real conversation and a written list of leaks.