Build client-facing apps and internal tools inside a branded business workspace
Assembly is a business platform with an AI app builder for professional-service firms and other teams that work with clients. Instead of publishing a separate application with its own accounts and hosting, a team builds inside an existing workspace that already has a CRM, client experience, messaging and payments. The result is intended for authenticated users, not for a public marketing website.
The builder follows a describe, plan, publish and iterate workflow. A user explains the required app in plain language, answers clarifying questions and reviews a plan before construction begins. Published apps can then be changed through further conversation. Assembly also supplies templates for recurring needs such as onboarding, document collection, time tracking, proposals and project tracking. A template provides a starting structure that can be adjusted to the firm's process.
Apps appear together within the client portal rather than as disconnected destinations. The platform handles sign-in and permissions, while the team's dashboard and each client's view serve different roles. This arrangement is useful when an internal process and a client-facing workflow need to use the same underlying information. The official site also describes connecting external services by authenticating the service or supplying an API key when the app requires one.
The free plan includes a small client allowance, one internal user and a limited number of apps and monthly build credits. Credits are used for creating or editing apps rather than normal use of an already published app. Paid tiers add capacity and capabilities such as API and MCP access, custom domains, automation and more advanced access controls. Running out of build credits does not, according to the pricing FAQ, stop existing apps from operating.
Assembly is most relevant when a firm wants several focused tools within one branded client relationship. It is less suited to a public directory or an anonymous consumer experience. Before publishing, teams should test permissions, client visibility and connected-service behavior using representative accounts, rather than judging an app only by its appearance.
