Author: Robert Duggan
Most established Irish businesses already spend money on digital. The website was rebuilt a few years ago, an agency runs the ads, someone else handles SEO, and the CRM was set up by a marketing manager who has since left. What is usually missing is a digital transformation roadmap deciding what happens in what order, who owns each piece and how anyone will know it is working.
Our July article made the case for treating digital transformation as a board-level decision. This is the practical follow-on, covering maturity, sequencing, the first 90 days and governance.
A digital transformation roadmap is a sequenced plan that sets out which digital work a business will do, in what order, who owns each piece and how progress will be measured. For an established business, it covers the commercial side of digital: brand and messaging, the website, search and AI visibility, paid media, data and the way suppliers are organised.
The roadmap sits between strategy and delivery. Strategy says where the business wants digital to take it, for example more qualified enquiries from a new sector or less reliance on referrals. The roadmap turns that into decisions about order and ownership. A list of projects with a budget beside each one does not do that job, because it says nothing about what has to be true before each project can succeed.
That gap is widest in businesses that have grown faster than their digital setup. When several suppliers each hold part of the picture, each one produces a plan for its own channel. Nobody produces the plan that decides between them.
Digital maturity describes how well a business’s digital activity is connected, measured and owned, which is a different thing from how much activity there is. The quickest way to assess it is to score six areas on a simple scale, from fragmented to connected, before any budget is committed to a single project.
The assessment is the practical version of the audit and diagnosis that starts any transformation. It tells you where the roadmap needs to begin, before anyone argues about which project deserves the budget.
| Area | Fragmented | Connected |
|---|---|---|
| Brand and messaging | Positioning varies by channel and by salesperson. The website still describes services the business has moved away from. | One agreed position, used consistently across the website, sales material and campaigns. |
| Website | Slow, hard to update without a developer and built as a brochure. Enquiries arrive with no source data. | Built around buyer questions and conversion paths, editable in-house, with every enquiry tracked by source. |
| Search and AI visibility | Ranks for the brand name and little else. No view of how the business appears in AI answers. | Visible for service and problem searches, cited in AI answers, with content feeding service pages. |
| Paid media | Judged on clicks and cost per lead. Run separately from the website. | Judged on qualified enquiries and pipeline, with landing pages built for each audience. |
| Data and reporting | Each supplier reports its own numbers. There is no figure the board trusts. | One reporting view linking activity to enquiries, pipeline and revenue. |
| Operating model | Several suppliers, no single owner, decisions made channel by channel. | One accountable owner, one shared roadmap and a regular review. |
Score each area from 1 to 3, and be strict about it. Most established businesses score unevenly: a strong brand next to a website nobody on the team can edit, or a well-run ads account sending traffic to pages that have not changed in two years. The lowest score is the useful one. If data and reporting scores 1, it goes to the top of the roadmap, because every later decision depends on being able to measure it.
Dependencies in a digital transformation roadmap are mapped by listing every piece of work the business is planning, then asking what has to be true before each one can succeed. The answers show which projects must wait, which can run in parallel and which single item is holding up the most work.
A worked example makes the method clearer. These are typical lines from an established business’s plans, with the hard dependency that decides when each one can start:
| Planned work | Hard dependency | Earliest sensible start |
|---|---|---|
| Increase the paid media budget | Enquiries tracked by source, and landing pages that convert | Once tracking is fixed and landing pages are improved |
| New service pages | Agreed positioning and priority services | Once positioning is signed off |
| CRM change | Lead stages agreed between sales and marketing | Once sales and marketing agree the stages |
| Website rebuild | Agreed positioning, page structure and a redirect plan for every existing URL | After positioning; the redirect plan must be ready before launch |
| Search and AI visibility content | A stable site structure, so URLs do not change after publishing | Alongside a rebuild once URLs are fixed, or now if no rebuild is planned |
The general order behind this, from audit and diagnosis through to continuous optimisation, is set out in our guide to digital transformation in Ireland. The mapping exercise is what turns that order into dates, owners and budget lines for one specific business, and it sits at the centre of our digital growth strategy work.
The most common roadmap mistake is planning by channel or by supplier, so the document ends up as several separate plans stapled together. Close behind are dependencies nobody wrote down, too much change packed into one quarter and deadlines with no measure of what each line is meant to achieve.
A small industrial equipment reseller selling directly to specialist buyers through its own e-commerce site came to us with a platform rebuilt months earlier. The rebuild looked sharper than what it replaced, but there was no way to measure whether it was working. No analytics platform had ever been set up: all reporting lived inside the e-commerce platform’s dashboard, and the business didn’t know anything else existed. Ecommerce tracking specifically had never been implemented anywhere, so there was no way to attribute a sale to organic search, paid media or any other channel. The ROI on marketing spend was, in effect, unmeasured. Basic SEO fundamentals such as page titles and meta descriptions also couldn’t be done, because platform access had never been extended beyond the client’s own team.
When we ran the initial audit, a second issue surfaced. The business was still publishing blog content on an older platform alongside its new e-commerce blog, so search authority was split across two domains instead of sitting in one place. None of this came from carelessness. The rebuild was scoped and delivered without anyone responsible for organic search involved, and the team never revisited the decision to keep two blogs running once the new site went live.
The first phase of the engagement focused on foundations rather than jumping straight into optimisation: standing up analytics from scratch, building out ecommerce tracking so revenue could finally be tied to a source, and securing the platform access needed to make on-page changes. That groundwork took the better part of four months to land properly, which meant a full two quarters of prior marketing spend had gone out with no reliable way to judge what it had returned. Once tracking was confirmed working, we scoped and ran a full migration of the blog section, moving close to thirty posts across to the new platform with dates, authors and images preserved.
The results validated the sequencing. In the first month after foundational tracking went live, the site recorded just over 1k clicks and around 70k impressions in Search Console. By month five, that had grown to nearly 5k clicks and close to 265k impressions, a fourfold increase on both measures. Organic keyword count and modelled visibility told the same story over the same period, roughly doubling, with the site now holding top two positions for its core commercial search terms. None of that improvement would have been visible, or arguably achievable in the same way, if the client had gone straight into content and campaign work without first fixing what could be measured.
The migration itself was not the end of the story. A follow up crawl, run to confirm the move had actually worked, found a number of old URLs still live and indexable months after the site was meant to have moved across, quietly competing with the new pages for the same rankings. A migration is not finished when the content has moved, it is finished when the old version has been checked and confirmed gone.
The dependency that was missed at the outset: a website rebuild without measurement or SEO access built in cannot be judged as working or not, however good it looks. In the dependency table, tracking and access come before optimisation, not alongside it, because you cannot sequence anything else sensibly against numbers you do not trust.
The first 90 days of a digital transformation roadmap should produce a measurement baseline, a set of agreed priorities and at least one visible improvement. Large builds belong in later phases. The early work makes sure those builds are aimed at the right problem and can be measured once they land.
| Area | First 90 days | Later phases |
|---|---|---|
| Measurement | Fix tracking, connect enquiries to the CRM and agree what counts as a qualified lead. | Attribution across channels and a reporting view the leadership team uses every month. |
| Brand and messaging | Confirm positioning, priority audiences and priority services. | Roll the messaging out across the site, sales material and campaigns. |
| Website | Fix pages that already get traffic but lose enquiries. Audit structure and platform. | Rebuild or restructure where the audit shows it is needed. |
| Search and content | Title and meta fixes on pages already ranking. Technical clean-up. | A content programme built around buyer questions, with AI visibility tracked. |
| Paid media | Tighten targeting and landing pages on existing campaigns. | Scale spend on what the tracking shows is producing qualified enquiries. |
| Operating model | Name the owner, set the review cadence and clarify each supplier’s remit. | Consolidate suppliers where overlap is costing time or money. |
The first-90-days column deserves more attention than it usually gets. Pages that rank on page one but win few clicks, or campaigns sending paid traffic to a generic homepage, can often be improved within weeks. Early results like these give the leadership team evidence the roadmap is working before the larger investment decisions arrive.
A digital transformation roadmap should be owned by one named person on the leadership team with authority across marketing, sales and operations. Suppliers and internal specialists deliver parts of it. The owner decides the order, settles conflicts between workstreams and reports progress to the board.
In practice, the governance around that person needs four things:
The quarterly point matters because a roadmap is a set of informed guesses. Some early fixes will outperform, some bigger bets will disappoint, and the plan should change when the evidence does. A roadmap that has not changed in a year has usually stopped being read.
Where the internal team does not have the capacity to run this day to day, an accountable full-service digital partner can hold the roadmap and coordinate delivery while the owner keeps the decisions.
Progress on a digital transformation strategy is tracked at two levels: whether each roadmap line was delivered, and whether it produced the result it was meant to. A roadmap that reports only delivery can finish on time and change nothing, so every line needs both tests written down before work starts.
| Roadmap line | Delivered when | Working when |
|---|---|---|
| Tracking and CRM connection | Every enquiry arrives with a source and a stage | The leadership team uses the report in its monthly review |
| Positioning | Agreed and signed off by the leadership team | Sales material and the website describe the business the same way |
| Priority page fixes | Changes are live on the pages that already get traffic | The enquiry rate on those pages rises against the baseline |
| Website rebuild | Launched with redirects in place for every old URL | Qualified enquiries hold or rise through the launch period |
| Search and AI visibility | Content published on the agreed topics | The business appears for its priority service and problem searches, including in AI answers |
Each phase also needs a phase gate: a short check before the next phase’s budget is released. Did the phase deliver what it promised, did its measures move, and has anything learned changed the order of what comes next? If the measures did not move, the next phase waits until the reason is understood.
For the search and AI line, Google’s guidance on AI features in Search confirms that clicks and impressions from AI Overviews and AI Mode are included in Search Console’s performance reporting, so the same reports can show whether visibility is building.
Set the measures before the first phase starts. A baseline taken halfway through a rebuild measures the disruption of the rebuild, and tells you very little about the business.
A digital transformation roadmap should include a digital maturity baseline, the dependencies between planned projects, a prioritised sequence of work, a named owner for each workstream, milestones and the measures used to judge progress. Madcraft builds roadmaps that cover brand, website, search, paid media and data in one plan.
Digital maturity is measured by scoring areas such as brand, website, search visibility, paid media, data and supplier ownership on how connected, measured and accountable each one is. Madcraft can run this assessment as the first step of a digital growth strategy.
The time needed to build a digital transformation roadmap depends on how many channels, suppliers and systems are in scope, and most of it goes into the maturity assessment and agreeing priorities with the leadership team. Madcraft agrees a timeline for the roadmap after an initial review of the channels and suppliers involved.
A commercial digital transformation roadmap should list IT systems such as ERP or CRM wherever customer-facing work depends on them, while the systems work itself usually sits with an IT partner. Madcraft maps those dependencies in the roadmap and works alongside whoever owns the systems.
A digital transformation roadmap should be reviewed monthly for progress and re-prioritised every quarter against results, so budget moves towards the work that is paying back. Madcraft reports against the same roadmap and measures at every review.
