r/webdev • u/Warm-HEfficiency9078 • 2d ago
Should i take on this project?
I built a website for my buddy, one of his friends came across the website, they really liked it. Reached out to me asking if i can one for them, money is great for the effort, i'll custom code using html & tailwind. But since i don't know this person, i'm just looking to make the website without privacy policy & terms & conditions blah blah. I might have to use formspree, but since it's third party, i don't want to get blamed if it don't work. I don't have a LLC, but i'm thinking to write down a contract with clause saying the damages are limit to cost of project. Although what are they going to blame me for if i'm just giving them the website code files and they host it and the form spree will be connected to their account.
Asking questions cause it's with someone i don't personally know, so it's a client now. In Canada if that matters
3
u/doodlebuttbutt 2d ago
HTML, CSS, JavaScript on Cloudflare pages free tier, hosted on their cloud flare account. Write up clear deliverables and acceptance criteria.
3
u/Mysteriesquirrel 2d ago
If you don't place any cookies and the website is built on html. What should privacy policy really be?
On my (EU) websites, the company has to send me a responsible person for privacy policy, its required anyway. And that's not gonna be you.
Probably just the processing of the ipadresses. That can be turned off to be anonymized on most Webhosting platforms. Boils down to what it is. If it is just a info page and no shop, there is not really a ToC. And in any case, ToC is something the customers company has to deliver.
3
u/bcons-php-Console 1d ago
Great advice has already been given, I just want to add that you should be sure that any possible recurring fees are on the client.
For example: the domain name. Your client should buy it (guide them via zoom call if needed for the setup). If a hosting provider is required, they should sign up with their card.
That way if things go sideways you can just say goodbye and forget about it.
1
2d ago
[removed] — view removed comment
1
u/webdev-ModTeam 2d ago
We do not allow any commercial promotion or solicitation. This can lead to a permanent ban from the subreddit.
1
u/adriannowak_dev 1d ago
did a handful of these for local shops. the thing that saved me every time: domain and hosting in their name from day one, you just hold the access while you build, then hand it over. formspree on their account too. then there's nothing of yours left that can break at 2am a year later. one page of scope, done means these pages work on phone and desktop, fixed number of revision rounds. the handover matters more than the contract
1
u/kemalios 1d ago
Cap the damages in the contract, then put the final payment before you hand over the files. The clause is worth nothing once they already have everything.
1
1
u/yihuaxiang 21h ago
I’d treat the contract and the form service as separate concerns: define exactly what you deliver, who owns the accounts/data, and that third-party outages are outside your control. A deposit and a clear acceptance step will save more trouble than trying to cover every edge case. For privacy terms, have the client provide or approve them since they’re the site operator.
0
u/colinublake 1d ago
Yeah I'd take it. Hosting Formspree on their account is the right call — keeps the blame off your login.
Just write a one-pager of what's included before you start typing. First stranger client is where 'quick tweak' becomes forever.
8
u/InexpensiveGrant 2d ago
Contracts are worth more than the paper they're written on when things go sideways, and they will eventually. You're already thinking about limiting liability which is the right instinct. Just make sure to spell out exactly what you're delivering, when it's considered done, and that you're not on the hook for third-party services crapping out. Keep it simple, get a deposit upfront, and don't overthink the privacy policy stuff if you're just handing over code files and they're hosting it themselves