Show You the Future: Why Kindling Has an Applied AI Lab
AI is moving too quickly for adoption to be a one-time strategy project. Kindling tests the frontier, translates what works into team workflows, and installs the rituals that make those workflows last.
By Dan McCool, Founder, Kindling
The future does not arrive as a software license. It arrives when a team learns to work differently.
The frontier is moving faster than the organization
New models, agent frameworks, coding workflows, plugins, automation tools, and applied patterns are appearing faster than most companies can evaluate them. The operating cadence of a normal organization was not built for this tempo. Annual planning, quarterly roadmaps, and vendor rollouts cannot keep up with workflows that change weekly.
The problem is not access to tools
Most teams already have access to ChatGPT, Claude, Copilot, Cursor, and a growing stack of AI vendors. Access does not create behavior change. A login does not tell a sales manager what research should happen before a call, a product leader how to compound customer interviews, or an engineering team when an agent should draft code versus when a human should slow down and decide.
What an Applied AI Lab does
The lab part of Kindling exists to absorb volatility. We test new capabilities constantly, build prototypes against real work, discard fragile patterns, and turn durable ones into tools, workflows, playbooks, and rituals. The point is not to chase novelty. The point is to know what is ready to matter inside a company.
The lab has to be connected to real work
A lab detached from operations becomes theater. A consulting team without a lab falls behind. The useful middle is applied: test at the frontier, then install what survives inside the systems, roles, meetings, data, and constraints of the business.
Product, process, culture
AI adoption sticks when three things change together. Product: there is a real artifact, automation, prototype, or internal system that makes the work different. Process: the workflow is adapted to the team’s cadence and responsibilities. Culture: people learn the new behavior through pairing, review, coaching, and repeated use on actual work.
How Kindling works
We embed with teams, build specific projects with them, bring along internal champions, and adapt our toolkit to the business instead of forcing a generic AI playbook onto a specific company. The goal is not a workshop high. The goal is a team that can keep using the tool, improving the workflow, and teaching the behavior after we leave.
If your company cannot afford to chase every AI change, do not. Work with a team that lives at the frontier and knows how to bring back what matters.