The Opsters blog

Playbooks, case studies and resources.

What we learn building operational systems: how the work actually arrives, what we do about it, and what it costs when nobody does.

Playbook

Building a client request process that survives growth

Client requests arrive in Slack, and one person per client quietly retypes them into your project tool.

Read
Playbook

How to set up monday.com for an IT services business

Customer cases and internal support are both ticket-shaped, which is why they end up competing in the same queue.

Read
Playbook

Getting more out of your monday.com boards

Views, filters, batch actions and the activity log: the features that separate a board you tolerate from one that works.

Read
Case StudyOne Event

How One Event runs 400 events a year across 14 offices

400 events, 14 offices, one live view of the operation, and 223 hours a year recovered from reporting.

Read
Case StudyOne Event

Letting 70 people raise invoices without losing control

Invoicing on Sheets, Excel and Word concentrated billing into a few people. The controls had to move into the system.

Read
Case StudyBathco Switzerland

Bathco Switzerland onboards a new hire in one click

HR, IT and Operations acting in sequence, on a deadline, for someone who does not work here yet.

Read
Case Study310 Tutors

How 310 Tutors tracks every student from inquiry to lesson report

Tutoring has no clean handover from sales to delivery, so we built the whole span as one connected system.

Read
Case StudyThought Bakery

Thought Bakery moved off spreadsheets in six weeks

Cost management for a distributed studio with global freelancers meant solving access layers first.

Read
Resource

AI readiness checklist

Score your foundations, find the processes that are genuinely AI-shaped, and decide what to do with both answers.

Read
Resource

Digital transformation project checklist

Structure for your first digital transformation project, from defining the why through to continuous improvement.

Read