Software consultancy services

Pick 72266000 when the deliverable is advice, not software. A contracting authority uses it to buy an architecture review, a build-versus-buy assessment, a platform or supplier evaluation, or specialist input before committing to a larger programme.

The boundary that trips authorities is 72262000: if the contract's main output is working software, that is development, even when advice is part of the job. Reserve 72266000 for engagements where the report, the recommendation, or the design is what gets accepted and paid for.

Two more neighbours matter. Systems consultancy (72246000) is the right pick when the advice spans hardware, networks and integration rather than the software layer alone, and Systems and technical consultancy services (72220000) is the broader parent. Where a single contract folds advice into a larger delivery, set the primary CPV code by the dominant deliverable, not by the whole bundle.

Winners here are advisory firms and boutique consultancies that sell senior expertise by the day, not delivery teams that sell built software. If you bid, your case rests on named consultants, their track record on comparable systems, and a clear method, far more than on tooling or headcount.

Several of the awards above are framework agreements, and that shape rewards getting onto the framework first, then winning call-offs against other named experts. Day-rate cards and named-expert references carry real weight alongside the written response.

Expect competition from two directions: development shops bidding under 72262000 that bolt on an advisory line, and general technical-consultancy firms arriving from 72220000. My read: an authority buying advice is paying for judgement it cannot staff in-house, so a sharp, specific architecture or strategy credential beats a generalist pitch. It is a quiet code, less crowded than the build codes next door.