Zylon builds AI tools for SMB employees who have no interest in prompt engineering – betting that usability, not capability, wins the enterprise market.
ENTRY ANGLES
Just-in-Time UI that dynamically constructs interfaces based on user context and task · Adaptive interfaces with clarifying questions and real-time UI adjustment · Simplified interface design for AI platforms to reduce prompt engineering friction
VERTICALS
CAPABILITIES
Adaptive UI/UX design and implementation, Context-aware interface generation, User intent prediction and clarification systems
ZYLON FOUNDER
“We focus on the audience that most AI product builders forget about,”
Most AI tools are designed by technical people for technical people. Zylon is working on the other problem: making AI actually usable by SMB employees who have no interest in prompt engineering.
"We focus on the audience that most AI product builders forget about," says one of the co-founders. "People without technical skills – which is the overwhelming majority of SMB employees."
The platform's first major enterprise feature is data privacy. The underlying AI engine can be deployed locally on a company's own servers, which prevents business data from being transmitted to LLM providers for model training – eliminating the risk of confidential information surfacing in responses to other users.
This is technically possible because Zylon is built on PrivateGPT, an open-source package. The core contributors to PrivateGPT are the same people who founded Zylon.
The platform is built multi-user from the ground up: employees can work on tasks together alongside the AI, and can see how colleagues are using it – accelerating internal adoption through peer learning.
Zylon describes its platform as being "for everyone" – meaning simple enough for people with no technical background to use without training.
Founded in 2023, currently in beta, the startup has raised $3.2 million.
The most interesting thing here isn't the product – it's the thinking behind why the founders believe Zylon can actually be used by everyone.
Their core argument, laid out in their blog: "AI shouldn't feel like magic." Because magic is unpredictable.
Users click a "magic button," hope the AI does exactly what they need, and when it doesn't, they click again or start experimenting with prompts – with results that are equally unpredictable.
AI platforms built around magic buttons try to guess what the user wants. A better-designed platform lets the user state what they want directly – without lengthy explanation or prompt engineering.
When anyone can ask the AI anything, results can be anything. That includes outputs that are incomplete, hallucinated, or simply wrong. And when magic buttons assume a single-step path to a result, nobody thinks to break the task into guided steps where the AI moves toward the answer incrementally, with the user steering at each checkpoint.
If information is missing or the AI can't make a reliable inference, it should say so. That's almost always better than the AI speculating and producing a confident-sounding answer built on nothing.
Chat is the dominant interface paradigm for AI right now – but it's not the best one for non-technical users, who may not know how to phrase their requests in ways that yield useful responses.
Counterintuitively, a traditional interface – input fields, dropdowns, buttons – can be a more reliable way to communicate clearly with an AI and get consistent results.
A blank text box is a blank canvas. Blank canvases are paralyzing. "Blank page syndrome" exists for a reason.
The right interface follows a Job To Be Done logic. Users should immediately see where to go and what to click when they need to accomplish a specific task.
Zylon's interface is built to remove the magic from AI interaction. At the top level, it's composed of cards – each one purpose-built for a specific task. Inside each card, there's no chat. Just controls. The user specifies what they need without becoming a prompt engineer, and gets a predictable result.
Zylon's reasoning calls to mind a presentation by Amjad Masad, founder of Replit, in which he argued that "Just-in-Time UI" – interfaces that construct themselves dynamically based on what the user is trying to do – is inevitable.
The pattern has historical precedent. When personal computers were only used by technical people, command-line interfaces were sufficient. As the audience expanded, windowed GUIs (Mac OS, Windows) emerged. But as software grew more powerful, those GUIs became cluttered and overwhelming.
Right before ChatGPT launched, there was a wave of enthusiasm for "text as the universal interface." ChatGPT validated some of that – but also exposed the problem: writing effective prompts is its own skill set, one that has even started to become a profession.
Now some AI platforms are experimenting with adaptive interfaces – asking clarifying questions, surfacing relevant controls based on context, adjusting the UI in real time to match the task at hand. That's the JIT UI: an interface the platform generates on the fly, tuned to what the user is doing right now.
These are early experiments, and the verdict on user adoption is still out. But the directional opportunity is visible.
Interface design matters enormously. Dropbox became massive not because cloud file storage was a new idea – there were plenty of alternatives – but because its interface was so much simpler. The iPhone wasn't revolutionary because of screen size; it was revolutionary because of an interface you could navigate with a single finger.
Zylon is applying that same logic to AI for SMBs. But the potential is broader.
The opportunity: build "Dropboxes" for specific AI use cases – cleaner, more intuitive interfaces that let non-technical users get reliable results without touching a prompt. All the underlying technology already exists. The work is choosing the right use case and wrapping it in an interface that actually fits the user. What's your use case? What tools would you use? What would the interface look like?