Get in touch →

Home/Work/Permit Solutions Automation

Permit Solutions Automation

Seven municipal record sources, sitting behind four different portal systems, consolidated into one reviewed queue that produces the documents and the invoices at the end of it. This is a record of a system that exists. It is not a savings claim: nobody timed the work before it was automated.

Internal operations consolePython · Flask · SQLiteDescribed as of 2026-08-15

Schematic of the Permit Solutions Services operations console: seven municipal record sources behind four portal platforms feed one normalizing filter, then a single database holding one record per case, then a deliberate human review, then document generation and tracked dispatch, with delivery status returning to the record.
The eleven stages, drawn from the source code. This is a schematic, not a screenshot: the console is internal and login-gated, so there is no public view of it to show.

Read this part first

Our other two records show a number that moved. This one does not, because nobody timed the work before it was automated. We are publishing it anyway, described exactly as far as it can be verified and no further, because the alternative is selling business automation with nothing published behind it at all.

Everything below is checkable against the source code of the system itself. Nothing below is an estimate.

The record

  • What it is: an internal operations console used daily by named operators, not a product and not for sale
  • Sources wired: seven municipal record sources across Miami-Dade County
  • Sources confirmed against real exports: three. The other four are built and connected but have not yet processed a real file, so their column mapping is unconfirmed
  • Portal systems handled: four, each needing a different integration
  • Console screens: 30 routes covering intake, review queue, pipeline, documents, invoicing, proposals, contracts, reporting and user administration
  • Code: 11,179 lines across the connectors, console, database, lookup and mail modules
  • Automated tests: 38, covering the record-to-document conversion and the delivery-status receiver
  • Before time per task: none exists. The manual process was never timed
  • After time per task: none exists. Not instrumented
  • Error and rework rate: none exists, before or after

The eleven stages, and the one a person still runs

Each of these is a real stage in the running system. The one step a person still does is marked, because a system that hides its human steps is a system nobody can trust.

  1. Open each municipal source and run a date-bounded search
  2. Pull only records newer than that source’s last successful run
  3. Normalize seven different record layouts into one shape
  4. Filter to the scope of work that is actually relevant
  5. Drop the near-misses that match a keyword but are the wrong kind of case entirely
  6. Write to one database, keyed so a re-run updates rather than duplicates
  7. Look up the property owner and mailing address
  8. Check the mailing address is deliverable before anything is produced
  9. Human review: an operator works the queue and decides what proceeds
  10. Generate the document and send it, tracked
  11. Receive the delivery status back and update the record

Invoicing and proposals sit on the same database, so the scope-of-services wording is assembled from reusable blocks with the job details substituted in, rather than retyped per job. Most service businesses recognize the retyping immediately.

What was replaced

  • Seven portals checked one at a time, by hand, in a browser → one queue
  • A spreadsheet as the system of record → one database that cannot double-count the same case
  • Owner and address looked up manually per record → looked up automatically
  • Scope wording retyped into each document → assembled from reusable blocks
  • No record of what was sent or whether it arrived → delivery status recorded against the case

What it does not prove

It does not prove hours saved, because the before was never measured. It does not prove fewer errors, for the same reason. It does not prove revenue. It proves that the system described here exists, runs, and does the eleven things listed above, and that is the entire claim.

On a new engagement the first thing we write down is how long the work currently takes and how often it has to be redone, before anything is built. Once work is automated, the numbers from before it are gone for good, which is why this page carries no hours-saved figure.

The business

Permit Solutions Services LLC resolves open permits, violations and unpermitted work in South Florida. Victor is an owner, which is disclosed here for the same reason it is disclosed on the other records: the relationship matters when you read a result. The console is internal and login-gated; there is no public demo of it.

Tell us what you need → All work