---
slug: "copilot"
title: "Assembly (formerly Copilot)"
language: "en"
canonicalUrl: "https://tools.utildesk.de/en/tools/copilot/"
category: "Business"
priceModel: "Freemium"
tags:
  - "client-portal"
  - "workflow"
  - "automation"
officialUrl: "https://assembly.com/platform"
---

# Assembly (formerly Copilot)

Assembly, formerly known as Copilot, is a platform for client portals and recurring service workflows. The distinction matters: this page is not about Microsoft Copilot or GitHub Copilot, but about Assembly's client portal product.

Its value appears when agencies, consultancies, law firms, bookkeeping firms, or service businesses need to organize many small client handoffs: files, forms, messages, invoices, status updates, and repeat onboarding steps.

## Who is Assembly for?

Assembly fits service businesses that no longer want to run client work through scattered emails, folders, and spreadsheets. It is especially useful for teams with recurring client processes that need a clear portal without building custom software from scratch.

It is less useful if the team only needs a simple task board or if clients should not log into a separate portal at all. In those cases, project management tools, CRM systems, or lightweight forms may be simpler.

<figure class="tool-editorial-figure">
  <img src="/images/tools/copilot-editorial.webp" alt="Illustration for Assembly: client portal with files, forms and service handoffs on a calm workspace" loading="lazy" decoding="async" />
</figure>

## Typical use cases

- build client portals for agencies, consultancies, and service businesses
- collect onboarding forms, tasks, and files in one place
- bundle invoices, contracts, messages, and status updates for clients
- structure recurring service packages or productized services
- embed external tools and automations in a client portal
- separate client communication from internal work management

## Strengths

- clear focus on client portals rather than generic project management
- useful for recurring client processes with many handoffs
- can combine automations, forms, files, and billing-related workflows
- often faster for small service businesses than custom development
- reduces scattered communication when roles and rules are defined

## Limitations

- easy to confuse with Microsoft Copilot or GitHub Copilot by name
- value depends on whether clients actually use the portal
- often not the right fit for internal product teams or pure developer workflows
- sensitive client data requires checks around roles, storage, and export
- portal software does not fix an unclear process; it only makes it visible

## Workflow fit

Before adopting Assembly, test one real client workflow: onboarding, recurring monthly documents, or a service package with fixed steps. The key question is whether clients ask fewer follow-up questions, whether the team can approve work faster, and whether information remains easier to find later.

A good pilot has a clear stop condition. If the portal becomes just another place next to email, chat, and project boards, the workflow is not ready yet.

## Privacy and data

Assembly can involve client data, files, messages, contracts, and payment-related information. Before production use, check responsibilities, export paths, roles, retention, deletion, and data processing terms. For sensitive client data, start with a narrow pilot and explicit permissions.

## Pricing & costs

Assembly uses a freemium or subscription-style model. The real cost is not only the license: setup time, client roles, integrations, automations, and ongoing maintenance of portal templates also matter.

**Provider:** https://assembly.com/platform

## Alternatives to Assembly

- [Moxo](/en/tools/moxo/): useful when secure client communication and digital workflows are central.
- [HoneyBook](/en/tools/honeybook/): useful for proposals, invoices, and client management in creative services.
- [Monday.com](/en/tools/monday-com/): better when internal project management matters more than a client portal.
- [ClickUp](/en/tools/clickup/): useful when tasks, docs, and team collaboration should live in a broader work platform.

## Editorial assessment

Assembly is interesting when client communication, files, and recurring service steps are too scattered today. The right test is not a demo portal, but one real client case with clear roles: the client provides material, the team reviews it, and an outcome is approved. If that workflow becomes measurably calmer, Assembly has a place.

## FAQ

**Is Assembly the same as Microsoft Copilot?**

No. This page covers Assembly, formerly Copilot, a client portal platform. Microsoft Copilot and GitHub Copilot are separate AI assistants for different use cases.

**When is Assembly worth it?**

When service businesses have recurring client processes that are currently spread across email, folders, forms, and manual follow-ups.

**What should be checked before adoption?**

Check roles, privacy, export, client adoption, integrations, and whether a real process becomes easier through the portal.

**What is the most common mistake?**

The most common mistake is introducing a portal before the client process is clear. Then it becomes just another place everyone has to maintain.