Commonwealth AI Partners
Who we work with SEC.02

Business Districts

For the staff who have to prove the district earned its assessment.

You run a clean-and-safe program, an events calendar, a small-business line and a marketing shop inside a boundary somebody drew on a map — and none of it counts until it is written down somewhere a board can check. We build the systems underneath so the record keeps itself.

Book a systems audit 30 min · If we’re not the right fit, we’ll tell you who is.

Fit check

  • Districts with roughly 2–20 staff, funded by an assessment the ratepayers inside your boundary did not volunteer to pay
  • Clean-and-safe logs, event counts and vacancy numbers that live in three places and meet each other once a year
  • A renewal or reauthorization vote on the calendar, close enough that you have started counting backward from it
  • A board with property owners who read every page, and a city that wants the same story in its own format

The pattern

We’ve seen this one before.

None of this is a competence problem. It’s what happens when the record of your work is spread across the city, your crew and a clipboard, and nothing ever puts it on one page.

P.01 Symptom

The annual report eats six weeks of somebody’s year.

It gets built the same way every time. One person opens last year’s file, then goes around asking everyone else for their numbers. Half are in a phone, half in a folder nobody else can open. The hard part was never the writing. It was the assembling.

P.02 Symptom

Your service log is a camera roll.

The crew photographs the graffiti, the overflowing can, the light that went out, and it all lands on a supervisor’s phone. Nothing totals it. When a ratepayer asks how many times their block got serviced last quarter, the honest answer is that somebody would have to sit down and scroll.

P.03 Symptom

Your ratepayer list and the city’s roll stopped matching.

Parcels change hands, a tenant closes, one storefront becomes two. The city updates its assessment roll on its own schedule and your list gets updated when someone happens to notice. So notices go to owners who sold years ago, and businesses well inside the boundary never hear from you at all.

P.04 Symptom

The board asked for a number nobody can produce.

Ground-floor occupancy, foot traffic, incidents on the corridor — someone at the table wants the trend and the room goes quiet. The data exists. It is at the city, with the police, and on your own staff’s phones. It was just never collected anywhere it could be counted. Before a reauthorization vote, that quiet costs you.

What we deploy here

Four things, in the order districts usually need them.

You probably need two of these to start. We tell you which two on the audit call, and we tell you if the answer is none of them.

Tools

These are the tools this work runs on.

We’re not asking you to throw any of this out. Most of what a district needs is already paid for, and some of it belongs to the city. If yours isn’t on this list, that doesn’t rule us out — it means we’ll be honest about the ramp-up on the call.

Field & service reports

SeeClickFix, Fulcrum, ArcGIS Survey123, and whatever app your clean team logs into

City systems

Open-data portals, 311 and work-order queues, the assessment roll, business licence and permit records

Events & tickets

Eventbrite, and whatever registration your website already includes

Email

Constant Contact, Mailchimp

Accounting

QuickBooks, Bill.com

Website & files

WordPress, Squarespace, Google Drive, Dropbox

FAQ

What districts ask before they hire us.

Q.01 We spend public money. Our procurement is not simple.
We have written to a scope before. Tell us what your rules require — a written scope, competing quotes, a not-to-exceed figure, a board resolution — and we write to that format. If the threshold means this has to go out to bid, we will say so on the call rather than after you have spent a month with us.
Q.02 Our city IT department will have opinions about this.
Good, and bring them in early rather than late. What we build lives in accounts the district owns, not on city hardware, which is usually the part they actually care about. If their answer is no, that is a real answer, and we would rather hear it in week 1 than week 6.
Q.03 Half our board are property owners. They will read all of it.
They should. Every number we put in writing shows the assumption behind it, so an owner who does not want to be here can pull the thread and get to the bottom of it. If a line cannot survive that, it does not belong in the document in the first place.
Q.04 Some of this could end up in a public records request.
Then we build it assuming it will. Your counsel decides what counts as a record — that is not our call. Ours is to keep the trail clean and the export easy, and to keep anything out of the system that you would not want read aloud at a public meeting.
Q.05 What does this do for us at reauthorization?
It is the date we plan backward from. The point is that the numbers for the renewal case are already sitting there in a form you can print, instead of being reconstructed in a panic over six weeks. We cannot vote for you. We can make sure the record is not the weak part of your argument.
Q.06 What if you look at this and there’s nothing worth doing?
Then we tell you that, in writing, and you keep the audit. We would rather lose the build than sell a district something it did not need — it is assessment money, which makes that worse, not easier. The referral from a district we were honest with is worth more than the invoice.
Next step SEC.02.99

Bring us last year’s annual report and the folder it came out of.

Thirty minutes, no deck, no pitch. We’ll tell you what we’d fix first, roughly what it takes, and whether it’s worth doing at all.