01 / START HERE
A useful way to approach it.
Two offers priced at the same amount may cover different work. One might include three active projects, while another charges for each project. Before comparing prices, define the customer's intended use and read the package boundaries. The useful output is a clear description of what a buyer receives under the same scenario, not a verdict based on the largest number on a pricing page.
This guide analyzes accessible public offers at a point in time. It does not promise ongoing price monitoring or reveal negotiated customer rates. Supply the relevant pages or retrieve them with enabled web search in signed-in o1, then confirm their terms yourself. All names, prices, and quantities in the worked table are fictional.
02 / THE PROCESS
Go from question to next step.
- 01
Define the buyer and usage scenario
Specify who is buying, how many people or projects they need, which features are essential, and the comparison period. Keep currency and region explicit. A price comparison for one person using two projects can produce a different result from a team sharing ten projects; neither scenario is automatically representative of all customers.
- 02
Capture the full published offer
Record the plan name, price, billing unit, included allowance, overage terms, stated exclusions, and access date. Note introductory discounts and whether the price depends on annual commitment. Link the relevant terms as well as the pricing page. When a condition is not visible, leave a clear question instead of filling it from memory.
- 03
Normalize comparable quantities
Translate each offer into the same scenario while preserving important distinctions. For example, separate per-seat charges from per-project limits and mandatory setup fees from recurring fees. Show the formula so someone can recalculate it. A monthly equivalent can aid comparison, but it should not erase an annual purchase commitment or cancellation condition.
- 04
Explain packaging and positioning
Compare how each offer bundles features and limits. Identify the customer described by the published package, the tradeoff it creates, and which information is still missing. Treat claims such as 'best value' as positioning language. Do not infer margins, actual customer spend, or price sensitivity from the public offer alone.
- 05
Choose a question for your own offer
Use the comparison to clarify your packaging, not mechanically match the cheapest competitor. Ask whether your customer understands the included work and whether your own constraints are clear. Validate proposed changes with evidence from your business and customers. Save the dated comparison and revisit the source pages before treating the information as current.
03 / YOUR STARTING POINT
A prompt you can make your own.
Replace the bracketed fields. Add only information you have permission to share. This is a reusable text prompt; it does not run a task from this page.
Analyze these public competitor offers for {{buyer}} needing {{usage}} over {{period}} in {{currency_and_region}}: {{sources}}. Record plan name, billing unit, commitment, included work, limits, stated exclusions, and access date. Normalize the same scenario with explicit formulas. Separate published facts, assumptions, and unknowns. Do not invent prices, negotiated discounts, margins, or buyer preferences. Explain how the packages differ and list the conditions I should verify before using this comparison to revise my offer.04 / SEE THE SHAPE OF IT
Illustrative package normalization
Fictional offers, prices, and usage. These are authored arithmetic examples rather than a current competitor price report.
| Fictional package | Two-project scenario | Package boundary |
|---|---|---|
| Elm: $30 each month | $30 for two active projects | Three active projects included |
| Pine: $18 per project each month | 2 × $18 = $36 | Each extra project adds a charge |
| Elm: annual offer | $300 annually; $25 monthly equivalent | Annual commitment remains visible |
| Pine: setup | No setup price supplied | Unknown; do not assume zero |
The model compares equal usage while showing the annual commitment and missing setup information. It does not establish which offer a real customer should choose.
05 / KEEP YOUR JUDGMENT
What to watch before you use it.
Ignoring billing units
Seat, project, account, and usage charges are not interchangeable. Retain the unit in every price row.
Treating a discount as a permanent price
Record introductory eligibility and duration. Keep a regular published price separate when the source provides one.
Inferring business economics
Public prices alone do not establish profit, customer willingness to pay, or sales performance. Those require different evidence.
06 / THE FINAL PASS
A little review goes a long way.
Your checks stay on this page. They do not approve or run a task.
07 / GOOD QUESTIONS
Before you begin.
Does a lower price mean better value?
Value depends on the required outcome, included work, constraints, and the buyer's priorities. First compare equivalent usage and essential requirements. A cheaper offer can be unsuitable if its package omits something the customer needs.
Can AI keep this comparison current automatically?
This guide describes a point-in-time research task. Reopen the sources when you need a current comparison. Do not assume the prompt establishes a monitoring service, a scheduled refresh, or notification behavior.
What if a competitor does not publish a price?
Mark the price as unpublished or unavailable in the reviewed material. You can compare other documented package conditions and prepare a question for the vendor. Do not invent an estimate and present it as the competitor's actual rate.