THE SHORT ANSWER
Price the exact site for year one and renewal year, including required add-ons and exit work. Choose only after testing the publishing workflow and confirming what can be exported.
BEFORE YOU READ
Who this research is for
Read now
- You need to make the decision described here using current primary sources
- You want a repeatable test rather than a universal product ranking
Check something else first
- You need individualized legal, tax, medical or security advice
- You are looking for a guarantee that a tool or course will produce a particular outcome
KEY POINTS
What matters most
- 01
Introductory and renewal prices can differ
- 02
Required apps, payments and collaborators can exceed base-plan cost
- 03
Export and migration constraints are part of total cost
DECISION TABLE
Total-cost components
| Component | Year-one question | Renewal or exit question |
|---|---|---|
| Base plan | Discounted or standard? | Renewal price |
| Domain | Included for how long? | Transfer and renewal |
| Included or separate? | Per-user cost | |
| Apps | Which are required? | Recurring app fees |
| Payments | Percentage and fixed fees | Refund and payout cost |
| Collaborators | Seats included | Extra-seat pricing |
| Export | What can leave? | Migration labor |
ACTION PLAN
Turn the comparison into a four-step decision
Use one real, low-risk task and record the evidence. The goal is a decision you can reproduce and reverse—not a one-time impression.
- 01
Fix the task and constraints
Write the input, desired output, frequency and unacceptable failure. Start from this criterion: Introductory and renewal prices can differ
- 02
Verify the current primary sources
Open the 3 listed sources, confirm the account, region and retrieval date, and note any unresolved conflict.
- 03
Run the decision table
Replace every example with your own volume, time and required condition. Record manual work that remains after using the product or process.
- 04
Set a review trigger
Keep the decision with its assumptions. Review when pricing, terms, workload or the required data changes; reverse it if the named benefit does not appear.
WORKED EXAMPLE
Worked example: make assumptions visible
This is a structure for your own test, not a performance promise. Replace each value or condition with observed data.
- Base plan
- Discounted or standard? → Renewal price
- Domain
- Included for how long? → Transfer and renewal
- Included or separate? → Per-user cost
- Apps
- Which are required? → Recurring app fees
What this example showsPrice the exact site for year one and renewal year, including required add-ons and exit work. Choose only after testing the publishing workflow and confirming what can be exported.
Specify the site before selecting a plan
List pages, forms, CMS records, traffic, collaborators, languages, commerce and integrations. Plan names are not comparable until the required capability is fixed.
A portfolio, booking site and content publication can need different tiers on the same builder.
Calculate year one and renewal separately
Promotions, free domains and annual billing discounts can make the first invoice unusually low. Record the standard renewal for every component.
Add email, paid templates, apps, payment fees and extra users. Use a realistic traffic and sales scenario rather than the minimum advertised price.
Test the editorial workflow
Create, review, schedule, update and archive sample content. Check mobile controls, permissions, backups and staging or preview behavior.
A builder that is fast for the first page can still create recurring labor when many articles or localized pages are added.
Confirm the exit path
Document export formats for content, images, form submissions and domain settings. Confirm whether custom code or design elements can move.
Estimate migration labor and downtime. Even if you never switch, exit clarity is evidence of how much operational control you retain.
COMMON PITFALLS
Where decisions go wrong
Treating a plan label as an outcome
A paid tier or popular product does not guarantee accuracy, completion or return. Test the final deliverable and the review work that remains.
Skipping the applicable source
We compare official pricing, domain and help documentation using a two-year total-cost and exit checklist.
Ignoring what can change
Prices, promotions, tax, features and domain conditions change by country and billing cycle.
DECISION NOTE
Decision record to keep
Record the use case, selected option, rejected alternative, decisive condition, source check date and review trigger. Current conclusion: Price the exact site for year one and renewal year, including required add-ons and exit work. Choose only after testing the publishing workflow and confirming what can be exported.
CLAIM → SOURCE
Claims and supporting sources
Each central claim points to a primary or public source reviewed for this article.
Introductory and renewal prices can differ
Required apps, payments and collaborators can exceed base-plan cost
Export and migration constraints are part of total cost
FAQ
Frequently asked questions
What is the short answer?
Price the exact site for year one and renewal year, including required add-ons and exit work. Choose only after testing the publishing workflow and confirming what can be exported.
How was this comparison built?
We compare official pricing, domain and help documentation using a two-year total-cost and exit checklist.
What should I verify before acting?
Prices, promotions, tax, features and domain conditions change by country and billing cycle.
METHODOLOGY
How this article was researched
We compare official pricing, domain and help documentation using a two-year total-cost and exit checklist.
Read the shared editorial method ↗SOURCES