HRIS
The people record
People and contracts, timesheets, time off, compensation, onboarding and offboarding, access and trainings.
HRIS, CRM and ERP in one, built for companies that deliver work.
Stop building reports. Just ask. People, clients, projects and invoicing live in one data model, set up around how you run — and you can ask it anything in Slack.
The problem
Every report answers a question
someone guessed in advance.
The real questions come up on a Tuesday afternoon, and they never fit the dashboard. Is this project still making money? What have we worked and not billed? Who is free next month?
So someone exports from one system, pastes into a sheet, matches it against a second — and by the time the number is ready, it has already moved.
Monksheets gives you the answer instead of the report.
Ask instead
Ask your company, the way you'd ask a colleague
Click a question to see the kind of answer that comes back in the thread.
Which projects are over budget right now, and who's on them?
Two projects are past 90% of budget: Northwind website (104%, Anna, Petr) and Atlas support (93%, Jana). Northwind went over last week on design hours.
What have we worked this month that hasn't been invoiced yet?
412 hours across 7 projects are worked and not yet invoiced. The largest are Northwind (160 h) and Atlas (95 h).
Which client requests are about to miss the response time we promised?
Three requests are inside their warning window. One Atlas request has 40 minutes left before it misses its agreed response time, and nobody is assigned yet.
Who's off next week, and which projects does that hit?
Petr is off Monday to Wednesday and Jana on Friday. Petr is the only person staffed on Northwind that week.
Which deals close this month, and who owns them?
Four deals are expected to close this month, worth 38,000 EUR together. Anna owns two, Tomas owns two.
One data model
Three modules, one record
The person on the project is the owner of the deal is the employee on leave. That is why questions that cross HR, sales and delivery have an answer.
CRM
The customer record
Clients and deals with owners, a client portal for requests, and the response times you promised — tracked on every request.
ERP
The operations record
Projects by contract type, resourcing, time and cost against budget, invoicing and margin on every project.
Built for delivery
The parts other systems leave to a spreadsheet
- Projects that know their contract. Time and materials, fixed price, prepaid hour packages and support contracts — each with the budgeting and billing logic it actually needs.
- Response times you can prove. Agreed reaction and resolution times per client, tracked on every request and flagged before they are missed.
- A portal your clients will use. Clients raise requests, follow their status and accept delivered work — without an email thread.
- Nothing worked goes unbilled. From hours to invoice by contract type, with every unbilled hour in plain sight.
Who asks what
One system, a question for every role
Which projects are over budget right now?
What have we worked this month that hasn't been invoiced?
Who's off next week, and which projects does that hit?
Which deals close this month, and who owns them?
Who hasn't completed their mandatory training?
Which client requests are about to miss their response time?
Set up with you
We don't hand you a login
and a help centre.
-
A 30-minute call. What you run today and what hurts most.
-
A short questionnaire. Your tools, your processes and what you want to keep.
-
We set it up on your data. Your sales stages, your leave rules, your approvals — connected to the Slack you already use.
-
You ask. And stop building reports.
Your own instance. Your own database.
Questions
Before you get in touch
Do we have to drop the tools we use today?
No. We start with the part that hurts most and keep what already works — Slack stays Slack. Nothing has to move on day one.
Do we need Slack?
Slack is where you ask, using your own Claude subscriptions. Everything also works in the web application, so a team without either still gets the whole system.
How do you get our data in?
We import your people, clients, projects and rates as part of the setup, and agree with you how much history comes along.
Where does our data live?
In your own instance with its own database — not in a shared pool with other companies. You can have a full copy of it whenever you ask.
How long does the setup take?
It depends on how many modules you start with and how much data comes along. You get a concrete timeline after the first call, not a guess before it.
We're setting it up with a small group of companies this year
Monksheets is early, and that works in your favour: we set it up with you, around what you actually need. Tell us what you run today, and we'll show you what you could be asking by next month.