Industries

Procurement shapes the architecture more than the architects do.

Public sector technology outcomes are largely set before delivery starts, by how the work was specified and bought. MENTARA is direct about what that means.

Discuss a public sector priority Read the detail

More in Industries

The sector's actual constraint

In public sector delivery, the most consequential technical decisions are frequently made during procurement, by people writing a specification that must be fair, comparable between bidders and defensible under challenge. Those constraints reward precise up-front specification — which locks in a solution shape before anyone has learned what the problem is.

The resulting contract then makes changing that shape expensive, so programmes proceed toward a design that was fixed at the point of least knowledge. This is not a failure of the people involved; it is what the procurement framework selects for.

The failure mode

Multi-year commitments in a sector with short political horizons.

Large public programmes commonly run longer than the political and administrative cycles that sponsor them. A change of minister, department priority or funding settlement can leave a programme mid-build with a sponsor who did not commission it — and the safest available choice for that sponsor is often to reduce scope or stop.

The programmes that survive this are the ones structured so each phase delivers something usable on its own. That is well understood in principle and frequently abandoned in practice, because a big-bang design is easier to specify in a procurement document and easier to price comparably between bidders.

The second pattern is that accessibility and legacy integration are treated as later workstreams. Both are architectural. Accessibility retrofitted late is expensive and usually incomplete, and legacy integration discovered late is the single most common source of public programme overrun, because the legacy system's real behaviour differs from its documentation and nobody budgeted for finding that out.

Priorities

Where the work usually sits.

01Phasing that survives a sponsor changeStructuring delivery so each phase stands alone, which is what makes a multi-year programme politically survivable.

02Pre-procurement problem definitionEstablishing what the problem actually is before it is specified into a contract — the point of highest leverage in the whole lifecycle.

03Legacy integration realityEstablishing what legacy systems actually do, early, rather than discovering it during build.

04Accessibility as architectureDesigned in from the start, against the applicable standard, rather than remediated before launch.

05Data sovereignty and residencyRequirements established explicitly, including for cloud and any AI components, which are increasingly scrutinised.

06Assurance and independent reviewAn outside view of whether a programme's plan and readiness are realistic, most valuable when it is least welcome.

Questions

What buyers ask.

Are you on any government framework agreements?

MENTARA is not currently listed on any public sector framework or purchasing agreement in the markets we work in, which limits direct engagement for a large proportion of public sector buying.

Where it can work: below-threshold procurement, direct award routes where permitted, or as a named subcontractor to a supplier who does hold the framework position.

Can you meet public sector security clearance requirements?

Not currently — we hold no security certification and no cleared personnel. Where clearance or accreditation is required, that is worth establishing at first contact rather than at contract stage.

Where MENTARA fits best.

Scope

Where we can be useful: pre-procurement problem definition, independent assurance, and subcontracted specialist work under a prime who holds the necessary position.

Framework-based procurement, cleared work and large multi-year public programmes are not routes open to us today — this is the sector where our stage is the biggest practical constraint, so it is worth establishing early.

MENTARA was incorporated in July 2026 and has no published client work in this or any sector, so the quality of the thinking on this page — and in a first conversation — is what there is to judge us on.

Where this connects

Services

Workforce model

Permanent Recruitment