Building the product is only part of the work
Artur Sabirov2 min readRevised September 7, 2026. Product details reflect this revision.
Imagine a small team launching a second product. The team knows how to build it. What takes time is setting up the services around it: somewhere to deploy, somewhere to store data, a domain, and a way to collect the first signups.
The first product already has those things. But its accounts, settings, and access decisions do not automatically answer what the second product needs.
That repeated setup is the problem we want Lessly to solve. A team should be able to launch another product without assembling its operating tools from scratch each time.
What repeats after the code is written
Take a simple example: a new app needs a waitlist before its public launch. The team has to put the site online, connect its domain, collect email addresses, and decide how invitations will work. Someone also needs to know where those records live and who can access them.
Each task is manageable. The work grows when the tasks belong to separate services with separate accounts. A new teammate needs access to the relevant ones. When that teammate leaves, somebody needs to check them all again.
The repeated work is knowing which service owns each part of the product and keeping the connections working.
What one account changes
Lessly brings deployment, managed Postgres, domains, and tools such as the waitlist into one platform. Each product has its own resources and access. People and agents can work through the console, API, MCP, or CLI.
For the example above, the team can deploy the site and manage its waitlist in the same account. It still has to choose the domain and decide who to invite. Those decisions remain product work; opening and coordinating a separate account for each service need not be.
Access control supports that arrangement. A team can grant access to a product, choose the allowed operations, and revoke the access later. It is part of running the bundle, not the whole reason to use it.
What the team still owns
A shared platform does not decide how your application should behave. You still write the application, check releases, and decide what data it should collect. You may also need services outside Lessly, with their own setup and permissions.
The useful test is a real launch: list what the product needs, check which parts Lessly provides, and identify the work that remains. That is more informative than counting how many tools fit into one account.
Lessly is available through the private-beta waitlist. Self-serve signup and billing are not available yet. The beta is where we can test whether bringing these tools together actually reduces the work of launching the next product.
Related posts
Building Lessly in the open
Follow along, and get early access to the private beta.