Owner
Owner
Signs the contract, appoints administrators and approves addenda.
Contracting
One contract per organisation.
Credits by usage.
No plans. Each organisation signs a contract sized to what it needs: modules, users and a pibiCash credit allowance. The mobile client is included.
How it is contracted
From the first call
to rollout
Three to six weeks, depending on how many systems have to be connected.
Enquiry
Creates no account and activates no trial.
Scope and contract
Users, modules, where the data lives, pibiCash allowance and integrations, with the data processing annex.
Thirty-day pilot
Under an already signed contract. It is not a free trial.
Enrolment
By invitation, with a single-use link. Nobody signs themselves up.
Governance
Seats, credits, retention and offboarding stay with the organisation.
The unit of consumption
What pibiCash is
The unit that measures machine work: minutes transcribed, summaries, generated minutes and assistant queries all draw down the contracted allowance.
A user does not acquire credits and never sees an amount: they draw against their organisation's allowance. The quarter's consumption has an agreed ceiling from day one.
Inside pibiCollab there are no amounts, no payment gateways and no purchase buttons. The commercial relationship lives in the contract, and only there.
Where the credit goes
What consumes it and what does not
CONSUMES
- Transcription, per minute of audio
- Summaries and extraction of commitments
- Assisted drafting of minutes
- Queries to the Second Brain
COSTS NOTHING
- Notes, tasks and calendar
- Calling a meeting, taking minutes by hand and signing them
- Scripts, import and export
- Attaching and downloading files
Mobile client
Included in the contract.
Not sold separately.
No limit on devices per contracted seat. It opens with the corporate identity the administrators enrolled; without that it does not start.
Download for users already enrolled
The mobile application contains no in-app purchases, displays no amounts, and offers no route to purchase or extend the service, inside the app or through external links.
Who can do what
Three roles in the organisation
Administration
Administration
Enrols and offboards users, distributes the allowance and sees consumption per seat.
User
Member or employee
Works in their seat and receives the actions assigned to them.
By default no role reads another user's individual scope. The organisation, as data controller, keeps the powers that belong to it, and the contract sets out when they are exercised.
Fair questions
What management usually asks
Can an employee buy this on their own?
No. There is no public sign-up and no purchase route inside the product. A user exists because their organisation's administrators enrolled them by invitation, under a contract already signed.
If there are no plans, how is it sized?
Before signing. From users, modules and an estimate of consumption, pibiCo returns the contract with the pibiCash allowance and its terms in writing.
What happens when a user runs out of pibiCash?
Notes, tasks, calendar, meetings and scripts keep working. Machine functions pause and the notice points at the organisation's administrators.
What happens to the data when someone leaves?
Administrators transfer their scope to another seat, export it or delete it. Minutes, signatures and actions stay: they belong to the organisation.
Next step
Tell us how many users and what you need to solve
We come back with scope, modules and credit allowance, in writing.