01
Intake and scope definition
Turn the business request into a buildable brief with ownership, audience, launch path, privacy needs, and constraints visible.
day 1
Leadership estimate
The factory answer to time, cost, and hosting.
Senior leadership will ask for the operating envelope before approving the model. For a standard static website with no CMS and roughly 3 to 5 pages, the Website Factory is positioned as a one-week, approximately 10k USD delivery path using one shared DEEP account as the reusable hosting foundation.
Phase 01 to 05
1 week
Estimated effort for a standard static website with no CMS and a 3 to 5 page scope.
Typical envelope
10k USD
Approximate cost target for a standard static website factory run with no CMS and 3 to 5 pages.
Hosting model
1 DEEP
One shared AWS DEEP account is proposed as the reusable hosting foundation for the factory.
Prototype the estimate.
This calculator makes the cost and effort logic visible. A standard request starts at 10k USD for up to three pages. Additional pages add 500 USD and 1 man-day each. At 25 pages or more, or when integrations or lead forms are needed, the estimate moves to TBD.
What the one-week path includes.
The estimate is not a promise to skip governance. It assumes the governance work is standardized, sequenced, and moved through a repeatable path instead of rediscovered for every request.
02
AI prototype
Create a visible direction so sponsors can approve the experience before production engineering begins.
day 1-2
03
Production code check
Apply accessibility, responsive behavior, SEO, metadata, security headers, performance, and maintainability standards.
day 3-4
04
Infrastructure setup
Use the approved static-hosting pattern so DNS, CDN, certificates, environments, and deployment controls are reviewable.
day 4
05
Testing and launch
Run automated checks, smoke tests, staging validation, UAT sign-off, cache purge planning, and production release.
day 5
The DEEP account decision.
The hosting model is one of the clearest leadership questions. The recommendation is to use a single shared DEEP account so the factory can reuse infrastructure, simplify maintenance, and govern the website portfolio consistently.
What can move the estimate.
The estimate is strongest when the request fits the static website lane. These conditions should be surfaced early because they are the usual reasons the one-week and 10k USD assumptions stop being realistic.
CMS or frequent editorial change
CMS delivery adds content modeling, permissions, integration, testing, and handover. It can use the shared DEEP account strategy, but it should not be priced or timed like a static site.
Missing or unstable content
The one-week path assumes the business can make decisions quickly and provide enough source material for prototype and production work.
Heavy localization
Multiple markets, translation workflows, legal variations, or geo-restrictions can increase review effort and launch coordination.
Custom integrations
Forms, CRM, gated content, personalization, analytics exceptions, or non-standard scripts introduce security and testing overhead.
New architecture decisions
When the request cannot use the approved static-hosting pattern, architecture review becomes part of the critical path.
Approval latency
The factory can accelerate delivery, but it cannot absorb long sponsor, brand, legal, privacy, or UAT waiting cycles.