# How to run a client project card: scope, hours and documents

https://krokul.com/en/blog/project-card-scope-hour-package/ · Krokul Team · Updated 2026-11-13

Krokul CRM is a B2B CRM for contract-based companies: deals, projects and profit per client in one system, implemented by integration partners. A client project card holds what was sold, the hour package, the delivery tasks, the hours log and the margin of one client project in one place.

**Short answer.** To run a client project in Krokul, hand over the won deal to a project, check what was sold, and set the hour pool for the whole project or per month with a rate over the pool. Put delivery tasks on the project, log hours against it and read the margin by hours. Create the monthly act from billable hours.

## When does a client project need its own card?

A project needs its own card when delivery starts after the sale and several people spend hours on it, because the promise, the hours and the money have to be read side by side. The card is where the numbers of the topic of [client and project profitability](https://krokul.com/en/blog/topics/project-profitability/) come from, and the guide on [calculating client profitability](https://krokul.com/en/blog/calculate-client-profitability/) explains how to read them.

- The deal was signed, and the delivery team asks the sales manager what exactly was sold.
- A monthly support package is sold, and nobody knows on the 20th how many hours are left.
- Hours are written in one place, tasks in another, and the debt of the client in a third.
- At month end someone rebuilds the act from a spreadsheet of hours.

- **Project scope** — Project scope is the list of what the client bought, with the quantity of each item, taken from the signed contract.
- **Hour package** — An hour package is a number of hours sold for a fixed amount, for the whole project or for each month.
- **Margin by hours** — Margin by hours is the project amount minus the cost of the hours spent, where each hour costs the rate of the person who worked.

## How do you run the project card in six steps?

### 1. Hand over the won deal to a project

In the won deal, use the hand-over to a project. The project takes the client, the contact, the amount and a snapshot of the items from the signed contract. Without a contract it takes the accepted quote, and without both it takes the items of the deal. The owner is the person you name or the manager of the deal.

Krokul creates one living project per deal, and a second hand-over answers with the existing project. The new project starts as planned, and the deal feed records the hand-over. Move the project to in progress when work begins.

### 2. Check What was sold

The What was sold block shows the items and the quantities that the client signed. In a project handed over from a deal it is read-only, so delivery cannot quietly change the promise. In a project created without a deal, you keep the list yourself with Add row.

Check the project amount in the Project block next to it. For a support package, the amount is the price of the package.

### 3. Set the hour package

In the Hours block write the hours budget, choose the pool, either For the whole project or Per month, and for a monthly pool write the hourly rate over the pool. A monthly pool marks the project as a support package. Without a rate over the pool, extra hours are counted but have no amount.

When a monthly pool runs out, Krokul notifies the project owner once per month while the project is in progress.

![Project card of a demo company: the Hours block with 13.5 of 10 hours, pool settings, margin by hours and hours log](https://krokul.com/img/en/blog/project-card-hour-package-pool.webp)

### 4. Put the delivery tasks on the project

In the Tasks block press Create task, and the form opens with this project already chosen. The counter under the title reads open of total. Sales tasks stay in the deal, and the project holds delivery work: what to do, who and by when.

Closing a task asks for a short result. The result goes to the feed of the deal or the client of the task, and the next task can be set in the same window.

### 5. Log hours against the project

Press Log hours, enter the hours (above zero, up to 24) and the date, choose a task or a ticket of this project and add a note. Under the form Krokul shows the remainder or the overrun of the pool. An overrun does not block the entry, and the window stays open for the next one.

Engineers can also use the timer, which writes into the same log, as the guide on [tracking hours with a timer and reading the hours report](https://krokul.com/en/blog/track-hours-timer-report/) explains. Only an admin or a manager deletes a log row, and a row that already belongs to an act stays.

### 6. Read the margin and create the monthly act

Admins and managers see the cost of hours, the project amount and the margin by hours. Krokul counts cost as hours multiplied by the rate of each person on the date of the entry, and it leaves the cost of goods out. The card also shows what the client owes and how many tickets the project has.

At month end, an admin or a manager presses Create act and chooses the month. The act takes only billable hours. For a monthly package it carries one line for the package amount and, if the package is exceeded, the extra hours multiplied by the rate over the pool. The window shows the lines before anything is written, and Krokul allows one live act per project and month.

## What does an exceeded hour package look like?

The table follows the support package in the picture above, a package of 10 hours per month for £750 with a rate of £85 over the pool. It is an example from the demo data.

Example from the demo data: a monthly support package of 10 hours:

| Item | Value | How it is read |
|---|---|---|
| Package | 10 h per month, £750 | Budget and project amount |
| Hours spent this month | 13.5 h | From the hours log |
| Over the pool | 3.5 h | 13.5 − 10 |
| To invoice over the pool | £297.50 | 3.5 h × £85 |
| Cost of hours | £862 | Hours × the rate of each person |
| Margin by hours | −£112 | £750 − £862 |

The act for the month carries the package line of £750 and the extra hours line of £297.50, which makes £1,047.50 for the client. The margin by hours of −£112 compares the package amount with the cost of the hours, and shows whether the package was sold at a price the team can deliver. A package that is exceeded every month needs a larger budget or a higher price.

## Which mistakes weaken a project card?

- Creating the project by hand when a won deal exists. Hand it over from the deal, so the client, the amount and the scope arrive from the contract.
- Leaving the rate over the pool empty. Extra hours are then counted without an amount, and Krokul refuses to create the act until the rate is set.
- Logging hours without choosing the project’s task. The hour still counts toward the pool but the log loses its context.
- Creating the act before all hours of the month are logged. Hours logged after the act are marked with the act number and do not enter it, so cancel the act and create it again.
- Reading margin without rates. Set the company rate first, because the card warns that cost is incomplete when rates are missing.

## A month-end checklist for the project owner

- All hours of the month are logged, and sessions marked for review are corrected.
- Non-billable hours are marked as such.
- The pool and the rate over the pool match the contract.
- The act for the month is created and checked before it is sent.
- Cost of hours and over-pool hours are compared with the previous month.

## What links to the project card?

Four other places link to the card. The deal that it came from stays one click away (see [the deal card and kanban board](https://krokul.com/en/blog/deal-card-kanban-board/)), the client card shows the debt, the tickets screen holds the support requests of the project, and the guide on [prepaid support hours](https://krokul.com/en/blog/prepaid-support-hours/) explains how to sell the package in the first place. Open the page on [projects and hour packages in Krokul](https://krokul.com/en/solutions/projects/) to see the screens together.

Projects, hours and acts belong to a higher plan than the free one. The client and the deal that the first project comes from can be prepared first.

## Frequently asked questions

### Can one deal produce two projects?

No. Krokul keeps one living project per deal, and a second hand-over answers with the project that already exists.

### Does an hour package run out and block logging?

No. An overrun is shown under the form, and the entry is saved. The owner of a monthly package gets a notification once per month when the pool is used up.

### Who sees the margin of a project?

Admins and managers. A salesperson with the agent role works with the project and the hours but does not see money.

### Do non-billable hours go into the act?

No. The act takes only billable hours. Untick Billable on the entry in the hours screen.

### Can I create an act again for a month?

Only after the existing act is cancelled. Krokul allows one live act per project and month.

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs
