AI agent team guide
AI Proposal Agents: Turn Discovery Into a Reviewable Offer
An evidence-linked proposal with scope boundaries and a buyer decision path

An AI proposal generator is only as useful as the discovery it receives. Start with what the customer actually asked for, the outcome you can support and the boundaries your team can honor. A four-agent proposal desk can turn that material into a clear draft while keeping prices, delivery commitments and acceptance with the people authorized to make them.
Sales Proposal Writer owns the draft, Sales Account Planner supplies the customer context, Pricing & Packaging Analyst compares stated assumptions and Mutual Action Planner reconciles the proposed next steps. Use the team to make an offer easier to evaluate, not to generate unsupported commercial promises.
Build your four-agent team
| Agent template | Its job on the team | Bring to its setup | Reviewable return | Team |
|---|---|---|---|---|
Sales Proposal WriterLead agent | Map accepted discovery into the proposal. | Approved notes, actual scope, exclusions and customer requirements. | A reviewable offer draft with open factual and commercial questions. | Add to team |
Pricing & Packaging AnalystSupporting agent | Compare explicit packaging and pricing assumptions. | Authorized price options, supplied cost assumptions and relevant customer evidence. | Transparent scenarios and approval questions, not invented discounts or margins. | Add to team |
Mutual Action PlannerSupporting agent | Reconcile the proposed decision path. | Documented next steps, dependencies and owners actually accepted. | A draft action plan distinguishing proposals from agreed commitments. | Add to team |
Sales Account PlannerSupporting agent | Preserve the customer’s decision context. | Confirmed needs, stakeholders and discovery evidence. | A concise account brief that explains why the proposed scope is relevant. | Add to team |
Set up your team in Finta
- Add each template individually. Use the Add to team action for each named coworker, review the import setup and complete its Getting Started skill.
- Give each role the right context. State the shared objective, then supply the authorized documents, notes or exports that role needs. Do not assume an unconnected system is available.
- Review the handoff. Accept or correct one return before giving its evidence and open questions to the next coworker. Importing four templates does not itself run a bulk team.
- Make recurrence deliberate. Complete a useful manual pass first. Review any supported routine and enable it only when the scope, inputs and permissions are right.
Prepare the evidence
- Customer-approved or accurately attributed discovery notes.
- Deliverables, exclusions and acceptance criteria your team can actually support.
- Authorized commercial inputs and a named pricing approver.
- The documented customer decision process and any genuinely agreed next steps.
Run the workflow
1. Reconcile the problem before the offer
Have Account Planner distinguish confirmed needs from seller assumptions. A request for reporting clarity is not permission to promise a complete systems replacement. Identify the specific problem the draft is meant to address.
2. Make scope observable
Ask Proposal Writer for deliverables and acceptance conditions that a reviewer can understand. Preserve exclusions and dependencies. Separate a proposed delivery date from a date the delivery owner has accepted.
3. Expose commercial assumptions
Give Pricing & Packaging Analyst only authorized options. Show the assumptions behind a comparison and leave unknown costs unknown. The commercial owner reviews the final price, payment language and any material terms using the appropriate approval process.
4. Make the next step genuinely mutual
Mutual Action Planner compares proposed milestones with the actual notes. A customer has not agreed merely because a seller wrote their name beside a task. Return a draft for review, then record the actions and approvals that actually occur.
A fictional proposal scope-to-decision matrix
This invented service example demonstrates structure. It is not a Finta price, contract or delivery commitment.
| Customer need | Proposed scope | Approval or dependency |
|---|---|---|
| A consistent handoff between two teams. | One documented handoff example and a review session. | Confirm the participating owners and available source material. |
| A clear definition of completion. | An accepted example identifies owner, required context and next step. | Customer and delivery owner must agree the acceptance condition. |
| A commercial option. | Use the organization’s actual approved price schedule. | No price is supplied in this example; do not invent one. |
| A next decision. | Review scope and unresolved questions in a follow-up. | The meeting and participants remain proposed until confirmed. |
A stronger proposal makes the decision clearer. It does not hide unknowns behind polished formatting or treat a draft as an agreement.
Copy the team brief
Prepare a reviewable proposal for [customer decision].
Use [accepted discovery], [approved offer and exclusions], [authorized commercial inputs] and [documented next steps].
Account Planner: summarize confirmed needs and open assumptions.
Proposal Writer: draft scope, deliverables, acceptance and exclusions.
Pricing Analyst: compare only supplied options and disclose assumptions.
Mutual Action Planner: distinguish proposed milestones from accepted commitments.
Return the draft, factual questions, required approvers and next decision.
Do not invent prices, guarantees, signatures, delivery capacity or agreement. Do not send or accept terms.Review the return
- The offer maps to confirmed needs and bounded deliverables.
- Commercial and delivery commitments have the appropriate actual approval.
- Proposed, sent, accepted and signed are different states.
Questions before you start
Can this produce a final contract?
This workflow prepares a customer proposal, not legal advice or a signed agreement. Any binding terms require the organization’s appropriate review and authorized acceptance.
Should every proposal include several price options?
Only when actual approved options help the customer decide. Do not manufacture tiers or discounts simply to fill a proposal template.
Sources and next steps
This playbook uses the current published Finta marketplace packages linked in the team table. Open each profile to review its instructions, context, Skills and any routines before importing.