- 0:00–0:06
List the pages you need • Start with a concrete page list. • Service pages • Example list • 3 service pages • 3 articles
Three service pages and three articles are an illustrative inventory, not a plan allowance.
- 0:06–0:12
Group pages by layout • Separate service layouts from article layouts. • Content still needed • Service layout • Article layout • Service pages • Articles
Pages move into their two matching layout families; reusing a layout does not remove the need for content.
- 0:12–0:18
Define both language versions • Plan Arabic and English together. • Service layout • English • Arabic • Layout
A layout branches into separately labelled English and Arabic versions with corresponding direction; no automatic translation is implied.
- 0:18–0:24
Name the system connection • State what the form must do. • Form • CRM • Proposed connection • Connection scope • API docs
A form is connected to the named CRM; a documentation card joins that connection as a scope input, not a completed integration.
- 0:24–0:30
Compare the same scope • Separate build, running costs and extras. • Layouts, languages, link • Build • Running costs • Extras • Agreed scope
The agreed scope moves into the build column while running costs and extras stay distinct; no price or sum is invented.
A silent example groups pages into layouts, identifies two language versions and a CRM connection, then separates the build scope from running costs and extras.
Read the article: How Much Does a Website Cost in Saudi Arabia? Prices by Scope