Use this guide before configuring QuoteSter.
It is designed to help teams keep proposal workflows clean, reduce mistakes, and avoid unnecessary cleanup later.
Before You Begin
- Review the current proposal process
- Confirm service categories and line items
- Identify outdated or duplicate items
- Choose the right configuration owner
- Confirm any ClientTether proposal limitations
Understand The Existing Proposal Process First
Before configuration begins, teams should understand how proposals are currently built inside the organization.
This includes service categories, line items, pricing structures, approval workflows, and common proposal patterns.
Best Practice
Review the current proposal process before starting configuration so QuoteSter reflects how the business actually operates.
Import Categories and Line Items Carefully
QuoteSter can import categories and line items from existing systems.
Importing everything works best when the current system is organized, accurate, up to date, and free of duplicates.
The selection process is often better when older systems include duplicate items, outdated services, old pricing structures, or unused categories.
Best Practice
If the current system contains clutter or older data, use the selection process to keep QuoteSter cleaner and easier to manage long-term.
Avoid Over-Configuring Fields
QuoteSter imports many field settings automatically.
Most fields should only be adjusted when there is a clear operational reason, such as permissions, visibility controls, workflow dependencies, or default behaviors.
Best Practice
Only modify fields when necessary. Over-configuring fields can make workflows harder to maintain later.
Keep Proposal Structures Consistent
Consistency improves both operational reliability and long-term usability.
Large differences between proposal structures can create confusion across teams and locations.
Best Practice
Standardize categories, naming conventions, and proposal structures whenever possible.
Have The Right Person Configure QuoteSter
The person configuring QuoteSter should understand proposal workflows, pricing structures, estimating processes, service categories, and day-to-day usage.
Configuration is operational setup, not just technical setup.
Best Practice
Use someone who regularly works with proposals or estimating workflows.
Understand Current ClientTether API Limitations
ClientTether currently supports updating the primary proposal for a customer through the API.
QuoteSter cannot yet create multiple completely separate proposals for the same customer through the API.
ClientTether also does not currently allow QuoteSter to pull proposal templates directly through the API.
Best Practice
Confirm which proposal should be updated before beginning work, and focus on building strong operational workflows instead of depending entirely on templates.
Summary
QuoteSter performs best when proposal workflows are organized, line items are reviewed carefully, configuration is kept clean, and teams follow consistent operational standards.
Strong configuration practices help create faster proposal generation, better consistency, reduced mistakes, and cleaner long-term workflows.