New PRO-dela: a client project from brief to invoice

We redesigned the design and positioning of PRO-dela around one specific job: managing a client project from the first request and brief to the result, documents, and invoice.

The main focus is owners and operations managers of small agencies, studios, and service project teams. Not because other teams are forbidden from using the system, but because the product needs a clear task: to maintain the connection between what was promised to the client, what the team is doing, and on what basis documents and invoices are issued.

Why we abandoned the idea of “another service for everyone”

In a universal description of any work management system, the same list quickly appears: projects, tasks, roles, comments, files, notifications, calendar, analytics, and AI. These features are important, but by themselves they do not explain why a team should change its usual set of tools.

Market research showed two things. The project management category exists, but broad search demand is heavily mixed with training, methodology, and government projects. At the same time, the market for universal task managers is already occupied by strong products with free tiers, integrations, and established trust.

Therefore, we narrowed the hypothesis. The most meaningful scenario for PRO-dela is client work, where the request, brief, stages, tasks, result, approval, documents, invoices, and expenses should remain parts of one project. We are now testing this focus with teams, not declaring it proven in advance.

A project falls apart not in tasks, but between them

Tasks usually do not disappear. The connection between them is lost. The client's request stays in messages, the brief in a file, the work on a board, expenses in a spreadsheet, and the invoice is prepared in a separate service. Before a meeting, the manager manually reassembles the project state.

The problem is not necessarily the number of tools. It arises in transitions: an agreement does not become a requirement, a requirement is not linked to a stage, the result is separated from the client's decision, and documents and money are separated from the completed work.

The new formula of PRO-dela: not a set of modules side by side, but a clear path of a single client project.

What this path looks like

1. Request. The team records the client's initial need and does not lose context.
2. Brief. The agreement turns into verifiable requirements.
3. Stages and tasks. Work gets assignees, deadlines, statuses, and a next step.
4. Result. The file, comment, and version stay next to the task.
5. Approval. The client's decision is saved in the project, not dissolved in correspondence.
6. Documents. The basis for an act or other document is linked to the completed stage.
7. Invoice and expenses. Financial context follows execution.
8. Overview. The manager sees where a client response is needed, which deadline is at risk, and what should be closed with documents.

PRO-dela does not claim to replace accounting, CRM, or every team tool. The task is narrower: to give participants a shared operational context of the client project and reduce manual restoration of connections between its parts.

What changed in the design

The previous presentation started with product features. The new one starts with the user's situation. The first screen immediately names the audience and the work: “Manage client projects from brief to invoice.”

Next, the page does not list modules but walks through one demo project. The same entities appear in different scenes and refer to each other: a requirement becomes a task, the result stays next to the decision, the act and invoice rely on the completed stage.

The visual system has become calmer and closer to a work tool: paper-gray background, white surfaces, dark text, one clear blue for actions and connections, and a warm accent only for truly important states. Large headings are set in Onest, body text in Golos Text.

What the new logo means

The mark is made of two layers and a checkmark. The layers are parts of one project: agreement, execution, result, and financial context. The checkmark means not “another closed task” but a verified transition from promise to done.

The logo works in the same logic as the interface: minimal decorative details, a clear outline, and one blue accent. The name PRO-dela remains the same — what changed is the way to explain what work the product should do for the team.

One project for different roles

A connected process does not mean the same screen for everyone. The owner monitors commitments, risks, and money. The project manager monitors stages, deadlines, and approvals. The team monitors their work and the next action. The client monitors clear progress and decision points.

The project structure remains common, and access is determined by role. This allows discussing the same result without parallel versions of state in different spreadsheets and chats.

Where AI and voice remain

AI and voice have not become the main promise of PRO-dela. They help prepare a draft faster: parse an incoming request, suggest a brief or task structure. The change is applied only after review and confirmation by a human.

For client work, this is an important boundary. Automation can remove mechanical transfer, but it should not make a project decision instead of a responsible participant.

Why we start with process analysis

Broad self-service is poorly suited to a task where each team already has its own stages, roles, approval points, and an accumulated set of tools. Therefore, the new entry scenario does not start with an empty space, but with one real client path.

1. We analyze how a client request currently passes through the team, documents, and finances.
2. We set up a project template: stages, roles, statuses, and approval points.
3. We launch the first project together with the team.
4. We compare the result with the pilot's goal and decide whether to continue.

The first analysis is free. The scope and cost of the paid pilot are determined after agreeing on the task. This format is not for artificially complicating entry, but to test value on real work before scaling.

Who should look at the new PRO-dela

• an agency or studio where several client projects run simultaneously;
• an operations manager who assembles status from chats, boards, files, and spreadsheets;
• a team that needs to connect brief, execution, approval, and financial context;
• a service business ready to start with one process and test it in a pilot.

If you only need a universal task list, there are already many mature solutions on the market. PRO-dela tests a different value: can a connected client delivery process make the project state clearer for the owner, manager, team, and client.

Show where your process falls apart today

Briefly describe one path: from an incoming request to the result and payment. In the first conversation, we will analyze the current transitions, show a suitable scenario in PRO-dela, and honestly say whether the product fits your team.

See the new PRO-dela and request a process analysis.