Ops-led no-code ML automation
Thilo Huellmann, CTO of Levity, on using no-code AI for workflow automation
Levity is selling into a budgeting gap inside companies, not just a tooling gap. Internal ML teams usually spend their limited time on projects tied directly to revenue or gross margin, like pricing or ranking, while messy inbox, PDF, and image workflows stay manual. Levity wins by letting an operations lead import past examples, train a classifier, and wire the result into Gmail, Drive, CRMs, or Zapier without waiting on a data scientist.
-
This is the long tail of automation. Levity focuses on teams at companies with roughly 100 to 1,000 employees that already automate clean, rules based work, but still handle unstructured data by hand. The pain shows up when a task eats 10 to 20% of several employees’ time and headcount scales linearly with volume.
-
The real substitute is usually not an internal ML platform, it is a person plus spreadsheets and email. Levity is built so the process owner can upload historical emails, PDFs, or images, label examples, hit train, then route predictions into downstream tools. That removes the slow ticket queue between an ops team and a specialized ML team.
-
This sits between Zapier and enterprise platforms like Workato. Zapier is strong when apps can already talk through triggers and actions, Workato sells broader integration to IT and large enterprises, and Paragon helps software companies build native integrations. Levity's wedge is the decision step, turning messy text and documents into a usable signal before the workflow runs.
The category is moving toward software that owns both the judgment step and the action step. As more workflow products add native AI, the durable advantage will be making custom models easy enough for an ops manager to deploy in one sitting, then embedding those outputs directly into the systems where work already happens.