Skip to content
Monksheets
Book a walkthrough

Modules

HRIS, CRM and ERP on one record

Built for companies that deliver work. The employee in HRIS is the deal owner in CRM is the person staffed on the project in ERP — so you can ask across all three.

HRIS

The people record

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

  • People and contracts. Employees and contractors, start and end dates, working time, concurrent contracts.
  • Time and attendance. Timesheets, approvals, period locking and reminders that run on their own.
  • Time off. Requests, approvals, balances and leave types set up to your rules.
  • Compensation. Salary history, visible only to the people who should see it.
  • Onboarding and offboarding. What has to happen when someone joins or leaves, step by step, and whether it did.
  • Access and training. Who has access to which systems, and who has completed the trainings they must.
Ask it Who's off next week, and which projects does that hit?
What it unlocks elsewhere Projects are staffed from real people, and time off shows up where delivery is planned.

CRM

The customer record

Every client, every deal and every request — connected to the people who own them.

  • Clients and deals. Value, stage and expected close date, with the pipeline set up to how you sell.
  • Ownership. Every deal has an owner, and that owner is an employee record — not a name typed into a text field.
  • Client portal. Clients raise requests, follow their status and accept delivered work without emailing anyone.
  • Promised response times. Agreed reaction and resolution times per client, tracked on every request and flagged before they are missed.
Ask it Which client requests are about to miss their response time?
What it unlocks elsewhere A won deal carries into delivery, and every client request sits next to the project it belongs to.

ERP

The operations record

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

  • Projects by contract type. Time and materials, fixed price, prepaid hour packages and support contracts, each with the logic it needs.
  • Resourcing. Who is staffed where, at what capacity, and where the gaps are.
  • Time and cost. What is being spent against what was budgeted, while there is still time to act.
  • Invoicing. From hours to invoice by contract type — recurring package invoices, multiple currencies, and nothing worked left unbilled.
  • Margin. Revenue against cost on every project.
Ask it What have we worked this month that hasn't been invoiced?
What it unlocks elsewhere Cost and budget sit next to the people doing the work, so an overrun shows up in week two, not week ten.

AI interface

Ask instead of building reports

Monksheets has a full web application. Most questions you'll simply ask in Slack, in the words you'd use with a colleague, and the answer comes back in the thread.

  • Which projects are over budget, and who's on them?
  • What have we worked this month that hasn't been invoiced?
  • Which client requests are about to miss their response time?
  • Who's off next week, and which projects does that hit?
  • Which deals close this month, and who owns them?
  • Questions don't map to screens. Every report was built by someone who guessed which question you'd ask. The useful ones are usually the questions nobody anticipated.
  • It answers as you. Everyone sees exactly what their own role allows — nothing more, whether they ask in Slack or open the app.
  • Every change is attributed and logged. You always know who asked for what, and when.
  • It works the way your company does. We connect it to your Slack and set it up around your processes during the implementation.

See it on your own data

Tell us what you use today and we'll show you what you could be asking — and what the move would look like.

Book a 30-minute walkthrough How it works