During Development

If you've heard from the Sales Call that this is how our Sales Rep has managed to secure the sale & the website is being developed in Duda, let's follow the following steps.

• Developer Notes: Add an instruction for the Dev to REPLICATE the legacy site.
  Our developers normally create a totally different & improved website which would instantly give away that we created a new site, which in turn would cause a reaction from the client, as that's not what was agreed upon during sale.
  
  
• Review the Site: As PM, you need to check if the legacy site has any special functionality that would be challenging to replicate in Duda. This way, you're a step ahead in finding a solution for it.

Launch

Prepare for the scenarios that could unfold when making your Launch Call.

• Audit the Site: Check if our site is indeed a Complete Replicate of the legacy site. Any difference would make it obvious to the client that we created a new website for them. Any issue, must be addressed immediately since the client was already sent the "Your Site is Ready to See" email at this point.
  
  
• Initiate Domain Pointing: To bring our website live on the legacy domain, initiate domain pointing right away. If the client asks what do you need this for, you can say this is for us to be able to publish the changes to their live site.
  

Already Launched

If the website has already been launched, & the design is completely different from the legacy site, the client will likely have already reacted negatively.

In this situation, we have to justify our process and explain our approach.

• New Platform: Explain to the client that the reason why we had to rebuild the site on our platform. We can say that our platform is specially optimized for SEO. It enables us to target a wide variety of keywords and locations to bring the website more visibility on the Search Engines, boosting their traffic & to generate more leads for their business

• New Design: If our website has a different design, you can justify this as us making the website more appealing for their visitors. If the client wants to keep the exact same design of the legacy website, we can easily rehaul the site. You'll need to buy time of preferably 2 weeks for us to do the rehaul. We can rush this if it is critically necessary
  
  To proceed with this ...
  
  
• Create a Rehaul Ticket for the Edit Team to do the rehaul work. Just set the ticket status to Urgent and ask Warren if we can prioritize it.

• Review the Legacy Site for any special functionality that might be challenging to replicate in Duda, so you can look for solutions on those right away.

• Audit the Ticket work once the ticket is closed to ensure no quality issues remain. If any instructions aren't followed, go ahead and reopen the ticket.

Below is an example of a difficult call with this problem, and how it was successfully handled saved by the PM.