Skip to main content

inference.health Pulse · v11 — Delivery · Hour times thirty is a month · Pulse · v7

Node · v10 · How we pick a lane before work star…

How we pick a lane before work starts

The questions Coplost Services asks before recommending a service, a fixed block, or a month.

A service is a guess until the job, the record, and the person are named.

On this page

Rate comes after the shape.

The order of the questions

The first question is what a person is trying to finish this week. A page they can send. A line they can stop retyping. A draft they can check against a source. If the answer is a department, a transformation, or a platform, the note is not ready and the reply will say so.

The second question is where the record already lives. The clinical system, the warehouse list, the booking engine, the help centre, the sheet. Coplost Services joins that record or writes a new tool only when the scope says the new tool owns it. Most requests do not need a new owner.

The third question is who is allowed to let something leave the building. A price on a public page, a message to a customer, a field written into a record. That person is part of the design. If nobody will put their name on it, the automation or the model is the wrong shape.

Only then do we talk about a line on the engagements page. Project work is an hourly starting rate. A month is that rate times 30. The line is a hypothesis. The scope is the decision. You can stop after the reply.

What a useful first note contains

  • The blocked person — A role, not a company-wide ambition.
  • The current path — Inbox, PDF, sheet, scan, or chat.
  • The record — The system that is allowed to win.
  • The refusal — What must stay manual even if we can automate it.

We would rather recommend a smaller block than invent a programme around a muddy note.

Coplost Services