How to calculate average revenue per hour based on a project's accepted proposals?

On Jestor's hourly project management dashboard, the "average revenue per hour" indicator is automatically calculated using only proposals that have already been accepted, cross-referencing the sale's value with the hours sold in each one.

Why look only at accepted proposals for this calculation?

Mixing proposals still under negotiation with ones already closed would skew the average — after all, a value that hasn't been confirmed yet could still change or fall through entirely. Calculating the average only over what's already been accepted gives a real picture of how much the company is actually earning per hour worked.

How does this indicator show up on Jestor's dashboard?

Every project has contracted hours and an hourly rate defined in the proposal.
Once the proposal is accepted, that data feeds the projected and current revenue calculations.
The average revenue-per-hour indicator cross-references the value of accepted proposals with the hours sold.
The same dashboard shows how many projects are at each stage — proposal, execution, delivered — to give context to that number.

Indicator	Calculation basis
Current revenue	Projects with an accepted proposal
Projected revenue	Projects still at proposal stage
Average revenue per hour	Value of accepted proposals divided by hours sold

Why choose Jestor?

This indicator is generated automatically from the same table used to manage projects and time activities, with no external spreadsheet needed to consolidate how much revenue each client is bringing per hour in Jestor.

Frequently Asked Questions

Does the calculation account for canceled projects? No, the indicator focuses on accepted proposals, which generate current revenue.

Can I see this average for a specific client? Yes, the dashboard lets you filter the indicators by client or by the responsible salesperson.

Is this indicator updated in real time? Yes, it reflects the data as soon as a proposal changes status on the project Kanban.

Reference video

Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all without code and with AI support.

Get to know Jestor at jestor.com and discover how to take your company's management to a new level of efficiency and integration.

How to build an automation roadmap for your company

A good automation roadmap doesn't start by automating everything at once — it starts with a simple starter template, validated with the team, and expands process by process inside a structured BPMS. That's how Jestor recommends starting any implementation. How Do You Build an Automation Roadmap Step

Common mistakes when automating internal processes and how to avoid them

Among the most frequent mistakes automating processes, you'll find automating a poorly mapped process, granting overly broad access to sensitive data, and editing a live workflow without testing it first. Jestor's BPMS, Security, and App Versioning help you avoid exactly these three mistakes. What Are the

How to measure the ROI of a process automation project

Measuring the ROI of process automation requires comparing the tool's cost against the time it saves and the errors it prevents — not just looking at the monthly fee. Jestor's dashboard helps turn this into concrete numbers, comparing before and after automation. How Do You Calculate the

How to identify priority processes to automate first

Priority processes to automate are usually the ones consuming the most team time, generating the most errors, and most affecting the end customer when they go wrong — in that order. Jestor's dashboard and BPMS help you see these three criteria with data, not guesswork. How Do You Prioritize