Skip to content
ProjEase

How it works together

Four products that pass work on.

14 links exist between them today. Below is every one of them, what to look for in the product, and — where we could record it — the demo of that exact handover. Everything you see is sample data from the ProjEase demo sandbox.

How they work together

14 links between the products. Every one of them real.

We do not claim that everything talks to everything. These are the places where one product hands work to another today — each switched on only when you hold both products, and each one you can watch happen.

The HubCollozaPlagendaOrgEntityBookuracy

The map walks the links by itself. Choose one to hold it there and watch its demo.

The Hub Colloza

Each link is one listener or one shared read in the code. There is no general rules engine behind them. See the stories they add up to

The stories they add up to

Five days that usually take four tools and a spreadsheet.

Nobody spends Monday morning adding one person to five tools.

A new hire’s first day

One invitation puts a new person where they need to be in every product you hold.

The Hub counts what is waiting on you in each product

Sample data, recorded in the ProjEase demo sandbox · 5.9s · no sound
What happens in this demo

The Hub dashboard shows a card for Colloza, OrgEntity, Plagenda and Bookuracy, each with a count of what is waiting on you in it. Open OrgEntity is pressed and OrgEntity loads, already signed in.

The hours you worked are the hours you bill, without a spreadsheet in between.

From project to paid

A project, its tickets, the time tracked on them and the invoice that bills it, in one line.

The project has its own zone, made when the project was

Sample data, recorded in the ProjEase demo sandbox · 7.7s · no sound
What happens in this demo

The Zones screen lists a zone named after the project, Apex Mobile Banking, beside General and Random. Opening it shows the project team talking in it, and its header carries the project: the project’s name, its running sprint, and how many tickets are still open. Its member list is the project’s member list.

A receipt should be typed in once, by the person holding it.

An expense against a project

A claim made in OrgEntity ends up in the books and on the project it was for.

OrgEntity dashboard with its counters for approvals, onboarding and offboarding
Sample data, captured in the ProjEase demo sandbox.

The last day should not leave a login open or a ticket orphaned.

Someone’s leaving

Offboarding ends access in every product and passes open tickets to a named person.

OrgEntity dashboard with its counters for approvals, onboarding and offboarding
Sample data, captured in the ProjEase demo sandbox.

Ten minutes to know what needs you, across everything.

A manager’s morning

Counts in the Hub, decisions in OrgEntity, the sprint in Plagenda.

The Hub counts what is waiting on you in each product

Sample data, recorded in the ProjEase demo sandbox · 5.9s · no sound
What happens in this demo

The Hub dashboard shows a card for Colloza, OrgEntity, Plagenda and Bookuracy, each with a count of what is waiting on you in it. Open OrgEntity is pressed and OrgEntity loads, already signed in.

Set your company up this afternoon.

Sign-up asks for your company, the plan, and who to invite, then builds the account: first zones, first project, leave types, currency. You have 14 days before anything is charged.