Write a complete customer business problem for your AWS co-sells with Tackle’s template builder in Field Mapper for AWS, and in any co-sell that has a generated or manually created business problem statement.
Tackle analyzes customer business problems across nine elements, generating a quality score (Weak, Fair, Good, or Strong) with insights to help you understand what is missing and what needs to be improved.
Note: The score generated by this evaluation is not the Amazon Web Services (AWS) Opportunity Quality Score. Complete detail can support a stronger opportunity quality score, but a score alone does not guarantee AWS Field-Engaged status—strategic fit still matters.
Before you begin
There are two ways to evaluate the quality of your customer business problems: in Field Mapper for AWS co-sells, and in each individual co-sell. In Field Mapper, you can configure and evaluate the template that Tackle uses to auto-create co-sells. The AWS co-sell form lets you evaluate the customer business problem on that deal.
Entry point | Who uses it | What you edit | Access | Scope of impact |
Field Mapper for AWS co-sells | An administrator configuring mappings | The Customer Business Problem template | Settings > Field Mapper | Every new AWS co-sell created from Salesforce after you save the template and publish the mapping |
AWS co-sell form | A seller working one opportunity | The generated customer business problem on that co-sell | Create or edit an AWS co-sell in Tackle Platform or Tackle for Salesforce | That co-sell only. It does not change the shared template or other deals |
Configure the Customer Business Problem template in Field mapper
Use this path if you are an administrator and want every new AWS co-sell auto-created by Tackle to start from a complete customer business problem.
What you are editing | Who can do this | What it affects |
The Customer Business Problem template used by Tackle to auto-create co-sells | An administrator configuring Field Mapper for AWS | Every new AWS co-sell created by Tackle co-sell automation |
Open the template in Field Mapper
In Tackle, go to Settings > Field Mapper > Co-Sell > AWS.
Scroll to the Customer Business Problem row.
Click Edit Template. The Customize template panel opens to show the current template in an editor.
Write the template
The Customer Business Problem field supports a text-based description up to 2,000 characters long. You can insert Salesforce fields so that Tackle uses data from the opportunity when the co-sell is created. Salesforce fields appear as a blue path, for example Opportunity > Account > Account Name.
For additional guidance, open the Template Tips tab to see the elements that AWS looks for. For complete customer business problem examples, open the Examples tab.
Nothing you change here is saved until you select Save. Closing the panel without saving leaves the existing template as it was.
Test the template against a Salesforce opportunity
Before you save, test the shared template against a real opportunity in your customer relationship management (CRM) tool so you see the paragraph exactly as Tackle generates it for that deal, including resolved Salesforce fields.
In the Customize template panel, select Test, and choose a Salesforce opportunity to test (search by opportunity ID, name, or keyword).
Review the generated customer business problem. Confirm Salesforce fields resolved to real values, and that the result reads as one specific customer story.
Use the Tackle quality scorecard to understand what is missing or too generic so you can edit before you save. The scorecard generates an overall score (Weak, Fair, Good, or Strong) and flags missing or generic elements.
Select Edit template to make changes to your template. The scorecard remains visible as you edit.
Fix the weakest elements first: named customer, customer problem, quantified impact, and why now. Then add evaluation criteria, decision process, competition, and the approver or champion.
Re-test after you edit. The scorecard updates from the latest template that you tested.
Save and publish the template
When you are ready to save your Customer Business Problem template, select Save in the Customize template editor.
Select Publish in Field Mapper when you are ready for new AWS co-sells to use the template. For more on mapping, see Map your Salesforce fields.
Existing co-sells keep what they already have. A seller can still improve one co-sell without changing this template
Improve the Customer Business Problem on one AWS co-sell
Use this path if you are a seller and need a complete Customer Business Problem on one deal.
What you are editing | Who can do this | What it affects |
The generated or manually entered Customer Business Problem on this co-sell | Sellers who can create or edit an AWS co-sell opportunity | The Customer Business Problem on this co-sell only. It does not change the shared Field Mapper template or other deals. |
Evaluate the Customer Business Problem
Open or create an AWS co-sell opportunity.
Go to the Customer Business Problem field. You can modify it or enter a new one directly in the form
Note: The APN Customer Engagements (ACE) limit for this field is 2,000 characters.
Click Evaluate to have Tackle analyze and generate a score.
Select View analysis to view the Tackle quality scorecard with insights about what is missing or generic. The scorecard generates an overall score (Weak, Fair, Good, or Strong) and flags missing or generic elements.
Fix the weakest elements first: named customer, customer problem, quantified impact, and why now.
Then add evaluation criteria, decision process, competition, and the approver or champion.
Evaluate the Customer Business Problem as many times as you need. The scorecard updates with each evaluation.
When you are ready to save the co-sell with your Customer Business Problem, select Save as Draft to save and continue working or Submit to send the co-sell to AWS.
What AWS looks for
Use these nine elements when you write the shared template or when you improve one co-sell. This reference material is available in both the Customer Business Problem template in Field Mapper for AWS, and the AWS co-sell form.
Template tips
Open the Template tips tab to see what AWS looks for, one element at a time, with a definition and common mistake for each.
Element | What to include | Common mistake |
Named customer | Name the company. Insert Account Name with @ so it appears on every co-sell. | Leaving the customer unnamed or using a placeholder that never resolves. |
Customer's problem | What is broken or slow today: a system, process, or situation in the customer's terms. | 'Needs better security' is too generic. A product pitch with no customer problem does not count. |
Quantified impact | One number that sizes this customer's problem or scale: cost, hours, users, or volume. | The co-sell amount and license quantity do not count. |
Why now | A forcing event with timing: contract end, audit, outage, mandate, migration deadline, new leadership, or budget cycle. | 'Urgent' is not enough. A close date says when, not why. |
Expected outcome | The result this customer expects. A numeric target is ideal; a specific operational result is enough. | 'Improve reliability' is too generic. |
Evaluation criteria | How this customer will choose a solution (requirements, constraints, or must-haves). | Leaving criteria unstated or copying generic product features. |
Decision process | The reviews, proof, or steps that must finish before they buy. | Omitting process or listing only an internal close date. |
Competition | What they are replacing or comparing, including an in-house option if that is in play. | Saying there is no competition when a status-quo or build option exists. |
Approver or champion | Who owns the budget or is sponsoring the work. | A title with no named role, or no owner at all. |
Complete examples
The Examples tab includes two sample paragraphs. Use them to see the structure of a complete customer business problem: a named customer, a specific problem, one number, a forcing event with a date, written criteria, a decision process, competition, and an owner.







