HOME
[kal_foundry]servicesworkaboutteamget a quote ↗

// civicOps · by KAL Foundry · for municipalities

software for the teams that keep a town running.

civicOps is KAL Foundry's engineering team for municipalities and public-sector departments. We build the software, automations, and applied AI your departments run on — fixed quote before work starts, and your organisation owns everything we build.

start a conversation see what we build
  • 7 lines of work
  • 5 steps, every project
  • a human reply within 1 business day
  1. 01

    fixed quote before work starts

    A written scope and price, agreed before we build. No open-ended hourly billing.

  2. 02

    a working build every week

    Something your staff can click through — not a status report.

  3. 03

    you own the code and the accounts

    Code, domains, hosting, and service accounts — in your organisation's name. No lock-in.

  4. 04

    a human reply within 1 business day

    Every inquiry gets a real answer from the people who would build it.

01 · capabilities

what we build for public-sector teams.

Seven lines of work — most projects combine two or three. Not sure which you need? Describe the problem in the form below and we'll tell you.

7 lines
public sector
01 / 07

permits, licensing & records

Move permit, licence, and records workflows off paper and spreadsheets.

./scope_permits_records →

what you get

  • Digital intake and review workflows
  • Status tracking from application to decision
  • Documents stored with each case
  • Reports on volume and turnaround

good fit when

  • Applications are tracked on paper or in spreadsheets
  • Finding an old record means a trip to the filing room
  • Staff can't see where a case is without asking around
public sector
02 / 07

dashboards & open data

Numbers staff and council can check without waiting for a report — and public data pages for residents.

./scope_dashboards →

what you get

  • Internal dashboards for department metrics
  • Public data pages residents can browse
  • Data pulled from your existing systems automatically
  • Downloadable datasets for anyone who wants the raw numbers

good fit when

  • Reports are rebuilt by hand before every meeting
  • The same data request keeps coming in
  • Department numbers live in separate spreadsheets
03 / 07

department tools & portals

Browser-based tools for staff, contractors, and partner agencies — built around how your department already works.

  • Internal tools that replace spreadsheet trackers
  • Portals for staff, contractors, and partners
  • Logins and permissions by role
  • Admin panels for the data your team maintains
./scope_tools →
04 / 07

mobile apps for field crews

iPhone and Android apps for inspections, public works, and anyone who works away from a desk.

  • Apps for iPhone and Android
  • Photos, location, and notes captured on site
  • Offline mode where the signal drops
  • Sync back to the office systems you already use
./scope_field_app →
05 / 07

automation & integrations

Make the systems your departments already use talk to each other — and stop retyping data.

  • Connections between the systems you already run
  • Reports and alerts that build and send themselves
  • Form and email data routed to the right team
  • Written docs, so staff know what runs where
./scope_automation →
06 / 07

applied ai

AI that helps staff with paperwork — grounded in your own documents, with a person reviewing the work.

  • Document and email processing — forms, applications, correspondence
  • Search across policies, minutes, and records
  • Drafting help for routine replies, reviewed by staff
  • A plain-language write-up of what it does and doesn't do
./scope_applied_ai →
07 / 07

websites + care plans

Department and project sites that stay current — and a team to keep them running after launch.

./scope_website →
  • Sites designed and built, readable on any phone
  • Forms that land in the right inbox
  • Domain and hosting in your organisation's name
  • Care plan: hosting, updates, fixes, and small changes each month

02 · the problems

typical problems we solve.

examples · not client stories
example / 01permits
before
Applications arrive on paper and are tracked in a spreadsheet.
after
Each application has a digital case, a status, and its documents in one place.
example / 02dashboards
before
Staff rebuild the same report by hand before every council meeting.
after
A dashboard that updates itself from the systems already in use.
example / 03field app
before
Inspection notes on paper, typed up back at the office.
after
An app that captures photos and notes on site — even offline.
example / 04applied ai
before
Answers buried in years of policies and meeting minutes.
after
Search that finds the passage and links the source document.

// illustrative examples of the work we do — not case studies of past clients.

03 · the process

how it works.

The same five steps for every project. Your team always knows what happens next and what it costs.

5 steps

  1. intro call

    Tell us what's slowing the department down. We ask questions — and tell you straight if software isn't the answer.

  2. written quote

    A fixed scope and a fixed price, in writing, before any work starts.

  3. build

    A working build every week. Your staff click through it, we adjust.

  4. launch + handover

    We launch, walk your team through it, and hand over the code and every account.

  5. care plan optional

    Hosting, updates, fixes, and small changes — one monthly plan.

04 · engagements

how engagements work.

Every project is quoted in writing before work starts. Pick the shape that fits where your department is today.

3 models
model / 01to start

discovery sprint

For when the problem is clear but the solution isn't.

  • A map of how the work flows today
  • A recommended scope, in plain language
  • A fixed quote for the build

fixed price, agreed up front
model / 02to build

fixed-scope build

For when you know what you need built.

  • Written scope and price
  • A working build every week
  • Launch, handover, and every account in your name

fixed quote before work starts
model / 03to run

monthly care plan

For keeping what we build fast, secure, and current.

  • Hosting and updates
  • Fixes when something breaks
  • Small changes each month

one monthly plan

05 · questions

questions departments ask.

7 answers
does our organisation own what you build?

Yes. The code, the domains, the hosting, and the service accounts are set up in your organisation's name. If we ever part ways, you keep everything — no lock-in.

what does it cost?

It depends on scope, so every project gets a written, fixed quote before work starts. If the scope changes mid-project, we agree on the change in writing first.

can you work with our procurement process?

Tell us what your process requires in the form below, and we'll say plainly whether we can meet it before anyone spends time on a proposal.

can you work with the systems we already use?

That's usually the point. We check what you run on the intro call and tell you up front if something can't be connected.

will ai see resident or staff data?

Only if the job needs it, and you decide. We map which data each AI feature touches before we build it, and the AI service accounts are set up in your organisation's name, like everything else.

do our staff need to be technical?

No. We explain decisions in plain language, and the weekly builds let your team judge the work by using it — not by reading code.

what do you need from us?

One person who can make decisions, a short weekly check-in, and access to the systems we're connecting. We handle the rest.

06 · start

start a conversation.

Tell us what the department is trying to fix. A few sentences is plenty — we read every inquiry and reply with next steps, or an honest "this isn't for us."

  • 01fixed quote before work starts
  • 02a working build every week
  • 03you own the code and the accounts
  • 04a human reply within 1 business day

prefer email? team@kalfoundry.com · running a business? strikeOps →

what do you need? · pick any
budget range · if known
timeline

* required · a human replies within 1 business day

fixed quote before
work starts start a conversation