The service class that was three procedures

A class named for a noun, containing three methods that share no state and call nothing in common.

final class OrderService
{
    public function place(Basket $b, Customer $c): Order {}
    public function cancel(Order $o, string $reason): void {}
    public function exportForAccounting(DateRange $r): string {}
}

// three dependencies used by one method each, injected
// into all three. and a test for cancel() that must
// construct an exporter.

A class whose methods share no dependencies is a namespace with a constructor, and the cost shows up in the tests — every test constructs everything. Splitting into three single-method classes named for what they do produced three constructors with one or two arguments each, which is more files and a smaller thing to hold in your head at any moment.