I'm a developer who works with startups, and I keep seeing teams spend months building UIs for workflows that could be described in a single sentence.
Now that AI assistants are becoming part of people's daily workflows, I wanted to test an idea:
For a lot of SaaS products, could the agent become the interface, while the actual product is just the data and the rules?
I decided to test this with something familiar: forms.
I built an experiment called Relay, a form builder that doesn't have a traditional dashboard. Instead, you interact with it through Claude, ChatGPT, or any MCP-compatible client.
You can create a form in one sentence, share a link, and later ask questions like "How's it going?"
A few things I learned along the way:
1. Natural language can replace surprisingly many settings pages.
Things like "close after 50 responses" or "close Friday at 6 PM" don't necessarily need dedicated UI controls. They're simple instructions that an agent can translate into structured settings.
2. Keeping AI off the server was one of the best architectural decisions.
Relay never calls an AI model itself. The MCP client handles the intelligence, while the server handles data and business logic.
This means no model API costs, simpler infrastructure, and no AI-generated statistics. Numbers come directly from database queries.
3. Business rules still need to live in the product.
For example, Relay won't allow edits that could change the meaning of answers people have already submitted.
You can't rely on prompting an agent to enforce important data integrity constraints. Those need to be enforced at the application level.
4. Authentication turned out to be harder than building the core product.
Getting OAuth working consistently across different AI clients took considerably more effort than I expected.
5. Removing the dashboard doesn't remove onboarding problems. It changes them.
Without a traditional login interface, the account key generated during signup effectively becomes your login credential. Losing it currently means losing access, so I'm working on a recovery mechanism.
The project is open source, so the implementation is available for anyone interested in exploring this architecture.
I'm curious about something:
If you were redesigning an existing SaaS product around AI agents, which parts would you remove from the UI entirely, and which would you insist on keeping?
I'd be particularly interested in hearing from people who've actually built and shipped SaaS products.