Missing information
Work stops while someone waits for a document, an answer, or an approval. Who follows up, and when?
Zero Conjecture · Brian Galura
AI workflows your team can actually operate.
I help you spend less time chasing updates and moving information between systems. We start with a process your team knows, build automation around the work, and measure whether it helps.
I work with real estate operations and other businesses where the same work comes around every day.
Start with the work
What keeps your team chasing the next step?
Your team knows what needs to happen. But keeping the work moving still takes reminders, status checks, and someone who remembers all the details.
Repeated coordination
People copy the same update into several tools, check who has responded, and piece together what happened before they can act.
Exceptions without a path
Routine cases move along. An unusual one sits in an inbox because nobody is sure who should handle it.
Illustrative workflows
Start with something you can measure.
These examples show how recurring work in property operations and construction can be scoped and measured.
Property operations
Unit readiness
When a unit becomes vacant, track inspection, assigned work, evidence, and the next action. Staff approve readiness and handle exceptions.
Measure: elapsed days to readiness and staff coordination effort.
Property operations
Application document follow-up
From application receipt to review, track missing documents, approved follow-up, and the handoff to the reviewer. Staff confirm completeness and make application decisions.
Measure: document wait and time to the review handoff.
Construction operations
Monthly card reconciliation
Each month, compare the card statement with accounting records, flag differences, and bring unresolved items to the person responsible for review.
Measure: staff effort per monthly cycle and unresolved items at review.
Construction operations
Project cost reviews
Bring each project's budget and recorded costs into one comparison. Resolve category differences and have the project owner review the result.
Measure: time to a reviewed comparison and corrections needed during review.
The details vary by business. The questions stay much the same: what happens next, who owns it, and what happens when something goes wrong?
The approach
Get the first process working. Build from there.
Understand and prepare
Look at real cases, including the ones that got stuck. Understand the rules, the systems, and how the work performs today. Then choose a useful starting point.
Build and operate
Connect the workflow to the tools your team already uses. Check it against real cases, with clear owners and a path for exceptions.
Measure and hand over
Compare the results with where we started. Give your team the documentation, training, and access they need to run what we build.
Expand from the foundation
Once we know your systems and how your team works, we have a better starting point for the next process. We agree what it needs before committing to a schedule.
Operator and engineer
I understand the business side and build the systems.
I've run a business and built infrastructure and platforms. I bring that experience to the work of connecting systems and making recurring processes easier to run.
I think through what your team will need to use, maintain, and adapt what we build.
More about Brian →From the archive
The engineering behind the work.
Earlier articles and talks from my work in infrastructure and cloud systems.
Start a conversation
What process would you like to improve?
Tell me where the work gets stuck, what your team uses today, and what you would like to change.
Discuss a workflow