How it works Capabilities Methods Workflows Why MCP FAQ Book a demo
Built-in prompt

Tune the estimate

Change roles, hours and estimate mode across a project without breaking what is there.

5steps 1human checkpoint 8Apropo methods
← All workflows

For: Estimators

Moving from single values to min-max ranges, or swapping a role across dozens of nodes, is slow and easy to get wrong by hand.

You saySwitch project <uuid> to min-max estimates and replace the generic Developer role with Backend and Frontend where it applies.

Run the MCP prompt workflow_manage_project_estimate_mode, or just describe the goal: an agent can load the same steps with apropo_get_workflow.

  1. Inspect the current mode

    The agent reads the estimate settings and the available worktypes first.

  2. Human decision

    Confirm the change

    The agent states what it will change and you confirm.

  3. Switch mode safely

    It applies the mode change while preserving the existing estimates.

  4. Adjust roles and hours

    It assigns, removes or replaces worktypes on nodes and sets min and max hours.

  5. Validate

    It reads the structure again to confirm the numbers after normalisation.

What you get

An estimate in the mode you want, with the history of your numbers intact.

Built-in safeguards

  • Existing estimates are preserved when the mode changes.
  • All hour edits carry the lock_version.

Want to see this run on
your own brief?

Book a demo and we will run this workflow live with your tools, with a person approving every step that matters.