industries · government & public sector
public sector software
citizens actually finish using.
we design and ship government-adjacent platforms in mena. citizen services, ministry portals, e-government workflows. arabic-first, accessibility-first, audit-ready by default.
three things this industry actually needs from a software partner. nobody else says them out loud.
01
a citizen portal is a public service.
if a citizen abandons a permit application halfway through, that is a service failure, not a product metric. we design with completion as the north star, not pageviews. the products that win are the ones grandparents finish on the first try.
02
arabic and accessibility are not optional.
public sector products serve the entire population. arabic-first, wcag-aa-compliant, screen-reader-tested are the floor. these are not differentiators; they are the brief.
03
procurement does not equal partnership.
many government contracts get sold by sales teams and shipped by junior consultants. we run government engagements with the same senior partners as commercial work. continuity matters more in public sector, not less.
what we ship for government teams, ranked by what most engagements actually need.
+45% completion
completion, not engagement, is the public-sector north star.
citizen-service completion uplift seen when ux is designed for finish-the-task, not for time-on-page.
identity + sso integration
national id, government identity providers, smart-card and biometric flows where required.
wcag-aa accessibility
screen-reader tested, keyboard-only navigable, color-contrast compliant. not a separate workstream.
audit + transparency logs
arabic-first ui
designed for grandparents, not power users
public-sector products serve everyone. plain language, large hit targets, forgiving error states, no jargon. tested with the actual citizens who use them.
four stages. fixed deliverables at each. no scope-creep invoices.
week 1 — discover
discover
we map the citizen journey, the regulatory perimeter, and the stakeholder landscape before any design.
week 2 — design
design
arabic-first, accessibility-first, plain-language design. tested with real citizens, not focus groups.
week 3 — build
build
production-grade engineering with audit trails, identity integration, and transparency logs from day one.
week 4 — operate
operate
launch, monitor completion rates, iterate with the policy team in the loop.
every agency lists what they do. here is what we explicitly won't do for government teams.
we will not contract directly when local registration is required
public-sector procurements often require local-entity contracting. for those engagements we partner with a saudi or uae registered firm and remain the technical and creative team. transparent structure, no fronting.
we will not ship without accessibility and arabic native support
public-sector software serves everyone. wcag-aa and arabic-first are the floor, not optional add-ons. we do not negotiate them out of scope.
we will not pretend ai automates compliance
we use ai for productivity in design and engineering. we do not use ai to draft policy responses, classify regulated data, or replace human review. some things have to stay human in public sector. they stay human.
pick the path that matches where you are.
how a government build at maxiphy actually runs.