Node · v10
More room than a service service track allows.
Walk-through notes spell out blocks, scopes, months, and review rounds. They never replace the engagements page where the tariff lives. Inbox scope still beats any note here.
Pick a walk-through to launch
Filter by topic
-
01 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.
-
02 What a written scope contains
The headings Coplost Services expects in the email that confirms a block of work.
The page shows a starting rate. The scope is the document that applies.
-
03 Monthly care, without the fog
How a Coplost Services month is calculated, spent, and refused.
A month is a fresh allocation. It is the hourly rate times 30.
-
04 A person in the loop
What review means when Coplost Services builds an automation or an AI draft.
If it can reach a customer, a patient, or a parent, a person sends it.
-
05 Pick a first block that fits
A plain way to pick a first block before you write to the studio.
Choose the job. The rate follows the job.
-
06 What you leave with
The artefacts a finished Coplost Services block is expected to include.
A block is finished when you can operate the result and explain the edge.
-
07 For operators
When the work is a queue, a packet, or two lists that drift.
Operators usually need a smaller first block than the one they were quoted elsewhere.
-
08 For founders
When the work is a first release, a site that can sell, or a pilot with an ending.
A first release is a boundary. It is not a smaller version of the whole company.
-
09 The first week of a block
What the opening days usually contain once a scope is confirmed.
The first week is for the trace and the edge, not for a surprise rebuild.
-
10 Glossary
The words Coplost Services uses on the site, in the sense we mean them.
If a scope uses one of these words differently, the scope should say so.