Modules & roadmap

Start with the essentials.
Add with intention.

A municipal website should grow from a useful foundation. Additional capabilities should earn their place through a clear public need and an agreed operating plan.
PROPOSED CORE FOUNDATION

The website comes first.

Structured civic content, service information, notices, council information and a coherent resident experience. Confirm exact scope and acceptance criteria in your proposal.

Explore the foundation

01 / Optional extensions

A roadmap, with clear boundaries.

All modules below are planned or exploratory. They are not represented as production-ready or included in a standard package. Timing, feasibility and price are proposal-specific.
Planned · optional

Advanced forms

Better questions. Clearer next steps.

Multi-step civic forms, accessible validation, routing and case-system connections. Define sensitive data handling, retention, consent and staff ownership before implementation.

BEFORE WE BUILD

Start with one service and test the entire submission-to-response journey.

Planned · optional

Alerts & subscriptions

Relevant information, responsibly delivered.

Topic-based updates and notification preferences are planned. Channels, emergency-use suitability, unsubscribe handling and delivery monitoring would need separate validation.

BEFORE WE BUILD

Confirm consent rules, delivery responsibilities and fallback communications.

Planned · optional

Editorial workflows

A clearer path from draft to public.

Role-based reviews, scheduling and revision history are planned beyond the simplified local notice preview. Control design must reflect your staffing and records obligations.

BEFORE WE BUILD

Map who can write, approve, publish, withdraw and audit each content type.

Planned · optional

Privacy-aware analytics

Learn what helps, with restraint.

Optional, opt-in measurement is planned. No external analytics run on this product website. Any future measurement needs an agreed purpose, provider and retention approach.

BEFORE WE BUILD

Decide which service questions need evidence, then collect only what is necessary.

Planned · optional

Localization tools

A website that speaks locally.

Translation coordination, locale-aware content and terminology controls are planned. No automated translation accuracy or language coverage is promised.

BEFORE WE BUILD

Identify your languages, human review process and equivalent-content obligations.

Exploratory · optional

AI assistance

A supporting role. Human accountability.

Optional drafting, summarization and content assistance are exploratory. No production AI integration is represented here. Public decision-making and unattended publishing are not an agreed scope.

BEFORE WE BUILD

Agree data boundaries, model providers, review steps and evaluation before a pilot.

Roadmap descriptions are discussion material, not a delivery commitment. Do not base a procurement decision on an uncontracted future feature. Review development status.

Built around your municipality

What would make the biggest difference?

Bring us one public-service challenge. We’ll help frame the requirements, dependencies and questions worth testing.