Forgotten work becomes billable revenue again.

forgotten advisory work

Accountancy

For offices that want month-end control without asking everyone to reconstruct small advisory moments.

Live: Clients, projects, rates and accounting links To build: Ledger suggestions per activity and service line

Live: Submitted hours instead of raw activity history To build: Matter-specific confidentiality profiles

Legal and advisory

small billable moments

For professionals where trust, client context and small billable moments all stay intact.

field hours after the workday

Construction

For project teams with mobile registration, budget visibility and approval before invoices go out.

Live: Mobile and desktop registration in one approval flow To build: Photo, location and extra-work capture for field teams

Live: Mobile hours close to the work To build: Work-order import and service appointment context

Installation and field service

unapproved crew time

For installation teams that want less admin after jobs and a cleaner handoff to invoicing.

Live: Mobile time registration for field and office teams To build: Field, crop, machine and season settings per activity

Agriculture and agri service

seasonal field work

For growers, contractors and agri service teams where work changes by field, season, machine and weather window.

unwritten advisory time

Consultancy and advisory

For advisory teams where billable value is spread across meetings, decks, research, follow-up and internal alignment.

Live: Customer, project, activity and rate context on every submitted hour To build: Retainer drawdown, change requests and write-off reasons per engagement

Live: Suggestions can become customer, project and activity hours after review To build: Campaign, channel and content-type settings per activity

Marketing and creative agencies

unbilled revision work

For agencies where client work moves between campaigns, content, design, calls and revisions before anyone writes the time down.

revision and meeting time

Engineering and architecture

For engineering and architecture teams where project value moves through drawings, meetings, calculations, field checks and corrections.

Live: Projects, customers, rates and approval keep technical work invoice-ready To build: Project phase, drawing number and revision status per hour

Live: Forgotten client context returns from the day To build: Retainer, fixed-price and mixed-rate project modes

Freelancers and small agencies

unbilled client work

For solo professionals and small teams that want invoices to reflect the real work without heavy administration.

Software and agents

Half5 connects activity, context and finance without exposing private timelines.

That makes the rollout clear for standard accounting packages, custom industry software and agents: they work from approved business output, not someone's full day.

See integrations

Discuss a custom link

Accounting systems

Approved invoice data can move to Moneybird, WeFact, Exact Online and e-Boekhouden, with more systems discussed on request.

CRM, projects and planning

The customer, project and budget structure that already runs the business becomes the place where hours land.

Agents and internal tools

AI agents and middleware can use suggestions, submitted hours, approvals and invoice data, not raw private timelines.

Start without a migration project

Half5 fits around the way your team already sells time.

A better time platform does not start with a giant migration. It starts where billable work disappears today, then proves the first team can recover value without giving up trust.

Excel, notes or memory

Stop rebuilding the week after the work is already gone.

Current situation: Hours depend on reminders, loose notes and Friday-afternoon reconstruction.
First Half5 step: Start with one billable team, customers, projects and private timeline suggestions.
Proof to decide: Recovered minutes, submitted hours and invoice-ready value show whether the switch pays back.

Manual time tracking tool

Keep the structure, remove the memory work.

Current situation: People can register hours, but still need to remember the client, project and activity later.
First Half5 step: Add personal suggestions before users submit anything to managers or finance.
Proof to decide: The team sees fewer gaps, cleaner approvals and less pressure before invoicing.

Accounting package first

Let accounting receive better hours instead of more manual corrections.

Current situation: Invoices are possible, but approved customer, project and rate context still arrives too late.
First Half5 step: Connect Moneybird, WeFact, Exact Online or e-Boekhouden after the approval layer.
Proof to decide: Finance receives approved lines with context instead of exported doubt.

Enterprise rollout

Prove adoption, privacy and revenue before making it company-wide.

Current situation: The risk is not buying software; the risk is rolling out a tool users do not trust.
First Half5 step: Choose one branch, user group, permission model and first integration route.
Proof to decide: A 30-day pilot makes recovered revenue, approval rhythm and privacy boundaries visible.

Start small, sell the result internally

The first rollout can be one branch, one team and one integration route. The outcome is a clear decision: keep scaling, adjust the route or stop before a broad rollout.

Plan a rollout demo

Open price case Operations

Routes by role

Every role gets a clear reason to move forward.

Finance sees the return, users see the privacy boundary, operations sees the first rollout and IT sees which approved data may move to systems and agents.

Finance

Does recovered revenue beat the subscription?

Use team size, hourly rate, missed minutes and price per user to judge the business case before rollout.

Which team should start first?

Pick the branch, workflow and first approval rhythm where missed work becomes visible fastest.

Choose branch Users

Who can see the raw timeline?

Only the user sees personal activity. The company receives submitted hours, approvals and invoice-ready output.

See privacy flow IT and systems

Which data can software and agents use?

Accounting, CRM, planning tools and agents connect to approved data, not private raw timelines.

View data routes

Fast qualification

The first rollout becomes concrete in four choices.

The team starts with a branch route, user volume, software destination and measurable pilot instead of another generic time-tracking rollout.

Plan rollout call

Calculate recovered revenue

01

Select branch

IT, accountancy, legal, construction, agriculture, field service or agency.
02

Set user volume

Calculate monthly price, discount and break-even with real team size.
03

Pick first system

Bookkeeping, CRM, planning software, export or agent route.
04

Run a 30-day pilot

Measure recovered minutes, approvals, invoice value and clean handoff.

Where revenue leaks

People do not forget billable work because they are careless.

They forget it because real work is fragmented: calls, tabs, files, code, email, travel and quick advice. Half5 catches those moments while they are still recognizable and lets the user decide what becomes business data.

See timeline model

Calculate missed revenue

The client call between meetings

Ten useful minutes feel too small to register now, then vanish before invoicing starts.

The quick fix nobody writes down

A Git commit, file change or browser session shows work happened, but the invoice never sees it.

The advice during a closing week

Small advisory moments are valuable, especially when the team is too busy to reconstruct them later.

The field note after the workday

Mobile work, travel context and project changes stay checkable before memory becomes the source.

User decides

The raw timeline is personal until the user turns a suggestion into submitted work.

Manager reviews

Team leads approve hours, projects and exceptions before finance receives them.

Finance invoices

Approved work becomes invoice-ready output for bookkeeping, CRM or agents.

Different by design

Half5 is not another place where people type yesterday's work.

Most tools make time registration easier after the memory problem already happened. Half5 starts earlier: it catches recognizable work, keeps the personal timeline private and turns approved hours into revenue data.

Why teams switch From admin tool to revenue system

Traditional time registration

Problem

asks people to remember later

Half5

suggests work while context is still fresh

Outcome

fewer missed billable moments

Automatic tracking without trust

Problem

feels like a manager looking over shoulders

Half5

keeps the raw timeline with the user

Outcome

team use without surveillance anxiety

Exports and spreadsheets

Problem

move messy data to finance

Half5

moves submitted and approved work only

Outcome

clean invoice, CRM and agent output

Best fit

Half5 is strongest when time registration is a revenue problem, not only an admin task.

Choose Half5 when

billable work disappears between systems, calls and memory.

The team already sells time, but too much work is reconstructed too late or never reaches the invoice.

A simple time app is enough when

people only need to clock hours they already remember.

If revenue does not leak through forgotten context, a lighter manual workflow may already solve the problem.

Enterprise becomes logical when

privacy, a custom agreement and approved data routes must work together.

The buying case is no longer just licenses; it is adoption, recovered revenue, onboarding and system handoff.

See the timeline model

Revenue lift

Forgotten work is revenue that has not reached the invoice yet.

For billable teams, time registration is revenue infrastructure. Half5 helps find the work that normally disappears between calls, browser tabs, files, meetings and invoice moments.

Submitted hours before invoicing Approval flow for teams Accounting handoff without exports

IT and software

Tickets, Git, support and calls become billable context.

For teams where project work is scattered across tools and invoices are rebuilt from memory at the end of the week.

Accountancy

Client reviews, advice and recurring work stay invoice-ready.

For offices that want month-end control without asking everyone to reconstruct small advisory moments.

Legal and advisory

Dossier work is captured without exposing private timelines.

For professionals where trust, client context and small billable moments all stay intact.

Construction

Project hours move from field work to finance without loose notes.

For project teams with mobile registration, budget visibility and approval before invoices go out.

Installation and field service

Crews submit cleaner hours before finance starts chasing.

For installation teams that want less admin after jobs and a cleaner handoff to invoicing.

Agriculture and agri service

Seasonal work, field visits and machine hours stay invoice-ready.

For growers, contractors and agri service teams where work changes by field, season, machine and weather window.

Consultancy and advisory

Workshops, research and client follow-up stay tied to revenue.

For advisory teams where billable value is spread across meetings, decks, research, follow-up and internal alignment.

Marketing and creative agencies

Campaign work, feedback rounds and quick fixes stop leaking margin.

For agencies where client work moves between campaigns, content, design, calls and revisions before anyone writes the time down.

Engineering and architecture

Design reviews, site meetings and revision rounds stay project-ready.

For engineering and architecture teams where project value moves through drawings, meetings, calculations, field checks and corrections.

Freelancers and small agencies

Small work stays connected to project value.

For solo professionals and small teams that want invoices to reflect the real work without heavy administration.

Example Revenue opportunity

Potential per year € 0 about €0 per month

Users 12 Forgotten minutes per day 30 Hourly rate € 85

Based on 220 billable workdays. Not a guarantee, but a useful way to see why missed time is expensive.

View team pricing

Discuss the revenue opportunity

Built for teams

A calm operating layer between work, approvals and revenue.

Half5 is not just a time sheet. It shows what happened, what is ready for review and which billable hours are ready to become invoices.

View integrations

Accounting contacts synchronized Phone timeline sync through QR Timeline access stays personal Approval before invoicing

This week Operations dashboard

Live

Ready for approval 42,5u

Ready to invoice € 5.780

Billable ratio 82%

Timeline suggestions Browser, program and file activity

Awaiting approval Team lead can review before finance

Draft invoices Moneybird, WeFact, Exact Online and e-Boekhouden

Capacity view 82%

Planned Worked Non-billable

Detect

Work appears automatically

Desktop activity, browser usage, files, Git context and location settings help rebuild the workday without asking people to remember every detail.

Approve

Managers see what is ready

Team leads approve hours before finance starts invoicing, so corrections happen before money is on the line.

Invoice

Billable work becomes revenue

Approved hours are grouped per customer and project, with invoice lines, discounts, tax rules and accounting handoff in one flow.

Control

The timeline stays personal

Only the user works with the raw activity timeline. The organization gets submitted hours, approvals and invoice-ready data.

Built for trust

The emotional promise is clear: no more revenue lost in someone's memory.

Half5 makes forgotten work visible without turning automatic time tracking into surveillance. That is the difference between a tool people tolerate and a workflow teams actually adopt.

Personal timeline boundary

Only the user works with the raw activity timeline. Managers see submitted hours, approvals and invoice-ready data.

Business control before invoicing

Team leads approve exceptions before hours move to finance, so recovered time stays explainable.

Existing software connects

Bookkeeping, projects, CRM, planning tools and agents work with approved hours.

Revenue per team

One branch or team can show recovered revenue before other teams join.

Enterprise rollout

A rollout path from first team to company standard.

Recovered revenue becomes visible in one team first, trust is protected from day one, software connects to approved data and scaling follows when the workflow works.

Calculate the business case

Discuss team rollout

01

Revenue-critical team

IT, accountancy, legal, advisory or field service teams usually feel the value fastest.
02

Projects, clients and rates

Half5 follows the commercial structure that already determines customer, project and rate logic.
03

Approval before finance receives it

Users keep timeline control, managers approve hours, finance receives clean invoice data.
04

Integrations and agents scale with the workflow

Accounting systems, internal software and agents become useful once the workflow is predictable.

Common questions

Answer the hard questions before the rollout starts.

Can managers open an employee's raw timeline?

No. The raw timeline is personal. The organization works with submitted hours, approvals, exceptions and invoice-ready output.

How does this increase revenue without annoying the team?

Half5 reconstructs the day from real work context and lets users correct suggestions. Less memory work, fewer missed billable moments.

Which systems can Half5 connect with?

Live accounting links include Moneybird, WeFact, Exact Online and e-Boekhouden. Other accounting, CRM, project and planning tools can be discussed around the first team, the approved data and the revenue it should recover.

Can AI agents use Half5 data?

Yes. Agents can use suggestions, submitted hours, approvals and invoice data. Private raw timelines stay outside the agent route.

Where does a larger organization start?

The strongest starting point is one team where missed hours hurt revenue. Once approval and invoicing work, expansion can follow by branch, administration or country with volume agreements.

Before rollout

Turn the demo into a rollout case every stakeholder can defend.

Half5 is easiest to approve when revenue, trust, first team and system handoff are clear in the same conversation.

Plan decision-ready demo

Revenue case

Missed minutes, hourly rate, team size and price per user make the payback concrete.

Trust boundary

Users keep the raw timeline personal. The organization only works with submitted and approved hours.

Pilot boundaries

The first branch, team or administration shows value before the rollout grows.

First handoff

Accounting, CRM, planning tools and agents receive approved output, not private activity.

30-day pilot

The first rollout shows value before a larger contract.

In 30 days you can see whether Half5 recovers minutes, creates a workable approval rhythm, produces invoice-ready value and hands clean data to finance or integrations.

Pilot scorecard

The four signals that show whether scaling makes sense.

Recovered billable minutes

Work that used to disappear between meetings, files, browser tabs and memory becomes measurable.

Approval rhythm

Submission and approval rhythm become visible before invoice pressure starts.

Invoice-ready value

Approved hours become customer, project, rate and invoice output finance can use.

Integration handoff

The route to accounting packages, exports, internal software or agents is tested with approved data.

Team lead view Approved hours before finance

Management view Billability and productivity

Finance route Accounting sync settings

What finance receives

After the pilot, finance sees concrete output instead of another opinion.

The pilot produces concrete output: logged hours, approvals, reports, rate hierarchy, invoices, PDFs, exports and accounting links.

Plan pilot call

Price the pilot

Hour report and export

Date, contact, project, user, activity and leave filters make the pilot auditable.

Rate hierarchy

Activity, project, contact, user and organization rates explain why a recovered hour has that value.

Invoice trail

Approved hours can become invoice lines, PDFs, status changes and external accounting output.

Accounting sync

Moneybird, WeFact, Exact Online and e-Boekhouden have dedicated integration flows and test coverage.

Inside the product

The workflow is visible before another promise has to be believed.

Before rollout starts, every role can see their part: users keep control, managers approve business hours, finance receives clean data and leadership sees recovered revenue.

User layer Timeline suggestions

Management layer Revenue insight

Finance layer Invoice and sync

Platform map

Every module supports a concrete part of the revenue system.

Personal timeline

Automatic suggestions without giving managers raw activity access.

Time registration

Billable work is registered, corrected and submitted with less memory work.

Approval flow

Control stays between teams and finance before revenue leaves the workflow.

Projects and budgets

Time stays connected to clients, projects, rates and profitability signals.

Invoice-ready hours

Approved hours become invoice lines instead of manually rebuilt invoices.

Revenue insight

See billability, missed hours and productivity before they become month-end noise.