Canberra Business Websites: The Procurement Standard

A contract officer has three shortlisted suppliers, a panel meeting on Thursday, and roughly ten minutes per firm to form a view. They are not going to read your website. They are going to check it. Entity name against the ABN. The names of the people who would actually do the work, and whether those names appear anywhere else. Whether the case studies describe real engagements or are decorative. Whether the site would embarrass anyone if it were pasted into a briefing pack.

That is the audience most Canberra businesses are genuinely writing for, and almost none of them design for it. In Sydney or Melbourne, a professional-services website's first job is demand generation — get found, get read, get an enquiry. In Canberra, for the consultancies, contractors and specialist firms selling into departments, the site's first job is verification. It is a due-diligence artefact that also happens to sell.

That inversion changes what belongs on the page. The full-screen hero video, the wall of five-star reviews, the scroll animation — all neutral at best in front of someone whose job is to reduce risk before spending public money. What actually matters is unglamorous, and most of it is missing.

Canberra's buyers verify, they don't browse

Public administration is the ACT's largest employer, and the second-order effect is bigger than the first. It isn't only firms holding a Commonwealth contract that sell into that world. It's the accountants, the recruiters, the fit-out builders working in Barton and Deakin, the training providers, the IT resellers. A large share of Canberra's private sector sells to people who buy for a living, and who buy under rules.

The path an enquiry takes is different because of it. Discovery frequently happens somewhere other than your website — on AusTender, through a panel or standing offer arrangement, or because a colleague said your name in a corridor. By the time someone loads your homepage, they usually already have it. They aren't asking what you do. They're asking whether this is a real, competent, low-risk organisation, and whether they could defend recommending it.

That's a different question, and it needs different pages. A homepage built for a stranger explains the service. A homepage built for a verifier proves the organisation. The best Canberra sites do both, in that order, and resist the temptation to lead with atmosphere. We cover the local specifics on our Canberra web design page, but the short version is that restraint reads as competence here in a way it doesn't everywhere.

The ten-minute skim, in the order it happens

Sit with anyone who does supplier due diligence for a living and you'll watch roughly this sequence, at speed.

None of that requires a large budget. It requires deciding the site's job is to be checked rather than admired.

Accessibility stops being optional when government is in the chain

This is the biggest differentiator available to a Canberra firm, and the one most often waved through as a compliance chore.

Australian Government digital services are held to WCAG Level AA. The Digital Transformation Agency publishes the Digital Service Standard that Commonwealth services are built against, and its accessibility bar has ratcheted upward over the years rather than down. The consequence for suppliers is flow-down: if you produce anything a department will publish, host or hand to the public — a report, a portal, a training module, a form — the accessibility obligation lands in your contract, and the department is the one asked about it if it fails.

Which gives the buyer an obvious shortcut. Before trusting you with an accessible deliverable, they check whether your own website is accessible. It costs them ninety seconds. Tab through the navigation without a mouse. Look at the contrast on that light grey body text. Check whether the headings are structured or just big bold paragraphs. If your own site fails, your claim that you'll deliver to standard is now an assertion contradicted by evidence they gathered themselves.

The rules apply to you regardless of who your clients are. The Disability Discrimination Act covers the provision of goods and services online, and it has nothing to do with whether government is your customer — we've written the plain-English version of what the DDA means for an Australian business website, and a practical WCAG AA checklist a non-developer can work through in an afternoon.

Two own goals worth naming. The capability statement shipped as an untagged, image-based PDF — an inaccessible document about how carefully you handle accessible documents. And the accessibility overlay widget, the floating icon promising conformance in one line of JavaScript. Buyers here have seen them and read them as a shortcut. Do the work instead.

The page almost no Canberra site has

Government and defence buyers expect a capability statement. Most firms have one — as a PDF, emailed on request, currently at version four with the logo from the last rebrand still on page one.

Put it on the web as a page. A real one, stable URL, linked from the main navigation.

What belongs on it: legal entity and ABN, business size, service categories described the way a buyer categorises them rather than the way you brand them, panels and standing offers you can be engaged through, clearances held by staff and any programme memberships you genuinely hold, current insurances, certifications if they're real, and referees you have written permission to name. Dated, so nobody has to guess whether it's current.

A page beats a PDF on every axis that matters. It's findable by search, so a buyer who half-remembers your name can get to it. It's linkable, so the officer can paste a URL into an evaluation note rather than attach a 4MB file. It's accessible if built properly, and it can be updated the day a certification changes. Keep the PDF as well — some processes need a document to attach — but generate it from the page so the two can't drift apart, and tag it properly.

Past performance when you can't name the client

The honest constraint in Canberra is that a lot of your best work can't be described. Confidentiality clauses, security classifications, agency communications policies that prohibit anything reading as endorsement of a supplier.

What works is describing the shape without the name. The type of entity — a federal regulator, a Commonwealth entity of around two thousand staff, an ACT directorate. The problem in one sentence. What you actually did. The outcome stated in terms you could defend if the client were sitting in the room, which is worth remembering given they sometimes are. Then: named referees available on request. A buyer who reads three engagements written that way knows more about you than one who reads twelve logos.

What fails deserves to be said bluntly. Department crests used as a trust wall without permission — that's a phone call you don't want, and it signals you treat client relationships as marketing inventory. Undated "trusted by government" claims with nothing behind them. And invented numbers, which are a particular danger here, because the person reading may well have worked at the agency you're describing and will know immediately that no such programme delivered a 40% saving.

We hold ourselves to the same line. Pryce Digital is a young studio, and we'd rather show reasoning than pad a client list. In front of a verifier, a short checkable claim outperforms an impressive unverifiable one every time.

Security posture is part of the first impression

The checks are cheap, and someone technical will run them the moment your firm gets close to a system.

The basics: HTTPS everywhere with a valid certificate and no mixed content, no forgotten subdomain running an abandoned install from a 2019 campaign, and working email authentication. That last one catches people out. SPF, DKIM and DMARC are what stop your domain being spoofed, and a department's mail gateway is exactly the sort of place unauthenticated email lands in quarantine. If your tender clarification goes to junk, a security failure has become a commercial one.

Then the claims. If you hold ISO 27001, say so and name the certification body and the scope. If you're working toward the Essential Eight maturity levels, describe where you are honestly rather than implying a level you haven't reached. Fabricated or fuzzy security claims are worse than silence, because verifying them is trivial and the reader knows how.

One more question worth answering on the page: when someone submits your enquiry form, which system receives it, where is it hosted, and who can read it. Most business websites can't say. A supplier that can, unprompted, has distinguished itself for the cost of a paragraph.

What this asks of the build

Design for the conditions the page will actually be read in. A locked-down department laptop, a browser two versions behind, a throttled network, and a reader skimming with intent rather than scrolling for pleasure. That argues for a text-first layout with real information density, fast loads without heavy media, semantic structure a screen reader can navigate, and pages that print cleanly, because someone will print them for the panel.

It also argues for building accessibility in at the design stage rather than retrofitting. Contrast decided when the palette is chosen. Focus states designed rather than disabled. Retrofitting a template build to Level AA regularly costs more than doing it correctly the first time.

Our custom builds start at $8,000 AUD. For a Canberra firm the question isn't whether that's more than a template subscription — it plainly is — but what a single lost shortlisting costs by comparison. We won't promise a website wins you contracts; nobody honest can. What a properly built one does is stop the site being the reason you're taken off the list. Before engaging anyone, local or otherwise, run through the questions to ask a web agency before signing, particularly the ones about who owns the code and what the accessibility commitment says in writing.

Where to start this week

Do the skim yourself, with a stopwatch, pretending you've never seen the business. Ten minutes. Write down what you couldn't find.

Then, in rough order of payoff: tab through your own site with the mouse unplugged and watch where the focus disappears. Open your capability statement PDF and try to select the text — if you can't, it's an image, and it's failing. Check the domain is registered to your own entity rather than a former developer's account. Test whether email from your domain lands in a Gmail inbox or its spam folder. Write the capability page. Get written permission from two referees before you need them.

A free audit of your site covers the mechanical half of that list — performance on a slow connection, the technical SEO surface, and the accessibility and security signals a buyer's first check would surface — in a couple of minutes. It won't write your capability statement.

For the judgement half, book 20 minutes or call us on 0421 933 907. Bring the last tender you didn't win, and we'll go through what a verifier would have found on your site while they were forming a view.