PRIXWERKZ
Platform demonstration & commercial proposal

Civitas

A multi-tenant digital services platform for municipalities in Gabon and Central Africa — built once, deployed for every commune.

Citizen portalOnline paymentsStaff workflowsInstitutional analytics
4
Communes live in demo
93 KB
First load, gzipped
100%
Offline-capable
1
Shared codebase
Prepared for
[Client / Municipality]
Date
August 2026
PRIXWERKZ  ·  Civitas · Digital Municipal Services PlatformCommercial in confidence  ·  01
The situation

Municipal services still run on paper and patience

Across Gabon and the wider region, the distance between a citizen and a simple certificate is measured in trips to the town hall, not in minutes.

  • Every request is a journey. A birth certificate means travelling to the mairie, queuing, returning days later to collect — often more than once.
  • No visibility. Once a file is submitted, neither the citizen nor the front desk can say where it is or when it will be ready.
  • Revenue leaks. Fees and local taxes are collected in cash, at a counter, during office hours only — with no reliable audit trail.
  • Decisions without data. Leadership has no reliable view of volumes, delays or collection rates across departments.
  • Connectivity is not a given. Any solution that assumes a stable connection excludes a large share of residents.
What this costs

Citizens

Lost working days, repeat trips, no way to plan

Staff

Manual registers, duplicated effort, no prioritisation

The commune

Uncollected revenue and no evidence base for budgeting

PRIXWERKZ  ·  Civitas · Digital Municipal Services PlatformCommercial in confidence  ·  02
The proposition

One platform. Every commune. Configured, not rebuilt.

Civitas is a complete digital front door for a municipality — and the administrative machine behind it. The same codebase serves every commune; only the configuration changes.

🏛️

Citizen portal

Services, news, procedures and local information in a single public site — mobile-first and searchable.

📄

Requests & tracking

Citizens submit civil-status and permit requests online, then follow each step to collection.

💳

Payments

Local taxes, fees and permits paid by card or mobile money, with an automatic receipt.

🗂️

Staff workflows

Configurable approval chains, assignment and status changes — with a full audit trail.

🔔

Notifications

Email and SMS at every transition, in the commune's own wording.

📊

Analytics

Volumes, processing times, approval and collection rates — per service and per period.

PRIXWERKZ  ·  Civitas · Digital Municipal Services PlatformCommercial in confidence  ·  03
Live demonstration

A public portal a commune can be proud of

Not a mock-up. This is the running application, built and served from the same repository we would deploy.

civitas.prixwerkz.in
  • Immediate action, above the fold. The three things residents actually come for — request a certificate, pay local taxes, report a problem — are the first three buttons.
  • Search that understands intent. Suggested queries reflect the real vocabulary residents use.
  • Identity of the commune, not of the vendor. Colours, imagery, wording and services all belong to the municipality.
  • Bilingual by design. French primary, English secondary, throughout.
PRIXWERKZ  ·  Civitas · Digital Municipal Services PlatformCommercial in confidence  ·  04
Live demonstration

From service catalogue to submitted file

Every service the commune offers is described once, then drives the catalogue, the search, the request form and the reporting.

civitas.prixwerkz.in/services

Service catalogue — grouped, filterable, each with its own requirements and fee

civitas.prixwerkz.in/demarches

Procedures — what to bring, what it costs, how long it takes, and where the file is

One definition, four uses. A service is described once by the administrator; that single definition drives the public catalogue, the search index, the request form and every figure in the reports. Nothing is maintained twice, so nothing can drift out of step.
PRIXWERKZ  ·  Civitas · Digital Municipal Services PlatformCommercial in confidence  ·  05
Multi-tenancy, proven

Four communes. One codebase. Zero forks.

Each of these sites is a separate production build from the same repository — with not a single line of component code changed between them.

Moanda Haut-Ogooué · mining town
Libreville Capital · eight services
Owendo Port city · logistics
Franceville Regional capital · mining

What is configured per commune

Name, crest and colour palette  ·  Photography  ·  Navigation  ·  Service catalogue  ·  Procedures and fees  ·  News  ·  Statistics  ·  Contact details  ·  Local wording

What never changes

Component code  ·  Request and approval engine  ·  Payment and reconciliation ledger  ·  Notification system  ·  Analytics  ·  Security model  ·  Accessibility work  ·  Offline behaviour

Why this matters commercially. Onboarding a new commune is a configuration exercise measured in days, not a development project measured in months. The marginal cost of municipality number five is a fraction of municipality number one.
PRIXWERKZ  ·  Civitas · Digital Municipal Services PlatformCommercial in confidence  ·  06
How it works

Configured at build time, isolated at run time

A deliberately simple architecture: one application, one database per commune, one deployment command.

Presentation
React 18 + Vite · progressive web app · installable, works offline
▼
Application
Node.js + Express · identity, services, requests, payments, workflows, notifications
▼
Data
PostgreSQL — one database per commune, no shared tables, no cross-tenant queries
▼
Integration
Payment gateway · SMTP · SMS (Twilio / Africa's Talking) · document storage
Complete tenant isolation
Moandaown database
Librevilleown database
Owendoown database
Francevilleown database
  • No shared database. A commune's data is physically separate. There is no query that can cross a tenant boundary, because there is no shared table to cross.
  • Self-hosted or managed. Each instance runs from a single docker compose up, on the commune's own infrastructure or on ours.
  • No vendor lock-in. Source code, infrastructure definitions and data are transferred to the client at final acceptance.
PRIXWERKZ  ·  Civitas · Digital Municipal Services PlatformCommercial in confidence  ·  07
Engineered for the region

Fast on a weak connection. Usable with none.

Performance here is not a vanity metric — it decides whether a resident on a 3G handset in a peripheral district can use the service at all. Every figure below is measured from the production build of this demo.

93 KB
Total first load, gzipped — the entire application
14 KB
Per-commune payload; other tenants' data never ships
<3 s
Time to interactive on a 3G connection
100%
Of visited pages available offline
📶

Offline-first, genuinely

Pages are cached on first visit. Submissions made offline are queued on the device and sent automatically when the connection returns — with retry and backoff.

🚫

No web fonts, no trackers

System fonts only and no third-party scripts. Nothing loads that the resident did not ask for.

📱

Installable

Residents can add the portal to their home screen and open it like a native app — no app store, no download barrier.

PRIXWERKZ  ·  Civitas · Digital Municipal Services PlatformCommercial in confidence  ·  08
Scope

What each audience gets

The platform serves three distinct audiences from a single deployment.

For residents

  • Public portal: services, news, local information
  • Account with verified email and phone
  • Submit civil-status and permit requests
  • Track every file to collection
  • Pay taxes and fees, download receipts
  • Report problems and follow resolution
  • Message departments directly

For staff

  • Queue of assigned files with priorities
  • Configurable approval chains per service
  • Status changes with mandatory audit trail
  • Document issue and certificate generation
  • Complaint assignment and escalation
  • Internal notes and citizen correspondence

For leadership

  • Volumes and processing time per service
  • Approval, rejection and backlog rates
  • Revenue by service and payment method
  • Collection rate and outstanding balances
  • Citizen adoption and repeat usage
  • Scheduled reports by email · CSV and PDF export
PRIXWERKZ  ·  Civitas · Digital Municipal Services PlatformCommercial in confidence  ·  09
Delivery

Four phases to a live commune

Each phase closes on something demonstrable and independently useful. Nothing is held back for a big-bang launch.

Phase 1Weeks 1–3
  • Authentication and citizen accounts
  • Public portal configured for the commune
  • Document requests and tracking
  • Offline queue and sync
Residents can register, request and track.
Phase 2Weeks 3–4
  • Online payments and receipts
  • Complaints and messaging
  • Staff console and approval chains
  • Service and workflow configuration
Staff can process; residents can pay.
Phase 3Weeks 4–5
  • Email and SMS notification engine
  • Editable message templates
  • Analytics dashboards
  • Scheduled and exportable reports
Leadership gets evidence, residents get updates.
Phase 4Week 5+
  • Accessibility audit (WCAG 2.1 AA)
  • Performance and load hardening
  • Administrator training and handbooks
  • Handover of code and infrastructure
The commune operates it independently.
Assumption. This timeline is for the first commune, which carries the full platform build. Subsequent communes are configuration and content, not development.
PRIXWERKZ  ·  Civitas · Digital Municipal Services PlatformCommercial in confidence  ·  10
Commercial model

A fixed core, and only what you actually need on top

The platform is priced so that a commune pays for the standard product once, and pays separately only for work that is genuinely specific to it.

Included in the core platform
The standard product

Everything demonstrated in this deck. Delivered, configured and branded for the commune, with training and handover.

  • Public portal, fully branded and bilingual
  • Citizen accounts, requests and tracking
  • Online payments, receipts and reconciliation
  • Complaints, messaging and notifications
  • Staff console and configurable workflows
  • Analytics, exports and scheduled reports
  • Offline-first PWA · self-hosted deployment
  • Administrator training and full handover
Quoted separately
Municipality-specific work

Anything outside the standard product is scoped and quoted on its own, at a published day rate — never bundled into the core price.

  • Integration with an existing register or legacy system
  • A service with a bespoke legal or approval process
  • Additional languages beyond French and English
  • Custom document or certificate templates
  • Migration of historical paper or digital records
  • On-site training beyond the standard programme
  • A regional payment provider not already supported
The principle. The core platform does not get more expensive because one commune has an unusual requirement. That requirement is quoted, approved and built as an increment — and if it proves broadly useful, it is folded into the standard product for everyone at no extra charge.
PRIXWERKZ  ·  Civitas · Digital Municipal Services PlatformCommercial in confidence  ·  11
Why Prixwerkz

Built by a team that has already solved this problem

This is not a concept deck. The application in these screenshots exists, builds in about a second, and is running today across four municipal configurations.

Working software, not slides

Everything shown here is the running product. You can open it, click through it, and switch between communes before you commit to anything.

Designed for the constraint

Low bandwidth, intermittent connectivity and entry-level Android handsets were the starting assumptions, not an afterthought at the end.

Public-sector engineering discipline

Data isolation per commune, audit trails on every state change, accessibility to WCAG 2.1 AA, and no dependency the client cannot take over.

You own the outcome

Source code, infrastructure definitions, documentation and data transfer to the client. Every third-party component is open source or a standard commercial service on your own account.

PRIXWERKZ  ·  Civitas · Digital Municipal Services PlatformCommercial in confidence  ·  12
PRIXWERKZ

Let's put your commune online.

We can configure a working instance for your municipality — your identity, your services, your data — and walk your team through it before any commitment.

Next step
A 45-minute working session
Contact
hello@prixwerkz.in
Web
www.prixwerkz.in
PRIXWERKZ  ·  Civitas · Digital Municipal Services PlatformCommercial in confidence  ·  13