Property Operations · Infrastructure · Systems & Automation

Operational systems for land development and property operations.

I work on the parts of an operation that are hard to document, hard to hand off, and easy to lose track of. Twelve years of that was land development and permitting: 865 sites across 23 states, taken from a dot on a map to a package construction could build. Then I built the software to do it faster.

Explore our systems Start a conversation

How we work

01 Establish the source of truth
02 Structure the operating data
03 Build the workflow and controls
04 Test, document, and hand off

Land & entitlement

Twelve years, still under contract today, and where the software started. See the practice

865Sites taken from search ring to construction handoff, across 23 states
13,875Project documents filed across 23 states

Systems & Automation

Two years, in property operations, private client work, and my own practice. See the systems

7Operational systems in daily production use
3Native applications built, notarised, and installed

Two areas of work. The same method in both.

Enumerated from the project archive, not estimated.

Most engagements are one of these. Some are both, and that is the case where having them in one place changes the work: the operating model gets written by someone who has run the operation, and the person automating it is the person who has to defend it in a hearing. What each practice covers

Selected outcomes

Work that has been delivered.

Clients are not named here. Names, markets, and supporting detail are available on request, and the case studies carry the full accounts.

Portfolio feasibility under a fixed deadlineFeasibility and permitting recommendations returned on a 316-site relocation portfolio inside a 60-day window, delivered through a document-generation pipeline built for the purpose. 317 packages in 60 days
Several hundred hearings, three denials in twelve yearsZoning boards, plan commissions, and boards of adjustment. One of the three I called before we filed, at a site that did not meet the ordinance. The other two were decided on political rather than regulatory grounds at sites that met every published requirement. All three denials, described
Documentation adopted as an enterprise standardSite feasibility and documentation forms taken up by two national carriers as their own standard, one of them across its national vendor base.
Seven operational systems in productionExpenses, property and location data, inventory, inspections, turnover, and an authenticated employee portal, in daily use by a five-person team at a property operator. Seven systems for one operation
One intake path, from first conversation to property setupForms, commercial terms, contract drafts, folders and property records joined into a single gated path, with each approval bound to the exact version it approved. A deployed private pilot, owner-only: contract generation, signature and property-record writes stay deliberately disabled until their approval gates complete. One intake path
Title cleared on a parcel written off as unleasableA blanket easement recorded across an entire eighty-acre parcel renegotiated down to its actual footprint, clearing title and allowing the ground lease and permit to proceed. Two contested outcomes
A care-coordination application delivered in two daysBuilt for my own family, who needed one private place to coordinate, and since published as a case study with a synthetic demonstration. Family Care Hub
A private product on six surfaces, from one contractApple TV, iPhone, iPad, Mac, an Apple TV Top Shelf extension and the web, all reading the same private contract. 202 commits and 990 tracked files inside 22 hours of repository history, and an Apple TV build that reached TestFlight review. Six surfaces, one contract
Apple accepted a notarised build 4 hours 24 minutes after the first commitProject control and invoicing across a Mac and a phone, sharing one store, with a rule that stops the same hour being billed twice. 18 accepted notarisations in all, across the twenty-five hours that followed. SCOPE

What we build

Systems the people doing the work can run.

Operating systems, not tools

A tool solves one task and leaves the operation to hold the rest together. A system carries the whole month: what is true, who decides, what happens on an exception, and what evidence exists afterwards.

Seven are in daily production use at a property operator, covering expenses, property data, inventory, inspections and turnover, reached through one authenticated portal and run by a five-person team without a technical specialist.

Controls that hold when something goes wrong

Versioned packages, schema versioning, staged QA gates that block submission rather than warn about it, deployment preflight, and a rollback path prepared before the change goes in.

A field submission once returned an error after it had already committed. The transaction was identified by its submission ID and payload hash, confirmed, and recovered, instead of a user being told to try again and a duplicate entering a record people trust.

Web applications for the people doing the work

An authenticated employee portal behind Workspace sign-in. A field inspection application opened from a QR code at the property, which works offline, stages drafts on the device, and asks for sign-in only at submission. A private, invitation-only application built for my own family. A client intake and onboarding application, deployed as an owner-only private pilot.

One intake path, from first conversation to property setup

Seven systems for one operation

Five web properties in production, three native applications installed. Engagements start where the work is stuck, not at a preferred product, so the same practice also produces governed spreadsheets and Apps Script where that is the right answer.

The full service areas

Go deeper

The record, in three places.

Land & entitlement

865 sites across 23 states, from search ring through due diligence, zoning, permitting and construction handoff. Three denials in twelve years of hearings. The disciplines, the programs by market, the bench, and the archive the figures were counted from.

The infrastructure practice

Systems & Automation

Seven operational systems in daily production use, three native applications built, notarised and installed, two of them macOS and one running on macOS and iPhone against a shared store, and the release controls around them: versioned packages, QA gates that block rather than warn, rollback prepared before the change goes in.

What gets built

The case studies

317 feasibility packages across 316 sites in a sixty-day window, on a pipeline built in three days. Documentation two national carriers adopted as their standard. Two land negotiations resolved rather than abandoned. A private application delivered in two days because the need required it.

Read the proof

Our approach

Context first. Tools second.

Complex operations rarely fail because a team lacks another tool. They fail when source information is scattered, responsibilities are unclear, field activity is hard to trace, and each handoff loses context. I organize those elements into usable operating systems, then apply automation and AI where they make the work more reliable.

I do not begin with a preferred software product. I begin with the people doing the work, the assets and records involved, the current source for each fact, the decisions and exceptions that matter, and the evidence needed to know the system worked. Tools are then selected or built around that operating model, and important actions remain visible, reviewable, and accountable to the people responsible for the outcome.

Learn about SSU

Let’s talk

Start with the work that is hardest to hand off.

jwatson@thinksynergy.biz