Web Development
Congratulations on approving the site design! The WATSON Team is now transitioning into the development phase. This involves scheduling resources, briefing our development team, configuring servers, sourcing technology, and meticulously planning every detail to ensure everything runs smoothly. During this phase, the website design is locked in, but we may still reach out with additional technical questions or recommendations.
Below are general timelines for a basic brochure website. These are based on having the entire site approved in Figma and all content organized on DRIVE before development starts. While we can expedite the process, this increases the risk of errors and may lead to more costly revisions. The timeline assumes timely content delivery and excludes any delays due to change orders or edits. Refer to the proposal from your Project Manager for exact timelines.
Timeline Breakdown:
Set Up: ~2 weeks
Development: ~6-12 weeks
Testing + Content Load: ~2 weeks
Client Review: 1+ weeks (varies depending on feedback and revisions)
Launch Prep: ~2 weeks
Soft Launch + Warranty Period: ~4 weeks
Official Launch: Announce your new site to your network!
Common Risks
Lack of Stakeholder Buy-In: Ensure all decision-makers are on board to avoid delays.
Third-Party APIs: These can be unpredictable and unstable, potentially causing integration issues.
Store Databases: Especially when dealing with multiple databases, things can get complicated.
Evolving Business Plans: Changes in business direction mid-project can lead to significant adjustments.
Tweaking Off-the-Shelf Software: Customizing pre-built software solutions can introduce unexpected challenges.
Contractual
Scope: Your website project is based on an agreed-upon scope, with some assumptions. Any features or behaviors beyond this scope will be quoted as additional charges at the Development handoff.
Notice and Alternatives: We’ll provide notice of any additional charges and offer alternatives when possible.
Our Process
Content Mapping: We begin by organizing all your content and content types. This involves creating a sitemap and wireframe for your page layouts.
Content Creation vs. Design Layouts: Content creation is separate from design layouts. During this phase, we’ll use “Beta” content for design while focusing on refining content in collaborative Google Docs.
Content Freeze: Two weeks into development, a content freeze will be implemented, meaning no further content edits can be made. Any additional edits will either be taught to you or handled as additional scope by our team.
Alpha and Beta Testing: Once development is underway, we’ll move to Alpha Testing, followed by Beta Testing, where the website will be live in a controlled environment. Initially, Beta Testing will be conducted in Google Chrome, so please focus your feedback on this browser before we move on to testing across other browsers and devices.
Optimization: During this phase, we’ll optimize the site by compressing images, connecting links, and dialing in SEO.
Device Testing: After Beta Testing, we’ll ensure the design and content are consistent across all browsers and mobile devices, within industry tolerances.
Training: Before launch, we’ll schedule a training session on the CMS with your team, either via web call or in person.
Launch: Finally, we’ll launch the site and assist with pointing your domain to our servers. While the redirect typically takes a few hours, it can take up to 72 hours in some cases.
Maintenance Plans
Once your site is launched, you’ll roll into a monthly Maintenance Plan with our development team. Your project manager or account manager will discuss the various options available to you at that time.