How a freelancer can manage multiple clients and their own product in PRO-dela

A freelancer manages each client as a separate project in PRO-dela while keeping their own affairs close: their product, learning, personal tasks. This solves the main challenge of solo work — not losing context between multiple orders when you are simultaneously a manager, executor, and accountant for yourself.

Below is an end-to-end scenario: how one person with multiple clients can build a lightweight but coherent process — from task setting to invoicing — without turning it into a heavy corporate system that only gets in the way.

Why a solo practitioner relies on memory

A freelancer has no team to remind them of agreements. Everything relies on their memory and a dozen tabs: a chat with one client, a folder with layouts for another, a spreadsheet with payments for a third. With two projects, it works. When there are five, confusion sets in: a revision for one client is sent to another, an invoice is issued based on a roughly remembered scope, and a promise from correspondence is forgotten.

PRO-dela helps a solo practitioner avoid building bureaucracy and instead regain context: where each client is, what needs to be done, what has been accepted, and what needs to be invoiced. Moreover, you don't have to implement the entire platform at once — you can start with tasks and gradually add the rest.

Step 1. Separate clients, don't lump them into one list

Each client or large order is created as a separate project. This immediately separates contexts: tasks, files, correspondence, and status of one client do not mix with others. Your own affairs — your product, experiments, personal tasks — can be managed as a separate project alongside.

If there are many areas and you want to separate them more strictly — for example, separate client work from your own product — companies help: each has its own projects, participants, and tariff. More details in the article "Companies and Tariffs".

Step 2. Lightweight structure: tasks, priorities, subtasks

Within a project, you don't need to build a complex hierarchy right away. To create a task, only the project and name are mandatory — the rest (description, deadline, priority) is added as needed. For solo work, there is usually one executor, so assignment can be kept simple.

A large order is broken down into subtasks — a clear list of steps within a task that can be completed in parts. A repeatable set of work (e.g., a standard process for a typical order) is saved as a template and expanded in a new project with one action, so you don't have to assemble the same thing manually. Priority helps separate urgent from important but does not rearrange cards on its own, so your manual order remains manageable.

The personal "My Tasks" list gathers work from all projects in one place with its own personal order — convenient when you need to plan your day across all clients. The full structure of tasks is in the article "Task Setting and Execution Control".

Step 3. Materials and agreements alongside work

Files and attachments are stored directly in the task they belong to, not in scattered folders. This reduces the risk of sending an outdated version of a layout to a client. The project's technical specification records the framework agreement: what we do, what counts as a result, what constraints exist — so that a month later you don't argue about "what was actually ordered."

It is convenient to keep work correspondence about a task in its chat: decisions remain tied to the task and do not dissolve into a general messenger. This way, even a solo practitioner gets a history they can return to.

Step 4. Involve the client only where needed

The client does not have to be immersed in all the details. You can start with an internal project and invite an external participant only when they really need access — to approve material, see status, or accept the result. The role determines what the client sees and can do.

Acceptance helps a solo practitioner protect themselves from endless revisions "within the same budget." The executor marks completion (finish), and the client as the acceptor either accepts the result (accept) or rejects it (decline) with a clear reason. "Done" and "accepted" become different states with a history, not a verbal "seems fine."

Step 5. Budget, expenses, and invoicing without accounting

For a solo practitioner, it is important not to forget to issue an invoice and not to lose track of expenses. An estimate of work — in hours or cost — can be recorded and, if needed, agreed with the client. Actual expenses and progress are collected in the project's budget statistics, so the volume of completed work does not have to be reconstructed from memory.

When the work is accepted, an invoice is generated based on it with line items and documents. PRO-dela does not replace a bank, tax accounting, or legally significant document flow — it is a way to link completed work to a financial event, not an accounting program. More details in the articles "Time and Expense Tracking" and "Project Budgets".

Step 6. Voice to capture thoughts on the go

A freelancer's ideas often come when not at the desk. Voice input helps quickly add a thought to a task, description, or technical specification without switching to the keyboard; the voice command goes through the path "recognize → show → confirm," so nothing changes unnoticed.

When PRO-dela is not needed for a freelancer

If you have a personal to-do list without projects, clients, documents, and payments, the platform will be excessive — a simple note will do faster. PRO-dela becomes useful when you have at least a few clients, agreements, materials, and invoices that are important not to lose.

It also will not replace a large CRM, a complex process builder, or full-fledged accounting. Its strength for solo work is to restore context and link an order to its result and payment.

Frequently asked questions

Will this be too heavy for one person?

No, if you start small. For work, you only need a project and tasks with names; descriptions, priorities, subtasks, budget, and invoices are added as needed. The platform does not require filling everything at once.

How not to confuse clients with each other?

Each client is a separate project with its own tasks, files, and correspondence. If you need to separate areas more strictly (e.g., clients and your own product), use different companies. The personal "My Tasks" list gathers work from all projects together.

Can I work without inviting the client?

Yes. First, run an internal project with tasks and materials. Invite the client only when they need access to approval, status, or acceptance of the result.

Will this replace accounting and contracts?

No. Invoices and documents in PRO-dela link completed work to a financial event within the project but are not a bank, tax accounting, or legally significant document flow.

Start with one order

Register in PRO-dela and create a project for a client you are already working with: transfer the nearest tasks, attach materials and agreements, and if necessary, add an estimate and invoice. For a solo practitioner, this is the fastest way to check whether a single circuit restores control over multiple orders.

Before starting, you can view current tariffs and the overview article "Who PRO-dela is for". Don't build a perfect system in advance — start with one live order.