Pricing models

IN THIS ARTICLE

One-off pricing

One-off estimates are calculated once and contribute a fixed amount to the phase total. Use one-off pricing for deliverables, setup costs, hardware, or any work that happens once regardless of phase duration.

Examples:

• A development team estimated at 40 days of effort
• A one-off setup fee of $10K
• 10 laptops at $1,500 each

One-off estimates can use roles, streams, products, or custom prices depending on the category's rules.

Choosing a resource to estimate

Recurring pricing

Recurring estimates repeat for the duration of the phase and automatically adjust as the schedule changes. Use recurring pricing for ongoing allocations, subscriptions, or managed services.

Examples:

• A Project Manager allocated at 2 days per week
• A monthly hosting package at $5K per month
• A per-user subscription for 500 users per month

Recurring estimates calculate a per-period amount and multiply it by the phase duration. When you adjust the schedule, recurring totals update automatically.

Recurring estimates can use roles, streams, products, or custom prices depending on the category's rules.

Recurring pricing

Mixed models

When a category allows both one-off and recurring pricing, you can combine both within the same category. This is useful for categories that cover a mix of fixed deliverables and ongoing costs.

For example, a single category could contain:

• One-off development effort estimated in days
• A recurring QA allocation spanning the phase
• A one-off hardware purchase

How categories control pricing

Each category in a phase template defines:

• Allowed resource types — which of roles/streams, products, and custom prices are available
• Allowed pricing models — whether estimates are one-off, recurring, or both

These rules are set in the phase template and apply to all items within the category.

Resource types and pricing