the point about a page that scores 100 on Lighthouse but feels janky being worse than a page that scores 85 but responds instantly is something i wish more people understood. i have started leading every client call with their current PageSpeed score and it genuinely changes the conversation about why performance matters. the INP section is particularly useful — i had not properly got my head around why it replaced FID until reading this.

the change request workflow is the bit i needed most. i have been absorbing way too many "quick additions" without logging them, and then wondering why projects feel exhausting even when the client is lovely. the 30-minute threshold for when to absorb vs log vs formal-request is really practical — i am going to steal that. also the exclusions section in the scope doc is genius, most of my scope creep comes from things i never explicitly said were not included.

the fact that the card borders respond to cursor position within each card rather than the viewport is such a nice touch — makes every card feel individually alive without being chaotic. the complement trick with 255 minus r for the blue channel is clever too, keeps everything from going muddy. genuinely makes me want to experiment with cursor-reactive colour on client sites, even in a subtle way.

the Brand Encoding Matrix concept is brilliant. i work with small businesses and the gap between "brand guidelines" (usually a logo and two colours in a PDF) and actual consistent output is massive. the rule of three before codifying a component is something i wish i had known earlier — i spent ages building a component library for a client before we had shipped enough to know what actually recurred. proper useful framework, bookmarking this.

the comparison table is spot on. i had a client last month who wanted a full rebrand and e-commerce site for £800 because "their nephew could do it for free but is busy with uni." i used to panic and offer discounts but now i just say okay and wish them well. the do-over tax is so real — half my best-paying projects have been rebuilds of cheap first attempts.

the menu vs prescription framing is spot on. i used to send these massive PDFs breaking down every single deliverable and wondering why people ghosted. now i lead with the problem they told me about on the call, what i would do about it, and one clear price. keeps it to one page and the close rate is way higher.

the bounce rate stats are wild. i had a client whose site was loading in 6+ seconds on mobile and they genuinely could not understand why nobody was filling in their contact form. swapped them to a static site with optimised images and their enquiries doubled within a month. speed is the one thing most small business owners completely overlook.

honestly notion has been fine for me with smaller clients but the moment you have more than three active projects it gets messy fast. the biggest issue is notifications, clients either miss updates completely or get overwhelmed. been looking at dedicated portals for exactly this reason so good timing on this post.

switching to project-based pricing was probably the single best business decision i made last year. the maths just works out so much better once you get faster at delivery. one thing i would add though, the initial discovery call is where you set the anchor. if you quote too early before properly understanding what they need, you end up either too cheap or scaring them off. i try to never give a number on the first call anymore.

the change request form is genuinely underrated. i started using something similar about six months in and it completely changed how clients talk about "just one more thing." the trick for me was making it feel collaborative rather than bureaucratic, like a shared google doc where we log changes together rather than a formal approval process. way less friction and they still think twice before adding stuff.