Is your business actually ready for AI? This guide sets out the full AI readiness assessment: what it measures, the six dimensions of AI readiness, a 1-to-5 scoring matrix with a worked example, the red flags that mean “not yet”, a costed 90-day plan to close the gaps, and an honest comparison of DIY versus consultant-led assessments for UK SMEs.
A discovery workshop is where an automation budget becomes a decision, and most of them are wasted because nobody prepared the numbers. This guide is what to expect in full: the one-line definition that separates discovery from a brainstorm and from a vendor demo, the six to ten people who belong in the room and the ones who do not, the preparation that decides whether the day finishes early or ends in another meeting, a seven-stage agenda, an hour-by-hour account of how the day actually feels, the five artefacts you should refuse to leave without, realistic UK costs and who really pays, the five red flags that mark a sales meeting in disguise, remote versus in-person formats, and a thirty-day plan that turns the shortlist into a go or no-go decision you can defend.
Your first automation is a credibility project before it is a productivity project, and the process you pick decides which. This guide is the selection method in full: the five properties every strong candidate shares, the five conditions that disqualify one instantly, where to find candidates using data rather than workshops, a seven-criterion weighted scoring rubric with worked thresholds, how to size volume, handling time and error rate honestly, the feasibility and risk checks that catch expensive surprises, why technology comes second, a full worked example reducing twenty-three candidates to one, and a 90-day plan from standing start to a go or no-go decision you can defend.
Every finance director asks what automation gives back for what it costs, and almost nobody answers honestly. This guide is a working calculator: the formula written out properly, the seven inputs it needs and where each one really comes from, a full cost model including the maintenance and change-management lines vendors leave out, two worked examples with numbers you can argue with — one that justifies the investment and one that does not — plus payback, NPV and break-even volume, the five errors that inflate most business cases, and a 90-day plan to prove the number on one process before committing to a programme.
Three categories answer the same complaint about work moving between systems, and vendors in all three use the same slide. They are not interchangeable: one is a rules engine that orchestrates through APIs, one is a robot that drives a screen because there is no API, and one is a model that decides the sequence itself. This guide compares what each does, what each costs across build, licence, run and maintenance, how each fails, and how to combine all three in a single process — with a three-question test, a decision matrix, indicative UK cost ranges and a 90-day pilot plan.
A cloud migration business case fails when infrastructure people write for finance people and the translation never happens. This guide is that translation layer: how to build an on-premises baseline that survives challenge, how to cost the cloud side without wishful thinking, where three-year benefit genuinely comes from, how to model payback and net present value against a 3.5% discount rate, how to stress-test the answer so a 30% overrun still clears the hurdle, and how to compress the whole thing onto one page a board will approve.
The four routes out of a legacy system are well known — rehost, refactor, rebuild or replace — and the wrong one gets chosen more often than not, usually because the decision is made on temperament rather than evidence. This guide works through what modernisation actually means, the four options in detail with the conditions each one suits, a six-factor scoring model that turns preference into a defensible ranking, what each route costs in money and elapsed time, how to sequence delivery with the strangler fig pattern so the business keeps running, and the failure patterns that sink modernisation programmes.
Ask five agencies to quote from a thin brief and you get five proposals that cannot be compared — different assumptions, different scope, and prices ranging from £40,000 to £250,000. This guide explains how to write a software development RFP that produces comparable, honest bids: why the document filters who bothers to respond, when an RFP beats an RFI or a direct conversation, the sections that belong in it and in what order, how to write requirements a developer can actually estimate, why publishing a budget range and your evaluation weightings improves what arrives, how to score responses and read the assumptions page before the price, the mistakes that drive the best suppliers away, a section-by-section outline with a realistic eight to ten week timetable, and straight answers to the questions buyers ask most.
Ask three agencies how long the same build will take and you can hear six weeks, five months and a year — and all three can be telling the truth. This guide explains why, and what a realistic schedule looks like: the five phases every build passes through, honest duration ranges from a six-week internal tool to a two-year regulated system, the factors that genuinely lengthen a build, how estimates are produced and why they slip, the delays nobody writes into the plan, a week-by-week schedule for a typical six-month departmental system, what safely compresses a date and what only appears to, and the questions that reveal whether a delivery date has any evidence behind it.
Two development partners can quote the same brief five times apart, because “we need a system to manage our jobs” is a sentence, not a specification. This guide explains the discovery phase that closes that gap: the seven deliverables you should refuse to sign off without, UK cost bands from a £3,000 single-process engagement to £45,000 for a regulated build, the five-to-ten-per-cent rule for sanity-checking a quote, realistic two-to-twelve-week durations, who has to be in the room, a week-by-week timeline, the warning signs of discovery theatre, and the three legitimate outcomes — including the one where the honest answer is don’t build.
