The business OS · Delivery & billing

Ship the work.
Chase the bugs. Bill the hours.

A delivery system with a real issue tracker inside it — one that will not take a bug report without steps, expected and actual — and timesheets that carry the rate they were logged at all the way to the invoice.

One module, 3 products. Sold separately almost everywhere else as project management, an issue tracker and time & billing.

Walk one issue through the five parts the tracker records

WMS-142Stock transfer saves against the wrong location WAREHOUSE MANAGEMENT SYSTEM · REPORTED 2 AUG

The actual product

What the delivery desk opens on.

Which projects are moving, what has already slipped past its date, and where the team's hours actually went last month — before anybody assembles a status report.

Ragenaizer Projects — project pipeline by status, overdue tasks needing attention, and hours logged per project
Delivery — the project pipeline, what is overdue, and where the hours went.
Hours to invoice

The part most tools stop just short of.

Plenty of tools will track time. Fewer will carry it to a bill without a spreadsheet in the middle — and fewer still get the rate right when somebody's rate changed in March.

Mon
Time logged against the task, in hours and minutesTime entry
rate snapshotted
Fri
Week submitted as one timesheet rather than forty entriesTimesheet
1 submission
Mon
Reviewed and approved from a pending queue, not an inboxApproval
named approver
Mon
Billable amount computed at the rate in force when the work was doneBilling
not today's rate
Tue
Invoiced against the same client record finance already holdsProjects → Accounts
0 re-keying
logged once, billed once0 spreadsheets in between
What it covers

Client, project, task, issue, hour.

One hierarchy the whole delivery side hangs off, so a question about a client and a question about a bug are answered from the same place.

Clients & projectsClients with several contacts, projects beneath them and sub-projects beneath those — one level of nesting, deliberately, because two is where structure becomes admin.
Issue trackerBugs, features, tasks and regressions with their own numbered key per project, severity, priority, component, environment and reproducibility.
Issue boardA board grouped by state, a personal "my issues" view, and bulk update for the afternoon somebody triages forty of them at once.
Threaded commentsReplies nest, so a long argument about one line of a bug does not flatten into a wall nobody can follow six weeks later.
AttachmentsScreenshots and logs on the issue and on individual comments — because "it looks like this" is usually faster than describing it.
WatchersFollow an issue without owning it, so the person who reported it and the person who cares about it both hear when it moves.
Issue historyEvery status change, reassignment and edit kept, so "when did this become critical, and who said so" has an answer.
Time trackingHours and minutes against a task or a project, entered daily or in one bulk pass at the end of the week when nobody did it daily.
Weekly timesheetsA week submitted as one thing, reviewed from a pending queue, approved or sent back. Chasing timesheets stops being somebody's Monday.
Billing ratesA rate per member per project, snapshotted onto each entry as it is logged — so changing somebody's rate never rewrites what you already billed.
Project roomsEach project gets a meeting room in the same platform, so the stand-up is not a link somebody pastes into chat every morning.
Tags & activityLabels across projects, tasks and issues, and an activity feed of what actually changed rather than what somebody remembered to announce.
Straight answers

The things people ask on the first call.

01

Is the issue tracker a real one?

Yes. Numbered keys per project, issue types, severity, priority, component, environment, reproducibility, resolutions, duplicate linking, threaded comments, attachments, watchers and full history.

And the three fields that make a report useful — steps, expected and actual — are required, not optional boxes somebody skips at five to six.

02

Do we need a separate bug tracker?

That is the point of it being here. Delivery teams usually run a project tool and a bug tracker and reconcile them by hand; an issue and the task it came from sit in the same hierarchy under the same client.

03

How is average resolution time worked out?

From timestamps the system records itself — first response, resolved, closed — not from anyone remembering to start and stop a clock. The same stamps give you the breakdowns by severity, priority, component and resolution.

04

What if somebody's rate changes mid-project?

The rate is captured onto each time entry as it is logged. Change a rate today and everything already billed stays as it was billed — a retroactive change cannot quietly rewrite last quarter's revenue.

05

How do timesheets get approved?

A week is submitted as a single timesheet and lands in a pending queue for review, where it is approved or sent back. It is not an email thread, and it is not forty separate entries somebody ticks off.

06

Can we bill from it?

Approved hours carry their snapshotted rate into a billable amount, and the invoice is raised in Accounts against the same client record — not a lookalike somebody created with a slightly different spelling.

07

How deep does the structure go?

Client, project, sub-project — and no further, on purpose. One level of nesting covers how delivery work is actually organised; two is where a structure starts costing more to maintain than it explains.

08

Who can see what?

Project membership decides it. Members see and log against their projects; administrators see across them. Creating an issue requires being on the project, so the tracker does not fill up with reports from people with no context.

One hierarchy, from the client to the hour.

Stop reconciling a project tool, a bug tracker and a timesheet spreadsheet that all disagree.

This is one module of the business OS, not a point tool. Projects on its own does what is usually sold as three: project management, an issue tracker, and time and billing. The same seat opens Meetings, Mail, Chat, Drive, CRM, HR, Accounts, Projects, Procurement, Learning and Research — eleven modules covering about twenty-eight products' worth, on one login, one permission model and one ledger. You are not buying a project tool; you are putting the company on one system.

See pricing Book a walkthrough →