Terrain, dependence, leverage, and freedom of maneuver
Sun Tzu’s ideas help me ask which AI dependencies an organization can still walk away from, and which ones it cannot.
About
The pattern behind the résumé.
I’ve spent more than a decade moving between transformation, operations, governance, and technology because organizations kept discovering they needed the next thing after I had already fixed the first one.
EMSAR hired me into financial planning and analysis. I ultimately designed the work-order system from order entry to end state across every work-order type, with metrics and controls at each stage. Reserve at Westcreek selected me for community management. I ended up rebuilding its governance, long-range capital planning, public relationships, and community-value strategy.
My best work begins where a problem crosses boundaries. I connect process, data, systems, incentives, and people, then stay with the work until the solution functions in practice.
How a personal system became an organizational question
MOSAIK makes the working method visible.
MOSAIK began after I relocated to Germany, while I waited for work authorization. I used that time to bring the same organizational discipline I had used throughout my career to my own digital life: files, decisions, and the record of why something was done a certain way. It was not meant to become anything more than that.
Partway through, I recognized the pattern. The personal problem was also an organizational risk. The intelligence and context developed through AI could become inseparable from the provider delivering it. That is when MOSAIK became a case study rather than just a personal system.
It matters for a second reason. Much of CF Consulting’s client work is protected by confidentiality. MOSAIK is deliberately public. It is the fullest available picture of how I approach a problem from first diagnosis through working implementation.
Career through-line
The titles changed because the problem kept expanding.
That is why my career has moved from analysis into process leadership, from consulting into operating design, and from a personal knowledge problem into MOSAIK. The titles changed, but the work kept asking the same thing of me: see the whole system, find what is producing the visible problem, and build something people can actually use.
Explore the full career storyCross-disciplinary practice
Useful patterns can travel between fields.
I build enough fluency to understand a field on its own terms, then look for mechanisms that travel. The value is not the collection of subjects. It is recognizing a useful pattern, translating it responsibly, and turning it into something another setting can use.
Staging, assignment, utilization, collection, and redistribution
Managing movement through a golf-cart fleet became a practical model for work-order routing, asset processing, and fleet design.
Create value instead of policing appearances
I treated community governance like long-term placemaking: build amenities, develop government relationships, and give realtors a reason to justify a premium price.
Twenty thousand organized files became a trustworthy data method
Cleaning names, categories, duplicates, and structure in a 20,000-file music library became the same discipline EMSAR’s financial data needed for reliable comparison.
Empathy plus commercial judgment
The first useful answer was no. The better answer became a scalable business.
I entered consulting by advising a small-business owner not to pursue the large contract he wanted. The company was not equipped to deliver it responsibly, and winning the work could have created a larger failure.
I kept asking what success was supposed to accomplish. The real objective was dependable growth, not that particular contract. That opened a different path: a recurring neighborhood service model built around route density, collective purchasing, and proactive compliance support.
The new model needed 20 homes to break even. It reached 92 homes by mid-season and expanded into three additional communities. It produced recurring demand, denser operations, and less dependence on one oversized customer. Saying no did not shrink the opportunity. It exposed the stronger one.
20homes needed to break even92homes reached by mid-season3additional communities entered
The more responsible answer became the stronger business model.