Hello! One client of mine has expressed the concern of being “tied” to Bricks, and I wonder what can I do as a Bricks developer to give him everything he would need in case he wants to go full PHP or use another tool in the future with another dev so the page doesn’t have to be completely remade.
Tell your client to stop doing your job. YOU decide what tools you use to finish his desired website. That’s the whole point of being a freelancer.
You wouldn’t go to the dentist and ask if the filling they use could be swapped for another one in five years, would you? You trust that they use good materials that will last. If that trust isn’t present, a contract should not be signed.
Also, you don’t “go full php” from this. That doesn’t even make sense.
2 Likes
You are completely right, I guess they just didn’t like my maintenance costs and are scared of being tied to me because of the tool I use. But even in that way they should just pay another dev the bricks license. Thanks for the answer!
I find that good documentation aleviates that worry. Having a sound website manual that explains what is used, why and how settings are configured in a certain way and what needs to be minded when updating, will put a client’s mind at ease. The website thereby becomes “transferable” to another developer, should you ever –God forbid– get hit by a bus or decide to part ways for other reasons 
1 Like
set a meeting for training and record that training as well so they re-watch it later
teach them just the basics and how stuff works …etc so they will feel safe long term and that will stop them asking you stupid questions and appreciate how good the bricks builder is and they will thank you for it…
1 Like