DIRECT ANSWER
Five factors make a website project more complex: the number of distinct customer journeys, the depth of content to research and approve, the interactive tools, the integrations with other systems and the technical requirements such as migration and accessibility targets. Each factor scales independently, and the one that changes the work most is the scope driver. Page count alone describes little of this.
Key terms
- Project complexity
- The amount and difficulty of the work a website requires, described by five factors: customer journeys, content depth, interaction, integrations and technical requirements.
- Complexity factor
- One of the five dimensions of project complexity, each of which can be lower, middle or higher independently of the others.
- Scope driver
- The complexity factor that changes the work most for a particular project, and the first one to specify in writing before quoting.
- Customer pathway
- The route one kind of visitor takes through a website, from the page where they arrive to a next step with the business. Full entry: How Many Customer Pathways Does Your Website Need?
Five factors that shape scope
Two websites with the same number of pages can require very different amounts of work. Page count describes how many containers a site has, which is why it misleads in proposals. Project complexity describes what has to be planned, written, built and tested inside them. Five factors account for most of the difference.
| Factor | Lower complexity | Middle | Higher complexity |
|---|---|---|---|
| Distinct customer journeys | One kind of visitor with one next step | Several customer pathways that share pages and a form | Many pathways, with self-selection, overlapping customer types and routing |
| Content depth | A few pages of facts the owner already has | Service pages plus a handful of researched guides | A full Knowledge Catalog with sources, tables and professional review |
| Interaction | Links and a simple form | Guided intake or a short self-assessment | Calculators, configurators, account areas or multi-step transactions |
| Integrations | Links to outside tools | Embedded outside tools, such as booking or ordering | Data synchronized between systems, such as inventory or listings |
| Technical requirements | A new site with no history | A redesign that preserves existing pages and addresses | Migration of many URLs, regulated requirements, several languages or large media libraries |
Each factor scales on its own. A site can be simple in four factors and complex in the fifth, and that fifth factor is often the scope driver: the one that changes the work most.
Why each factor adds work
Customer journeys. Each distinct pathway needs its own entrance, its own answers and a tested route to its next step. Overlapping customer types add routing and cross-links, as described in serving several customer types.
Content depth. Content is research, writing, fact approval and review, and only then a page. A catalog entry that cites sources and passes professional review takes far longer than a page of copy the owner dictates. Google's people-first content guidance asks whether content gives a substantial, complete description of its topic [4], and meeting that standard is work.
Interaction. Every interactive tool needs written logic, test cases and a defined result for every input, including wrong ones. Interactions that create a legal commitment or a financial transaction carry added requirements: WCAG 2.2 asks that such submissions be reversible, checked for errors or confirmed before they are final [3].
Integrations. A link, an embed and a synchronized integration are different kinds of work with different failure modes, as covered in links, embeds and integrations. Synchronized data depends on the outside provider's access, terms and reliability, and someone has to own the connection after launch.
Technical requirements. Replacing an existing site means mapping every old address to its new one and redirecting it. Google's guidance on site moves asks for a mapping of old to new URLs, permanent redirects kept in place for at least a year and monitoring afterward, and notes that rankings may fluctuate for weeks while the site is reprocessed [1]. Accessibility targets add their own testing: WCAG 2.2 assigns each of its success criteria to level A, AA or AAA [2], and the target level shapes what is checked. The redesign side is covered in what to preserve during a redesign.
Reading a complexity profile
A complexity profile records the level of each factor for one project. It is more useful than a single label because it shows where the work concentrates and where questions need answers before anyone quotes. A profile with one high factor calls for that factor to be specified in writing first: the pathways mapped, the content inventory listed, the tool logic defined, the provider's access confirmed or the URL map drafted.
The profile describes work, and it sets no price. How any provider turns scope into a price belongs in its written proposal.
Applications
An auto repair shop
Illustrative example. An independent auto repair shop needs one main pathway, booking a service appointment, with a second for drivers who need a tow or urgent help. Content is a handful of pages the owner can verify quickly. The booking tool the shop already uses can be embedded. The current site is small and has few pages worth preserving.
| Factor | Level | Note |
|---|---|---|
| Customer journeys | Lower | Two pathways, one shared contact path |
| Content depth | Lower | Facts the owner already has |
| Interaction | Lower | A simple form for urgent requests |
| Integrations | Middle | The existing booking tool, embedded |
| Technical requirements | Lower | A small site with little to migrate |
The scope driver is the booking embed: confirming it works on phones and fits the shop's pathway is the part of the project that needs specifying first.
A boat dealer
Illustrative example. A boat dealer sells new and used boats, services engines and rents storage. Buyers of new and used boats, service customers and storage tenants follow different pathways. Inventory changes daily and lives in the dealer's management system. The current site has several hundred inventory and article pages that receive visitors from search.
| Factor | Level | Note |
|---|---|---|
| Customer journeys | Higher | Four pathways with overlapping customers |
| Content depth | Middle | Model and service pages, a few buying guides |
| Interaction | Middle | A trade-in request and a service intake |
| Integrations | Higher | Inventory synchronized from the management system |
| Technical requirements | Higher | Hundreds of URLs to map and redirect |
Three factors drive the scope. The inventory integration and the URL migration each need written specifications before design starts.
Limits and edge cases
- Hidden complexity. Some complexity appears only on inspection: an old site with years of pages, a booking tool without an embeddable version or content that needs professional approval. A discovery review surfaces it before scope is fixed.
- Complexity the business adds later. A new service, a new location or a new outside tool changes the profile. Scope agreed at the start describes the project as known then.
- Focused projects. A low profile describes a focused project. A single page with one clear pathway can be exactly what a business needs. The stages a site can grow through are covered in landing page, growing website or authority-building experience.
- Justify every addition. More pathways, tools and integrations make a site larger. Each one is justified by a customer need.
Profile your project
Choose a level for each of the five factors. The tool shows the profile, names the scope drivers and lists what to specify in writing before quoting.
Profile your project
Rate each factor lower, middle or higher: customer journeys, content depth, interaction, integrations and technical requirements. The highest-rated factors are your scope drivers. Specify each one in writing before asking for a quote.
The profile describes work. It does not calculate a price, and it does not replace a discovery review of the actual site and business.
How So It Sticks applies this
We profile every project across these five factors before we scope it, and we specify the scope drivers in writing first. Our plans page explains how we scope builds. Start a Project Brief and describe your customers, your content and the tools you already use.
Sources and method
The five factors, the levels, the examples and the tool are So It Sticks editorial frameworks. The examples are illustrative and describe no real business. Each linked source supports only the statements numbered beside it. Sources verified October 15, 2026.