Websites for public agencies that do not track your residents

Accessibility

We build to WCAG 2.1 Level AA and test every release against it — automated scans across the whole site, then a manual pass with a keyboard only and a manual pass with a screen reader. Those two catch what scans cannot: focus order, whether a control announces what it does, whether a form error is reachable by someone who never touches a mouse.

Residents are not the product

Most website analytics work by following a person. Ours does not, and for a public agency that difference stops being a preference and starts being a procurement answer.

Hosting and reliability

You are buying an outcome, not a server. There is no control panel to learn, no PHP version to choose and no update to schedule — those are ours, and they are the reason the annual fee exists.

• U.S. infrastructure. Hosted and administered in the United States, with no offshore handling.
• Updates are ours. WordPress core, plugins and security patches, applied by us.
• SSL is automatic. Issued and renewed for your domain without anyone remembering to.
• Monitored every five minutes, with a public 90-day history per component on our status page.
• Unlimited traffic. You pay for the site, never for visitors, so a good month is never a bill.

The full detail an RFP usually asks for — hosting location, encryption, access control, incident response and subprocessors — is set out on our security page and in the procurement packet.

Analytics your board will understand

The difference between a traffic report and a useful one is whether anybody knows what to do after reading it. Queantic writes the numbers as ranked actions, in order of likely impact, naming the page.

• Real against automated traffic, separated, so last month’s figure means something.
• Page-level detail — which property, which event, which programme, which form.
• Sources, including whether the directories and campaigns you pay for send anybody.
• Ranked recommendations, written as the next three changes rather than a wall of charts.
• Exportable, so a figure can go straight into a board packet.

One thing in progress and worth knowing before you scope it: the single board-ready monthly export — one document, plain language, no covering note — is being built. The underlying data is collected and retained from the day the site goes live, so nothing is lost in the meantime. Ask for the current version when you ask for the quote and judge it rather than this paragraph.

These pages run Queantic’s own analytics, which makes this section a live demo rather than a description. Ask us what this page did last month and we will read you the answer.

Procurement-ready

• Itemised pricing. A one-time build figure broken into line items, and a fixed annual hosting and support figure. Nothing per-visitor.
• A vendor packet you can attach to a requisition — security overview, data ownership and exit statement, sample pricing sheet, sample agreement, uptime summary and business registration.
• You own everything. Site, content and data, with a written handover plan and a five-business-day export commitment.
• We will answer your process, whether that is an RFP, an ITB or three written quotes.

See the procurement packet

Proof

We have not yet done a project for an economic development office or a tourism board, and we are not going to imply otherwise — this is a new line of business and the first agency to hire us will be the first. What we can show you is a public institution we already build for, a platform build, and the volume behind the rest.

If references from a comparable agency are a scored requirement in your solicitation, say so when you write to us. We would rather tell you we cannot meet that criterion yet than waste your evaluation committee's afternoon.

Questions public buyers ask

Can we use our own .gov or existing domain?

Yes, on every plan. Point it at us and the SSL certificate is issued and renewed automatically — a .gov is no different to any other domain in that respect. You keep the registration; we never take ownership of your domain.

Who owns the site, the content and the data if we leave?

You do, throughout. On request we produce a complete export — a standard WordPress content export, the uploads directory and a database dump — within five business days, together with a written handover plan naming what you receive and in what format. One thing stated plainly because it would otherwise be a surprise: the role an owner is handed deliberately cannot run the export itself, so it is a request to us rather than a button. That is a safety decision, not a lock-in one, and the commitment above is what makes it safe.

How many staff can edit, and can we require approval before something publishes?

As many as you need, with no per-seat charge. Approval uses WordPress’s own review step — a Contributor submits and an Editor publishes — which means it is a standard behaviour your staff can be trained on rather than a custom workflow that only we understand. Restricting an editor to one department’s pages goes beyond the built-in roles and is quoted as work.

What happens during an outage, and where can we see uptime?

Every service is checked every five minutes, and the result — including a 90-day history for each component — is public on our status page, reachable even when the application itself is down. There is no login and no invitation needed to read it, which is the point: the people who most need a status page are the ones who cannot sign in.

Do we need a cookie banner?

Not for anything Queantic does. Our analytics set no cookies, write nothing to the browser and build no cross-site identifier, so there is nothing for a resident to consent to. A banner only returns if you add a third-party embed that needs one — a video player, a social feed, an external map — and we will tell you which of those do before you commit to them.

How do you handle accessibility on content our staff add later?

Honestly: we can guarantee the build, not every future paragraph. What we do is make the right thing the easy thing — alt text prompted at upload, a heading structure that is already correct, colour and focus styles your staff cannot accidentally break from the editor — and give you written guidance for documents and images, which is where most problems actually originate. We will also re-test on request after a large content change.

Can you respond to our RFP, or provide three written quotes?

Yes to both, in the format your policy requires. Send the RFP and we will answer it against your evaluation criteria; if your threshold is met with three written quotes instead, say so and ours will be one of them, itemised.

Is pricing fixed, and what does the annual fee cover?

Yes — the build is a one-time itemised figure and the annual fee is a fixed figure, both set before you commit, with no per-visitor or per-bandwidth component at all. The annual fee covers hosting, SSL renewal, uptime monitoring, support and security updates. A sample pricing sheet with every line item is in the procurement packet.