These are the 12 most common gaps found in Umbraco project scopes. Each one is a silent margin killer — they look trivial in the brief but surface as unbudgeted work mid-delivery. Estimated hours are typical overruns when the item is missed at scoping.
Content Architecture
1. Content model complexity
Custom document types, compositions, nested content, and block editors multiply far faster than clients expect. A "simple news section" often hides 6+ document types.
+12–20h
2. Template multiplication
Every document type variation needs its own Razor template or partial. Clients describe content as "similar pages" when they are actually distinct templates with unique logic.
+8–16h
3. Custom property editors
Bespoke Umbraco editors (custom Angular, React, or plain JS) for non-standard inputs are often treated as "minor UI tweaks" but require full front-end build pipelines.
+16–30h
Integrations
4. Third-party integration assumptions
CRM, e-commerce, DAM, and marketing automation integrations almost always require undocumented workarounds. Never scope an integration without reviewing the target API first.
+20–40h
5. Umbraco Forms / workflow
Forms seem packaged but custom validation, conditional fields, multi-step forms, and notifications routinely add unscoped hours. Workflow approvals are a separate cost entirely.
+8–14h
Content & Migration
6. Content migration scope
Migrating from a legacy CMS or flat HTML almost always requires custom transformation scripts. "Just copy the content" is never just copying the content.
+16–32h
7. Multi-language / multi-site
Umbraco's multi-site and multi-language setup requires upfront architectural decisions that are very hard to retrofit. Scoped late, they collapse timelines.
+24–48h
8. Media management setup
Image crops, focal points, CDN integration, and asset libraries each require explicit scoping. Projects with large image libraries add significant overhead not captured in content hours.
+6–12h
Infrastructure & QA
9. Hosting and scaling setup
Azure App Service config, load balancing for distributed cache (Redis), Examine index management, and auto-scaling rules are often assumed to be "handled by the host."
+8–16h
10. Testing environments
Staging, UAT, and production parity gaps (environment-specific configs, Umbraco Cloud vs. self-hosted differences) create late-stage bugs that burn time at the worst moment.
+6–10h
Handoff
11. Editor training
Umbraco's back-office has a learning curve. Unscoped training sessions are routinely pulled into the project budget after delivery when clients can't use what was built.
+4–8h
12. Accessibility compliance
WCAG 2.1 AA is increasingly a client requirement and a legal obligation. Retrofitting for accessibility after build costs 3–5× more than scoping it from the start.
+10–20h
Typical unscoped overrun if all 12 are missed138–266 hours