A twelve-month digital roadmap for small organisations, quarter by quarter

A twelve-month digital roadmap for a small or mid-sized organisation works best in four stages: foundation, visibility, conversion, then automation and AI. The order matters more than the list, because each quarter produces the data, the traffic or the revenue that pays for the next one. Skipping ahead usually means paying twice.

Sequence the year so each quarter funds the next

Twelve-month plans tend to fail on order of operations rather than on ambition. An organisation buys ads before it can tell which enquiries close, or writes a content library on a site that search engines struggle to crawl. The work is not wrong; it is simply early, and early work gets redone.

A useful test before starting anything: what does this depend on, and does that thing exist yet? Paid search depends on conversion tracking. Conversion rate work depends on enough traffic to read a result. Lifecycle email depends on a list and a reason to write. Automation depends on a process someone has already written down. Draw those dependencies once and the calendar mostly writes itself.

The funding logic follows the same chain. Quarter one gives you measurement, so quarter two can be judged rather than argued about. Quarter two brings people to the site, so quarter three has enough volume to improve. Quarter three lifts the return on the same traffic, which is what pays for the build work in quarter four. If a quarter cannot show a result the next quarter depends on, it was the wrong quarter.

Quarter one: foundation you will not have to redo

Start with the three assets everything else sits on: the website, the analytics, and the customer record.

On the site, the priorities are speed on a mid-range phone, a structure that reflects how buyers actually search, and accessibility. Meeting WCAG 2.2 AA is not a compliance chore; it forces clear headings, real form labels, sensible contrast and keyboard order, all of which help every visitor and every crawler. Get the technical basics right at the same time: clean URLs, one canonical version of each page, an accurate sitemap, and page titles that describe the page rather than the company. This is the quarter where a rebuild is cheapest, because nothing has been optimised on top of it yet. Our notes on web development go into how that groundwork is scoped.

On analytics, define the handful of events that represent real business outcomes: enquiry submitted, quote requested, call started, purchase completed. Name them once, document the definitions, and resist the urge to track everything. Then connect them to a CRM, even a simple one. The point is not the software; it is that every enquiry lands somewhere with a source attached and a status that a human updates.

By the end of the quarter you should be able to answer one question without a spreadsheet exercise: where did last month's enquiries come from, and what happened to them?

Quarter two: visibility, including the AI answer layer

With measurement in place, spend the second quarter being findable. For most small and mid-sized organisations that means three things at once.

Organic search comes first, because it compounds. Build a small set of pages that answer the questions buyers actually ask, each one thorough enough to stand alone, each one linked to from somewhere sensible. Depth beats volume here: a handful of pages that genuinely answer something will do more for you than a large library of thin ones. That is the ground covered by SEO and content.

Generative engine optimisation is the same discipline pointed at a newer surface. Assistants and AI answer panels tend to quote pages that state things plainly, define terms, use clear headings and carry structured data that matches what is on the page. Writing for citation means putting the direct answer near the top, keeping claims specific, and making sure your organisation, services and contact details are consistent everywhere they appear. Most of the work overlaps with ordinary SEO and content practice, which is convenient: you are not running two programmes.

Local visibility is the third leg. Claim and complete every profile, keep name, address and phone identical across them, and gather reviews as a habit rather than a campaign. If you serve more than one region, give each one a page with something real on it rather than a template with the city name swapped in.

Quarter three: conversion and lifecycle

By the third quarter you have traffic and you can read it, which is when conversion work starts to pay. Begin with the friction you can see without a test: forms asking for information nobody needs, pages that bury the next step, quotes that take days to go out, mobile layouts where the button sits below three paragraphs of preamble.

Then test the few things that matter. A small organisation rarely has the volume for a long testing queue, so pick changes big enough to show a difference: the offer, the headline, the length of the form, the presence or absence of a plain explanation of how you work. Run one test at a time, decide in advance what counts as a result, and write the outcome down whichever way it goes.

The least expensive growth available to most organisations is the enquiry they already received and never followed up.

Lifecycle email is the other half of this quarter, and it is the part that keeps working after the quarter ends. A welcome sequence, a follow-up for people who asked for a quote and went quiet, a short re-engagement note, and a monthly message with something worth reading. Four sequences, written once, working every day. Pair that with honest reporting so you can see which source produces enquiries that actually close, not just enquiries. That is the work covered in analytics and CRO.

Quarter four: automation and AI, on solid ground

Automation is last for a reason. It makes an existing process faster, so it needs a process that already works and data that is already clean. Applied to a broken workflow, it produces the same mistakes at higher speed.

Start with the internal jobs your team repeats every week: routing enquiries, drafting quote documents, chasing missing information, reconciling records between two systems, turning meeting notes into follow-ups. Each of these is small, measurable in hours saved, and low risk if it fails.

Customer-facing AI comes after that. A retrieval assistant answering from your own documentation, a triage step that classifies enquiries before a human sees them, a search that understands phrasing rather than keywords. The rule for anything customer-facing is simple: a person reviews output before it goes out, and the system says clearly when it does not know. Keep the scope narrow, keep a human in the loop on anything that commits the organisation to something, and check what happens to your data before you send it anywhere. If you are weighing options, our view on AI development is that the smallest useful build usually beats the ambitious one.

In-house or hired out, and how to dodge the shiny objects

The dividing line is not seniority or budget. Keep what depends on knowing your customers and your business; hire out what needs specialist tooling, happens once, or would take a year to learn properly.

The shiny-object problem is real and it has a cheap fix. Keep a parking list. When a new platform, channel or tool appears mid-quarter, it goes on the list with one line explaining which roadmap outcome it would improve. At the quarter boundary you review the list and either promote an item or delete it. Nothing enters the current quarter's work. This does not make you slow; it makes the cost of switching visible, which is usually enough to settle the argument.

Where OlDevs fits

OlDevs has been building for the web from Vancouver, British Columbia since 2014. One accountable team can cover the whole roadmap, from the site build and accessibility work through search, analytics and lifecycle to the automation and AI that comes last. We show a working demo every week, so you see the quarter progressing rather than hearing about it, and you own all the code, designs, accounts and IP outright. We work in English and French. Clients outside Vancouver are served remotely, with video calls in your time zone and on-site visits when the work calls for it, and we reply to every enquiry within one business day.

If you would like a twelve-month plan shaped around your organisation rather than a generic template, request a quote and tell us where you are starting from. We will tell you honestly which quarter you are actually in.