Step 1
Scope questionnaire
Use the standalone questionnaire to collect municipality size, department structure, staff/users, source links, existing systems, volume, security, training, and procurement needs.
Scope proposal
Start with one department, one City Pack, and a measurable review queue setup.
The setup proves whether CodeFlow reduces documentation friction, catches source gaps earlier, and gives staff cleaner packets to review.
Step 2
Setup + monthly model
Use the explainer for how Kyber turns questionnaire answers and official online sources into a final one-time setup quote plus monthly CodeFlow subscription.
Setup
Official-source intake, City Pack configuration, municipal system-stack mapping, issue-family setup, staff roles, and access provisioning.
Workflow
Case draft queue, source-gap flags, permit/existing-case checks, reviewer notes, and staff approval gates.
Launch
Training, QA checklist, launch measurement, and next-step recommendation after the scoped run.
Procurement posture
Sales-assisted, not anonymous checkout.
Municipal scope, records posture, staff users, payment/procurement path, and timeline are confirmed before provisioning. Subscription access is gated until paperwork/payment/procurement approval is complete.
Typical setup includes
- City Pack setup with system-of-record boundary
- Portal users and subscription status
- One configured case workflow
- Review queue training
- Evidence-backed launch report
City-specific stack
CodeFlow maps each municipality’s current software, lookup paths, and export/attachment workflow before representing any integration capability.
System-of-record boundary
Already using MGO or another municipal platform?
CodeFlow does not replace MGO, Tyler/EnerGov, Accela, OpenGov, GIS, or any official system of record. It sits beside those systems as a workflow-discipline layer for source separation, conflict handling, review gates, records readiness, and review-ready packet prep.
Honest export posture
Manual export first. Integration only when verified.
CodeFlow makes the system-of-record boundary, manual export / packet attachment path, source-gap flags, conflict state, review-gate status, and packet readiness visible before anything official happens. AI suggests and assembles; staff verifies and approves.