Use cases

17 things that happen in a services company. Step by step.

Not a feature list — the actual sequence, with what lands where and who picks it up next. Every figure below is one the demo workspace really holds, so you can sign in and find the same numbers.

All seventeen, at a glance

01Somebody joins on the 3rdHR & People
02She wants Thursday and Friday offAttendance & Leave
03It is the 25th and payroll is duePayroll
04Work is finished and needs billingFinance & Accounting
05Six invoices are lateFinance & Accounting
06The team needs three laptopsProcurement & Purchasing
07A cab to the client's officeExpenses
08₹53.8L was delivered and never invoicedProjects & Delivery
09The client's login stopped workingSupport & Helpdesk
10A scope question, and the answer six months laterCommunication & Collaboration
11Somebody leaves on FridayAdmin & Facilities
12A deal is won on FridaySales & CRM
13An RFP lands with a two-week deadlinePre-Sales & Bids
14A contract renews in sixty daysCustomer Success
15Two hundred numbers to work throughTelecalling
16Did that campaign pay for itself?Marketing
17Two people run the same reportAnalytics & Reporting

01People

Somebody joins on the 3rd

HR, and then four modules that never had to be told

HR & People →

3 Sept
HR creates one record
People
35th
name, department, and who she reports to
Same day
Her leave opens by itself
Balances
12 · 12 · 18
casual, sick and earned, already there
Day two
She is put on a project
P-ACME
assigned
so her hours can be booked and billed
25 Sept
Payroll finds her
September run
included
nobody added her to a second system

One record entered once. No re-keying, and no system disagreeing about who approves her leave.

The screen this happens on — Somebody joins on the 3rd

02People

She wants Thursday and Friday off

Anybody, and their manager

Attendance & Leave →

Tue
She applies from her phone
Earned leave
2 days
no form, no email to HR
Tue
Her manager sees it
Waiting on me
1
the manager the org chart says, not a guess
Tue
Approved
Balance left
16 days
the balance updates as it is approved
25th
Payroll already knows
September run
paid leave
nobody re-enters it at month end

The leave register, the approval and the payslip are the same record — so they cannot disagree.

The screen this happens on — She wants Thursday and Friday off

03People

It is the 25th and payroll is due

HR, then whoever signs it off

Payroll →

25th
The month is opened
August 2026
34 people
hours come from attendance, nothing to import
25th
It calculates
Gross
₹26,42,806
earnings and deductions applied across the run
26th
It waits for approval
State
calculated
it cannot be paid from here
28th
Three people sign it
Signed off by
3
stored in order, on the run itself
30th
Released
Net paid
₹25,74,806
and every payslip exists

Six months later, “who approved August?” is a column — not an archaeology project through somebody's mail.

The screen this happens on — It is the 25th and payroll is due

04Money

Work is finished and needs billing

Finance, without chasing delivery

Finance & Accounting →

01 Sep
A draft is assembled
From
3 sources
approved hours, milestones, billable expenses
01 Sep
It is numbered
2026-27/0002
in order
per financial year, without a counter to maintain
01 Sep
Issued to the client
Total
₹15,96,422
GST applied at the right place of supply
18 Sep
Part payment lands
Outstanding
₹13,56,959
credited against the invoice, not a note somewhere
Any time
It sits in the books
Ledger
balanced
double entry, and the reports read these rows

Nothing was retyped between what was delivered and what was billed, so nothing could be missed.

The screen this happens on — Work is finished and needs billing

05Money

Six invoices are late

Whoever has to make the calls

Finance & Accounting →

Now
The ageing is already done
Outstanding
₹37,20,263
across ten invoices, six of them late
Now
Sorted by how bad
Over 60 days
₹12,39,000
four invoices, and you call those first
Now
One cannot even be sent
Brix Ltd
no GSTIN
flagged on the project, not discovered at month end
Ongoing
A rule chases the rest
Notify
email
when an invoice passes its due date

Receivables stops being a spreadsheet of what somebody remembers chasing.

The screen this happens on — Six invoices are late

06Money

The team needs three laptops

Whoever asks, and whoever pays

Procurement & Purchasing →

Mon
A requisition is raised
Requested
3 units
with a reason and a project attached
Tue
It is approved
Approval
on record
so nobody argues about it later
Tue
A purchase order goes out
PO
issued
the vendor sees it in their own login
Next week
The bill arrives
Matched to
the PO
ordered against invoiced, before you pay
Due date
It sits in payables
Owed
with a date
the mirror image of receivables

Buying stops running out of an inbox, and what was agreed is checkable against what was billed.

The screen this happens on — The team needs three laptops

07Money

A cab to the client's office

Anybody who travels

Expenses →

Tue
She files it with the receipt
Claim
₹1,240
against the project she travelled for
Wed
Her manager approves
Approval
1 verb
approving is a different permission from filing
01 Sep
It joins the invoice
Billable
yes
with the hours and the milestones
Payday
She is reimbursed
Ledger
posted
and the books know about both sides

Filing your own claim and billing a customer are different acts, so they are different permissions.

The screen this happens on — A cab to the client's office

08Delivery

₹53.8L was delivered and never invoiced

The founder, a quarter earlier than usual

Projects & Delivery →

Ongoing
Hours book against a budget
Platform
204 of 600
the bar is the plan, not a mood
Ongoing
Finished work adds up
Unbilled
₹35L
on that project alone
Now
The screen totals it
Across 15
₹53.8L
delivered, approved, never invoiced
Now
And says what is stuck
Brix
blocked
no GSTIN on file, so it cannot be billed at all
Today
Somebody fixes the record
Then
billable
instead of finding out in January

This is the number most companies find a quarter late, from finance. Here it is while the work is still running.

The screen this happens on — ₹53.8L was delivered and never invoiced

09Delivery

The client's login stopped working

Your client, at no cost to you

Support & Helpdesk →

09:40
They raise it themselves
Their portal
free
the account costs you nothing, ever
09:40
It lands on their account
Scope
theirs only
decided at sign-in, not by what they type
09:52
Somebody picks it up
Assigned
to a person
against the client and the project
11:15
Closed, and counted
Reports
measured
which is only possible because it was not an email

Support stops living in individual inboxes — the only condition under which it ever gets measured.

The screen this happens on — The client's login stopped working

10Delivery

A scope question, and the answer six months later

Everybody who joins the project after

Communication & Collaboration →

Mon
It is asked in a channel
Not
WhatsApp
inside the workspace that knows the org chart
Mon
A file answers it
Attached to
P-ACME
under the same scope rules as the project
Tue
The call is recorded
Meeting
on record
with who was in it
March
Somebody new finds it
Search
one box
and only sees it if their scope reaches it

The decision stays with the work it changed, and does not leave with an employee's personal phone.

The screen this happens on — A scope question, and the answer six months later

11Delivery

Somebody leaves on Friday

Admin, on the day rather than a month later

Admin & Facilities →

Day one
A laptop was assigned
Asset
logged
to the same employee record HR uses
Ongoing
A licence sits against them
Seat
1
with its renewal date
Friday
Their account is disabled
Seat cost
₹0
the record stays for the audit trail
Friday
The list says what is out
Outstanding
1 laptop
read off the record, not remembered

Office administration stops being one person's private spreadsheet.

The screen this happens on — Somebody leaves on Friday

12Growth

A deal is won on Friday

Sales, then delivery, without re-typing anything

Sales & CRM →

Weeks
It moves down the pipeline
Stage
tracked
with a value and an owner
Fri
Won, against a client record
Acme Corp
one record
the same one finance and support use
Fri
A contract is raised
Signed
on file
including the GSTIN finance will need
Mon
Delivery starts
P-ACME
opened
nobody re-entered the client or the numbers

The handover from sold to delivered stops being a re-entry exercise between two systems.

The screen this happens on — A deal is won on Friday

13Growth

An RFP lands with a two-week deadline

Pre-sales, and the delivery team who inherit it

Pre-Sales & Bids →

Day 1
A bid is opened
Due
14 days
with what is being bid for
Day 4
The effort is estimated
Estimate
with workings
the assumptions stay with the number
Day 6
A quotation goes out
Issued
v1
built from that estimate, not retyped
Day 9
They ask for a revision
v1
superseded
never overwritten, so v1 stays legible
Day 14
Won
Becomes
a project
and delivery inherits the assumptions too

Nobody has to ask which numbers the client actually received.

The screen this happens on — An RFP lands with a two-week deadline

14Growth

A contract renews in sixty days

The account manager, before it lapses

Customer Success →

T-60
It appears with an owner
Renewal
60 days
not a date inside a PDF
T-45
They check the account
Same client
one view
delivery, tickets and invoices together
T-30
A review is recorded
QBR
logged
with what was promised
T-0
Renewed, or not
Reason
recorded
either way it is on the record

Nobody finds out a contract expired because a client stopped paying the next invoice.

The screen this happens on — A contract renews in sixty days

15Growth

Two hundred numbers to work through

The caller, and the pipeline afterwards

Telecalling →

Morning
A list is assigned
Queue
200
not a shared spreadsheet
Ongoing
Outcomes are recorded
Against
the contact
not a personal notebook
Ongoing
Do-not-call is applied
By
the product
held, so it is applied rather than remembered
Afternoon
The good ones convert
Pipeline
as leads
on the same contact record

Calling activity becomes a number instead of an anecdote about how busy the team was.

The screen this happens on — Two hundred numbers to work through

16Growth

Did that campaign pay for itself?

Marketing, answering with a number

Marketing →

Launch
A campaign runs
Audience
defined
against contacts you already hold
Weeks
Leads arrive attributed
Source
carried
into the pipeline sales already works
Later
Some convert
Deals
won
against the same client records
Quarter
It has a revenue number
Answer
in rupees
from the system that raised the invoice

Spend stops being argued about and starts being measured.

The screen this happens on — Did that campaign pay for itself?

17Insight

Two people run the same report

A delivery manager and the finance controller

Analytics & Reporting →

09:00
The manager runs it
Utilisation
their team
narrowed before it reaches them
09:01
The controller runs it
Same report
everything
their scope is global, so it is a different answer
Neither
Configured a permission
Tools used
one
there is no separate reporting product
Both
Are on the record
Report runs
logged
because a report is an export

A report cannot show somebody what their own screen would refuse — there is no second copy of the data to get it wrong.

The screen this happens on — Two people run the same report

Recognise two or three of these? That is usually enough.

Have a look round Start free