Framer cost planning: Site plans, editors and languages

Scope each published site

A small service page and a continually growing case-study site may need different CMS structures. List pages, collections, bandwidth assumptions and forms for each site before matching a plan. Base the first-year budget on the work actually planned, rather than every feature that might someday become useful.

Convert the displayed equivalent

The verified table displays Basic at a USD 10 monthly equivalent under annual billing. Under that stated assumption, the base annual amount is 10 × 12 = USD 120. This excludes other charges and taxes. Do not reuse the annual equivalent as the price of a month-to-month subscription.

Count roles rather than logins

Distinguish the owner, people who change design and people who only update content. Official Site guidance describes editor-role pricing differences. Instead of sharing credentials for occasional work, verify the least access that lets each contributor complete the job and include its incremental cost.

Inventory localization and extras

A Japanese-English site requires both editorial translation work and a check of localization entitlements. Add external booking, selling or email subscriptions if the project relies on them. Label mandatory and optional items so optional add-ons do not quietly become assumed launch requirements.

Choose a budget review trigger

Revisit the budget when content volume, observed traffic, editing roles or language count exceeds the original assumptions. It is unnecessary to compare every plan on every update. Defined review triggers make the boundary between project work and recurring publishing costs easier to manage.

Scope a bilingual two-editor estimate

For a Japanese-English company site edited by communications and a designer, inspect site, language and role requirements independently. Establish whether both people change design or one only edits content. Record the actual entitlement rather than assuming that two people simply double the base fee.

First-year work may also include domain configuration and initial translation that are not recurring platform charges. Separate first and subsequent years to keep implementation work distinct from renewals and continuing editorial updates.