A useful price starts with the work a customer actually runs. The team describes that work in a sentence or keeps it as a swarm file, and the swarm names the steps that make up each job.
Price the structure
Each step carries a predicted price based on its model, its effort and what earlier jobs cost. The step prices roll up to one job budget. Expected volume then rolls the job budgets into a weekly commitment.
Acceptance checks and recovery belong in the same estimate. They are part of delivering the result, so their cost remains visible when the job is priced and when it runs.
Commit with the customer
The swarm is versioned. A person reviews the steps, thresholds and expected volume, then commits the price. When the team ships a new version of the swarm, Moji prices it, and new jobs use it once a person commits it.
Keep public examples illustrative
Figures on this site explain the product flow. They are illustrative until they are grounded in a connected workflow and agreed with the customer. The live report then compares the committed price with actual delivery.
To price one workflow, get in touch.