From a dot on a map to a package construction could build.

I co-founded the firm that did that work and ran it for eight years. I recruited and managed staff and subcontractors, and on every site I directed a technical bench: surveyors, title researchers, environmental and geotechnical consultants, architects, engineers, and power engineering. I still do that work today under contract.

In late 2024 a client handed my firm a relocation portfolio and 60 days to return feasibility and permitting recommendations on every one of them. It was not achievable by hand. I asked for three days, taught myself to code from nothing, and built the pipeline that delivered it.

That is when I understood that the discipline I had been applying to land could be applied to the systems a business runs on, and that most organizations are carrying their process around in a few people’s heads.

Synergistic Solutions Unlimited is what came out of that. I design operating systems for complex work: data foundations, workflows, production controls, and human-directed AI that keeps judgment with the person accountable for the outcome.

I am a founder-operator, not an adviser. Everything I recommend I have had to live with afterward.

The infrastructure record in full →

Whether the deliverable is a permitted tower site or a monthly expense close, the question is the same. How do you build something that works efficiently, is reliable, is reputable, and is backed by sound methodology. And how do you make it survive being handed to someone else.

I have now answered that question in land development, in software, and in back-office operations. That is what tells me it is a method, and not something I only knew how to do in one industry.

I begin with the people, decisions, exceptions, and source material already in motion. Every operation has an existing logic: who owns which decision, which source is trusted, what happens when something goes wrong. Automating before that logic is understood just makes the confusion run faster.

So the first work is modeling. Which source controls each kind of information, how conflicts get resolved, what states the work moves through, and where handoffs happen. Make the work understandable before making it automatic.

This is written down and I work to it. Quoted as written:

Every solution we ship should be: durable · safe · elegant · beautiful · easy to use · effective · impactful

A fix that works but fails these tests is not done. “Elegant” means one mechanism expressed consistently rather than parallel special cases; “beautiful” applies to deliverables and to the artifacts the owner reads: reports, prompts, and dashboards are part of the product.

“Beautiful” is on that list because the report you read every month is as much the product as the system that generates it.

When I need something from you, you will get the decision stated in one line, what is blocked without it, two to four options with their cost and reversibility, and my recommendation with a default.

You will never be asked a vague question, and you will never be asked for something I could have looked up myself.

Every system should make it possible to answer: What is current? Where did this information come from? Who owns the next decision? What changed? How was it tested? What happens if it needs to be reversed?

In practice that means event records instead of silent edits, version and review states instead of guesswork, evidence for completion claims, and backup and rollback readiness before changes go live. Important actions carry visible responsibility and human approval, not just an automated result.

SAGE, the Synergistic Agent Guidance Engine, is a local-first operations platform I am building. It is installed and in active internal use while development continues, and it is being prepared for beta testing. It is not commercially available.

It brings together source-grounded retrieval, project state, decision support, reviews, handoffs, and provider-flexible AI assistance, while keeping consequential actions under human control.

It grows out of the same operating patterns as the client work: one source for each fact, explicit roles and authority, evidence before completion claims, durable handoffs, visible quality checks, and recoverable change.