When you probably do not need a banner
If the site uses only strictly necessary storage for things like core functionality or basic site operation, you may not need a consent banner. In this version, the site is static and does not load analytics or marketing scripts, so the practical answer is to keep it cookieless for now.
When you do need consent tooling
If you add tools that track behavior for analytics, remarketing, advertising, CRM enrichment, or cross-site profiling, you should assume you need consent management before those scripts run for EU and UK visitors. That commonly includes setups using Google Tag Manager, Google Analytics, HubSpot tracking, Meta Pixel, LinkedIn Insight Tag, Hotjar, or session replay tools.
Practical setup options
Best privacy path: no non-essential cookies, no banner, simple privacy notice.
Middle path: privacy-focused analytics configured for first-party, non-cross-site measurement, with careful review of whether consent is still required in your target markets.
Full marketing path: analytics plus CRM plus ads, with a consent manager that blocks non-essential scripts until the visitor opts in.
What to do if you want Novee-style marketing tooling
Novee appears to load Cookiebot, Google Tag Manager, and HubSpot on its site, and its privacy policy says it uses cookies and analytics tools including Google Analytics. That is a normal stack for a lead-generation site, but it is exactly the kind of setup that pushes you into cookie consent management.