Revenue Enablement report
Mutual Action Plan Generator: your result
This answer uses a made up example company. Change the details above and press Run to see your own result.
Mutual Action Plan Generator
For account executives near the close. The decision: what has to happen, by whom and when, for the deal to sign on time?
Give it the deal name and the target close date, and get a close plan with stakeholders, success criteria, dated phases, risks and a communication plan.
Count the working days from today to your target close date, then assign owners and due dates across Evaluation, Business Case and Alignment, Commercial and Legal, Procurement, and Close and Launch, with blocker milestones in Mutual Action Plan Generator.
This sample is a made up example, built from the inputs behind Fill in an example. It shows part of one section of the answer.
Show on the buyer's own case that the criteria are met, and start the reviews that take longest.
| # | Milestone | Owner | Due Date | Status |
|---|---|---|---|---|
| 1 | Choose the team and the real project or workflow for the trial, and agree the baseline and the measure before it starts | Both teams | 2026-11-04 | Pending |
| 2 | Connect the tools the trial must work with and set up the first users | Buyer IT reviewer with Seller (solutions engineer) | 2026-11-06 | Pending |
| 3 | Run the trial on that work and check use every week | Buyer champion | 2026-11-10 | Pending |
| 4 | Review the result against the baseline and agree what the rollout covers and in what order | Both teams | 2026-11-12 | Pending |
See the full example answer or run it with your own details.
Revenue Enablement report
This answer uses a made up example company. Change the details above and press Run to see your own result.
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
What next? Work with Shashwat Try another tool See all 85 tools and skills
Generated on 2 November 2026 from this branch, with the inputs behind Fill in an example. Your own inputs give a different result.
Revenue Enablement report
This plan takes the deal "logistics account expansion" from the evaluation stage to a signed contract on 2026-12-15: 31 working days from 2026-11-02, 43 calendar days. The seller is offering our product. The buyer works in logistics, read from the deal name.
Sector: not clear from your inputs (name the industry for sector notes). Business model: not stated. Tell us how you charge and the plan will adjust.
On the seller side the account executive owns the deal and the plan, a solutions engineer owns the technical validation, and an executive sponsor is called in at the phase gates and for escalation.
Until the buyer names what they will judge the deal by, the evaluation has no pass mark.
Show on the buyer's own case that the criteria are met, and start the reviews that take longest.
| # | Milestone | Owner | Due Date | Status |
|---|---|---|---|---|
| 1 | Choose the team and the real project or workflow for the trial, and agree the baseline and the measure before it starts | Both teams | 2026-11-04 | Pending |
| 2 | Connect the tools the trial must work with and set up the first users | Buyer IT reviewer with Seller (solutions engineer) | 2026-11-06 | Pending |
| 3 | Run the trial on that work and check use every week | Buyer champion | 2026-11-10 | Pending |
| 4 | Review the result against the baseline and agree what the rollout covers and in what order | Both teams | 2026-11-12 | Pending |
| 5 | Security and compliance review of the vendor and its data handling | Buyer security reviewer | 2026-11-16 | Pending |
| 6 | Reference calls with similar our product customers (only if one has agreed) | Buyer champion | 2026-11-17 | Pending |
Put the result in a business case the economic buyer can approve, and answer every open question in writing.
| # | Milestone | Owner | Due Date | Status |
|---|---|---|---|---|
| 1 | Present the business case, built from the buyer's own figures, to the economic buyer | Seller (account executive) | 2026-11-19 | Pending |
| 2 | Check the cost and value figures with the finance contact | Buyer finance contact | 2026-11-20 | Pending |
| 3 | Agree the commercial shape of the deal: the scope, the term and the price | Seller (account executive) | 2026-11-24 | Pending |
| 4 | Confirm in writing that no question is left open | Both teams | 2026-11-25 | Pending |
Settle the terms and the legal text.
| # | Milestone | Owner | Due Date | Status |
|---|---|---|---|---|
| 1 | Turn the commercial shape agreed in the business case phase into contract terms and send the draft to the buyer's legal and procurement teams | Both teams | 2026-11-27 | Pending |
| 2 | Complete the legal review and resolve the redlines | Buyer procurement and legal | 2026-11-30 | Pending |
| 3 | Confirm the implementation timeline and the owners on both sides: the access, the integrations and the first users | Both teams | 2026-12-02 | Pending |
| 4 | Obtain the economic buyer's approval of the contract terms | Economic buyer | 2026-12-03 | Pending |
Complete the buyer's purchasing steps.
| # | Milestone | Owner | Due Date | Status |
|---|---|---|---|---|
| 1 | Complete vendor registration and submit the documents the buyer's process asks for | Buyer procurement and legal | 2026-12-07 | Pending |
| 2 | Finalize the payment terms | Buyer procurement and legal | 2026-12-09 | Pending |
| 3 | Complete the purchasing approvals: the purchase order and the budget code | Economic buyer | 2026-12-11 | Pending |
Sign, and agree how the first weeks run.
| # | Milestone | Owner | Due Date | Status |
|---|---|---|---|---|
| 1 | Contract signed | Economic buyer | 2026-12-14 | Pending |
| 2 | Kickoff scheduled, with the owners and the dates confirmed in the commercial phase | Both teams | 2026-12-15 | Pending |
| 3 | Success criteria written down | Seller (account executive) | 2026-12-15 | Pending |
| Cadence | Participants | Purpose |
|---|---|---|
| Weekly | Buyer champion and the account executive | Progress against the table above and the open questions |
| Every two weeks | The buyer's technical evaluators and the solutions engineer | Progress of the tests |
| At each phase gate (2026-11-17, 2026-11-25, 2026-12-03, 2026-12-11) | Economic buyer and the executive sponsor | Decisions and the next phase |
Escalation runs from the buyer's champion to the economic buyer first; if that does not clear it, the seller's manager goes to the buyer's executive.
| Priority | Action | Owner | Due |
|---|---|---|---|
| High | Find and confirm the champion | AE | 2026-11-03 |
| High | Find out who signs, and ask for that person by name | AE | 2026-11-04 |
| Medium | Share this plan with your main buyer contact | AE | 2026-11-02 |
| Medium | Ask which buyer step takes longest and start it now | Both | 2026-11-05 |
This only works as a mutual plan once the buyer has corrected the dates and the owners; update it as things change.
To sharpen this plan, give:
buyer champion (it would change who keeps the plan alive on the buyer's side and owns the first meetings)economic buyer (it would change who approves the business case and owns the final approvals)technical evaluators (it would change the owners of the technical and security steps, which now use roles)procurement contact (it would change the owner of the legal, vendor registration and payment steps)known requirements (it would change the criteria table, now empty, into one row for each with a test)known process steps (it would change the milestones, which would then include the buyer's own approvals with dates)blockers (it would change the Risks & Blockers table, which would then answer each one)Last updated 2026-11-02.
How the answer is laid out, using the sections the tool prints. Both teams work through the four phases together.
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
The generator works backward from your Target close date (moving a Saturday or Sunday date to the Friday before) and counts both working days and calendar days from today across five phases: Phase 1: Evaluation, Phase 2: Business Case & Alignment, Phase 3: Commercial & Legal, Phase 4: Procurement, and Phase 5: Close & Launch. It prints Key Stakeholders, Success Criteria (noting that the evaluation has no pass mark until the buyer names what they will judge the deal by), dated milestone tables, Risks & Blockers, a Communication Plan, and Next Actions (This Week). Treat this as a draft to share with your buyer champion: it only becomes a real mutual action plan once the buyer corrects the dates, process steps, and owners on their side.
Re-run the generator as soon as the buyer shares their Buyer champion, Economic buyer, Technical evaluators, Procurement contact, Known requirements, and Known process steps so every milestone carries a real name and buyer-confirmed date. The tool applies the same fixed rules every time. It does not call an AI model, and this site does not keep what you enter.
Add Revenue Enablement once (see Use it in Claude, ChatGPT or Gemini), then ask in plain words. Here is a prompt built from the tested example:
My role is not stated. Ask me for my role first. Use Revenue Enablement's Mutual Action Plan Generator tool. deal name: logistics account expansion; target close date: 2026-12-15; current stage: Evaluation; your solution: our product. If this tool is unavailable, ask me to open its web page; do not invent its output. In Gemini CLI or Antigravity, use the Helix GTM Suite skills package for related guidance, without claiming to run this connector.
You do not need to sign in. A web browser is enough, and the answer comes back in a second or two.
It applies fixed rules in the Revenue Enablement code to the inputs above and returns text. It does not call an AI model, does not look anything up, and does not store what you type. The web form and the AI assistant connector run the same tool code, so the same input gives the same answer in both.
MCP tool name: mutual_action_plan_generator. REST: POST https://revenue-enablement.gtmhelix.com/api/tools/mutual_action_plan_generator with this JSON body (see How it works):
{
"input": {
"deal_name": "logistics account expansion",
"target_close_date": "2026-12-15",
"current_stage": "evaluation",
"your_solution": "our product"
}
}
Run a Helix tool in your browser, then take the result to ChatGPT, Claude or Gemini. Connectors work with supported plans in Claude, ChatGPT, Cursor, VS Code and Windsurf. The Helix GTM Suite skills package supports Claude Code, Gemini CLI, Antigravity, Cursor and VS Code, and is available through skills.sh. Each plugin has its own installation steps, below or on its own page.
Connector setup guides · Skills package setup guide · Find the skills on skills.sh