Templates
Save and reuse proposal structures, fork community templates, and browse built-in industry templates.
4 min read
What you'll learn
- How to create templates from scratch or from existing proposals
- How to use a template when creating a new proposal
- How version history and forking work
- Template limits by plan
Why use templates?
If you frequently write similar types of proposals — for example, website redesigns, consulting engagements, or branding projects — templates let you start from a proven structure instead of generating everything from scratch. This saves time and ensures consistency across your proposals.
Built-in templates
Ergate includes 14 industry-specific templates to get you started immediately:
- Web Development, Mobile App Development, SaaS MVP
- Brand Identity, UI/UX Design
- SEO & Digital Marketing, Content & Technical Writing
- E-Commerce, Cloud Migration
- Security Audit, Legal Compliance
- Data Analytics, and more
Each built-in template includes a pre-defined structure with sections, sample pricing data, and industry-appropriate deliverables. Use them as-is or fork them to customize for your needs.
Create a template
You can create templates in two ways:
From scratch
Go to the Templates page and click New Template. Give it a name, description, and optionally assign topics and tags. Write or paste the template content in the editor. This is useful when you want to build a reusable framework based on your best practices.
From an existing proposal
Open any completed proposal and click Save as Template in the toolbar. Ergate captures the proposal's structure, text, pricing line items, and timeline as a reusable template. This is the fastest way to template your best work.
After winning a proposal, save it as a template. Winning proposals are your best reference material for future pitches in the same category.
Use a template
When creating a new proposal, you'll see a Template selector. Choose a template and the AI enforces its structure when writing your proposal — combining your proven format with content tailored to the specific client brief you provide.
Edit a template
Open any template from the Templates page to edit its content, name, or description. Changes to a template do not affect proposals that were previously created from it.
Version history
Every time you save changes to a template, Ergate creates a new version. You can view the full version history for any template, compare changes between versions, and restore a previous version if needed. This keeps your templates safe as you iterate and improve them.
Community templates and forking
Templates can be published with three scopes:
- Personal — only you can see and use it
- Team — shared with your team members (Agency plan)
- Community — available for others to fork and use
Forking
When you find a community template you like, click Fork to create your own copy. The forked template is fully editable and appears in your personal templates. The original is not affected by your changes.
Fork limits vary by plan:
| Plan | Community forks | |------|----------------| | Free | 3 | | Solo | 10 | | Pro | Unlimited | | Agency | Unlimited |
Template limits
| Plan | Template limit | |------|---------------| | Free | 1 | | Solo | 10 | | Pro | Unlimited | | Agency | Unlimited |
If you need more templates, consider upgrading your plan. Pro and Agency plans include unlimited templates along with other advanced features. See Plans for a full comparison.
Marketplace
Templates can also be listed on the Marketplace for others to discover, purchase, or fork. If you're on a Pro or Agency plan, you can sell your templates to the community. See the Marketplace guide for details.
Template best practices
- Name templates descriptively — use names like "SaaS Development Proposal" or "Brand Strategy Package" so you can quickly find the right one
- Keep templates general — avoid client-specific details that won't apply to future proposals
- Update regularly — as your services evolve, keep your templates current so new proposals reflect your latest offerings
- Create category-specific templates — build different templates for different project types rather than trying to make one template fit everything