Classic template
IN THIS ARTICLE
The Classic phase template preserves the original four-category estimation model. This page explains how the classic categories map to the current system for users with existing deals or workflows built around the legacy structure.
Overview
Before dynamic categories, all phases used four fixed estimation types: Features, Overheads, Services, and Expenses. The Classic phase template recreates this exact structure so that migrated deals and established workflows continue to work without changes.
All existing deals were migrated automatically with identical totals and behavior.
Category mapping
The Classic template contains four categories that match the original estimation types:
| Classic category | Resource types | Pricing model | Equivalent to |
|---|---|---|---|
| Features | Roles, Streams, Custom price | One-off | Time-based deliverables and effort |
| Overheads | Roles, Streams | Recurring | Persistent role allocations spanning the phase |
| Services | Products, Custom price | Recurring | Subscriptions, hosting, managed services |
| Expenses | Products, Custom price | One-off | Hardware, travel, one-off product costs |
When to use Classic
- Migrated deals — existing deals use the Classic template by default
- Familiar workflow — teams who prefer the established four-category structure
- Backward compatibility — when you need estimates to match the original model exactly
Moving to dynamic categories
You are not required to change existing deals. New deals can use any phase template, including Classic.
To explore dynamic categories with more flexibility, consider the Standard or Blank templates when creating new deals or phases.