Blog

Introduction

At the end of a website project with clients there’s two options for what’s going to happen. Either you’re going to maintain the website for your client moving forward, or you’re going to hand-off the website to your client for them to manage themselves.

Now, if you’re the one managing it, then hunky dory, you built the website and now you’re the one who gets to manage that system.

But, for most client projects that I work on, I’m handing off the project to the client, which means I’m also handing off the keys to the website for the client to have full reign on. And this can be a problem, mainly because we want our clients to not be burning the website to the ground, and quite frankly they have the opportunity to do so.

So we’re going to cover all the steps to effectively hand-off a Webflow website to a client to ensure we know that it’s going to be in capable hands.

But first…

1. Starting with a System

To do this you might use Finsweet’s Client First, or use Wizardry, or use something similar to these that works best for you.

The point is that you’re starting from a place of stability where everything has a reason, there are rules to be followed, and when you hand-off the website to the client you can show them that the website is built to last and that even they can understand and use it.

You should be using whatever system you want to use, and making sure that you understand the rules of whatever system you are using. If you don’t have the rules, then you won’t be able to show your client the rules, and the project can become a mess.