Signals from Private Early Access
Butler is still in invite-only early access. We have not opened the product to everyone, and access remains limited to people who request an invitation or are invited to try it.
In its first month, Butler has received more than 1,200 access requests, reached 9 paying customers and attracted an enquiry from a business interested in enterprise access for its team.
For an early-stage product, these are useful signals. They do not establish product-market fit, and we are not treating them as proof that we have found a repeatable growth model. They give us something more practical to work with: people expressing interest, customers willing to pay and a business asking how Butler could work for its team.
Here is what we're learning as we build Butler at Sevorse.
The First Month of Butler Early Access
We deliberately began with a limited rollout rather than opening Butler to everyone at once.
An AI product can look promising in a demonstration and still fall short when people try to use it for real work. Early access gives us an opportunity to see where the product delivers value, where it creates friction and what needs to improve before we expand availability.
The initial numbers are encouraging:
- 1,200+ access requests: People have expressed interest in getting access to Butler.
- 9 paying customers: A first group of customers has chosen to pay for the product.
- 1 enterprise enquiry: A business has approached us about access for its team.
These numbers describe different things. Access requests indicate interest, paying customers indicate an initial willingness to spend, and the enterprise enquiry gives us an opportunity to explore a potential business use case.
We believe each signal is worth understanding on its own.
What 1,200+ Access Requests Tell Us
For a product available through invite-only early access, receiving more than 1,200 requests in its first month gives us a reason to keep investigating demand.
But an access request is not the same as an active user.
The next questions matter more: How many people who receive access actually try Butler? Which capabilities do they use? Do they return? What problems are they trying to solve, and would they continue paying to solve them?
Those are the questions we need to answer as the product develops.
We don't want to optimise Butler around a large waiting list if the people on it cannot find lasting value in the product. Our goal is to turn interest into useful product experiences and, ultimately, sustained adoption.
Nine Paying Customers: An Early Commercial Signal
Butler has also reached nine paying customers during this early stage.
We see that as an initial commercial signal, not a final verdict on the business. A small number of paying customers cannot tell us whether demand will scale, whether customers will stay or whether the economics will work over time.
Those questions require continued testing.
We need to understand which capabilities customers value, what makes them willing to pay, how frequently they use the product and what would persuade them to continue.
That learning will influence our product priorities, pricing decisions and the modules we develop next.
For us, the objective is not to convert as many people as possible once. It is to build something useful enough that customers have a reason to keep coming back.
An Enterprise Enquiry Changes the Questions We Ask
During the same period, a business approached us about enterprise access for its team.
This is an enquiry, not a signed enterprise contract. We have not yet established whether it will convert into a customer.
Even so, the conversation opens up a different set of questions from those we face with individual users.
A business evaluating an AI agent may need to understand how the product fits into its existing workflows, which capabilities its team needs, how access should be managed and what level of reliability it can expect.
Those requirements can influence both product design and commercial packaging.
We're interested in understanding the business's actual needs before assuming that one request represents a broader enterprise market. If the use case is a good fit, the conversation can help us identify what Butler needs to support teams more effectively.
Why This Matters for Butler's Modular Approach
Butler is being built as a modular AI agent. The idea is to let users access specialised AI capabilities according to their needs rather than requiring everyone to use the same collection of features.
The early-access phase gives us an opportunity to test whether that approach works in practice.
Different users may come to Butler for different reasons. Some may need a specific capability; others may be interested in how multiple capabilities could support a wider workflow.
We need to learn which use cases matter most and whether users see enough value to pay for them.
The enterprise enquiry is particularly useful as a conversation to explore because a team may have requirements that differ from those of an individual user. We want those requirements to inform our decisions, rather than building features simply because they sound appealing.
Our broader goal remains the same: build specialised modules that solve real problems and bring them together within a common platform.
What We're Focused on Next
The next stage is about moving beyond initial interest and understanding actual product value.
That means improving onboarding, studying how users interact with Butler, learning what drives paid conversion and listening closely to feedback. It also means tracking retention and repeat usage as more customers spend time with the product.
We will continue exploring business requirements as well, including the needs raised through enterprise conversations.
Not every assumption will hold up. Some capabilities may need to change, and some use cases may prove less valuable than we expected. We would rather learn that early than build an increasingly complicated product around the wrong priorities.
An Early Milestone, Not the Finish Line
The first month has given us three concrete signals: more than 1,200 access requests, nine paying customers and an enterprise enquiry.
We are encouraged by the interest, but we know what remains to be proven. We need to turn requests into active usage, early payments into sustained customer value and business conversations into a clearer understanding of what organisations need.
That is the work ahead.
We're building Butler in public where we can, learning from the people who want to use it and improving the product one step at a time.