Skip to content
Monksheets
Request access

Modules

One system, four ways in

Three modules and an interface. They share a data model, which is the whole point — the employee in HRIS is the account owner in CRM is the person costed on the project in ERP.

HRIS

The people record

Everything about who works here and on what terms — held once, used everywhere.

  • People and contracts. Employees, contractors, roles, start and end dates, terms.
  • Org structure. Reporting lines, teams and how they change over time.
  • Time off. Requests, approvals, balances and calendars — requested and approved in Slack, not in a portal.
  • Compensation. Salary, changes and history, with access limited to who should see it.
  • Onboarding and offboarding. What has to happen when someone joins or leaves, and whether it has.
Who it's for Founders and operations leads who are running people admin out of a spreadsheet and a shared calendar, and have reached the point where that costs real time and real mistakes.
What it unlocks elsewhere Because HR data is not in a silo, the CRM knows an account owner is leaving before the renewal does, and the ERP can cost a project in salary time rather than a guess.

CRM

The customer record

Companies, the people inside them, and every deal in motion — connected to the people who own them.

  • Companies and contacts. Who they are, who you talk to, what has been said.
  • Pipeline. Deals, stages, value and close dates. Configured to how you actually sell.
  • Ownership. Every account and deal has an owner, and that owner is an employee record — not a text field that goes stale when they leave.
  • Activity. The conversations, meetings and commitments attached to the account.
  • Renewals. What is up, when, and what it is worth.
Who it's for Teams whose CRM has become a reporting obligation rather than a working tool — where updating it is the tax you pay after the selling is done.
What it unlocks elsewhere A closed deal is a project the ERP can staff and a cost the ERP can track, without anyone re-typing it.

ERP

The operations record

What the business is doing, what it earns, and what it costs to deliver.

  • Projects. Scope, budget, timeline and status.
  • Resourcing. Who is staffed where, at what capacity, and where the gaps are.
  • Time and cost. What is being spent against what was budgeted.
  • Invoicing. What has been billed, what is outstanding, what is late.
  • Margin. Revenue against true cost, per project and per customer.
Who it's for Companies that deliver work rather than ship units — agencies, consultancies, studios and services teams — where the difference between a good quarter and a bad one is whether you knew about the overrun in week two or week ten.
What it unlocks elsewhere Cost data flows back to the customer record, so account profitability is a property of the customer rather than a quarterly exercise.

AI interface

The way you actually use it

Monksheets has a full web application. Most days you will not open it.

The interface is Slack. You ask for what you want in the words you would use with a colleague, and the answer — or the change — comes back in the thread.

What asking looks like

  • "How much holiday does Marta have left this year?"
  • "Put Tomáš on the Kaufland project at 60% from Monday."
  • "Which deals close this month and who owns them?"
  • "What did we make on the Rohlík account last quarter, after salary cost?"
  • "Invoice the November retainer."

Why this beats clicking through screens

  • Questions do not map to screens. Every report that exists was built by someone who guessed in advance which question you would ask. The interesting questions are the ones nobody anticipated, and they are usually the ones that cross two modules.
  • Adoption is the hard part of any operating system. Software that replaces three systems fails when people keep using the old ones. Nobody avoids a system that works by being spoken to in the place they are already typing.
  • The record stays current. Updating a CRM is a chore people do late and badly. Saying what happened is not a chore. The data is fresher because keeping it fresh costs nothing.
  • Every action is attributed and reversible. Conversational does not mean loose. Each change records who asked, what changed and when, and can be undone.

Slack today. Microsoft Teams next.

Why one system

Three systems you can buy
anywhere. One record you cannot.

You could buy a better standalone HRIS. A better standalone CRM certainly exists. The reason to run all three here is the thing no integration gives you: they are not three systems agreeing with each other, they are one system.

Integrations copy data between databases on a schedule and drift in between. A shared record does not drift, because there is nothing to copy.

Start with one module. The argument gets stronger with the second.

See it on your own data

The fastest way to judge an operating system is to point it at the systems you already run. Tell us what you use today and we will show you what the move looks like.

Request access