From ITSM Consultant to Founder

I started my career implementing and consulting on enterprise workflow systems: incident management, asset tracking, approvals, onboarding, service catalogs, and ITSM operations.

ServiceNow is powerful, and working with it taught me how serious companies think about process, governance, audit trails, and operational reliability. The discipline it enforces — structured states, defined transitions, clear ownership, traceable records — is the right discipline. Large enterprises need that level of rigor, and ServiceNow delivers it.

But it also made something clear. Many companies need those same principles without the cost, the complexity, and the specialist dependency that often come with enterprise platforms. Every mid-sized company I worked with had real workflow problems — processes that lived in email chains, approvals that happened over Slack, audit trails that existed only in someone's memory. They knew they needed structure. They couldn't afford the implementation.

AI changes that equation

With the right guardrails, business users and technical teams should be able to describe, generate, and evolve workflows without needing months of specialist configuration. The platform should handle structure, permissions, auditability, integrations, and process logic underneath. The model handles the translation.

That is not hypothetical. The pieces exist. What is missing is a platform built from the ground up with that model in mind — not an enterprise system with AI bolted on top, and not a chatbot with no process infrastructure underneath.

Why Flowlakes

Flowlakes is my attempt to close that gap. It is a service-management and workflow platform designed for companies that need the discipline of enterprise workflow without the enterprise implementation model.

The foundation is the same regardless of what an AI layer does on top: forms, tables, defined workflows, permissions, audit trails, integrations. When an AI agent participates in a process inside Flowlakes, it is not generating free-form output. It is moving a record through a defined workflow, with the same constraints a human user would have, with every action logged.

That combination — governed process infrastructure plus AI that can act inside it — is what I am building. I will document it here as I go.

If you want to follow along, start with Why AI Agents Need Business Process Infrastructure.