Requesting Good Plans

Use this guide to ask for HubSpot changes that produce clear, reviewable write plans.

Name The Portal And Goal

Start with the target portal and the business outcome. Good requests say what should change, why it should change, and how the user will know the result is correct.

Example request shape:

• Target portal or customer account.
• HubSpot area, such as contacts, deals, lists, reports, workflows, or properties.
• Desired outcome in plain language.
• Existing assets to reuse or avoid.
• Any names, filters, owners, dates, stages, or records that must be exact.

Scope The Change

Narrow requests are easier to review. Ask for one workflow, one report, one list, or one schema change when possible. For larger work, ask for a first draft that creates foundations before adding automation or broad edits.

For records and assets, include the exact names users expect to see in HubSpot. For filters, include the business rule in words and any known property names.

Handle Destructive Work

For delete, archive, merge, or broad update requests, state the safety rule clearly. Ask the assistant to identify the target asset, explain why it matches, and avoid destructive changes unless the plan is easy to verify.

If the plan contains a destructive operation that was not requested, reject it and ask for a revised draft.

Ask For Revisions

A rejected plan is a normal part of the workflow. Ask for a revision when the plan targets the wrong portal, uses the wrong assets, asks for unexpected permissions, or solves a broader problem than requested.

When asking for a revision, name the exact part of the draft that should change. This helps the next plan stay close to the original intent.

Review Before Execution

Treat every generated plan as a draft. The final check happens in Daeda AI: portal, title, description, operations, warnings, missing permissions, bridge status, and affected records.