Service
Citizen & staff portals
Self-service portals that let residents apply, pay, and check status — and internal staff portals that replace spreadsheets, email chains, and aging Access databases.
Resident-facing
Citizen self-service portals
- Permit applications and renewals
- Business licensing & registration
- Tax and utility payments
- 311-style service requests
- FOIA / public records requests
- Inspection scheduling
- Online forms with conditional logic
Staff-facing
Internal portals & intranets
- Department dashboards and case queues
- Staff directories with org charts
- Document libraries with version control
- Internal forms (HR, IT, facilities)
- Approval workflows with audit trails
- Reporting dashboards for leadership
- SSO with your existing identity provider
Built-in Foundations
Every portal ships with these
Identity & SSO
SAML, OIDC, and integration with state/county identity systems. MFA optional or required by role.
Payments
PCI-compliant integrations with Stripe, Authorize.net, and major government payment processors.
Document upload
Virus-scanned uploads with automatic redaction support and audit-ready storage.
Notifications
Email and SMS notifications driven by workflow events. Configurable per applicant preference.
Audit logging
Every action is logged. Full audit trail available for FOIA, OIG, and internal review.
Accessibility
Every component is WCAG 2.2 AA conformant out of the box. Tested with assistive tech.
Who it’s for
Departments that still run on paper and email
This fits a permits office that takes applications by PDF and email, a clerk’s office that tracks records requests in a spreadsheet, or a department that runs on an aging Access database. A portal can cover one process or grow one service at a time. The department head usually leads, with IT as a partner.
The problems are the same everywhere. Residents cannot see where their request stands, so they call. Staff retype form data into other systems. Approvals live in inboxes, with no record of who signed off.
What your agency provides
- A process owner for each service in the portal
- Current forms, fee schedules and approval steps
- Access to the systems the portal must read or update
- Identity provider details for staff sign-in
- Staff and residents willing to test early versions
The process
How a portal project runs
-
1
Discovery and scoping
We walk through each process with the staff who run it and map every form, fee and approval. You get a written scope.
-
2
Design and architecture
We design the resident and staff screens, the data model and the workflow, and review the screens for accessibility.
-
3
Build and iterate
We build one service at a time in two-week sprints, with demos to the staff who will use it.
-
4
Test, train and launch
Staff and a group of residents test it. We train staff, move open cases over and launch with a runbook.
-
5
Hypercare and transition
We stay close as the first real applications arrive, then hand off to maintenance or your team.
These are the same phases we use on every project. The full plan is on our implementation page.
Related work
How it fits with our other services
- System integrations connect the portal to your permitting, tax, payment and GIS systems.
- The portal can run on our managed hosting, with backups, monitoring and audit logs.
- A website redesign puts the portal’s entry points where residents look first.
- An accessibility audit can check the full resident journey, from search to payment.
Every service is listed on our capabilities statement. To scope your first service, tell us about the process on our contact page.
FAQ
Questions about portals
How do we buy a portal project?
How long does a portal take to build?
Who owns the portal and the data residents submit?
Can residents with disabilities use it?
What support is there after launch?
Related Services
Often paired with this engagement
Let’s talk about your project
Tell us what you’re trying to accomplish and we’ll respond within one business day with next steps.