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 .
Everything17 People3 Money4 Delivery4 Sales5 Reporting1
01 People Somebody joins on the 3rd HR, and then four modules that never had to be told
HR & People →
3 Sept
HR creates one record
name, department, and who she reports to
Same day
Her leave opens by itself
casual, sick and earned, already there
Day two
She is put on a project
so her hours can be booked and billed
25 Sept
Payroll finds her
nobody added her to a second system
One record entered once. No re-keying, and no system disagreeing about who approves her leave.
Tue
She applies from her phone
no form, no email to HR
Tue
Her manager sees it
the manager the org chart says, not a guess
Tue
Approved
the balance updates as it is approved
25th
Payroll already knows
nobody re-enters it at month end
The leave register, the approval and the payslip are the same record — so they cannot disagree.
03 People It is the 25th and payroll is due HR, then whoever signs it off
Payroll →
25th
The month is opened
hours come from attendance, nothing to import
25th
It calculates
earnings and deductions applied across the run
26th
It waits for approval
it cannot be paid from here
28th
Three people sign it
stored in order, on the run itself
30th
Released
and every payslip exists
Six months later, “who approved August?” is a column — not an archaeology project through somebody's mail.
01 Sep
A draft is assembled
approved hours, milestones, billable expenses
01 Sep
It is numbered
per financial year, without a counter to maintain
01 Sep
Issued to the client
GST applied at the right place of supply
18 Sep
Part payment lands
credited against the invoice, not a note somewhere
Any time
It sits in the books
double entry, and the reports read these rows
Nothing was retyped between what was delivered and what was billed, so nothing could be missed.
Now
The ageing is already done
across ten invoices, six of them late
Now
Sorted by how bad
four invoices, and you call those first
Now
One cannot even be sent
flagged on the project, not discovered at month end
Ongoing
A rule chases the rest
when an invoice passes its due date
Receivables stops being a spreadsheet of what somebody remembers chasing.
Mon
A requisition is raised
with a reason and a project attached
Tue
It is approved
so nobody argues about it later
Tue
A purchase order goes out
the vendor sees it in their own login
Next week
The bill arrives
ordered against invoiced, before you pay
Due date
It sits in payables
the mirror image of receivables
Buying stops running out of an inbox, and what was agreed is checkable against what was billed.
07 Money A cab to the client's office Anybody who travels
Expenses →
Tue
She files it with the receipt
against the project she travelled for
Wed
Her manager approves
approving is a different permission from filing
01 Sep
It joins the invoice
with the hours and the milestones
Payday
She is reimbursed
and the books know about both sides
Filing your own claim and billing a customer are different acts, so they are different permissions.
08 Delivery ₹53.8L was delivered and never invoiced The founder, a quarter earlier than usual
Projects & Delivery →
Ongoing
Hours book against a budget
the bar is the plan, not a mood
Ongoing
Finished work adds up
on that project alone
Now
The screen totals it
delivered, approved, never invoiced
Now
And says what is stuck
no GSTIN on file, so it cannot be billed at all
Today
Somebody fixes the record
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.
09:40
They raise it themselves
the account costs you nothing, ever
09:40
It lands on their account
decided at sign-in, not by what they type
09:52
Somebody picks it up
against the client and the project
11:15
Closed, and counted
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.
Mon
It is asked in a channel
inside the workspace that knows the org chart
Mon
A file answers it
under the same scope rules as the project
Tue
The call is recorded
with who was in it
March
Somebody new finds it
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.
Day one
A laptop was assigned
to the same employee record HR uses
Ongoing
A licence sits against them
with its renewal date
Friday
Their account is disabled
the record stays for the audit trail
Friday
The list says what is out
read off the record, not remembered
Office administration stops being one person's private spreadsheet.
12 Growth A deal is won on Friday Sales, then delivery, without re-typing anything
Sales & CRM →
Weeks
It moves down the pipeline
with a value and an owner
Fri
Won, against a client record
the same one finance and support use
Fri
A contract is raised
including the GSTIN finance will need
Mon
Delivery starts
nobody re-entered the client or the numbers
The handover from sold to delivered stops being a re-entry exercise between two systems.
13 Growth 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
with what is being bid for
Day 4
The effort is estimated
the assumptions stay with the number
Day 6
A quotation goes out
built from that estimate, not retyped
Day 9
They ask for a revision
never overwritten, so v1 stays legible
Day 14
Won
and delivery inherits the assumptions too
Nobody has to ask which numbers the client actually received.
14 Growth A contract renews in sixty days The account manager, before it lapses
Customer Success →
T-60
It appears with an owner
not a date inside a PDF
T-45
They check the account
delivery, tickets and invoices together
T-30
A review is recorded
with what was promised
T-0
Renewed, or not
either way it is on the record
Nobody finds out a contract expired because a client stopped paying the next invoice.
15 Growth Two hundred numbers to work through The caller, and the pipeline afterwards
Telecalling →
Morning
A list is assigned
not a shared spreadsheet
Ongoing
Outcomes are recorded
not a personal notebook
Ongoing
Do-not-call is applied
held, so it is applied rather than remembered
Afternoon
The good ones convert
on the same contact record
Calling activity becomes a number instead of an anecdote about how busy the team was.
16 Growth Did that campaign pay for itself? Marketing, answering with a number
Marketing →
Launch
A campaign runs
against contacts you already hold
Weeks
Leads arrive attributed
into the pipeline sales already works
Later
Some convert
against the same client records
Quarter
It has a revenue number
from the system that raised the invoice
Spend stops being argued about and starts being measured.
09:00
The manager runs it
narrowed before it reaches them
09:01
The controller runs it
their scope is global, so it is a different answer
Neither
Configured a permission
there is no separate reporting product
Both
Are on the record
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.
Recognise two or three of these? That is usually enough.
