For government and the public sector

Websites and systems for the public sector

A public body speaks to residents, providers and partners at once, and every word has to be accurate and current. We build the portal, the official email behind it and the way your staff keep it up to date without a developer in the loop.

Built for agencies, commissions, secretariats and state-level bodies.

Portal of a presidential fiscal policy and tax reform committee, with its mandate headline
Website of an African industry advisory firm, with consulting, training and industry intelligence sections
Website of a lawyers’ association with membership and events
The parts of a public portal we build and run.

The problem this fixes

Most public portals grow page by page until no one can find anything, and a single out-of-date figure undermines trust in the whole site. Residents give up, providers call instead, and the office carries the load by hand.

Official communication also leaks when email is not locked down. Fake messages that copy your domain reach the public, and there is no record of who changed what, or when.

A public portal has to stay accurate, searchable and accountable, and it has to let your own people publish without waiting on anyone.

What we do

One team builds the portal and the systems around it, and stays responsible for them after launch.

  • A portal residents can use

    A clear structure for every audience, fast on a phone, and built so search engines and the public find the right page. We design the journeys for registration, enrolment and enquiries, not just the pages.

  • Self-service publishing

    Your secretariat posts news, documents and updates from a simple dashboard, with no developer in the loop. The public stays ahead of rumour because the source is current.

  • Official email, locked down

    We set up the records that prove your mail is really from you (SPF, DKIM and DMARC), filter phishing and add a second sign-in step. Impersonation of your domain gets much harder.

  • Enrolment and payments

    Registration, applications and payments on the portal, with a record the office can rely on. We work with the payment and identity providers the agency already uses.

  • An accountable record

    Content, access and changes are logged, and we keep the technical records an internal auditor asks for. When a request comes, answering it takes a day.

Public bodies we build for

Client names and full write-ups live in Our Work. Here is the work by its facts.

  • A national policy platform, by type

    A federal reform committee: a national policy platform of about 19 interlinked pages, a personal income tax calculator, and a newsroom the secretariat publishes itself.

  • A state health insurance portal, by type

    A state health insurance agency: a public portal for residents, providers and administrators, with registration, payments and a media centre, moved across with its content intact.

  • Our Work

    Case studies for the agencies, firms and public bodies we build and run systems for.

  • Discuss an enterprise engagement

    For a multi-agency rollout or a formal procurement, the enterprise path covers the NDA, the sample statement of work and the capability pack.

Where our part ends

In public work, everyone needs to know who owns what.

Included

  • Designing, building and hosting the portal
  • Setting up and securing official email and accounts
  • Wiring registration, enrolment and payments to your chosen providers
  • Training your staff to publish, and keeping the technical records

Not included

  • Policy decisions and the wording you must approve, which stay with your office
  • Legal or regulatory advice, which stays with your counsel
  • Changes inside third-party payment or identity platforms, owned by their vendors
  • Certifying or guaranteeing compliance with any regulation

How we start

  1. Scoping call

    We go through who the portal serves, what they must do on it, and what it has to connect to.

  2. Your fixed price

    You see the scope and a fixed price before any build starts. It splits what we deliver, what your office decides and what a vendor controls.

  3. Phased build

    We build in stages you can review, starting with the pages and journeys that carry the most traffic.

  4. Handover and upkeep

    We train your publishers, hand over the records we hold, and keep the portal fast and current after launch.

Questions public bodies ask

Can our staff update the site without calling a developer?

Yes. We build on a dashboard your secretariat uses to post news, documents and updates. We train your publishers at handover and stay available if you need us.

Can you move our existing content across?

Yes. We migrate your pages, documents and media into the new portal and keep the links working, so people who saved the old addresses still arrive at the right place.

Do you handle registration and payments?

Yes. We build the registration and enrolment journeys and wire payments to the provider you use, with a record the office can rely on. The payment platform itself stays with its vendor.

What does a public portal cost?

It depends on the number of audiences, the journeys involved and how much content moves across. After one scoping call we send the scope and a fixed price before any build starts.

Start with a scoping call

Tell us who the portal serves and what it must do. You get a clear scope and a fixed price before any build starts, and no sales pitch.

Or WhatsApp us

Monday to Friday, 9am to 6pm. We reply within one business day.