In this episode we discuss when and how to say "No". We talk about when developers need to say no as well as when a client should say no.
- When to say to no to a brand new client.
- Talk about budget early.
- Client requirements are unclear.
- Include expiry for proposals.
- Overbooked
- Ethics & Morals
- Reputation and rumors.
- Advice when working with a developer.
- Keep it positive.
- Give better options.
- How to say no.
- Mental health.
Show Links
Web Jargon part 1Web Jargon part 2View Episode Transcript
More Website 101 Podcast
Email the Podcast!TwitterSean on LinkedInMike on LinkedInAmanda on LinkedIn