Meet the builder
I'm Paul Falor, the independent builder and operator behind Cinch. My career has moved from hands-on security into global technology leadership and, now, enterprise AI—while staying grounded in the work of designing and building real systems.
Technology executive · security leader · hands-on builder
Career arc
I have spent my career widening the frame: from individual controls and technical risk, to enterprise platforms and operating models, to the strategic adoption of AI across complex organizations.
My career began in security consulting, information protection, audit, and enterprise risk at KPMG, TRX, SunTrust—now Truist—and Global Payments. That foundation taught me to see technology as a connected system of trust, operations, and business consequence.
At North Highland, I served as Chief Information Officer and Senior Managing Director across technology, product development, data, security, and enterprise platforms. The work spanned transformation, cloud, acquisitions, operating-model change, and translating technology investment into business strategy.
Today I am a Managing Director and the Americas Lead for Secure & Responsible AI and Data Protection at Accenture Cyber Services. I help executives adopt emerging technology with the architecture, governance, and security needed to make it useful in the real world.
The intersection
The thread through my career is not technology for its own sake. It is helping organizations understand a new capability, secure it, connect it to strategy, and turn it into an operating advantage.
I work close enough to new technology to understand what it can actually do—and build with it myself, not only advise from a distance.
My security background makes trust boundaries, failure modes, privacy, resilience, and responsible adoption part of the design from the beginning.
I connect technical choices to operating models, investment decisions, customer value, risk appetite, and the outcomes leaders are accountable for.
Current performance fieldwork
Ongoing capacity and resilience work treats client certainty, authoritative durability, service continuity, recovery behavior, and cost as separate questions. The goal is to find the limiting path, make one evidence-led change, and repeat the same exercise before drawing a conclusion.
Deterministic synthetic company data, real authorization paths, and concurrent authenticated clients expose behavior a mocked benchmark cannot.
Acknowledgement deadlines, durable outcomes, late commits, duplicates, disconnects, and cleanup are measured as different signals.
Service loss, queued work, cold reconstruction, rolling change, and exact rollback are treated as workflows to exercise—not assumptions.
Routing, transaction shape, backup cadence, and resources are adjusted only when evidence identifies the limiting path, then compared again.
Current evidence boundary: this remains internal engineering evidence—not a public capacity, SLA, availability, recovery-time, production-sizing, or enterprise-readiness promise. Results will be promoted only after repeated trials and exact-wording review.
Outside the work
My wife and I live in Roswell, a community just north of Atlanta, with our three children. Atlanta has been the center of most of my career—from consulting and financial services to technology leadership—and it remains the place where I build, work, and raise my family.
Why Cinch
Cinch began with a product idea: team communication should give attention back instead of turning attention management into a second job.
It also became a way to test a broader engineering question: can one qualified operator use agentic assistants to build and run a credible, inspectable system without hiding behind vague claims about autonomy or productivity?
That is why this site exposes more than features. The release log, decisions, security posture, infrastructure, resilience limits, roadmap, and engineering economics are all part of the project—and all ultimately have a human owner.
Inspect the work