# SharpHaw llms-full.txt One senior software engineer runs the website, ads, content and AI automations for European businesses, from owner-operated companies to e-commerce. A website from €1.000/month, all four services from €2.500/month, plus VAT, no annual contract. Everything SharpHaw publishes about itself, in one file: the pages in full, then as much of the blog as fits. The complete index of both is in [llms.txt](https://sharphaw.com/llms.txt). ## Pages: full text The 21 pages that say what SharpHaw is, what it costs and what the terms are. Sections are shared components, so a block that renders on several pages appears once here, under the first page that carries it. ### SharpHaw | Digital work that compounds [Read on sharphaw.com](https://sharphaw.com) Website, ads, content and automations #### A senior digital partner. On subscription. SharpHaw is a senior-led digital agency subscription for European businesses. It starts with your website and grows into your ads, content and automations. One fixed monthly fee, month-to-month, cancel anytime. A senior engineer with 12+ years inside large product companies does the work. The SharpHaw thesis ##### Websites used to be hard to build, so that’s what everyone sold. But nobody ever wanted a website. You want strangers becoming customers, and that runs across your ads, your site, your content and follow-ups, whatever happens after someone raises a hand. You need someone that can connect the dots, instead of pushing them into different directions. Stranger Customer Stranger - Site - Ads - Content - Follow-ups Customer SharpHaw draws the line first, then builds the dots to sit on it. Covering every piece used to take a department. It doesn’t anymore. What comes out the other side is a digital strategy instead of just another link on the internet. The answer ##### Four dots, one line. Your website, content, ads and automations, built and run by the same senior engineer on one weekly loop and one monthly fee. From Growth up all four run together; Foundation is the website on its own. - yoursite.com Espresso beans €18 Buy now Conversions Sold New order ###### Conversion-First Websites Built around the enquiry or sale you want, then kept up to date. - How we roast for espresso, step by step By you · 6 min read ###### Content Engine Articles in your name for Google and AI search, cut into posts. - Sales from ads Meta Google ###### Ads Management Meta and Google as one, tested weekly, tracked click to client. - Contract saved Call booked Lead logged ###### AI Automations Your tools connected, so leads and follow-ups run themselves. Plan. Build. Iterate. ##### Launch is where the work starts. Gabriel spent 12+ years building software inside large tech companies, and none of them treat a product as finished. They improve it in sprints: short rounds of work, one after another, each built on what the last one taught them. SharpHaw runs your website, content, ads and automations the same way, because your business keeps changing, and if your marketing stands still, a competitor’s won’t. A one-off project puts nothing live until its launch in week 6, then stays the same. The weekly loop ships improvements to the website, content, ads and automations every week, so by week 12 it has passed the project and is still rising. An illustrative first quarter Week 12. Still going. - Weekly loop - One-off project Website Content Ads Automations Week Launch Unchanged since launch Still improving Website Content Ads Automations 1 2 3 4 5 6 7 8 9 10 11 12 - 01 Start of the week ###### Plan We pick the one change most worth making this week, on your site, content, ads or automations, and agree how we’ll know it worked. - 02 During the week ###### Build We make it and put it live the same week: small enough to ship fast, careful enough not to break what already works. - 03 End of the week ###### Iterate We check what it actually did. What worked gets pushed further, what didn’t gets fixed, and that decides next week’s plan. Next Monday, it starts again. Who you work with ##### You talk to the engineer. I’m Gabriel, Gabs to most people. I grew up in Rio de Janeiro, I live in Lisbon, and I spent my career as a senior software engineer inside large companies in Europe and Brazil. I built SharpHaw because I kept seeing the same gap: good people each doing their slice well, and nobody accountable for the whole. So I hold the whole. I plan, build and ship your work myself, in English or Portuguese. No account manager in between, no junior learning on your account, and the same person on every call. Gabriel Espinheira Founder and senior software engineer · Lisbon, Portugal Nothing hidden ##### You keep what’s yours. Every term is published before you sign, including the one that isn’t in your favour. In your name Yours, always. Yours from day one, and it leaves with you whenever you leave. - Domain - Brand - Content - Data - Analytics - Ad accounts Leaves with you, with documentation Run by SharpHaw Ours, maintained. The engine we build, host and keep improving as part of the fee. It stays with us. - Website code - Automations - Custom software - Infrastructure Kept running and improved for you From the first month to the last - Day one ###### No setup fee No discovery fee, no setup invoice, no minimum term. - Every month ###### Move up, down or out Change plan or cancel any month, with no penalty. - If you cancel ###### Two more months live Your site stays up while we deliver your export with you. - On the way out ###### €0 to leave No exit fee. Everything of yours leaves, with documentation. ##### Let’s make your digital work compound. Choose a time on Gabriel’s calendar. We’ll go through where you are today, what’s slowing growth, and what’s worth doing first, whether or not we work together. Gabriel Espinheira Senior software engineer · English or Portuguese A focused 30 minutes, not a sales pitch. --- ### Four services, one loop [Read on sharphaw.com](https://sharphaw.com/services) #### Four parts of one digital brand, built to convert. Your website, your ads, your content and your automations, run as one weekly loop on one fee from Growth up, with one person accountable for all four. ##### Everything the subscription covers The SharpHaw thesis --- ### Conversion-First Websites, built and maintained [Read on sharphaw.com](https://sharphaw.com/services/conversion-first-websites) #### A website built to turn visitors into enquiries. Gabriel, a senior software engineer with 12+ years inside large product companies, leads the design and build around the one thing your site has to do: get the right people to call, book or buy. Then he keeps it online and up to date on one monthly fee. The Problem ##### Visitors look around, then leave without a word. Your site gets visitors, and most of them leave without calling, booking or sending a message. Usually nothing is broken. The page answers questions nobody asked, hides the next step, or loads slowly on a phone, and no one can tell you which, because nobody is measuring it. The usual fix is a redesign: a project that ends on launch day, just when the real learning starts. A year later the site is dated again, and every small change needs a new quote. - Visitors, but no calls, bookings or messages. - No one can say where people drop off. - Redesigns that look newer and sell no better. - Every change is a ticket, a quote and a wait. The Solution ##### Built around one action, then looked after. Before any design, we agree what a visitor should do: call, book, buy or send an enquiry. Every page is then written and built to lead there, in the words your buyers use, and fast on a phone. Tracking follows each visit from the first click to the enquiry, and every enquiry lands in SharpOS, where you see it too. After launch the site is kept online and up to date under the same fee. From Growth, Gabriel also reads the numbers, rewrites what underperforms, and ships the fixes every week. - Every page has one job and one next step. - Copy written in your buyers' own words. - Tracked from first click to enquiry in SharpOS. - Improvements included in the fee, not quoted per job. What’s included ##### Everything the system ships. The site, its security, tracking and upkeep, run as one system; landing pages, audits and search work join from Growth. Landing page Form Enquiry Call booked ###### A site built as a sales path Every page leads somewhere: the landing page answers the buyer’s question, the form asks only what it needs, the enquiry lands in one inbox you can see, and the call gets booked. ###### Trust, built in before the first call Who is behind the business, real photos, reviews and clear terms, placed where buyers hesitate, so the page reassures before you pick up the phone. ###### Secure, private and built for EU rules HTTPS enforced, strict security headers, a cookie banner where no is as easy as yes, and forms that ask only what they need. ###### Measured, audited, and fixed Visits and enquiries tracked in one dashboard. From Growth, a regular site audit scores speed, search and structure, then lists what to fix next. ###### Built to be found, and quoted Clean structure, fast pages and schema so Google can index every page. From Growth, search work adds the plain answers AI assistants can quote. ###### Designed for the phone first Buyers often find you on a phone, so every page is designed there first and scaled up to the laptop, never squeezed down from it. In this service: E-commerce, Landing pages, Accessibility, Uptime monitoring, Audits, Branding, Security, Compliance, Responsive. Pricing ##### The price, before you ask. Foundation €1.000/month, Growth €2.500/month and Scale €4.000/month are published; Custom is scoped on the call. Plus VAT, no annual contract, no setup fee. Move up, down, or out any month. ###### Foundation €1.000/month For a business whose website is the problem, with no marketing programme to run alongside it. - Website - Blog - SharpOS - Designed for you, not from a template - Conversion-focused, built to sell - A blog: write your story, build trust - Looks right on phones and big screens - We keep it online and up to date - Text and photo changes, just ask - Contact forms, all in one place Let’s get started All prices are plus VAT, which varies by your country of taxation. No annual contract, no setup fee, no minimum term. ###### Frequently asked questions How long until my new site is live? It depends on the scope, which is agreed with you before any work starts, so no delivery date applies to everyone. You can follow the build in SharpOS as it happens. Once the site is live, Foundation keeps it online and up to date, with small changes when you ask; from Growth it is also improved every week. Will you rebuild my site or improve what I have? Whichever the work actually needs. That is an honest call, not a default rebuild. If your foundation can convert, we iterate on it; if it's holding you back, we rebuild. Either way, your domain, brand, content and data stay yours, and the code that runs the site stays ours, kept running as part of the fee. Because it's a subscription, the site is looked after for as long as you subscribe instead of going stale: small changes on request on Foundation, weekly improvements from Growth. Is this just a redesign? No. A redesign finishes. This is a site built around one action (the call, booking or enquiry you need) and looked after for as long as you subscribe. On Foundation that means the site, its blog, hosting, upkeep and small changes on request, with every enquiry landing in SharpOS. Landing pages, SEO and weekly improvements come with Growth. Will I actually own my website? Your domain, your brand, your content, your data and your analytics are yours from day one and leave with you, handed over with documentation. The code that runs the site is SharpHaw property, kept running and improved as part of the fee. Cancel any month with no penalty. No exit fee. --- ### Content Engine for SEO and AI search [Read on sharphaw.com](https://sharphaw.com/services/content-engine) #### Content that gets your business found where buyers search. Articles written from your expertise, published under your name and linked to the page that sells. We interview you and write every piece; nothing goes live until you approve it. The Problem ##### You publish regularly. It doesn't bring in work. You were told to post, so you did: an article when there was time, social posts most weeks. Months later there is a little more traffic, a few more followers and the same number of enquiries. The pieces aren't built around what buyers search for or linked to anything that sells, and they cost you evenings. Meanwhile Google's AI Overviews and ChatGPT answer many questions before anyone clicks. They draw on pages that answer plainly. If yours isn't one of them, you're not in the answer. - Posts go out, enquiries stay flat. - Topics picked by mood, not search demand. - Nothing links the posts to a page that sells. - Missing from ChatGPT, Perplexity and AI Overviews. The Solution ##### A planned cluster, written from your expertise. It starts with research into what your buyers search for, what AI assistants already answer, and where the competition is thin. That becomes a cluster of articles aimed at one page that converts. Each month we interview you, write the pieces in your voice and send them for approval. Nothing ships until you say yes. Every article is structured to rank and to be quoted by AI search, then cut into shorter social posts. Once a month you see what ranked, what got cited and what brought enquiries. - Topics chosen from real search demand. - Structured for Google and for AI answers. - Your voice, your byline, your approval. - Every article is yours, exportable any time. What’s included ##### Six parts, one engine. Posts that rank on Google and get cited by AI search, internal-linked into the page that does the closing. Month one’s posts are still published, still linked and still pointing at the same enquiry page when month six ships. That is what compounds. Founder interview We roast light because cafés can taste the difference. Gabriel, head roaster - Why we roast light - Where our beans come from - What cafés ask us - Fresh roast, explained - Our first wholesale order ###### Your story, behind every article It starts with an interview: why you started, how you work, what you know that others don’t. That story becomes the thread every article and post comes back to. Search Traffic Intent how to store beans wholesale coffee what is a flat white espresso for cafés ###### Topics chosen where buyers are searching Research into what buyers type and ask, ranked by whether the person asking is ready to buy, not by traffic alone. ###### Written by someone who knows Your byline, your experience and first-hand detail in every piece: the signals Google and AI assistants check before they trust a source. ###### Every post points at the page that sells Articles link to each other and to one enquiry page, so last month’s posts keep sending readers where they can buy. ###### One article, many posts Each article is cut into the shorter posts and carousels that follow it, so one conversation feeds every channel. ###### Long-form, in your voice, with your yes Researched, written from your interview, published under your name, and live only after you approve it. In this service: SEO, Social media content, GEO, Email campaigns, Copywriting, Blog writing, Media Center. Pricing ##### The price, before you ask. ###### Growth €2.500/month For a business that wants one partner for its website, content, ads and automations. - Website - Content - Ads - Automations - SharpOS - Website improved every week - 1 landing page a month - 4 blog posts a month - Meta and Google ads, managed - Automations for recurring work - Up to three social channels - SEO, GEO and a monthly report Start with a 30-min call ###### Frequently asked questions How is this different from hiring a freelance writer? Freelancers write. We build a system. Strategy, keyword and GEO research, internal linking, social repurposing, and monthly reporting run as one engine, so the content compounds instead of piling up. How many posts do I get? Four a month on Growth, two a week on Scale, with more social content across the channels as the strategy calls for it. Growth is €2.500/month and Scale €4.000/month, with Custom scoped on the call. Content production is not part of Foundation, the €1.000/month website plan. All plus VAT, no annual contract, and the fees are on the Plans page. How much of my time will this take? Very little. Your job is to validate, not to produce. We do the industry research and the founder interviews; you review each piece before it ships. Read the draft, approve it or say what is wrong. There is no brief to write and no calendar to fill. How will you write about my industry credibly? Industry research and founder interviews. Every post is SEO + GEO optimised and written in your voice. You validate it before it ships, so nothing generic goes out under your name. --- ### Ads management, tracked to the client [Read on sharphaw.com](https://sharphaw.com/services/ads-management) #### Ads judged by the enquiries they bring in. Meta and Google campaigns run as one system, tracked from the first click to the booked call. Every week you see cost per enquiry and cost per booked call next to the spend that produced them. Your ad accounts stay in your name, and the platforms bill you directly. The Problem ##### The dashboard looks busy. The inbox doesn't. Ad platforms report what they can count: impressions, clicks, cost per click. Those numbers move every day, so they fill the report. The one that matters, which enquiries became paying clients, sits outside it. Meanwhile the ads send people to a homepage that was never built to answer them, so the clicks you paid for leave. Round numbers, invented for the example: €3.000 spent in a month, a report full of green arrows, and nobody can name a client it produced. - Reports stop at clicks, never at clients. - Ads land on pages that don't answer them. - Meta and Google managed as separate silos. - No one can say which ad found which client. The Solution ##### Meta and Google, run as one tracked system. Tracking comes first. Before a campaign spends, every form, call and booking is wired so we know which ad produced it. Meta and Google then run from one plan, and each ad lands on a page built to answer it, because the person running the ads also builds the site. New creative is tested every week, and what doesn't bring enquiries is switched off. You see the results in SharpOS weekly. You set the budget, the platforms bill you directly, and we never mark up the spend. - One plan across Meta and Google. - Tracked from click to enquiry to booked call. - Weekly creative tests and weekly reports. - Ad accounts in your name, spend billed to you. What’s included ##### Everything the ads need, included. Ad accounts rarely die from bad targeting. They die from everything around the campaign: the page that leaks, the copy nobody tested, the report nobody reads. So the whole path lives in one subscription, and it gets worked every week. ###### From ad to follow-up, one path The ad makes a promise, the landing page keeps it, the form captures the enquiry, and the follow-up goes out straight away, so a lead you paid for doesn’t go cold. ###### Meta ads, made for the feed Photo and video creative for Instagram and Facebook, written in your buyers’ words and refreshed every week. ###### Google ads on buying searches Search campaigns built on what people type when they’re ready to buy, with the searches that only waste budget kept out. ###### Every enquiry traced to its ad Pixels, conversion events and tagged links are set up before a campaign spends, so each enquiry and booked call shows which ad started it. ###### Weekly numbers that end at a call Every week: cost per enquiry and cost per booked call, next to the spend that produced them, in one report you can read in a minute. In this service: Google Ads, Social ads, Analytics and dashboards. Pricing ##### The price, before you ask. ###### Frequently asked questions What ad budget do I need? We set it on the first call. You get a budget recommendation with a realistic revenue projection: a number tied to what the spend has to return, not a media plan PDF. The subscription covers the management, the landing pages, the creative and the reporting. Ads management runs from the Growth plan up: €2.500/month plus VAT, no annual contract. It is not part of Foundation, the €1.000/month website plan. Do you run Meta or Google? Both, as one tracked system. Campaigns, landing pages, analytics, and weekly optimisation are connected around qualified enquiries and revenue, not run as two separate dashboards. Will ads work if my website is weak? Honestly: if your current site doesn't convert, your ads won't either. That's why websites and ads run inside the same subscription from Growth up: the landing pages get built and fixed as part of the work, not quoted separately. How fast will I see results? No timeline is promised, because none is honest before the account is read. What is fixed is the reporting: weekly from week one, counted in revenue rather than impressions (cost per lead, cost per booked call, cost per closed deal), with the number the spend is meant to move agreed before it launches. --- ### AI Automations [Read on sharphaw.com](https://sharphaw.com/services/ai-automations) #### Automate the work that doesn’t need you. Follow-ups, lead routing, confirmations, reports, the same answer sent for the tenth time. We map where your team's week goes, build workflows that take over the repetitive part, and keep them running as your tools change. Built by a software engineer, not a no-code consultant. The Problem ##### The same small tasks, every day, by hand. Someone fills in your form and waits a day for a reply. Then a person copies the details into the CRM, sends the same confirmation, chases the same unsigned proposal and answers the same question in the inbox. None of it is hard. It just never stops, and it lands on the people you hired for better work. Most of it could run on its own. It doesn't, because wiring it properly takes engineering time nobody has, and the one automation someone did set up broke quietly months ago. - New enquiries wait hours for a first reply. - Data copied by hand between tools. - The same emails, written again and again. - Old automations broke, and nobody noticed. The Solution ##### Workflows built, explained and kept running. We start by mapping a normal week: where requests arrive, where data gets copied, where people wait. The biggest time sinks are automated first, with the tool that fits each job: Make, n8n, Zapier, OpenAI, Airtable or custom code. Every workflow comes with a plain-language note on what it does and what to do if something looks off. Anything that needs your judgement still comes to you for a yes. When a connected tool changes and a workflow breaks, fixing it is part of the fee, not a new project. - Your biggest time sinks automated first. - Tools chosen per workflow, not per vendor. - You approve anything that needs judgement. - Kept running on the fee when tools change. What’s included ##### Automations that keep running. Every engagement starts with a workflow audit, not an automation menu: an engineer reads the process before picking a tool. What ships is explained in plain language, asks for your yes where it needs judgement, and is kept running as part of the fee. ###### One form, everything after it handled A form on your site starts everything: the enquiry is saved as a customer record, a confirmation goes out, you get a message, and the follow-up is already scheduled. ###### Answers on your site, day and night A chat on your site answers from your own knowledge base at any hour and hands over to you when it should. It runs on your own AI account, with a spending limit. ###### Your yes before anything goes out Drafts, proposals and anything sent in your name wait for your approval, and approving takes one tap. ###### Checked every day, fixed when it breaks Every workflow’s runs are checked daily. When a connected tool changes and something fails, it’s fixed as part of the fee, not quoted as a new project. ###### The repetitive work, off your desk Follow-ups, order entry, confirmations and invoices: the tasks that repeat every day are the first ones automated. ###### Connected to the tools you already use Your workflows connect Google Calendar, Analytics, Search Console, Meta, Resend and WhatsApp, set up for you, and custom code covers the rest. In this service: Support chat, CRM, Surveys, Integrations. Pricing ##### The price, before you ask. ###### Frequently asked questions Do I need to be technical to use the automations? No. You approve outcomes; we handle the engineering. Every workflow ships with a plain-language write-up of what it does, what it touches, and what to do if something looks off. No diagrams to decode, no scripts for anyone on your side to maintain. How do you decide what to automate first? With a workflow audit, before any tool is picked. We map where your team's hours actually go, every recurring task, who touches it and how long it takes, then rank them by the time each one buys back against the work to automate it. The top five ship first. You can't automate what you haven't measured, which is why the work starts here rather than with an automation menu. Can you build AI chatbots? Yes, two kinds. A chat on your website that answers common questions around the clock from your own knowledge base, in your own words, is set up and run from Growth, like the other automations; the replies run on your own OpenAI or OpenRouter key with a spending limit. An assistant built inside your own systems is separate software, scoped on Custom against what it actually has to do. Neither is part of Foundation, the website-only plan. Both are explained in plain language and kept running when the systems underneath them change. Your knowledge base and conversations stay yours; the software is SharpHaw's, kept running as part of the fee. What tools do you use? Make, n8n, Zapier, OpenAI, Airtable, and custom code when needed, chosen per workflow, never per platform loyalty. An engineer reads the process first, then picks the simplest thing that will survive it. Sometimes that is an off-the-shelf connector, sometimes code written and run for you. Either way it is documented in plain language. The data it handles stays yours; the workflow itself is SharpHaw's, kept running and improved as part of the fee. --- ### Website, SEO, ads and automation capabilities [Read on sharphaw.com](https://sharphaw.com/capabilities) Capabilities #### Everything the subscription covers. The specific work inside each service, with the plan it starts on. The website and its upkeep come with every plan; content, ads and automations join from Growth. - Every plan ##### Websites A site built as a sales path, designed for you rather than from a template. - From Growth ##### SEO Clean structure, fast pages and schema, with topics chosen by what buyers search before they buy. - From Growth ##### Social media content Each article cut into the posts and carousels that follow it, across up to three channels. - From Scale ##### E-commerce Online shops built and optimised inside the subscription. Large builds are scoped under Custom. - From Growth ##### Google Ads Search campaigns on what people type when ready to buy, with the wasted searches kept out. - From Growth ##### Support chat A chat that answers from your knowledge base at any hour, and hands over to you when it should. - Every plan ##### CRM Every enquiry saved as a customer record in one inbox, with the follow-up automated from Growth. - From Growth ##### GEO Plain answers and first-hand expertise that AI assistants can quote, as well as Google. - From Growth ##### Email campaigns Newsletters and campaign emails to your list, in the same voice as the rest of your content. - From Growth ##### Landing pages A page per campaign or offer that answers the buyer’s question. One new page a month from Growth. - Every plan ##### Accessibility Pages tested for readable contrast, keyboard navigation and labels a screen reader can announce. - Every plan ##### Uptime monitoring We keep the site online and up to date, and monitor its uptime, in the monthly fee. - From Growth ##### Audits A regular audit that scores speed, search and structure, then lists what to fix next. - From Growth ##### Copywriting Headlines, page and ad copy in your buyers’ words and your voice, approved before it goes live. - From Growth ##### Social ads Photo and video creative for Instagram and Facebook, in your buyers’ words, refreshed weekly. - From Growth ##### Analytics and dashboards Visits, enquiries and ad spend in one dashboard, each enquiry traced to the ad behind it. - Every plan ##### Branding Logos, colours, type and corners in one brand kit, picked up by your forms and link pages. - From Growth ##### Blog writing Long-form posts from your interview, under your name. Four a month on Growth, two a week on Scale. - Every plan ##### Security HTTPS enforced, strict security headers and spam-filtered forms, handled as engineering. - Every plan ##### Compliance A cookie banner where “no” is as easy as “yes”, and privacy pages that match what the site does. - Every plan ##### Responsive Every page designed on the phone first and scaled up to the laptop, never squeezed down. - Every plan ##### Surveys Feedback forms sent straight to clients, for testimonials or check-ins, saved to their record. - From Growth ##### Integrations Your workflows connected to Calendar, Analytics, Search Console, Meta, Resend and WhatsApp. - Every plan ##### Media Center Photos, videos and brand files in one library, ready for the site and posts, exportable anytime. --- ### SharpOS: the workspace included with every plan [Read on sharphaw.com](https://sharphaw.com/sharp-os) #### SharpOS: all your work, in one place. SharpOS is the private workspace that comes with every plan. See what we’re working on, what needs your approval and what has already shipped, so you always know where things stand without a status call or a chasing email. SharpOS Open the showcase full screen The real interface, running on a sample business in your browser. Click anything, or open it full screen. Request a demoSee plans A demo is your own SharpOS workspace, empty and free for 30 days: no card, no plan. On day 30 it pauses, and your data is kept if you subscribe later. The difference ##### Most agencies send a report. You get the workspace. SharpOS is the workspace SharpHaw does your work in, so where things stand is never something you have to ask about. The usual way With SharpHaw Where things stand The usual way: A status call next week, or an email asking for one. With SharpHaw: This week’s board, open whenever you want to look. How it’s going The usual way: A PDF at the end of the month, read once and filed. With SharpHaw: Analytics and site audits that stay open and keep updating. Where your things live The usual way: Logins on the agency’s accounts, files in someone’s Drive. With SharpHaw: One private workspace for your business, with your team in it. What’s inside ##### Every part of the work has a place. 11 parts of one workspace. Pick one and it opens below, live, on the same sample business. ###### The week, on one board. Queues, approvals, blockers and shipped work in one place instead of scattered across status calls. Read it before the call, not during it. SharpOS · Boards Open the showcase full screen What it replaces ##### The stack you don’t pay for any more. Most owners running a small marketing operation pay for a stack of single-purpose tools. For the work SharpHaw ships, SharpOS covers the layer on top of them. The systems you already depend on, like a CRM, stay where they are. Old stack SharpOS features - 01 Notion Confluence replaced by Pages - 02 Trello Asana replaced by Boards - 03 Salesforce HubSpot replaced by Customers - 04 Google Forms Typeform replaced by Forms - 05 Semrush Lighthouse replaced by Audits - 06 Google Drive Dropbox replaced by Media Center - 07 Figma Canva replaced by Studio - 08 A brand guidelines PDF replaced by Brand Kit - 09 Zapier n8n replaced by Automations - 10 Intercom Zendesk replaced by Support - 11 Linktree Bio.link replaced by Spotlight - 12 Google Calendar Google Calendar Google Sheets Google Sheets Cal.com Cal.com Resend Resend WhatsApp WhatsApp Facebook Facebook ElevenLabs ElevenLabs OpenAI OpenAI OpenRouter OpenRouter connected in Integrations - 13 Looker Google Analytics replaced by Analytics - 14 Asking for an update, then waiting on the reply replaced by Live work, all the time Included with every plan. No workspace fee, no per-seat pricing, no portal add-on bolted onto the engagement. It comes with the subscription because it is how the subscription works. Who does what ##### You use it. We run it. ###### You Read the week, approve drafts and send requests. Then use it for your own business too: your customers, forms, link page and support inbox. ###### Your team Invite the people who need it, each with a role: owner, manager, editor or viewer. Access is per workspace, never priced per seat. ###### SharpHaw Does the work in it, keeps it running and keeps improving it. Improvements reach your workspace as they ship, with nothing to install. What’s yours Your content, your customers and your files. Pages export as Markdown, cards as structured data and media as an archive, so if you leave, they leave with you. SharpOS itself stays SharpHaw’s platform, kept running and improved as part of the fee. Built, not bought ##### An agency that built its own software. SharpOS isn’t a client portal added onto someone else’s project tool. Gabriel wrote it to run SharpHaw, and your workspace runs on the same system the work is done in. Gabriel Espinheira Founder · built SharpOS ###### A private workspace per business Your workspace holds your business and nobody else’s, and every person in it has a role. ###### Open to your other tools Every core action is available over a REST API and an MCP server, so your other systems, and the assistants you already use, can work with it too. ###### Improved in public Every release is written up on the SharpOS changelog, newest first. FAQ ##### Frequently asked questions. Do I have to use SharpOS? No. The work ships either way. The workspace is where you can see it happening and use the tools that come with it, whenever that is useful to you, and your team can look in without asking anyone for access to a folder. Is the business in the showcase a real client? No. It is SUMI, one of the concept builds on our cases page, running on the real SharpOS interface with made-up data. Nothing you click or change in it leaves your browser. Will it replace the tools we already pay for? For the work SharpHaw ships, the shared docs, the project board, the asset folder and the audit PDF can all live in it instead, and so can your customer list, forms and link page. It is an orientation, not a parity claim: SharpOS is not a full replacement for every specialist tool, and the systems you depend on stay where they are. What does the support assistant cost to run? The Support inbox is in SharpOS on every plan; the website chat that answers from your knowledge base is set up from Growth. The one cost outside your plan is the AI model usage behind it, which runs on your own OpenAI or OpenRouter key if you switch it on, so you pay the provider directly and see exactly what it uses. Is SharpOS in the Foundation plan too? Yes. Every plan includes SharpOS, from Foundation up, and it is never restricted to push you towards a bigger plan. --- ### A website on subscription, built and looked after [Read on sharphaw.com](https://sharphaw.com/new-website) Foundation · €1.000/month 🇬🇧 🇬🇧 English 🇵🇹 Português #### A website that turns visitors into customers. The question is not whether you have a website. It is what it does once someone opens it. Most sites describe the business and stop, so the visitor reads, nods and leaves. The ones that win customers say who they are for, answer the question the visitor came with, and ask for the next step. This page shows what that looks like, starting with a complete site built to that standard, one scroll down. The standard ##### Judge the standard before you commit. You cannot judge a website from a description of it, so open one. Stillwood Architects is a company we invented and built a complete, working site for, so the standard can be seen without a client’s permission. The design, the code and the forms are exactly what we would build for you. ##### What the site does after someone opens it. 01 · Trust ###### What they find decides what happens next. They look you up before they call. A site that looks current and says plainly who you are reads as a business with its house in order; one that looks wrong on a phone reads the other way, and you never see which. So yours is designed for your business and your brand by the engineer who builds it, never dropped into a template. 02 · The enquiry ###### Good design is the entry fee. The job is the enquiry. A visitor arrives with one question and very little patience. Every page here says who it is for, answers that question, then asks for the next step: the call, the booking or the form. Nothing is left for them to hunt for. 03 · Your customers ###### An enquiry nobody sees is a customer nobody gets. Two things decide whether an enquiry becomes a customer: a form that asks the right questions, and somewhere to keep the answers. Yours land in one customer list you can actually work, with what they asked for and what you told them, instead of in an inbox folder nobody owns. 04 · Your story ###### Nobody chooses a business they know nothing about. How you started and what you know is why people choose you over the next name, and none of it is written down anywhere. The blog is where it goes: yours to write in, ready at launch, publishing takes minutes, and the posts belong to you. Each one is one more page to be found by. 05 · Every screen ###### Wherever your customer is, the page has to work. A large screen at the office, a laptop on the sofa, a phone in a queue in bad light. The site is built for the phone first and checked on the rest, so the same page asks the same question wherever it is opened, and the enquiry works from any of them. 06 · Why a subscription ###### A website is not a project. It is the front of the company. A company changes: a new service, a new price, new hours over Christmas. A project site stops the day it is handed over. This one is somebody’s job after launch: kept online with nothing for you to set up or renew, text and photo changes done when you ask, and cancel any month with no exit fee. Who you’d be working with ##### The name behind the work. Gabriel Espinheira I’m Gabriel. I build every site SharpHaw sells, and this plan is my work from end to end. If you decide to go ahead, I’m the one who builds it, keeps it online and answers when something needs changing. No account manager in between, and no junior learning on your account. Before SharpHaw I built software inside large product companies in Europe and Brazil, as a senior engineer. I started it because I kept watching good businesses get a website from someone who could design but not build, or build but not design, with nobody responsible for it a year later. You don’t have to take my word for any of this: the site above is my work, and the standard yours would be built to. Nothing ties you in, either. No annual contract, cancel any month, and your domain, your brand and your content stay yours. - Senior software engineer for 12+ years before SharpHaw. - Lisbon, from Rio de Janeiro. I work in Portuguese and English. - Independent professional in Portugal: the person who invoices you is the person who does the work. ##### Everything, including the price. The price, everything Foundation includes and everything it does not. The questions people ask before they commit are answered beside it. ###### Straight answers, before the call What does €1.000 a month actually get me? A complete website for your business: the pages that explain who you are, what you do and how to reach you, and a blog of your own, designed for you rather than dropped into a template. Once it is live, the same fee keeps it online, keeps it up to date and covers the text and photo changes you ask for. You are not buying a file that is handed over and starts ageing; you are paying for a site that someone is still responsible for next year. Is there anything to pay up front? No. There is no setup fee and no website-creation fee: the build sits inside the subscription, which is unusual and deliberate. A normal agency charges several thousand to build the site and then leaves you to maintain it. Here the build costs nothing extra and the relationship is the product. Billing is monthly, there is no minimum term, and you can cancel any month. What do you need from me, and how long does it take? One form, after the call: what your business does, who it is for, the services you sell, your logo, any photos you already have, and the words you want on the pages that matter. Nothing open-ended, nothing you have to write from a blank page, and we shape what you send into something that reads well. When it comes back we agree the scope and start building. One engineer working to an agreed scope is a project measured in weeks rather than months, though we will not put a date on it before we have seen what you actually need. Can I add ads, content or automations later? Yes, any month, and nothing is rebuilt. Foundation is the website on its own. From Growth up the same site carries the rest of SharpHaw: we write and publish the content, run your Meta and Google ads and automate the follow-ups, as one weekly loop in the same workspace, with the same person. Foundation is the ground floor of that, not a separate product. What happens to the site if I cancel? It stays live for two months while we plan and deliver your export with you, and there is no exit fee. Your domain, your brand, your content, your data and your analytics are yours and leave with you, handed over with documentation. What does not transfer is the code that runs the site: that stays SharpHaw property, which is the trade for it being maintained rather than handed over and left to rot. If you need a fully static HTML copy of the pages, we can agree one. ##### Say hello, and I’ll take it from there. Everything after this is on me. I read what you send, look at what you have today, and come back with a first take and a time to talk it through. Then the site gets built, goes live and stays looked after, while you get on with running the business. - A reply from the founder, not a sequence, usually the same day. - No setup fee, and you can cancel any month. - If Foundation is not the right fit, I’ll say so. Leave this empty Name Email or phone Your current website (optional) What’s the biggest thing you want this website to do? Submit see the privacy policy. --- ### Plans and pricing [Read on sharphaw.com](https://sharphaw.com/plans) #### Every plan, month to month, no exit fee. Pick the plan that fits today and change it any month. Cancel, and your site stays live for two months while we hand your material over. ##### Plans ###### Scale €4.000/month For larger companies and e-commerce businesses that need more content and channels. Everything in Growth, plus: - Two blog posts a week - More social across the channels - More than three social channels - E-commerce builds and optimisation - Deeper analytics and reporting Book a 30-min call ###### Custom Custom Pricing For a company that needs a separate, tailor-made system for its operations, beyond what SharpOS already covers. - Website - Content - Ads - Automations - Custom software - SharpOS Everything in Scale, plus: - Internal operational software - Bespoke product and integration systems - AI agents inside your own systems - Large e-commerce builds - Built by the engineer who built SharpOS - Kept running and improved in the fee Scoped on the call, once we know what the software has to do. Get in touch Compare plans ##### What each plan covers. From Growth up, one fee covers the work of a website developer, a media buyer, a content writer and someone to wire your automations together. €2.500/month plus VAT Per month, plus VAT Foundation €1.000/month Growth €2.500/month Scale €4.000/month Custom Scoped on the call ###### Website Feature Foundation Growth Scale Custom Designed, built and kept online Included Included Included Included Changes to the site Small changes on request Improved every week Improved every week Improved every week New landing pages — Not included 1 a month 1 a month 1 a month E-commerce — Not included — Not included Builds and optimisation Large builds ###### Content and search Feature Foundation Growth Scale Custom Blog You write the posts 4 posts a month, by us 2 posts a week, by us 2 posts a week, by us Social content — Not included Agreed together More, agreed together More, agreed together Social channels — Not included Up to 3 More than 3 More than 3 SEO and GEO — Not included Included Included Included Reporting — Not included Monthly report Deeper analytics Deeper analytics ###### Ads Feature Foundation Growth Scale Custom Meta and Google ads, managed — Not included Included Included Included ###### Automations and software Feature Foundation Growth Scale Custom Automations for recurring work — Not included Included Included Included Bespoke software and integrations — Not included — Not included — Not included Included AI agents inside your own systems — Not included — Not included — Not included Included ###### Workspace Feature Foundation Growth Scale Custom SharpOS workspace Included Included Included Included Nothing hidden ##### You keep what’s yours. The subscription is month-to-month and every term is on the page, including the one that isn’t in your favour. ###### Who owns what ###### Yours from day one. Domain, brand, content, data, analytics, and ad accounts. ###### Ad spend stays yours. You set the media budget, the platform bills you, and we never rebill it. ###### The engine stays ours. Website code, automations, custom software, infrastructure, SharpOS. ###### How billing works ###### Pause or cancel, any month. Move up, down, or out. No penalty. ###### No exit fee. Everything of yours leaves with you, with documentation. ###### If you leave ###### Two months after you cancel. The website stays live while we plan and deliver your export with you. ###### Your data exports. Pages to markdown, boards to structured data, assets archived. ###### A static site, by agreement. A fully static HTML export if we agree one. Not the dynamic site, not SharpOS. FAQ ##### Frequently asked questions. Choosing a plan, what the fee buys, and who is actually doing the work. Which plan should I start on? Foundation if the website is the problem and there is no marketing programme to run yet. Growth if content, ads and automations need to run alongside it: it carries all four services and up to three social channels, such as Instagram or LinkedIn. Scale for larger content and channel needs, including e-commerce. Custom when you need separate operational software beyond SharpOS, scoped on the call. You can move up or down any month, so the first choice commits you to nothing beyond that month. What does the €1.000 Foundation plan include? A complete institutional website (your business information, your services, your contact forms), built to a scope we agree before any work starts, and laid out to read properly on phones as well as laptops. It ships with a blog of its own, which you write and publish in yourself: the place to tell your company's story, show what you actually know, and build a brand people have a reason to trust. Most businesses have that story and nowhere to put it. After the site is live the same fee covers keeping it online and up to date, and small text and photo changes whenever you ask. Hosting is part of that: there is no separate bill for it, and nothing for you to set up or renew. The SharpOS workspace comes with it at no separate platform charge, so the enquiries your contact forms collect land somewhere you can work them. There is no setup or website-creation fee, no minimum commitment, and you can cancel any month without a penalty. What Foundation does not include is the ongoing programme: we do not write your blog posts or social content, run your ads, build custom automations or build an online shop. Those run from Growth up, or get scoped separately. Nothing about SharpOS is held back to push you upwards: the difference between the plans is how much work we do, not what the platform will let you use. What am I actually buying for €2.500 a month? A senior software engineer's week, every week, and everything underneath it. The website work, the ads, the content, the AI automations and the SharpOS workspace all sit inside the one fee, from Growth up. No setup invoice, no per-seat licences, no separate workspace bill, and no scope conversation before a page gets fixed. The comparison most owners reach for is a shelf of tool subscriptions. The honest one is the hire you haven't made, or the four suppliers you would need to get all of this moving at once. You are not buying a team of ten, or a promise about a specific result. You are buying a week that ships, and the right to stop paying for it any month. Foundation is €1.000/month for the website alone, Growth €2.500/month, Scale €4.000/month, Custom is scoped on the call. All plus VAT, no annual contract. What can I request? Anything across the four disciplines we run as one system: your website, ads, content, and AI automations. All four run from Growth up; Foundation is the website on its own, so it covers the site, its blog, its hosting and its upkeep. Either way it goes into a single weekly queue inside SharpOS. One queue, one invoice, one fixed monthly fee. Underperforming pages get reworked inside that queue rather than re-quoted. What ships each week is set by priorities we agree together. How fast will I see progress? Every week from Growth up. That is the operating model, not a milestone you wait for. The loop is a Monday-to-Monday rhythm you can watch inside SharpOS: Plan. Build. Iterate. What each change is meant to move is agreed before it ships and measured after it lands, rather than promised on a timeline. On Foundation, the site is kept up to date and small changes land when you ask. Why are there no client case studies? Because SharpHaw is finishing its first projects and has no paying clients yet, and we would rather say so than show logos we cannot back. What you can inspect instead is the work itself: concept websites built in-house for fictional businesses and labelled as such, the blog, the SharpOS workspace, the published prices and exit terms, and a 30-minute call with the engineer who would do your work. Real cases go up once real clients have agreed to them. --- ### About [Read on sharphaw.com](https://sharphaw.com/about) #### Your whole digital operation. One engineer. One senior software engineer, Gabriel Espinheira, runs your website, ads, content and AI automations as one weekly loop for businesses across Europe, from owner-operated companies to e-commerce. One published monthly fee, no annual contract, and, from Growth up, something new shipped every week. ##### On a professional note ###### The name behind the brand “Espinheira” is Gabriel’s surname, and he reads it as thorn or haw: nature’s edge. We don’t do soft edges, vague timelines, or fluffy metrics. We do sharp, pointed work with a published price, a week that ships, and every change logged where you can see it. ###### One fixed monthly cost, not project chaos Forget the big upfront invoice and the three-month timeline before anything ships. You pay a published monthly price (Foundation €1.000/month, Growth €2.500/month, Scale €4.000/month, Custom scoped on the call, all plus VAT with no annual contract). From Growth up we ship every week across websites, ads, automations, content and analytics. Foundation is the website on its own, built and then maintained. Clear scope. Predictable cost. Cancel any month. ###### Async by design, visible by default No daily check-ins. No 9am stand-ups. Everything runs through SharpOS: clear boards, a weekly queue, and every change logged as it ships. The best work happens when people have space to think, not when they’re stuck in calls about other calls. ##### On a personal note ###### Where I come from I’m Gabriel, or Gabs. Originally from Rio de Janeiro, now based in Lisbon. I spent years as a senior software engineer inside large companies in Europe and Brazil. That background shaped how I think about quality, speed, and what it actually means to ship something that works. ###### Why I built SharpHaw The gap I kept running into was structural rather than personal: technical, design, marketing and sales judgement sitting in different heads, on different contracts, with nobody accountable for the whole picture. Good people can each do their slice well and the business still ends up carrying the coordination. I built SharpHaw to be the one partner who holds all of it. ###### How I work Remote-first, serving businesses across Europe in English and Portuguese. Async whenever possible, because deep work beats busy work. You work with me directly. No layers, no middlemen. If something breaks, I fix it. If an opportunity shows up, I move on it. You won’t get daily check-ins from me. You’ll get a week that ships. Gabriel Espinheira The SharpHaw thesis ##### Four parts of one digital brand, built to convert. Running a business is more than having a website. The ads, the content and the automations around it run in the same weekly loop, on the same fee, and there is one person to ask about any of them. - yoursite.com Espresso beans €18 Buy now Conversions Sold New order ###### AI Automations Built with The stack behind the work: chosen per job, never one platform applied to every problem. --- ### Values [Read on sharphaw.com](https://sharphaw.com/values) Values #### Seven values. One rule. Every agency has a values page, because the words are free. The rule here makes them cost something: every value below ends with where to check it, against something already published. ##### The seven values - 01 Transparency ###### Transparency, not theatre. Three things are usually knowable only late: what the price is until the proposal, what’s happening until the deck, what leaving costs until you try it. SharpHaw publishes all three. Foundation, Growth and Scale carry published fees on the plans page next to their terms, and Custom is scoped on the call. The week’s work is visible in SharpOS while it happens, not summarised in a monthly PDF. Leaving is published too: cancel any month, no exit fee, and the site stays live for two months while the export is delivered. Where to check PlansFAQSharpOS - 02 Ownership ###### Yours, ours, in writing. SharpHaw is a subscription, and the ownership line is drawn in writing rather than discovered at exit. Your domain, your brand, your content, your data: yours, and they leave with you. The engine underneath (the website code, the automations, the custom software, the infrastructure, SharpOS) is SharpHaw property, kept running and improved as part of the fee. Cancel and the website stays live for two months while we deliver the export with you; a fully static HTML copy of it can be agreed. You rent the machine. You never rent your own business back. Where to check The ownership terms in every agreement, stated here in public before you sign anything. - 03 Seniority ###### Senior at the table. No account managers relaying notes. No junior staff learning on your account. Gabriel Espinheira, founder and senior software engineer, runs the strategy, the engineering, and the weekly cadence directly, with a tight contractor stack for specific specialisms. The person on your first call is the person who ships your work. Where to check About, with his GitHub and LinkedIn - 04 Compounding ###### Compounding, not finishing. A finished website starts decaying the day it launches: rankings drift and the market moves on. So nothing here finishes. Four services run as one weekly loop from Growth up: Plan. Build. Iterate. Every change is measured, then sharpened the week after. On Foundation the same principle runs on the website alone: it is hosted, maintained and kept current rather than handed over and left. Each month starts where the last one ended, not from zero. Where to check The loop on ServicesThe dated cadence on the Blog - 05 Honesty ###### Sharp, no fluff. There is no countdown timer or “two slots left” banner anywhere on this site. Pressure mechanics are what selling sounds like when the work can’t do it. Claims here carry a number or a term, or they don’t ship. Client reporting runs on the same rule: enquiries, bookings, and calls. Never follower counts. Where to check Any page of this site, read as cynically as you like. - 06 Tooling ###### The right tool, used properly. SharpHaw builds with the tools the industry actually runs on: real code in version control, infrastructure from providers you already know. Nothing exotic, nothing that dies with a vendor. SharpOS is built in-house because off-the-shelf project tools made clients do the coordination work. Every tool earns its place: AI where it multiplies output, software where it removes drag, a person where judgement is the work. Where to check The Built-with stack on the homepage and the AI rules below. - 07 Compliance ###### EU-ready, by design. Analytics run consent-first on EU infrastructure, behind a cookie banner with a real decline path: decline, and nothing loads. AI-assisted work is disclosed, as the EU AI Act now requires. The next section of this page is that disclosure. Prices are in euros with VAT stated up front, from Lisbon, in English and Portuguese. Where to check The cookie banner’s decline button. It works. AI, on the record ##### Agents make the volume. A person makes it true. SharpHaw runs on AI agents and says so in plain text, not fine print. Agents draft, build, audit, and report. That is how one senior partner ships four disciplines every week at a published price. What they never hold is publish authority. These are the standing rules. - 01 Publish authority ###### Humans approve everything public. Every public word on this site, the blog, or client work passes a human edit for facts and voice before it ships. Nothing publishes straight from a draft. - 02 Disclosure ###### Disclosed, not disguised. This page is the disclosure the EU AI Act’s transparency rules call for (Article 50, in force since August 2026). It sits in the open, not in a footnote. - 03 Facts ###### No invented facts. A claim with no source doesn’t ship. The rule is enforced hardest on AI drafts, because drafts are where invention creeps in. - 04 Identity ###### No fake humans. No AI avatar fronting as the founder. No synthetic testimonials. No bot writing “personal” replies in your name or ours. - 05 Client work ###### Same gates, your sign-off. The engine that writes for SharpHaw is the engine clients subscribe to, and client content passes the same approval gate: your job is to validate, not to produce. The proof is the blog: every post drafted by the engine, edited and signed by the founder, dated. The same system clients buy, working in public. --- ### The blog for smarter digital growth [Read on sharphaw.com](https://sharphaw.com/blog) #### What actually works online. Plain answers on websites, ads, content and automations for owner-operated businesses in Europe: what to fix first, and what to skip. Gabriel Espinheira Author Latest · 17 Oct 2026 17 Oct 2026, 08:00 · Ads ##### Performance Max can now skip your website for your Business Profile Performance Max can now send ad clicks to your Google Business Profile instead of your website. When that suits you, and four settings to check first. 16 Oct 2026, 08:00 · Website ##### EU green claims rules: rewrite "eco-friendly" into a fact Since 27 September 2026, EU law bans eco-friendly, green and offset-based climate neutral claims without proof. Where they hide on a site and how to fix them. 15 Oct 2026, 08:00 · Content Engine ##### Fake author profiles: Google now calls them deception Google's guidance now calls fake author profiles deception. Check who your blog byline names and put the real person behind the knowledge on every post. 13 Oct 2026, 08:00 · Content Engine ##### Search Console AI report: read it before you opt out of AI Overviews Google's new Search Console AI report shows which pages AI Overviews and AI Mode cite. What it misses, who controls the opt-out, and what to check first. 12 Oct 2026, 08:00 · Website ##### Do you need a website if your Instagram already works? Instagram makes people want you. A website answers the prices, hours and booking questions they check next. What a small site needs, and when to skip it. 11 Oct 2026, 08:00 · Website ##### Client waitlist: what your website should say when you're full Build a client waitlist that explains availability, deadlines and what joining means. Give visitors a next step when your service business is fully booked. 26 Sep 2026, 08:00 · Website ##### Why SharpHaw works monthly: websites improve through sprints Why SharpHaw works monthly: see how website sprints connect customer feedback, useful changes and care. Explore Plan. Build. Iterate. and the trade-offs. 21 Sep 2026, 08:00 · Automations ##### How to reduce appointment no-shows: start with an attendance audit Audit appointment no-shows, check confirmations and measure attendance before adding reminders. Includes a worked example and practical checks. 10 Sep 2026, 08:00 · Marketing ##### How much does a marketing agency cost per month Compare monthly website, content, ads and automation costs with SharpHaw plans, including setup fees and the tools SharpOS could replace in your budget. 8 Sep 2026, 11:00 · Website ##### Website maintenance: what are you actually paying for? Learn what a website maintenance fee should cover across hosting, technical care, content changes and conversion improvement. 5 Sep 2026, 08:00 · Automations ##### Gemini 3.8 Flash changes the model-routing question Gemini 3.8 Flash changes model routing: default reversible, testable work to Flash, then escalate ambiguity, blast radius, and costly verification at runtime. 4 Sep 2026, 08:00 · Website ##### Framer or Webflow template vs conversion-first service Compare a Framer or Webflow template with a conversion-first website service across strategy, tracking, ownership, iteration and ongoing work after launch. Page 1 of 14 Previous - … The newsletter ##### New posts, in your inbox. One email per post, covering websites, ads, content and AI automations for owner-operated businesses in Europe. It goes out when a post is published, which in a quiet month means nothing at all. No drip sequence, no sales cadence, and every email carries a one-click unsubscribe. Leave this field empty Name Email We don’t sell or share your details. See the privacy policy (opens in a new tab). --- ### The newsletter: one email per post [Read on sharphaw.com](https://sharphaw.com/newsletter) #### Newsletter Websites, ads, content and AI automations for owner-operated businesses in Europe: the work we sell, written up as we do it. Leave this field empty Name Email One email per post Sent as it goes live. No digest, no drip sequence: a quiet month means no email at all. The post, not a teaser The opening and a link to the rest. Nothing is gated behind the address. Leaving takes one click From any email, or here. We don’t sell or share your details. --- ### Cases: real sites you can open, not screenshots [Read on sharphaw.com](https://sharphaw.com/cases) #### Websites you can use, not just look at. Every case is a complete website, designed and coded in-house and running on its own address. Find the one closest to your business and use it the way your customers would: browse the rooms, reserve a seat, ask for a valuation. The companies are invented, so the work can be shown at full strength without putting a real business on display. Everything else is real: the design, the code and the forms are exactly what we would ship for yours. ##### The concept builds - stillwood-architects.sharphaw.com Architecture studio ###### Stillwood Architects A home in conversation with the landscape - quinta-da-espinheira.sharphaw.com Winery ###### Quinta da Espinheira A Douro wine estate, arrived at from the air - sumi.sharphaw.com Restaurant ###### SUMI A sushi counter, drawn in ink - lumina-clinic.sharphaw.com Aesthetics clinic ###### Lumina Clinic Subtle work, sold on restraint - tagus-co.sharphaw.com Law firm ###### Tagus & Co. Cross-border counsel without the fog - whitmore-finch.sharphaw.com Estate agency ###### Whitmore & Finch Period London houses, walked room by room - ironhouse.sharphaw.com Fitness studio ###### IRONHOUSE A strength club with standards - palazzo-marzano.sharphaw.com Boutique hotel ###### Palazzo Marzano Fourteen rooms on Ortigia - northlight.sharphaw.com SaaS product ###### Northlight Product analytics teams act on - vell.sharphaw.com Fashion label ###### VELL Womenswear in permanent collection - foss-gray.sharphaw.com Architecture studio ###### Foss & Gray Architecture drawn from its site - fernweh.sharphaw.com Travel agency ###### Fernweh Travel Co. Itineraries you could not google - mara-lindqvist.sharphaw.com Photographer ###### Mara Lindqvist The port at night, developed in front of you - harbourline.sharphaw.com Financial advisor ###### Harbourline Wealth Fiduciary advice, measured in decades Services --- ### Book a call [Read on sharphaw.com](https://sharphaw.com/contact) #### Book a call. 30 minutes with the engineer who’d do the work. No pitch, no discovery fee, and a straight answer if we’re not the right fit. Leave this field empty Name Email What should we look at first? Pick a time (optional) We only use your details to reply to you, and we never sell or share them. Read the privacy policy (opens in a new tab) and cookie policy (opens in a new tab). Gabriel Espinheira Replies to every enquiry himself, in English or Portuguese. On the call - 01 Where you are - 02 What’s slowing you down - 03 What to do first ##### What happens next ###### You send it One honest line about what’s not working is enough. ###### Gabriel replies himself Not a sales sequence. If you didn’t pick a time, he suggests one. ###### The call 30 minutes, and you leave knowing what to fix first, whether or not we work together. Only need a website? Start on Foundation Prefer email? contact@sharphaw.com --- ### Frequently asked questions [Read on sharphaw.com](https://sharphaw.com/faq) FAQ #### Frequently asked questions. What the monthly fee buys, who does the work, how often it ships, what you own, and where we're not the right fit. All answered straight, in terms you can check on this site rather than promises about results. ##### How it works What exactly do I get for one monthly fee? One senior software engineer running your website, your Meta and Google ads, your AI automations and a content engine built for Google rankings and AI-search citation. From Growth up, something new ships every week. You're not paying for a finished project or a static retainer. You're paying for a system that compounds. Every week we ship something that moves a real number: a new landing page, an ad iteration, a published article, an automation that takes a recurring task off your team. Everything lives inside SharpOS, the workspace that ships with your subscription, so you can see what's been done without scheduling a meeting. That is the picture from Growth up, where all four services run together and the tiers differ in how much content and how many channels they cover, with Custom adding separate software built for your operations. Foundation is the narrower plan underneath it: the website and its blog, built to an agreed scope and then hosted and looked after. See the Plans page for the detail. How fast does work actually ship? Every week from Growth up. That's the cadence, not a milestone you wait for, and you see each change inside SharpOS as it lands. On Foundation, small changes land when you ask. The operating model is a weekly loop, not a quarterly campaign: Plan. Build. Iterate. Each week we agree on the next thing to ship, build it, measure what it moved, and stack the next iteration on top. That's why the work compounds: instead of waiting six months for a redesign reveal, you watch one system get sharper every week. Who actually does the work? Gabriel Espinheira, the founder. A senior software engineer who built inside large product companies before founding SharpHaw. No account managers. No junior staff learning on your account. No salespeople who can't answer a technical question. The engineer who built the system is the one shipping your work and the one you'll talk to next week. A tight contractor stack supports specific specialisms (paid media buying, motion, copy editing). Gabriel runs the strategy, the engineering, and the weekly cadence directly. You're one person. What happens if you're ill, or you disappear? One person is the trade. You get the senior engineer directly, and you carry the risk of a single supplier. So every term is written so that leaving is cheap and orderly. The downside first: a week where Gabriel is ill is a week that ships less, and there is no bench to hide that behind. What there is instead is a set-up where an absence can't cost you what's already built. Your accounts stay yours throughout: domain, ad accounts, analytics, content. Nothing of yours is locked in a format you can't export, everything in SharpOS exports, and the subscription is month-to-month, so if the cadence isn't there you cancel that month and your side of it leaves with you. ##### Pricing and terms What is in Foundation, and what is not? A complete institutional website at €1.000/month, with a blog of its own: built to a scope agreed before work starts, then hosted, kept up to date and looked after, with SharpOS included. In it: your business information, your services and your contact forms, laid out to read properly on phones as well as laptops, plus a blog you write and publish in yourself: the place to tell your company's story, show what you actually know, and build a brand people have a reason to trust. Once the site is live the same fee covers keeping it online and up to date, and small text and photo changes whenever you ask. Hosting is part of that: there is no separate bill for it, and nothing for you to set up or renew. SharpOS comes with it at no separate platform charge, so the enquiries your contact forms collect land in a workspace you can work them in. There is no setup or website-creation fee, no minimum commitment, and cancellation any month without a penalty. Not in it: us writing the blog posts or the social content, ads management, custom automation development, online shops and bespoke operational software. Those sit in the higher plans or need their own scope assessment. The scope of the website itself is agreed with you first; there is no page count, monthly-change allowance or delivery date that applies to everyone. What Foundation is not is a cheaper version of the full service, and it is not a trial: it is a smaller amount of work, useful on its own, and SharpOS is not restricted to push you up a tier. Am I locked into an annual contract? No. Every SharpHaw plan is month-to-month. Cancel any month with no penalty. An annual term protects the supplier, not the buyer: it converts a bad quarter into a bill you keep paying. SharpHaw publishes the fees on the website and bills month to month on purpose. If the work isn't compounding, you should be able to leave, and you can. Are there hidden fees to start? No. No discovery fee, no setup invoice, no minimum term. Billing is monthly, month to month. Move up, down, or out any month. On Foundation there is no setup or website-creation fee either: the build is inside the subscription. The Plans page publishes the fees: Foundation €1.000/month, Growth €2.500/month and Scale €4.000/month, with Custom scoped on the call. All plus VAT, with no annual contract. What happens to my stuff if I leave? Your domain, brand, content, SharpOS data and ad accounts. All of it leaves with you, and the website stays live for two months while we do it. Cancellation starts an export plan rather than a cut-off: the site keeps serving for two months while we hand over with documentation, and there is no exit fee. Inside SharpOS, pages export to markdown, board cards export to structured data, and assets can be archived. A fully static HTML export of the site can be agreed as part of that handover, which is the pages as flat files, not the dynamic site or SharpOS. What does not transfer is the engine underneath: the website code, the automations, the custom software, the infrastructure and SharpOS itself are SharpHaw property, kept running and improved as part of the fee. Is ad spend included in the fee? No, and neither is AI model usage in SharpOS Support. Both are billed to you by the provider, never rebilled by us. Campaign management, the technical setup and the ad content and creative are all inside the subscription. The media itself is not: you agree the budget with us, grant access through Meta Business, and Meta or Google bills your own account. SharpHaw never collects or rebills ad spend, and the ad accounts stay yours. The same line runs through SharpOS Support: where AI replies are switched on, you supply your own OpenAI or OpenRouter key and choose a suitable small model, so the usage is billed to your provider account with budgets and limits set to control it. SharpOS itself is included at every tier with no separate workspace fee. Who sells and invoices the service? Gabriel Espinheira, operating under the SharpHaw brand. SharpHaw is Gabriel's practice rather than a holding company with an account team behind it. He works as an independent professional in Portugal, issues the receipts himself, and takes payment through Stripe. The person who invoices you is the person who does the work. ##### Ownership and SharpOS Will I own my website? Your domain, your brand, your content, your data, your ad accounts and your analytics are yours from day one, and they leave with you. The code that runs the site is SharpHaw property. That is the subscription line, drawn in writing rather than discovered at exit: you rent the machine, you never rent your own business back. The engine underneath (the website code, the automations, the custom software, the infrastructure and SharpOS) stays SharpHaw property and is kept running and improved as part of the fee, rather than handed over and left to rot. Everything on your side of that line is genuinely yours: there are no hostage logins, and nothing of yours sits in a format you cannot export. Is SharpOS a separate SaaS product? No. SharpOS is bundled with every SharpHaw subscription. It is part of how the service works, not a separate tool sale. It's included at every tier, with no separate workspace fee. Access is workspace-based, never per-seat priced. The one thing billed outside it is AI model usage in Support, which runs on your own provider key if you switch it on. Does SharpOS replace our CRM, CMS, or ad accounts? No. Your core systems of record stay where they are. SharpOS is the workspace where the work is planned, tracked and reported. Pages, boards, audits, analytics, media and CRM context in one place. ##### Fit and proof Is SharpHaw the right fit for my business? If you run a European business with a site that has traffic but doesn't convert, ad spend that isn't returning, or content that's stalled, then yes. SharpHaw is built for owners who've outgrown freelancers and don't want to hire a full marketing team yet, and for larger companies and e-commerce businesses that need more content and more channels than one supplier usually carries. It serves businesses across Europe, in English and in Portuguese with the founder directly. It is not the right fit if you're shopping on price, want a one-off project with no follow-through, need a source-code handover, or need a 50-person agency org chart. The call is free. If it's not a fit, we'll say so on it. I already work with a freelancer or an agency. Is a call worth it? Only if you want an honest read on what you've already got. The call is a conversation, not a pitch to replace whoever you're working with. The thirty minutes run the same way whether or not you become a client: where you are today, what's slowing growth, and what looks worth doing first. It is a conversation rather than a written audit, and no fix list is promised at the end of it. If one slice is broken and the rest is working, a specialist is the better buy, and we'll say so rather than sell around it. Do you have testimonials or case studies? Not yet. And we'd rather be straight about that than show logos we can't back. The honest proof we do have is our own blog (every post dated and founder-bylined, quiet months included), the published Plans page, and the live SharpOS workspace. And thirteen working case builds you can open and use: invented companies, real code, disclosed as such on the page. --- ### Accessibility statement [Read on sharphaw.com](https://sharphaw.com/accessibility) Accessibility #### Accessibility statement SharpHaw is committed to making sharphaw.com usable by as many people as possible, including people who browse with a keyboard, a screen reader, magnification, or reduced motion enabled. This statement describes where the site stands today. ##### The standard we target We aim to meet Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. The site is partially conformant with that standard: most of it meets Level AA, and the exceptions we know about are listed below. ##### What the site does - Every page is reachable and operable with a keyboard alone, and interactive elements show a visible focus ring rather than relying on the browser default. - Text contrast meets the Level AA ratio against the site’s dark ground. Dimmed states are drawn with a readable colour step, never with reduced opacity on live text. - Every animation on the site respects the operating system’s reduced-motion setting. Where a section is animated, such as the work stream on the homepage, the process loop and the scroll reveals, a static composition ships as the complete design, not as a degraded fallback. - Images that carry meaning have descriptive alternative text; decorative images and looping preview clips are hidden from assistive technology so they are not announced twice. - The site is built as server-rendered HTML, so content is present and readable before any JavaScript runs. ##### Known limitations These are the items open at the last review. They come from our own audit of the site, and each is scheduled rather than accepted. - Card links on the plans and service pages. Some cards are wrapped in a single link whose accessible name summarises the card rather than repeating all of its visible text. Voice-control users may not be able to activate one of these by speaking every word they can see (WCAG 2.2 success criterion 2.5.3, Label in Name). - The thirteen concept builds under /cases. These are illustrative demonstration sites, each designed in a different visual language. They are not held to the same accessibility standard as sharphaw.com itself, and some do not meet Level AA. - The support chat widget. The in-page assistant is a third-party embed (SharpOS). We do not control its markup, and we have not independently verified it against WCAG 2.2 AA. Every function it offers is also available by email. ##### Reporting a barrier If you hit something on this site you cannot use, tell us and we will fix it. Email contact@sharphaw.com with the page address and what happened. We aim to reply within five working days, and we will tell you when the fix will ship rather than close the report without one. If you need something on this site in a different format, whether a document, a page’s content or a proposal, ask at the same address and we will provide it. ##### How this statement was prepared This statement was prepared following a self-assessment of sharphaw.com carried out with automated testing (Lighthouse and axe rule sets) alongside manual keyboard and screen-reader checks. It is reviewed whenever the site’s structure changes, and at least once a year. Last reviewed: 4 August 2026 --- ### Terms [Read on sharphaw.com](https://sharphaw.com/terms) Legal #### Terms By accessing and using the SharpHaw website (sharphaw.com) and our services, you agree to be bound by these Terms of Service. If you do not agree to these terms, please do not use our website or services. ##### 1. Acceptance of Terms By using our website, you acknowledge that you have read, understood, and agree to be bound by these Terms of Service and our Privacy Policy. These terms apply to all visitors, users, and others who access or use our website and services. ##### 2. Use of Our Website You agree to use our website only for lawful purposes and in accordance with these Terms. You agree not to: - Use the website in any way that violates applicable laws or regulations - Attempt to gain unauthorized access to any part of the website - Interfere with the proper working of the website - Copy, distribute, or modify any content without our written permission ##### 3. Intellectual Property The content, design, graphics, and other materials on our website are owned by SharpHaw and are protected by copyright, trademark, and other intellectual property laws. You may not reproduce, distribute, modify, or use our intellectual property without prior written consent. ##### 4. User Content If you submit content to our website (such as testimonials, comments, or feedback), you grant SharpHaw a non-exclusive, royalty-free, perpetual, and irrevocable right to use, reproduce, and display such content for any purpose. ##### 5. Third-Party Links Our website may contain links to third-party websites or services that are not owned or controlled by SharpHaw. We are not responsible for the content, privacy policies, or practices of any third-party websites. We recommend reviewing the terms and privacy policies of those websites. ##### 6. Disclaimers Our website and services are provided “as is” and “as available” without any warranties of any kind, whether express or implied. We do not guarantee that our website will be error-free, secure, or continuously available. ##### 7. Limitation of Liability To the maximum extent permitted by law, SharpHaw shall not be liable for any indirect, incidental, special, consequential, or punitive damages resulting from your use of or inability to use our website or services. ##### 8. Indemnification You agree to indemnify and hold harmless SharpHaw and its team from any claims, damages, losses, or expenses arising out of your use of the website or violation of these Terms. ##### 9. Governing Law These Terms shall be governed by and construed in accordance with applicable laws. Any disputes arising under these Terms shall be resolved in accordance with applicable legal processes. ##### 10. Changes to These Terms We reserve the right to modify these Terms at any time. Any changes will be posted on this page with an updated “last modified” date. Your continued use of the website after any changes constitutes acceptance of the new Terms. ##### 11. Contact Information If you have any questions about these Terms of Service, please contact us at contact@sharphaw.com ##### Related Policies Please also review our: - Cookie Policy: learn how we use cookies and similar tracking technologies - Privacy Policy: understand how we collect, use, and protect your personal information --- ### Privacy Policy [Read on sharphaw.com](https://sharphaw.com/terms/privacy-policy) Legal #### Privacy Policy At SharpHaw, we are committed to protecting your personal data and respecting your privacy. This Privacy Policy explains how we collect, use, store, and protect your personal information in compliance with the General Data Protection Regulation (GDPR) and other applicable European Union data protection laws. ##### 1. Data Controller The data controller is Gabriel Espinheira, an independent professional established in Portugal who trades as SharpHaw. For any question about this Privacy Policy or how your data is handled, contact: - Email: contact@sharphaw.com - Website: sharphaw.com ##### 2. Data We Collect We may collect the following categories of personal data: ###### 2.1 Information You Provide Directly - Contact information (name, email address, phone number) when you fill out a form or contact us - Business information (company name, job title) if you represent a business - Communication preferences and any other information you choose to share ###### 2.2 Information Collected Automatically - IP address and browser type - Pages visited and time spent on our website - Referring website or source - Device and operating system information - With your consent, a recording of how you use our pages (mouse movement, clicks, scrolling), with form entries masked ###### 2.3 Cookies and Tracking Technologies We use cookies and similar tracking technologies. For detailed information about the types of cookies we use, please refer to our Cookie Policy. ##### 3. Legal Basis for Processing We process your personal data based on the following legal bases under Article 6 of the GDPR: ###### 3.1 Consent Where you have given us explicit consent to process your data for a specific purpose (e.g., marketing communications) and analytics and advertising cookies, which are only set once you accept them. You can withdraw your consent at any time. ###### 3.2 Contract Performance Processing necessary to fulfill our contractual obligations to you when you engage our services. ###### 3.3 Legitimate Interests Processing necessary for our legitimate business interests, such as improving our website and services, provided these interests are not overridden by your rights and freedoms. ###### 3.4 Legal Obligation Processing necessary to comply with legal obligations we are subject to (e.g., tax and accounting requirements). ##### 4. How We Use Your Data - To provide and improve our services - To respond to your enquiries and communicate with you - To send you marketing communications (with your consent) - To analyse website usage and improve user experience - To comply with legal obligations - To prevent fraud and ensure security ##### 5. Data Sharing and Transfers - Service providers who assist us in operating our website and providing services (e.g., hosting providers, email services) - Analytics and advertising providers, only after you accept cookies: Google (Google Analytics 4, Google Tag Manager), Meta (Meta Pixel) and PostHog (EU Cloud, Frankfurt). The Cookie Policy lists what each collects and how long it is kept. - Professional advisors (lawyers, accountants) when necessary - Government or regulatory bodies when required by law We do not sell your personal data to third parties. When we transfer data outside the European Economic Area (EEA), we ensure appropriate safeguards are in place in accordance with GDPR requirements. ##### 6. Data Retention We retain your personal data only for as long as necessary to fulfill the purposes for which we collected it: - Contact form data: Retained for 2 years after last interaction - Analytics data: Retained for 14 months - Session recordings: 30 days - Marketing data: Retained until you withdraw consent When data is no longer needed, we securely delete or anonymise it. ##### 7. Your Rights Under GDPR Under the GDPR, you have the following rights regarding your personal data: ###### 7.1 Right to Access You have the right to obtain confirmation as to whether or not personal data concerning you is being processed, and to request access to your personal data. ###### 7.2 Right to Rectification You have the right to request correction of inaccurate personal data and to have incomplete personal data completed. ###### 7.3 Right to Erasure You have the right to request erasure of your personal data when there is no legitimate reason for us to retain it. ###### 7.4 Right to Restriction of Processing You have the right to request restriction of processing in certain circumstances. ###### 7.5 Right to Data Portability You have the right to receive your personal data in a structured, commonly used, and machine-readable format. ###### 7.6 Right to Object You have the right to object to processing based on legitimate interests. ###### 7.7 Right to Withdraw Consent Where processing is based on consent, you have the right to withdraw your consent at any time. ##### 8. How to Exercise Your Rights To exercise any of your rights, please contact us at contact@sharphaw.com. We will respond to your request within one month. This period may be extended if necessary. ##### 9. Data Security We implement appropriate technical and organisational measures to protect your personal data against unauthorized access, alteration, disclosure, or destruction. ##### 10. Third-Party Links Our website may contain links to third-party websites. We are not responsible for their privacy practices. ##### 11. Children Privacy Our website is not intended for children under 16. We do not knowingly collect personal data from children. ##### 12. Changes to This Policy We may update this Privacy Policy periodically. Any changes will be posted on this page with an updated date. ##### 13. Supervisory Authority If you have a complaint about how we handle your personal data, you have the right to lodge a complaint with the relevant supervisory authority in your EU member state. In Portugal, that authority is the Comissão Nacional de Proteção de Dados (CNPD, cnpd.pt). --- ### Cookie Policy [Read on sharphaw.com](https://sharphaw.com/terms/cookie-policy) Legal #### Cookie Policy This Cookie Policy explains how SharpHaw (“we,” “our,” or “us”) uses cookies and similar tracking technologies on our website sharphaw.com By using our website, you agree to the use of cookies as described in this policy. ##### What Are Cookies Cookies are small text files stored on your device (computer, tablet, or mobile) when you visit websites. They help the site function properly, remember your preferences, and provide insights to website owners about how visitors interact with their site. ##### Types of Cookies We Use ###### 1. Necessary Cookies These cookies are essential for the website to function properly. They enable basic features like page navigation, secure areas access, and remembering your preferences (such as language or region). The website cannot function without these cookies. These cookies do not store any personally identifiable information. ###### 2. Preferences Cookies Preference cookies allow the website to remember choices you have made (such as your username, language, or region) and provide enhanced, personalised features. They may also be used to remember changes you have made to text size, fonts, and other customisable elements. The information these cookies collect is anonymised and cannot track your browsing activity on other websites. ###### 3. Analytics Cookies Analytics cookies help us understand how visitors interact with our website by collecting and reporting information anonymously. They help us identify which pages are most visited, how long users spend on each page, and any errors users encounter. This information is used to improve the performance and user experience of our website. All data is aggregated and anonymised. ###### 4. Marketing Cookies Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user. These cookies may be set through our site by our advertising partners and may be used to build a profile of your interests and show you relevant advertisements on other sites. They do not directly store personal information but are based on uniquely identifying your browser and internet device. ##### Third-Party Cookies We may use third-party services that set their own cookies on our website. These third parties include analytics providers (such as Google Analytics) and advertising networks. We have no control over these cookies. They are set by the respective third parties and governed by their own privacy policies. We recommend reviewing the privacy policies of these third parties for more information about how they use cookies. ##### The Services We Use None of these loads until you press Accept on the cookie banner. If you decline, none of them is downloaded. - Google Tag Manager (Google Ireland Limited) loads some of the scripts below after you accept. It sets no cookies of its own. - Google Analytics 4 (Google Ireland Limited) counts visits, the pages you view and how you reached the site. Cookies: _ga and _ga_, up to 13 months. - Meta Pixel (Meta Platforms Ireland Limited) measures whether our Meta ads lead to enquiries, and lets us show our ads to people who have visited the site. Cookie: _fbp, 90 days. - PostHog (PostHog EU Cloud, data stored in Frankfurt, Germany) records the pages you view, your clicks, scrolling and form interactions, your device and browser, and an approximate location worked out from your IP address. Cookie and local storage: ph__posthog, 12 months. PostHog also records sessions: a replay of how our pages respond to your mouse, clicks, scrolling and typing, which we use to find the parts of the site that confuse or break. Anything you type into a form field is masked before it leaves your browser. Recordings are deleted after 30 days. Our host, Vercel, also measures page views and loading speed for every visitor, without cookies and without storing an identifier on your device. You can change your choice at any time with “Cookie settings” in the footer of every page. Choosing Decline switches these services off, reloads the page without them and deletes the cookies they set. ##### Managing Your Cookie Preferences You have the right to decide whether to accept or reject cookies. You can manage your preferences in the following ways: - Browser settings: most web browsers allow you to control cookies through their settings. You can set your browser to notify you when you receive a cookie, giving you the choice to accept or reject it. - Third-party opt-outs: you can opt out of specific third-party cookies by visiting tools like the Digital Advertising Alliance (DAA) or Network Advertising Initiative (NAI) opt-out pages. - Cookie consent banner: when you first visit our website, a banner asks before any analytics or marketing cookie is set. Accept turns those tools on; Decline keeps them off, and none of them is downloaded. You can change your choice at any time with the “Cookie settings” button in the footer of every page. Declining after you had accepted switches the tools off and deletes the cookies they set. Note: Disabling necessary cookies may impair the functionality of the website, as some features may not work correctly. ##### Cookie Duration Cookies we use have varying expiration times. Session cookies are automatically deleted when you close your browser. Persistent cookies remain on your device for a set period (no longer than 13 months; each service’s cookies are listed above) until you delete them or they expire. ##### Updates to This Policy We may update this Cookie Policy periodically to reflect changes in our practices or for operational, legal, or regulatory reasons. Any changes will be posted on this page with an updated “last modified” date. We encourage you to review this policy regularly to stay informed about how we use cookies. ##### Contact Us If you have any questions about this Cookie Policy or how we use cookies, please contact us at contact@sharphaw.com Last modified: 25 September 2026 ## Pages: index only - [Every restaurant booking, confirmed and seated](https://sharphaw.com/lp/solutions-for-restaurants): A restaurant reservation path on your own domain, confirmations guests can answer, and a waiting list the host can work. From €2.500/month plus VAT. - [Every clinic visit ends with the next one booked](https://sharphaw.com/lp/solutions-for-aesthetic-clinics): Booking in sync with your diary, a client record with the next date set before they leave, and aftercare in the clinic's own words. From €2.500/month plus VAT. - [A winery that keeps the customer after the tasting](https://sharphaw.com/lp/solutions-for-wineries): Winery tastings booked on your own domain, a consented record of what each visitor tasted, and reorders that come back to you. From €2.500/month plus VAT. - [A venture capital site that declines the wrong deck](https://sharphaw.com/lp/solutions-for-venture-capital-funds): A venture capital thesis with published edges, one comparable founder submission, and a dealflow board that never scores a deck. From €2.500/month plus VAT. - [A dental practice that fills the hour it just lost](https://sharphaw.com/lp/solutions-for-dental-practices): Dental pre-booking answers in your own wording, confirmations that ask for a reply, and a released hour offered to waiting patients. From €2.500/month plus VAT. - [A law firm site that says what it does not take](https://sharphaw.com/lp/solutions-for-law-firms): Practice-area pages a law firm partner signs, a four-question intake, and routing to a named person with a response time. From €2.500/month plus VAT. - [A studio where every trial books the next class](https://sharphaw.com/lp/solutions-for-fitness-studios): Studio classes booked on your own site, the next one offered before the trial ends, and a missed week the coach hears about. From €2.500/month plus VAT. - [An estate agency the vendor finds first](https://sharphaw.com/lp/solutions-for-estate-agencies): Vendor-intent campaigns in your estate agency's own accounts, a property-shaped valuation path, and follow-up you own. From €2.500/month plus VAT. - [An architecture practice a client can shortlist](https://sharphaw.com/lp/solutions-for-architects): An architecture practice's projects published twice: the photographs, then the constraint, the decision and the brief. From €2.500/month plus VAT. - [A hotel site that answers while the guest decides](https://sharphaw.com/lp/solutions-for-boutique-hotels): Hotel rooms a guest can tell apart, answers at the hour they ask, and a booking path that behaves on a phone. From €2.500/month plus VAT. - [The adviser explains. The page never advises.](https://sharphaw.com/lp/solutions-for-financial-advisers): Explainers built from your advisers' own words, each with a named reviewer and a date, and personal questions routed to a person. From €2.500/month plus VAT. - [A travel agency where enquiries arrive quote-ready](https://sharphaw.com/lp/solutions-for-travel-agencies): A travel agency funnel per trip type, a first draft from your own approved destination notes, and a specialist who signs off. From €2.500/month plus VAT. - [SEO services, run every week](https://sharphaw.com/capabilities/seo): SEO services on a monthly subscription: keyword research by buyer intent, technical fixes, schema, weekly content and a monthly report, from the Growth plan. - [Social media management, cut from your articles](https://sharphaw.com/capabilities/social-media-content): Social media management from the Growth plan: posts and carousels cut from each article, in your voice, approved by you, across up to three channels. - [Ecommerce website design, built and optimised](https://sharphaw.com/capabilities/ecommerce): Ecommerce website design on subscription: your shop built, then optimised every week with deeper analytics, from the Scale plan. Large builds are Custom. - [Google Ads management on buying searches](https://sharphaw.com/capabilities/google-ads): Google Ads management from the Growth plan: search campaigns on buying searches, wasted terms kept out, every enquiry tracked, and a weekly report. - [Website chat that answers from your knowledge base](https://sharphaw.com/capabilities/support-chat): A website chat that answers visitors from your knowledge base at any hour, hands over to you when it should and logs every conversation. From the Growth plan. - [CRM for small businesses, filled by your forms](https://sharphaw.com/capabilities/crm): A CRM for small businesses where every form enquiry is saved as a customer record, with its source and history. On every plan; automated follow-up from Growth. - [Generative engine optimisation (GEO)](https://sharphaw.com/capabilities/geo): Generative engine optimisation from the Growth plan: plain answers, first-hand expertise and schema that ChatGPT, Perplexity and AI Overviews can quote. - [Email marketing services from your own content](https://sharphaw.com/capabilities/email-campaigns): Email marketing services from the Growth plan: a newsletter for every post, campaign emails you approve, sign-ups saved to your customer records. - [Landing page design, one new page a month](https://sharphaw.com/capabilities/landing-pages): Landing page design on a monthly subscription: one new page a month for a campaign or offer, with its copy, form and tracking, from the Growth plan. - [Website accessibility, tested as we build](https://sharphaw.com/capabilities/accessibility): Website accessibility tested on every plan from Foundation: readable contrast, keyboard navigation, visible focus and labels a screen reader can announce. - [Website maintenance, in the monthly fee](https://sharphaw.com/capabilities/website-maintenance): Website maintenance in the monthly fee from the Foundation plan: hosting, updates, security, uptime monitoring, and text and photo changes whenever you ask. - [Website audit, scored and tracked over time](https://sharphaw.com/capabilities/audits): A regular website audit from the Growth plan: speed, search, marketing and technical scores, with findings kept open, fixed in the weekly work and tracked. - [Copywriting services in your voice](https://sharphaw.com/capabilities/copywriting): Copywriting services from the Growth plan: headlines, landing pages, ad copy and articles in your buyers' words and your voice, approved before going live. - [Social media advertising on Instagram and Facebook](https://sharphaw.com/capabilities/social-ads): Social media advertising on Instagram and Facebook: photo and video creative, weekly tests, tracking to each enquiry and a weekly report, from the Growth plan. - [Marketing dashboard and weekly reporting](https://sharphaw.com/capabilities/analytics-dashboards): A marketing dashboard with visits, enquiries and ad spend in one place, every enquiry traced to its ad, weekly and monthly reports, from the Growth plan. - [Brand kit for your forms and pages](https://sharphaw.com/capabilities/branding): A brand kit on every plan from Foundation: logos, colours, typefaces and corners stored once, used by your forms, link pages and, from Growth, support chat. - [Blog writing services, from your own interview](https://sharphaw.com/capabilities/blog-writing): Blog writing services from the Growth plan: long-form posts written from your interview, under your name, approved by you. Four a month, or two a week on Scale. - [Website security, built in from day one](https://sharphaw.com/capabilities/security): Website security on every plan from Foundation: HTTPS enforced, strict security headers, spam-filtered forms, and updates and monitoring in the monthly fee. - [GDPR compliant website: what's built in](https://sharphaw.com/capabilities/compliance): A GDPR compliant website starts with consent: a banner where no is as easy as yes, trackers held until visitors choose, matching privacy pages. Every plan. - [Responsive web design, phone first](https://sharphaw.com/capabilities/responsive): Responsive web design on every plan: each page designed on the phone first, then scaled up to tablet and laptop, with speed tracked after launch. - [Customer feedback forms, sent to each client](https://sharphaw.com/capabilities/surveys): A customer feedback form sent straight to each client, for testimonials, feedback or check-ins, with every answer saved to their record. On every plan. - [Workflow integrations for the tools you use](https://sharphaw.com/capabilities/integrations): Workflow integrations from the Growth plan: Google Calendar, Analytics, Search Console, Meta, Resend and WhatsApp connected to your site and set up for you. - [Media library for every photo and file](https://sharphaw.com/capabilities/media-center): A media library on every plan from Foundation: your photos, videos and brand files stored once, used across your site and posts, and exportable at any time. ## Concept builds Working sites for companies SharpHaw invented, published as proof of the work rather than as client references. Links only: the copy on them is the invented company's, not SharpHaw's. - [Stillwood Architects · concept build](https://sharphaw.com/cases/stillwood-architects) - [Stillwood Architects · A home in conversation with the landscape](https://sharphaw.com/cases/stillwood-architects/details) - [Quinta da Espinheira · concept build](https://sharphaw.com/cases/quinta-da-espinheira) - [Quinta da Espinheira · A Douro wine estate, arrived at from the air](https://sharphaw.com/cases/quinta-da-espinheira/details) - [SUMI · concept build](https://sharphaw.com/cases/sumi) - [SUMI · A sushi counter, drawn in ink](https://sharphaw.com/cases/sumi/details) - [Lumina Clinic · concept build](https://sharphaw.com/cases/lumina-clinic) - [Lumina Clinic · Subtle work, sold on restraint](https://sharphaw.com/cases/lumina-clinic/details) - [Tagus & Co. · concept build](https://sharphaw.com/cases/tagus-co) - [Tagus & Co. · Cross-border counsel without the fog](https://sharphaw.com/cases/tagus-co/details) - [Whitmore & Finch · concept build](https://sharphaw.com/cases/whitmore-finch) - [Whitmore & Finch · Period London houses, walked room by room](https://sharphaw.com/cases/whitmore-finch/details) - [IRONHOUSE · concept build](https://sharphaw.com/cases/ironhouse) - [IRONHOUSE · A strength club with standards](https://sharphaw.com/cases/ironhouse/details) - [Palazzo Marzano · concept build](https://sharphaw.com/cases/palazzo-marzano) - [Palazzo Marzano · Fourteen rooms on Ortigia](https://sharphaw.com/cases/palazzo-marzano/details) - [Northlight · concept build](https://sharphaw.com/cases/northlight) - [Northlight · Product analytics teams act on](https://sharphaw.com/cases/northlight/details) - [VELL · concept build](https://sharphaw.com/cases/vell) - [VELL · Womenswear in permanent collection](https://sharphaw.com/cases/vell/details) - [Foss & Gray · concept build](https://sharphaw.com/cases/foss-gray) - [Foss & Gray · Architecture drawn from its site](https://sharphaw.com/cases/foss-gray/details) - [Fernweh Travel Co. · concept build](https://sharphaw.com/cases/fernweh) - [Fernweh Travel Co. · Itineraries you could not google](https://sharphaw.com/cases/fernweh/details) - [Mara Lindqvist · concept build](https://sharphaw.com/cases/mara-lindqvist) - [Mara Lindqvist · The port at night, developed in front of you](https://sharphaw.com/cases/mara-lindqvist/details) - [Harbourline Wealth · concept build](https://sharphaw.com/cases/harbourline) - [Harbourline Wealth · Fiduciary advice, measured in decades](https://sharphaw.com/cases/harbourline/details) ## Blog: full text 38 of 162 published posts, newest first, reproduced in full. The file is capped at 500 KB so it arrives whole rather than truncated mid-article, and the pages above are taken out of that first. ### Performance Max can now skip your website for your Business Profile [Read on sharphaw.com](https://sharphaw.com/blog/performance-max-business-profile) · Ads · published 2026-10-17T08:00:00Z > Performance Max can now send ad clicks to your Google Business Profile instead of your website. When that suits you, and four settings to check first. Google Ads has added a new destination to Performance Max, the campaign type that runs one ad across Search, Maps, YouTube and Gmail. It is called "Google Business Profile (optimised for ads)". Search Engine Watch reported it on 9 October 2026, after the Google Ads specialist Thomas Eccel posted the setup screen on X. With it, a paid click can land on a Google-hosted version of your Business Profile instead of your website. For a locksmith whose customers only ever ring, that may cost nothing. For a clinic or a consultancy that wins work through an enquiry form, it moves the most expensive visit you buy onto a page you don't control, and swaps your inbox for a count Google keeps. **TL;DR:** Performance Max can now send ad clicks to a Google-hosted Business Profile instead of your website. Results then show up as call and direction clicks that Google counts, while your enquiry form gets fewer visits. Accept it only when you really sell by phone or in person, and check Final URL expansion, which is on by default. ##### What does the Business Profile destination in Performance Max change? The change is where the person lands after they click. Until now, a Performance Max ad sent people to a page on your site: the final URL you chose, or another page Google picked from your domain. In Eccel's words, "instead of always sending users to your website, PMax can now take them to a Google-hosted Business Profile experience designed for ads." The visitor sees your name, photos, reviews and opening hours, with buttons to call or get directions, laid out by Google. Search Engine Watch put the consequence plainly: advertisers "may see traffic and conversion data shift to calls, directions, and other profile actions, and their website may get fewer visits." What changes is the page that answers the click, and who holds the record of what happened next. At the time of writing we couldn't find a Google help page for the option, so the open details (which countries have it, whether it comes pre-selected, which campaign goals it works with) rest on that one setup screen. Look at your own account before you act on anyone's summary, ours included. ##### Who loses most when the ad skips the website? Picture a physiotherapy clinic in Porto running Performance Max for new patients. Its website has a page for each treatment, an explanation of the first appointment and a booking form that asks what hurts and which week suits. A visitor who fills that form in arrives as a lead with context, even at eleven at night with the phone off. Send the same visitor to the Business Profile and the best they can do is tap call. If the call comes in during a session and nobody answers, Google Ads still records a call click. The campaign counts a result; the clinic never meets the patient. A business that sells through a considered decision loses the most. It needs the page that answers the questions people have before they book, and the form that catches them when nobody can pick up. It also needs a number it can check. A form enquiry lands in your inbox with a name on it. A direction click lands in a report. ##### When is a Google-hosted profile the better landing page? Sometimes the profile is closer to the sale than the website. Google already builds campaigns around exactly these actions: it describes Performance Max for store goals as maximising "store visits, store sales, and local actions such as call clicks, or direction clicks", with ads on Search, Maps, Waze, YouTube and Gmail. For a tyre fitter, a takeaway or an emergency plumber, the customer wants the number or the route, now. A website page between them and the button is one more tap. So the test is where a new customer becomes a customer. If it happens on a call that someone reliably picks up, or when a person walks in, the profile is a reasonable place to send paid clicks. If it happens through a form, a quote request, a booking with choices or a decision made after reading, the website is where the sale happens and the profile is a detour around it. ##### What to check in Performance Max before you accept it Four checks, in this order, for every Performance Max campaign you run: 1. **The destination.** Open the campaign settings and see where clicks go. If the Business Profile option is selected and you never chose it, make the decision yourself. 2. **Final URL expansion.** Google's help page says it "is turned on by default for Performance Max campaigns" and lets the campaign "replace your Final URL with a more relevant landing page" from your domain. The same page warns it "can sometimes lead to ads pointing to unintended pages if not managed carefully with URL exclusions." If one enquiry page is your only route to a lead, switch it off: Google says the campaign then sends people only to the URLs in your page feed and asset groups. 3. **What counts as a conversion.** If call clicks and direction clicks are set as conversions, the campaign will chase them. Decide whether a tap on a call button is worth as much to you as a filled-in enquiry, given that the tap only means someone pressed the button. 4. **Your own numbers.** Put the campaign's reported conversions for the last few weeks next to the enquiries that reached your inbox and the calls you actually took. If Google reports more results while your inbox stays flat, the destination is the first place to look. ##### Why the website still has to do the selling I'm strict about one part of every site we build: the enquiry form. On our own [Foundation page](https://sharphaw.com/new-website), the form saves the enquiry first and only then offers a 30-minute call time, so a lead exists somewhere we own before anything else can go wrong. Paid traffic deserves the same rule. Keep your Business Profile current; it is often the first thing a local customer sees. But it is Google's page about you. Your website is the one place where the ad's promise, your answers and your form sit together and every enquiry arrives with a name. If you are going to pay for a click, send it to the page that can close. If that page isn't ready for paid traffic yet, fix the page before you buy more clicks. Our [Ads Management and website work](https://sharphaw.com/plans) start from that order. ##### Frequently asked questions **What is "Google Business Profile (optimised for ads)"?** It is a destination option inside Google Ads Performance Max, reported on 9 October 2026, that sends people who click an ad to a Google-hosted version of your Business Profile instead of a page on your website. The visitor sees your profile details with call and directions buttons, and your website gets fewer of those visits. **Can Final URL expansion send my ads to the wrong page?** It can. Google turns Final URL expansion on by default in Performance Max and lets the campaign swap your chosen page for another page on your domain. Google's own help page warns this "can sometimes lead to ads pointing to unintended pages" unless you exclude URLs. Switch it off when one page is your only route to an enquiry. **Is a call click the same as a phone call?** No. A call click records that someone tapped a call button in your ad or profile. It doesn't confirm that the call connected, that anyone answered, or that the caller booked. Compare call clicks with the calls you actually took in the same weeks before you treat them as leads. **Should I stop using my Google Business Profile?** No. Your profile is often the first thing a local customer sees, so keep its hours, photos and services current. The question here is narrower: where a paid click should land. Send it to the profile when the sale happens by phone or in person, and to your website when it happens through an enquiry. If you'd like a second opinion on whether your enquiry page is ready for paid clicks, [book a 30-minute call](https://sharphaw.com/contact) and bring the campaign with you. --- ### EU green claims rules: rewrite "eco-friendly" into a fact [Read on sharphaw.com](https://sharphaw.com/blog/eu-green-claims-rules-website) · Website · published 2026-10-16T08:00:00Z > Since 27 September 2026, EU law bans eco-friendly, green and offset-based climate neutral claims without proof. Where they hide on a site and how to fix them. Read your homepage the way a competitor's lawyer would. "Eco-friendly cleaning". "A green stay in the Douro". "Climate-neutral delivery". Since 27 September 2026, each of those lines is a green claim the EU treats as misleading unless you can prove it, and the rules cover the website you published years ago just as much as the one you launched last week. The law is Directive (EU) 2024/825, known as EmpCo. Most of the coverage is written for brands with packaging and product catalogues. This guide is for the owner of a small service business whose green claims sit in a hero line, an About page and a meta description, and who wants to keep saying what is true about the business without the risk. **TL;DR:** Since 27 September 2026, EU law bans generic green claims such as "eco-friendly", "green" and "climate friendly" unless you can prove recognised excellent environmental performance. Offset-based "climate neutral" claims and self-made eco badges are banned too. Website text has no grace period. The fix is to replace each adjective with the specific fact behind it, on the same page. ##### Which green claims did the EU ban on 27 September 2026? The EmpCo directive adds green claims to the list of commercial practices that are banned in all circumstances, with no case-by-case test. Four of the new bans are the ones a small business website trips over. - **Generic words.** The directive's own examples are "environmentally friendly", "eco-friendly", "green", "nature's friend", "ecological", "environmentally correct", "climate friendly", "gentle on the environment", "carbon friendly", "energy efficient", "biodegradable" and "biobased". They are banned unless you can demonstrate recognised excellent environmental performance, which in practice means the EU Ecolabel or an officially recognised ecolabel scheme. - **Offsetting.** "Climate neutral", "CO2 neutral certified", "carbon positive", "climate net zero", "climate compensated", "reduced climate impact" and "limited CO2 footprint" are banned when they rest on buying offsets outside your own value chain. No amount of explanation saves them. - **Home-made labels.** A leaf badge from your website theme, or a "Green Choice" seal you designed yourself, is banned unless it comes from a certification scheme with independent checks or from a public authority. - **The part sold as the whole.** A claim about the whole business that is only true of one part of it. The European Commission's reason is on the record: a 2020 Commission study found that 53.3% of the green claims it examined were vague, misleading or unfounded, and 40% were completely unsubstantiated. ##### Does it apply to a small service business website? Yes, and size is no defence. The rules apply to every business that talks to consumers in the EU, with no turnover or headcount threshold, which is the main difference from the large-company sustainability reporting rules many owners have heard of. They also cover services as well as goods: the directive's examples of banned offset claims apply to "a product, either a good or service". The website matters more than anything else you publish. Printed stock got some sympathy: the Commission's FAQ and national consumer authorities ask for proportionate enforcement on goods already produced, such as stickers over old packaging. Online claims got none. They have had to comply since the day the rules applied, because a web page can be edited in an afternoon. Enforcement in most countries will start with a letter, from a competitor, a consumer association or a regulator, so the practical question is whether you can answer that letter with a fact. ##### Where green claims hide on a business website A small business rarely writes "eco-friendly" on purpose all over its site. It writes it once in a hero line and the phrase spreads. These are the places to search, in order of how often they get forgotten: 1. **Page titles and meta descriptions.** The words Google shows under your link are advertising too, and they are usually written once and never read again. 2. **Image alt text and file names.** "eco-friendly-office.jpg" is invisible to visitors and very visible to anyone scanning your HTML. 3. **Icons and badges.** The directive says a claim in words, combined with colours or images, can be a generic claim. A leaf icon next to "our approach" counts. 4. **The About page and footer.** "A sustainable business from day one" usually lives here. 5. **Supplier text.** If you pasted a supplier's description of a product you use, the claim is now yours. 6. **Everywhere outside the site.** Your Google Business Profile description, social bios and booking platform listings carry the same sentence. Use your browser's find (Ctrl+F or Cmd+F) for "eco", "green", "sustainab", "climate", "carbon", "neutral", "natural" and "planet" on every page. Then run a `site:yourdomain.com eco` search on Google to catch the pages you forgot existed. Brand names are in scope too: the Commission's FAQ says a business name containing "green" or "eco" counts if customers would read it as an environmental promise. ##### How to rewrite "eco-friendly" into a claim you can prove The rule that makes this fixable is in the directive itself. A claim stops being generic when its specification is given "in clear and prominent terms on the same medium". The directive's own example: "climate-friendly packaging" is a banned generic claim, while "100% of energy used to produce this packaging comes from renewable sources" is a specific one. So every green adjective on your site is a placeholder for a fact. Some illustrative rewrites for service businesses, each one only usable if it is true and you can show the evidence: | On the site today | Rewrite to the fact | |---|---| | Eco-friendly cleaning | We clean with products that carry the EU Ecolabel | | A green guesthouse | Our hot water is heated by the solar panels on the roof | | Climate-neutral delivery | Orders inside the city centre go out by cargo bike | | Sustainable coffee | Our beans come from one roaster in Porto, who names the farm on every bag | | Environmentally conscious design studio | We specify heat pumps and reuse existing walls where the structure allows | The rewrite is better copy as well as safer copy. "Eco-friendly" is what every competitor already says. "Cargo bike inside the city centre" is a reason to pick you. I hold my own writing to this. When we built Vell, a fictional Copenhagen clothing label on our [concept sites](https://sharphaw.com/cases), the collection page never says "sustainable". It says "eleven in recycled wool, nine in organic cotton, four in dead-stock silk", and names the mill near Porto that weaves the cotton. Read again against these rules, one line still needs evidence: "repaired free for life" is a repair promise, and a real label would need written repair terms behind it before publishing it. ##### What can you still say about the environment? A lot. The directive bans vagueness, and it leaves room for anything specific and true. - **Specific facts about one named part of the business**, like the rewrites above, kept on the same page as the claim. - **Recognised labels you actually hold**, such as the EU Ecolabel, with the scheme named next to the claim. - **What you fund, described as funding.** The directive says businesses can still advertise investments in environmental projects, including carbon credit projects, as long as they are described accurately and kept separate from a claim that your service itself is neutral. "We fund a reforestation project in the Serra da Estrela" survives. "Carbon-neutral stays" does not. - **Future targets with a plan.** "Net zero by 2030" needs a public, detailed implementation plan and regular checks by an independent expert. For most small businesses that plan does not exist yet, so the target belongs in the internal to-do list, not on the homepage. Keep the evidence in one folder: the certificate with its number and expiry, the energy bill, the supplier's invoice. If a letter arrives, the answer is a link to that folder. ##### Frequently asked questions **Is the word "sustainable" banned?** "Sustainable" is not on the directive's list of examples, but it is riskier than "eco-friendly". The directive says words like "conscious", "sustainable" and "responsible" also cover social characteristics, so even an EU Ecolabel cannot justify them on its own. Replace them with the specific fact. **Do the rules apply to businesses that only sell to other businesses?** The EmpCo directive amends EU consumer law, so it targets communication aimed at consumers. Some member states extend similar rules to business-to-business advertising through national law, and general misleading-advertising rules still apply. A website that both consumers and companies read should follow the consumer standard. **Is there a transition period for old web pages?** There is no transition period for website text. The Commission's FAQ and consumer authorities ask for proportionate treatment of goods and packaging already produced before 27 September 2026, but online claims had to be corrected from that date, because they can be edited immediately. **What is the Green Claims Directive, and is it the same law?** The Green Claims Directive is a separate EU proposal on how businesses must substantiate environmental claims, and the Commission still lists it as pending. EmpCo is the law that already applies. When people say the EU banned "eco-friendly", they mean EmpCo. ##### What to do this week Search your site for the eight words above, list every hit with its page, and decide each one: keep it with evidence, rewrite it to the fact, or delete it. Do the meta descriptions and the Google Business Profile in the same pass, because they are the copies nobody rereads. Then write down the date you checked, so the record exists before anyone asks for it. This is copy work more than legal work, and it is the kind we do on every site we maintain: concrete claims, evidence on file, pages that get reread. If your site needs that pass and you would rather not do it alone, [book a 30-minute call](https://sharphaw.com/contact) and we will go through it together, or see what a maintained site includes on the [Foundation plan](https://sharphaw.com/new-website). For a claim you are unsure about, or anything in a regulated sector, check it with a lawyer who knows your country's transposition of the directive. --- ### Fake author profiles: Google now calls them deception [Read on sharphaw.com](https://sharphaw.com/blog/fake-author-profiles-google-deception) · Content Engine · published 2026-10-15T08:00:00Z > Google's guidance now calls fake author profiles deception. Check who your blog byline names and put the real person behind the knowledge on every post. Look at the name under your last blog post. If it is a "Sarah, Content Specialist" nobody at your business has met, Google now has a word for that. In the version of its helpful content guidance dated 1 October 2026, Google added a paragraph saying that fake author profiles, built with "AI-generated headshots, made-up names, or false credentials", are "a form of deception". The same paragraph says deception makes a page untrustworthy to readers and to Google's "automated quality systems". For a small business whose blog is written by an agency, a freelancer or a tool, this is a byline check you can finish today. You can keep the agency or the tool. The invented person on top of their work has to go. **TL;DR:** Google's people-first content guidance now calls fake author profiles deception and "a signal of a low-quality page". Bylines themselves do not help a page rank, so an invented expert gains nothing in search and now carries a named risk. Put the real person behind the knowledge on it, usually the owner, and say plainly how the post was written. ##### What did Google add about fake author profiles? The new text sits in the "Who" section of Google's page [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content), straight after Google's advice to add accurate bylines. It reads: "However, avoid using deceptive authorship information. Fabricating creator profiles (such as by using AI-generated headshots, made-up names, or false credentials to make content appear as if it was written by human experts) is a form of deception. Any form of deception makes a page untrustworthy to both users and our automated quality systems, and is a signal of a low-quality page." The idea is older than the paragraph. [Search Engine Journal reported](https://www.searchenginejournal.com/google-fake-author-warning-site-owner-guidance/591806/) that section 4.5.3 of Google's quality rater guidelines already told raters, the people Google pays to grade its search results, to treat made-up author profiles and false claims of expertise as deception, and to give those pages the Lowest rating. What is new is where the warning sits: in guidance written for site owners, instead of only in a manual for raters. ##### Will a fake author get my blog penalised? Google has not announced a penalty, a detection method or a ranking update tied to this paragraph. What the guidance does say is that deception is a signal of a low-quality page, and that it reaches Google's automated systems, not only human raters. Weigh that against what the fake author was supposed to buy you. Google's Search Liaison account, the company's public voice on search, said in January 2024 that bylines do not help a page rank better, [as Search Engine Journal reported](https://www.searchenginejournal.com/google-fake-author-warning-site-owner-guidance/591806/). So an invented expert never earned the page anything in search, and it now sits in the exact category Google calls deceptive. There is a second cost that has nothing to do with Google. A customer who books a call and asks for the "senior consultant" from your blog, and finds out she does not exist, starts doubting everything else on the site. ##### How do small business blogs end up with a fake author? Few owners set out to invent a person. The made-up byline usually arrives with the outsourcing. One agency owner described the habit years ago in a [discussion on r/SEO](https://www.reddit.com/r/SEO/comments/7rkmwa/which_author_name_should_you_use_on_the_blog_to/): before posting a client's articles, "we would agree before posting to use the clients name or a 'persona' of the client to make it look more personable." The client's own name is honest when the client stands behind the post. The persona is where it goes wrong. A typical version on a service business's site looks like this: - an author box with a friendly first name and a stock or generated headshot; - a title such as "Marketing Expert" or "Head of Content" for a role the business does not have; - a bio that claims years of experience nobody can trace; - the same person writing about plumbing on Monday and tax deadlines on Thursday. In many of these posts the knowledge is real. It came from the owner's notes, a call, or years of answering the same customer questions. Only the name on top is invented, which makes the fix smaller than it sounds. ##### The byline test: who answers if a customer asks? Here is the test we use. Imagine a customer reads the post, rings the business, and asks to speak to the author about it. Whoever would take that call is the honest byline. If the owner gave the interview, checked the facts and approved the post, the owner's name belongs on it, even if someone else typed the sentences. If nobody at the business would recognise the post, a new byline will not save it. That post needs someone at the business to check it and stand behind it. Google's same page defines low effort as using "generative AI to produce large amounts of text without manual oversight or curation", and its [guidance on AI content](https://developers.google.com/search/docs/fundamentals/using-gen-ai-content) says it is "critical to manually factcheck and review all AI-generated content for accuracy and trustworthiness before publishing." At SharpHaw, the Lisbon web and content agency Gabriel Espinheira runs, we apply the same test to client blogs. A post is written from the owner's own interview, published under their name, and approved by them before it goes up. Because the experience in the post is theirs, they can take that call. ##### How do you fix the author on your blog? Work through it in this order: 1. **List every name.** Open each post, the author pages and any "team" section. Write down every person named as a writer. 2. **Match each name to a real person.** Every name should belong to someone who works with the business and would recognise the post. If an agency or freelancer writes for you, ask them who each byline is. If the answer is "a persona", ask them to switch it to you or to the company name. 3. **Swap generated headshots.** Use a real photo of the real author, or leave the photo out. A generated face presented as a person is one of Google's three named examples; an author box without a photo is not. 4. **Cut credentials you cannot back up.** Titles and years of experience in a bio should be ones the author could defend to a customer. 5. **Give the byline somewhere to go.** Google's guidance asks whether "bylines lead to further information about the author". Link the name to your About page or a short author page. This is for the reader who wants to know who is talking, not for rankings. 6. **Say how the post was made when a reader would wonder.** Google suggests disclosing automation where someone might ask "How was this created?" One line works: written with help from our content partner, from an interview with the owner, reviewed before publishing. Do not bulk-delete old posts to start clean. The same Google page warns that adding or removing lots of content only to make a site look fresh will not help. ##### Frequently asked questions **Can I use my company name as the author instead of a person?** Yes. A company byline is accurate when the company stands behind the post. Google's guidance asks for accurate authorship information and bylines "where one might be expected", and nothing in it says the byline must name a person. Use the owner's name where their experience is in the post. **Do I have to say that AI helped write my blog posts?** Google does not require a label on every post. It suggests saying how content was made where readers would reasonably expect to know, and it asks that AI-generated text be checked by a person before publishing. One short note on how your posts are written, plus a person who reads each post before it goes live, does both. **Will changing the author name on old posts hurt my rankings?** Google has said bylines do not help a page rank, so swapping an invented name for a real one is not a ranking change. It removes the deception Google now names as a low-quality signal. Change the byline, keep the post, and fix any claims the real author would not stand behind. ##### What to do next Check the name on every post this week, put the real person on it, and add one honest line about how the post was made. If your blog has no real person behind it at all, that is the bigger problem, and a new name will not fix it. If you would rather have a blog you can sign, our [Content Engine](https://sharphaw.com/services/content-engine) writes posts from your interview and publishes them under your name once you approve them. It runs from the Growth plan; the [plans page](https://sharphaw.com/plans) lists what each one covers. Or [book a 30-minute call](https://sharphaw.com/contact) and we will go through your current blog together. --- ### Search Console AI report: read it before you opt out of AI Overviews [Read on sharphaw.com](https://sharphaw.com/blog/search-console-ai-report-before-you-opt-out) · Content Engine · published 2026-10-13T08:00:00Z > Google's new Search Console AI report shows which pages AI Overviews and AI Mode cite. What it misses, who controls the opt-out, and what to check first. On 31 August 2026 Google finished rolling out two things to every Search Console property: a generative AI performance report, and a switch that removes your site from AI Overviews, AI Mode and the AI features in Discover. Most of what has been written since asks whether you should flip the switch. For a business whose website exists to win enquiries, the Search Console AI report matters more than the switch. The report is the first list Google has ever given you of the pages its AI answers link to. Read that list against the pages that bring you work, find out who actually controls the switch on your domain, and write your decision down with a date to revisit it. **TL;DR:** The Search Console AI report counts how often your pages appear in AI Overviews and AI Mode, by page, country, device and date, with no clicks and no queries. Leave the default setting on, compare the cited pages with the pages that bring enquiries, and make sure the domain property belongs to your business. ##### What the Search Console AI report shows Google's [generative AI performance report](https://support.google.com/webmasters/answer/16984139) answers one question an owner could not answer before: is Google using my pages in its AI answers, and which ones? It counts impressions: each time a link to one of your URLs was shown inside an AI feature on Google Search. Google announced it on 3 June 2026, tested it on a subset of sites, and finished the worldwide rollout on 31 August. You can group the count by page, country, device and date, and separate typed searches from image searches made with Google Lens or Circle to Search. The report leaves out most of what an owner wants to know. There is no query, so you cannot see what someone asked when your page appeared. There are no clicks, no click-through rate and no position inside the answer. A month of impressions on your service page tells you Google used the page, and nothing about whether anyone came. One quirk catches people on the first visit. The chart counts once per property, so two of your pages in one answer make one impression, while the table counts per page. The totals will not match, and that is expected. ##### Should you switch off AI Overviews for your site? For most businesses that sell a service or a product, no. Google's own [help page for the control](https://support.google.com/webmasters/answer/16908024) gives the reason: if you exclude your site, "content from other sites will still be available in those features, and it may appear similar to yours." The question a buyer typed does not go away when you leave. Someone asking AI Mode for an accountant in Porto who handles non-resident tax still gets an answer. It just names a different accountant. The case for leaving is narrow. It fits a business whose product is the information itself, such as a paid research service or a training provider, where a summary gives away what a reader used to pay for. For a clinic, a studio or a shop, a citation without a click is annoying. Losing the citation as well is worse. Two facts stop owners from pulling the wrong lever. The control is not a ranking signal, and Google says it does not affect your ordinary results. It also has nothing to do with AI training. Training runs through a separate robots.txt token, Google-Extended, which many sites set in the belief that it kept them out of AI Overviews. It never did; the difference between [training bots and answer bots](/blog/block-ai-crawlers-training-bots-vs-answer-bots) is its own decision. Leaving Google Search entirely is a third tool, `noindex`, and a much bigger call. Our own robots.txt at sharphaw.com allows every crawler, Google-Extended included, and blocks only the API routes. ##### Which pages is Google citing, and are they the ones that sell? Use the report for one comparison. Open the Pages tab and compare the last four weeks with the four before, since AI features trigger unevenly from day to day. Put that list next to the pages that produce enquiries: the service pages, the booking page, and the pages your analytics shows people reading just before they fill in the contact form. Two mismatches are worth looking for. **Google cites an old blog post or FAQ, and never the service page.** The service page probably answers the same question less plainly. Move the specific answer near the top in ordinary text: what you do, for whom, in which area, and how someone books. Those are the facts an AI answer can quote, and a page that buries them under a slogan gives Google nothing to lift. **Google cites the pages that sell, and enquiries from search are falling.** This is the case the report cannot settle, because it has no clicks. Set the AI impressions for those pages beside their Google organic visits and enquiries in your analytics, keeping in mind that some AI referrals [arrive labelled as direct](/blog/track-ai-search-traffic-when-ga4-calls-it-direct). If AI impressions climb while visits fall over the same weeks, on the same pages, and the standard Performance report shows their rankings holding, the answer is probably being given on Google's page. The page's job then is to make the click worth it with something a summary cannot hand over, such as a booking slot or a quote form. Check the Devices tab while you are there. If most AI impressions are on mobile, the page those people land on has to be quick and readable on a phone. ##### Who controls the AI switch on your domain? Each property inherits its setting from the one above it. By default every property follows the closest parent property that has set its own choice, and at the top sits the domain property, the one verified for your whole domain through a DNS record: one setting for every subdomain and subfolder beneath it. In the property picker, a domain property shows the bare domain (`example.com`); a URL-prefix property shows a full address starting `https://`. A child property, such as `https://example.com/blog/`, can override its parent, and the owner of the domain property sees a notice when one does. Search Console properties pile up over the years. One was verified by the developer who built the first site, another was added by an SEO supplier, a third covers the subdomain of a booking tool. Each owner can set the switch for their slice of your site, and some of those people no longer work with you. Open every property you can reach, look at Settings and then Users and permissions, and check two things. The domain property should be verified under a Google account your business owns. No older property should override it without a reason somebody can still explain. Under SharpHaw's terms the [domain belongs to the client](/blog/domain-ownership-the-login-that-can-take-you-offline), so the Search Console domain property should sit in the client's Google account too, with the supplier added as a user. The same goes for any supplier you work with, because whoever owns that property decides whether your business appears in Google's AI answers. ##### What should you write down before you decide? The switch is cheap to reverse. Google says an exclusion takes effect within one to two days of going live, longer for cached content. A decision nobody recorded costs more, because in six months nobody will remember why the site vanished from AI Mode. Write four lines wherever you keep notes on the website: - the date you checked, and the setting you found on each property; - the pages the report says Google cites, and the pages that bring enquiries; - what you decided, and why; - the date you will look again. Put that date in December. The UK Competition and Markets Authority [has required Google](https://www.searchenginejournal.com/what-opting-out-of-googles-ai-search-features-means-now/584321/) to share click and click-through data for its AI features, with most of those measures due to start in December, and page-level controls by March 2027. Until clicks arrive, you are weighing impressions against nothing, which is a good reason to give the decision a review date. ##### Frequently asked questions **Does the UK ruling on AI data cover sites outside the UK?** The report and the switch already cover every site worldwide, according to Google's help pages. The click data is different: the Competition and Markets Authority's requirement is a UK obligation, and Google has not said whether those figures will reach every country. Check your own report in December. **Where is the switch, and what is it set to now?** In Search Console, under Settings, then Search generative AI. Every property starts on include. A property with a parent above it starts on inherit, which means it follows the closest parent that has made its own choice, ending at the domain property. **Why can't I see the generative AI report in Search Console?** Google says the report usually stays hidden when a site has not had enough impressions in AI features to show anything. It can also mean the site, or a parent property above it, is set to exclude. Check the Search generative AI setting before assuming the data is missing. **Can I see which searches triggered my AI impressions?** Not yet. The report groups impressions by page, country, device and date, with no query dimension and no click data. The nearest substitute is to read each cited page, note the question it answers best, and compare that with the queries the same page earns in the standard Performance report. ##### The short version The Search Console AI report will not tell you whether AI answers are costing you enquiries. It does tell you which of your pages Google quotes, which is enough to start work. Make the pages that sell as quotable as the pages that get cited, put the domain property in your own name, and date your decision for December. If you want to talk through what your report shows and which pages to fix first, [book a 30-minute call](https://sharphaw.com/contact). --- ### Do you need a website if your Instagram already works? [Read on sharphaw.com](https://sharphaw.com/blog/website-if-your-instagram-already-works) · Website · published 2026-10-12T08:00:00Z > Instagram makes people want you. A website answers the prices, hours and booking questions they check next. What a small site needs, and when to skip it. A café owner with a full Instagram grid asked [r/business](https://www.reddit.com/r/business/comments/16b4vad/is_a_website_really_necessary/) a question that comes back every few months in some form: does he really need a website, "considering he uses Facebook, Instagram, and a few other social media sites for his business"? The most useful reply had nothing to do with design: "your friend does not own his facebook page, his instagram page or any other social media. He can lose those pages for literally any silly reason." If your Instagram already brings in customers, you still need a website, and ownership is only half of why. Instagram is very good at making people want you and poor at answering what they check right before they book. The account it all runs through can also be switched off, and getting a person at Meta to look at it is slow. **TL;DR:** Yes. If Instagram already works, you still need a website, and a small one is enough. Keep Instagram for attention. Put the facts a buyer checks before acting (services, prices or price ranges, hours, location, how to book) on a site you control, point your bio at it, and take enquiries through a form that needs no Meta login. ##### What can a website do that an Instagram profile can't? A website answers the questions a buyer asks in the minute before they act, while Instagram answers the question before that one. The feed proves the work is good and the place feels right. Then the buyer wants a price, a menu, opening hours, whether you cover their area, and a way to book that doesn't depend on you replying to a DM. Highlights, pinned posts and the contact or booking buttons on a business profile help, but on most profiles the answers still end up spread across a pinned post from last spring, a highlight and a caption, and some are nowhere. One commenter in the same r/business thread described what that costs. They find a café on Maps and need the menu: "I seriously got to poke around and happen to bump into it on the FB page? It's obviously not going to be found on Instagram. What about the hours and contact info?" Their conclusion: "I'm done trying to deal with this nonsense and look for another cafe." That commenter isn't an outlier. In SOCi's 2026 Local Discovery Index, a survey of more than 1,000 US consumers [published on 5 October 2026](https://martech.org/ai-usage-surges-6x-for-local-search-fragmenting-the-digital-ecosystem/), 43% said they preview a business on social media before committing, and 63% had walked away from a business that couldn't answer a question they needed answered. Instagram gets you into the shortlist. Whether the question gets answered is a separate job. A feed is ordered by date and a website by question. That's why a busy Instagram makes the missing website more expensive: every extra person the feed persuades arrives at a profile that can't tell them what they need to know. ##### What happens to your business if Meta locks the account? In June 2025, [TechCrunch reported](https://techcrunch.com/2025/06/16/instagram-users-complain-of-mass-bans-pointing-finger-at-ai/) that Instagram users had complained "for weeks" about a significant increase in accounts being mistakenly banned or suspended, and that some appeals got no response at all. Businesses were caught in it. A gym owner wrote that the ban "has directly affected my business and all of the hard work and branding that I've spent countless hours pouring into my business, my gym, and my students." The same report said affected users had no other way to directly contact a member of Meta's support team unless they paid for one of Meta's subscriptions that offer priority access to customer service, and Meta offered no on-record statement at the time. When the profile is your only home online, a lockout takes the shop window and the enquiry inbox at the same time, along with every DM conversation with a customer. You can appeal, but you can't open a parallel account and expect anyone to find it. A website on a [domain you own](/blog/domain-ownership-the-login-that-can-take-you-offline) keeps the address, the facts and the enquiry form working while you sort the account out. Customers who search your name still land somewhere that says you're open. ##### Doesn't Instagram show up on Google now? Partly. Since 10 July 2025, Instagram lets search engines show public posts from professional accounts of adult users, [switched on by default](https://ppc.land/instagram-content-becomes-searchable-on-google-starting-july-10/) under Settings → Privacy. So a Reel or a carousel can now appear in Google results. That helps a post get discovered. Someone searching "lash extensions Lisbon price" or "boiler repair Saturday Lisbon" wants a page that answers that query, and a post only answers whatever its caption happened to say on the day it went up. Prices change, a service gets added, the Saturday hours stop; the old post keeps ranking with the old facts. For local searches, your [Google Business Profile](/blog/your-google-business-profile-outsells-the-website-you-obsess-over) does more work than either. It also has a website field. Point it at an Instagram profile and the person who just searched for you by name lands on a feed instead of your hours and prices. ##### When is Instagram alone enough for a small business? Instagram alone is enough when new customers come almost entirely through people who already know you, and the DM queue never slips. A fully booked barber with a waiting list of regulars won't feel much difference from a new website next month. In the r/business thread one commenter knew cafés in a large capital city whose websites got "a whopping 12 unique visitors per month". If that's you, spend the money elsewhere. You've outgrown Instagram-only when any of these start happening: - you answer the same price, hours and availability questions in DMs every day; - an enquiry got lost because it arrived on a busy afternoon and sank under newer messages; - customers ask whether you're still open, because the last post is three weeks old; - you want buyers who don't use Instagram. As one commenter put it, "I deleted my facebook and instagram... There are countless of people like me." ##### What should a small website for an Instagram business include? A small website for a business that already sells through Instagram needs fewer pages than most owners expect, and every one of them answers a question the feed can't: - What you do and where: one sentence a stranger understands, plus the area you cover. - Prices, or honest "from" ranges. A missing price is a DM you'll have to answer. - Hours and address, kept current. - Real photos of the work and the place. Your Instagram already has the best ones. - One way to book or enquire: a form or booking link that lands somewhere you check every day, with a clear reply expectation. Our post on [contact forms](/blog/your-contact-form-is-where-european-enquiries-quietly-die) covers where those enquiries go missing. - A link back to Instagram for the latest work. Then change one setting: point your Instagram bio at the website instead of a page of nine links. ##### How we split the work between Instagram and the website We're SharpHaw, a Lisbon web agency, and we run our own content on the split this post recommends. Our Instagram Reels end by sending viewers to the full article on sharphaw.com, where the newsletter signup and the contact form sit on pages we control. If the account went dark tomorrow, the articles and the form would still be there. For a café or a salon the same split is simpler: the feed shows today's work, and the site holds the menu, the prices, the hours and the booking form. For a business in that position we have a plan called [Foundation](/new-website): the website on its own, built to a scope we agree before any work starts, hosted and kept up, with small text and photo changes on request. The domain is registered in your name and the content is yours to export, and enquiries from the site's form land in SharpOS, our client workspace. It doesn't include content or ads work, so it suits a business whose Instagram is doing its job and whose website is missing. ##### Frequently asked questions **Can I use my Instagram profile as my website?** You can link to it, but it can't do a website's job. A profile can't hold a price list, opening hours and a booking form in the order a buyer looks for them, and you don't control the account. Use Instagram for discovery and a small website for the facts and enquiries. **Is a link-in-bio page enough instead of a website?** A link-in-bio page is a list of links, so it moves the question somewhere else without answering it. It also usually sits on the tool's own domain, so it disappears if you stop paying or the service closes. A one-page site on your own domain does the same job and stays yours. **Will a website take followers away from my Instagram?** A website and Instagram do different jobs, so they rarely compete. Instagram brings strangers to you, and the website turns the interested ones into bookings or enquiries. Add a link from the site back to your feed and visitors who want to see recent work can follow you from there. ##### The short version If Instagram already works, keep it and give it somewhere to send people: a small site, kept current, with the facts a buyer checks before booking and a form that still works if the account is ever locked. If your feed is doing its job and the website is the missing piece, [book a 30-min call](/contact) and we'll look at what your Instagram sends you today and what the site needs to answer. --- ### Client waitlist: what your website should say when you're full [Read on sharphaw.com](https://sharphaw.com/blog/client-waitlist-website-fully-booked) · Website · published 2026-10-11T08:00:00Z > Build a client waitlist that explains availability, deadlines and what joining means. Give visitors a next step when your service business is fully booked. When your service business is fully booked, a client waitlist should tell visitors when you expect to have room, what joining means, and what happens if a suitable opening appears. Put that information beside the enquiry button. A visitor should be able to decide whether waiting fits their deadline before writing a brief. Imagine a landscaping company with a full schedule and a website still inviting everyone to request a consultation. The owner receives enquiries for jobs they cannot start. Prospective clients wait for a reply without knowing whether there is a realistic route to hiring the company. A waiting list can give both sides a useful next step, provided someone owns the list and the promise attached to it. **TL;DR:** A client waitlist works when the website explains current availability, asks about the visitor's deadline, and makes the next contact clear. Joining should record interest without implying a reserved booking. Publish the allocation rule, keep availability current, and offer an honest alternative when the visitor cannot wait. ##### Which client waitlist are you offering? A place on your client waitlist should mean exactly what the business can deliver: consideration for future work, notification of a cancellation, or a place in a defined queue. Those are different offers. Choose one before writing the button. For recurring appointments, a cancellation notification can be enough. [SimplyBook.me's waiting-list documentation](https://help.simplybook.me/wiki/Waiting_List_custom_feature) describes invitations to book when an appointment becomes available. Its documented system notifies everyone waiting for that date; the first person to book gets the opening. The notification itself does not reserve the appointment. A project business may need to review scope before offering a start. A designer or landscaping company can have an opening that fits a small job but cannot accommodate a larger one. A place on that list can mean the owner will contact prospects whose scope and timing fit the available capacity, rather than offering the same slot to everyone. Write the distinction beside the form. "Join the cancellation list" and "Ask about a future project" help visitors understand what they are requesting. "Reserve your place" is a poor label if no place is being reserved. If you allocate work by fit rather than arrival order, say so before the visitor joins. ##### How do you show availability without promising a date? "Fully booked" leaves a visitor unable to judge whether to wait, so your service page needs the most useful availability information you can support. That may be an earliest start window, a month when you will review new projects, or a plain statement that you cannot estimate an opening yet. Keep estimates separate from confirmed commitments. In an illustrative landscaping example, "We expect to review new garden projects next month" describes the next decision. "Your garden starts next month" commits to delivery before anyone has checked the job. Even an accurate calendar cannot settle scope, location, access, or the client's own timing. Ask for the latest acceptable start date when that changes whether you can help. A visitor who needs the work before an event can rule themselves out without an unnecessary sales call. A visitor planning further ahead can leave enough context for a relevant reply. Keep this message on the service page and beside the form. A banner on the homepage is easy to miss when someone lands directly from search. Give one person responsibility for updating availability when the delivery calendar changes. The website needs to reflect the capacity you have, including time for existing commitments, rather than every empty square in a diary. ##### What information belongs in the waiting-list form? Start with the information needed to match a future opening: contact details, the service requested, and timing. Add a question only when its answer changes which opportunity you would offer or whether you can take the work. For the landscaping example, location and a short description of the work may be useful. Ask for a budget range if that determines whether you can take the job. A detailed planting plan and inspiration folder can wait until the company is ready to discuss the project. Asking for a full brief now creates review work before there is capacity to act on it. [SimplyBook.me's client waitlist guide](https://news.simplybook.me/6-strategies-for-effective-client-waitlist-management/) recommends structured enquiries and a record of prospective clients. At SharpHaw, we would start with the smallest record that supports a real decision: requested service, acceptable timing, the person responsible for replying, and whether the prospect is waiting, booked, or no longer interested. A spreadsheet can do that job while the list is small. Buy additional tooling when a specific failure gives it something useful to fix. To check the form's placement, open a service page and follow its enquiry journey. Where would someone with an urgent deadline first discover that you cannot start? Our [website concepts](https://sharphaw.com/cases) offer working examples of page and enquiry layouts you can inspect for that question. They are concept builds, not evidence of waitlist results. ##### What should happen after someone joins? The confirmation should explain what you recorded, whether anything is reserved, and how the visitor will hear about a suitable opening. Send the same information in the acknowledgement so the person can find it later. For example, an appointment service might say: "You're on the cancellation list for this service. We'll email if an opening becomes available. Your appointment is confirmed only after you complete a booking." A project service might explain that it reviews enquiries for scope and timing before offering a discussion. Use the promise your operation actually supports. Decide how to offer an opening before sending the first invitation. If you contact everyone at once, say that availability can change before they book. If you contact prospects individually, decide how long an offer remains available and explain that in the invitation. Avoid letting a visitor believe you have held a slot when you are still offering it elsewhere. Allow people to leave the list or update their deadline. Remove enquiries from the active list when the work is booked, declined, or no longer needed. Keep a tally of those outcomes for demand planning instead of treating every old contact as someone still waiting. Neither enquiry count is confirmed work. If you manage website changes in a [shared workspace](https://sharphaw.com/sharp-os), record who updates availability as well as who replies to enquiries. Otherwise a revised delivery calendar can leave an obsolete promise on the page. ##### What to change in your next website iteration Start the website change with a real constraint from your delivery calendar. Add the supported availability message beside the relevant form, decide what joining means, and name the person who will act on the enquiry. That is a focused piece of work to plan, build, and review, which is how we approach continuing website improvements. Test the revised journey with a deadline you cannot meet. The visitor should find an answer before joining: a later booking, an invitation to wait with the uncertainty explained, a suitable referral, or a clear refusal. If the form accepts the enquiry anyway, inspect what the acknowledgement promises and who receives the request. If you need help changing that journey, [discuss your website with us](https://sharphaw.com/contact). --- ### Why SharpHaw works monthly: websites improve through sprints [Read on sharphaw.com](https://sharphaw.com/blog/why-sharphaw-works-monthly-website-sprints) · Website · published 2026-09-26T08:00:00Z > Why SharpHaw works monthly: see how website sprints connect customer feedback, useful changes and care. Explore Plan. Build. Iterate. and the trade-offs. A customer asks whether installation is included. The answer is obvious to you, but your newly launched website never says. A week later, someone wants to know which measurements to send before requesting a quote. Neither question was in the original brief. That is why SharpHaw works through a monthly website subscription. The first build gives your business a working site. Continuing collaboration gives us a way to act on what customers teach us afterwards, while the people doing the work still understand the decisions behind it. Our method is **Plan. Build. Iterate.** Short rounds of focused work, each informed by what happened before. **TL;DR:** SharpHaw's monthly website subscription funds continuing care and improvement after launch. We use short rounds of planning, building and review to connect customer feedback with the next useful change. Useful work accumulates when we retain what helps, correct what fails and adapt priorities as your business changes. Results still need evidence. ##### Why does SharpHaw charge monthly for a website? SharpHaw's monthly fee keeps someone responsible for the website as the business and its customers change. That responsibility includes maintaining the site, deciding what deserves attention with you, making the agreed changes and reviewing what happened. A launch brief can specify pages, design direction and the enquiry journey. It cannot fully predict the questions customers will ask once the site is in use, or the new service you will introduce later. Continuing work gives those discoveries somewhere to go. The monthly arrangement also preserves context. When the person changing the service page knows why the form asks a particular question, a seemingly small edit can be judged against the whole journey. The reasoning stays attached to the work in our shared [SharpOS workspace](https://sharphaw.com/sharp-os). At SharpHaw, I want the next improvement to begin with something the last one taught us. I am Gabriel Espinheira, the founder and senior engineer leading the work. The subscription is how I have chosen to organise that continuing responsibility. A recurring invoice earns its place only while the service remains useful. ##### How do engineering sprints apply to a website? Software teams using Scrum organise work into sprints: fixed periods of a month or less with a goal, a usable piece of work and opportunities to inspect and adapt. The [official Scrum Guide](https://scrumguides.org/scrum-guide.html) puts it simply: “Sprints are the heartbeat of Scrum”. For a business owner, the useful idea is a short commitment followed by a review. SharpHaw borrows that rhythm for website work through Plan. Build. Iterate. You do not need to learn Scrum roles or attend daily engineering meetings to take part. **Plan:** Agree the most useful problem to tackle next. Name the customer difficulty, choose a change small enough to complete responsibly, and decide what evidence would tell us whether it helped. **Build:** Design, write or implement the change. Test the affected journey, including mobile use and the steps after a submission. Put the work live when it is ready and approved through the agreed process. **Iterate:** Inspect the change and the available feedback. Keep what is useful, correct a failed assumption, or leave the site alone while more evidence arrives. Use that decision to shape the next round. Weekly shipping is our working cadence. Monthly is the billing period. Neither means every business result can be established in seven days. ##### What could three website sprints look like? An illustrative service business sells fitted storage. Its website shows attractive finished rooms, but prospective customers keep asking what the service includes. The following sequence shows how the work could develop; it is not a SharpHaw client case or a promised delivery schedule. **First round: explain the service.** The owner brings recurring questions about installation and preparation. We plan a clearer service-page section, build it and ask prospective buyers to explain the offer in their own words. We also review subsequent enquiries for the same confusion. The goal is understanding, so a new section alone does not prove success. **Second round: make the enquiry practical.** Suppose reviewing the enquiry journey reveals a different problem: customers are asked for room measurements without knowing which ones matter. The next change could add a labelled measuring example and let people explain when they do not have the measurements yet. We test whether a person can complete the form without being coached. **Third round: improve what arrives.** Suppose a test enquiry reaches the business, but the room details appear without their labels. Fixing that message becomes more useful than adding another homepage section. We verify that the information reaches the right person in a form they can act on. The service explanation, measuring guidance and corrected enquiry message remain useful together. Each round follows a specific finding. If the first review exposes a broken form instead, the order changes. The plan is allowed to learn. ##### How do website improvements compound over time? Useful website improvements can reinforce later work because the site retains both the improvement and the knowledge behind it. A clear explanation can inform the next service page. A tested form component can support another enquiry journey. Recorded customer questions can prevent the next brief from repeating an old assumption. There are two things worth accumulating: work that still helps the visitor, and evidence that improves the next decision. Fifty unrelated edits would not establish either. The benefit becomes easier to see over a quarter. In the fitted-storage example, a visitor could eventually understand what is included, prepare the relevant information and send an enquiry the business can use. That is a more complete journey than attractive photographs with a generic contact button. Whether it produces more suitable enquiries must still be measured. Your business may change during that quarter too. You might offer a new service, narrow your delivery area or discover that customers need a different explanation. Continuing attention lets the website reflect those decisions without waiting for a full redesign. **Digital work that compounds** means useful work can build on useful work. It does not describe compound interest, a guaranteed upward graph or a reason to keep adding features. Sometimes the next improvement is removing a confusing choice. ##### What should a weekly website review measure? A weekly website review should distinguish a working change from a demonstrated business outcome. A correctly delivered test enquiry proves the delivery path worked in that test. It does not prove that the new page caused more sales. Before building, choose a check that matches the question. For a form repair, verify completion and delivery. For unclear copy, observe whether relevant readers understand the service. For a commercial improvement, follow suitable enquiries and their outcomes over enough time to make the comparison useful. A small business may have too little traffic for a meaningful weekly conversion comparison. Customer conversations, observed tasks and actual enquiries can still expose problems. Record the limits of that evidence rather than treating a quiet week as a failed experiment. Keep a short record of the change, the reason for it, the check performed and what remains unknown. A later review can then distinguish a decision from a guess. If the change causes a problem, repair or reverse it. If the evidence is inconclusive, the next responsible action may be to wait. ##### When does a monthly website subscription make sense? A monthly website subscription fits a business that needs continuing changes and wants an external partner to own the technical work with it. The client still contributes business knowledge, feedback and approvals. The arrangement works best when there is a useful shared priority, rather than pressure to make visible changes just to fill a week. A defined project with a capable internal owner can be the better choice for a stable site with occasional updates. A project-built website can improve over time too. The deciding question is who will organise, implement and review that work after handover. For SharpHaw, [Foundation covers the website and its continuing care](https://sharphaw.com/new-website), with its blog and SharpOS. Growth adds Content Engine, Ads Management and AI Automations. The [current plans](https://sharphaw.com/plans) explain the scope so a website enquiry does not have to become an all-services commitment. The ownership trade-off matters as well: clients own their domain, brand, content and ad accounts; SharpHaw retains the website source code. Cancellation includes two months of website continuity and assistance exporting client materials. A fully static HTML export is available by agreement. Choose the model with those boundaries understood. A useful question for any ongoing arrangement is: what did the last change teach us, and why does that make the next change worth doing? The answer should connect the work to your business. If your website needs that continuing attention, [discuss your website and priorities with Gabriel](https://sharphaw.com/contact). --- ### How to reduce appointment no-shows: start with an attendance audit [Read on sharphaw.com](https://sharphaw.com/blog/reduce-appointment-no-shows-attendance-audit) · Automations · published 2026-09-21T08:00:00Z > Audit appointment no-shows, check confirmations and measure attendance before adding reminders. Includes a worked example and practical checks. A full booking calendar can still leave expensive gaps in the working day. Before adding another reminder, find out which appointments actually happened—and whether customers received enough information to attend. **TL;DR:** To reduce appointment no-shows, audit a completed week, separate missed appointments from cancellations and unknown outcomes, and test the confirmation journey yourself. Then change one part of the process and measure attendance again. Booking totals alone cannot tell you whether the problem is forgetfulness, confusion, or a failed handoff. ##### Start with appointments that were due to happen Pick a completed week. Export or list the appointments scheduled to take place during that week, using the appointment start date rather than the date the customer booked. Leave future appointments out: nobody has missed a meeting that has not happened yet. Give each appointment an outcome: attended, no-show, cancelled, moved to another time, or unresolved. A blank outcome belongs in unresolved until someone checks it. A calendar event reaching its end time does not establish that either person attended. Agree what counts as a no-show before calculating a rate. For example, an appointment can count as missed when the customer did not attend and had not cancelled before the agreed cutoff. Keep late cancellations visible as their own category if the business handles them differently. Apply the same definition next time; otherwise an apparent improvement may just be a change in bookkeeping. This is a small operational audit. Start with a spreadsheet if that is where the records are. The useful work is reconciling the rows, not choosing a dashboard. Ask the person who ran each appointment to resolve uncertain outcomes while the details are still fresh. ##### Calculate a rate you can explain Here is a **hypothetical example, not a SharpHaw or client result**. A business had 25 appointment slots on the calendar for a completed week. Five were cancelled or moved before the start time. Of the remaining 20 appointments, 16 were attended and four were missed. Every outcome has been checked. The no-show rate for the appointments still due to happen is: **4 missed appointments ÷ 20 expected appointments × 100 = 20%.** The five cancellations or moves remain in the report. Excluding those rows from this particular denominator does not make the lost time disappear. Record whether the released slots were filled again, and how much notice the business received. If two outcomes are still unknown, do not quietly count those appointments as attended or missed. Show the unresolved count beside any provisional rate and settle the records before comparing periods. An empty field measures missing information. Count lost hours as well as appointments if slot lengths vary. Missing a 15-minute introduction and missing a two-hour treatment each add one to an appointment count, but the capacity cost differs. Keep that calculation separate from revenue: an empty hour is not automatically an hour of lost sales at the headline price. ##### Follow one booking from form to front door Make a test booking through the same route a customer uses, with a test address you can check. Read the success page, confirmation email, calendar invitation and reminder on a phone. Verify the actual date, time zone, location or meeting link, expected duration and any preparation needed. Then try changing the appointment. Does the cancellation or rescheduling route work? Does the old time disappear from the relevant calendar? Does the customer know which time is current? A reminder that repeats an obsolete appointment makes the process worse. At SharpHaw, the contact flow distinguishes an accepted enquiry from a time that could not be confirmed. The success page says a calendar invitation will arrive and gives a fallback if it does not. That wording matters because saving a form submission and completing a downstream calendar action are different events. It is evidence about the website's behaviour, not evidence of a lower no-show rate. A [website built around the customer journey](https://sharphaw.com/new-website) should make the next action clear. The audit extends beyond the website, though: a polished form cannot compensate for a missing meeting link in the invitation. ##### Make reminders useful before making them frequent A useful reminder lets a customer answer three questions quickly: when is the appointment, where do I go, and what do I do if I cannot attend? Put the appointment details in the message and include the actual route for changing the booking. Test that route instead of assuming a button label proves it works. Choose reminder timing around a decision the customer can still make. An appointment requiring travel or preparation may need different notice from a short online call. Start with the process the business can reliably operate; adding messages creates little value if each message still lacks the location. Current scheduling products support reminders and distinct booking events. For example, [Cal.com's webhook documentation](https://cal.com/docs/developing/guides/automation/webhooks) distinguishes booking creation, rescheduling, cancellation and no-show updates. Those distinctions are useful when designing a workflow. The existence of a feature does not establish how much the feature will improve your attendance. Business owners also ask how to reduce missed slots without making booking unfriendly; that concern appears in [this small-business discussion](https://www.reddit.com/r/smallbusiness/comments/1tz6m53/how_do_you_reduce_noshows_for_service/). Treat the discussion as a demand signal, not a controlled comparison of reminder strategies. If a customer does not reply to a reminder, that silence alone is not permission to cancel an appointment. Any reconfirmation requirement needs to be communicated clearly as part of the booking terms and operated consistently. ##### Match the intervention to the failure If the confirmation never arrives, investigate the delivery path and give customers a reliable fallback. If the time zone is confusing, fix how the time appears. If customers need to change appointments but cannot find the route, make the route obvious and usable. These are different problems, even when the calendar ends up with the same empty slot. Deposits or stricter cancellation terms may suit some scarce, costly appointments. They also add a decision or payment step before booking. Do not impose them because another business reports fewer no-shows. First establish whether your missed appointments come from weak commitment, avoidable confusion, or a technical failure. Explain any terms before the customer commits and check requirements that apply to your business before changing them. Keep the scope of the first fix small enough to evaluate. For example, correct a missing location in the confirmation and check subsequent bookings through that route. Changing reminder frequency, deposits and cancellation rules together makes it harder to tell what helped or what discouraged suitable customers. An operating system such as [SharpOS](https://sharphaw.com/sharp-os) can hold the work around a customer journey. Whatever system you use, make one person responsible for resolving missing appointment outcomes. A new automation cannot recover a fact nobody recorded. ##### Compare attendance, not just the booking total Run the same audit for another completed period after the change. Keep the appointment types, definitions and reporting window comparable. Record bookings, attended appointments, no-shows, cancellations, moves, unresolved outcomes and released slots filled again. A smaller no-show count alongside a sharp fall in bookings is not enough to call the change a success. For low-volume businesses, one or two appointments can move a weekly percentage substantially. Keep the raw counts beside the percentages, and look across several comparable periods before drawing a confident conclusion. Note holidays, changes in service mix or other disruptions that could explain the difference. The first useful result may be finding a broken confirmation or discovering that the team never records attendance. Fixing that gap gives you something concrete to test next. It does not require a claim that one reminder schedule works for every business. If the break starts with your website's booking or enquiry journey, [talk to SharpHaw](https://sharphaw.com/contact). Bring an example of the confirmation a customer receives and the step that fails. That is a better starting point than a full calendar alone. --- ### How much does a marketing agency cost per month [Read on sharphaw.com](https://sharphaw.com/blog/how-much-does-a-marketing-agency-cost-per-month) · Marketing · published 2026-09-10T08:00:00Z > Compare monthly website, content, ads and automation costs with SharpHaw plans, including setup fees and the tools SharpOS could replace in your budget. A marketing agency can cost a few hundred euros per month for one focused service, or several thousand for a website, content, advertising management and ongoing automation work. In the published European offers below, buying those four areas separately adds up to **€4.254 per month**, before software, setup fees and advertising spend. SharpHaw Growth includes all four service areas and SharpOS for **€2.500/month plus VAT, no annual contract**. Add an illustrative €90,50 of separate tool subscriptions to the comparison basket, and the difference becomes **€1.844,50 per month**. The deliverables differ, so the scope beside each price matters as much as the total. **TL;DR:** Our separate-service example totals €4.254 a month, or €4.344,50 with three optional paid tools. SharpHaw Growth, with all four service areas and SharpOS, is €2.500/month and Scale is €4.000/month. Foundation, the website on its own, is €1.000/month. All plans are plus VAT, no annual contract, and Custom is scoped on the call. Compare content volume, channels, ongoing work, setup and ownership before choosing. Count software savings only when you can cancel the corresponding subscription. ##### What does each marketing service cost per month? Published prices become useful when you can see what they buy. The examples here come from German providers serving the European market, checked on 9 September 2026. We describe each by its model rather than its name. They are a small set of public offers, **not a statistical market average**. We use the listed fees before applicable taxes and keep one-off charges separate. | Service | Published monthly examples | Price used below | What that selected offer covers | |---|---:|---:|---| | Managed website | €129–€359 | €279 | Business website, up to 15 pages, hosting and care, two hours of changes monthly | | Content and social media | €750–€1.995 | €1.995 | Five channels, 25–30 social posts and four blog articles monthly | | Google Ads management | €290–€890 | €490 | Search, Shopping and remarketing; intended for up to about €5.000 monthly media spend | | Ongoing AI automation | From €1.490 for continuing development | €1.490 | Automation operation plus an allowance for continued expansion | | **Selected recurring service total** | | **€4.254** | Four separate purchases at these listed prices | The website example is a German agency's website subscription at its business tier. It also carries a €1.490 setup fee and a 12-month minimum at the selected rate. A maintenance allowance is different from a commitment to deliver a new campaign landing page every month. The content example is a German social-media agency's top package, with €1.890 setup. It is selected because it includes four monthly blog articles. Its five-channel social scope exceeds Growth's three channels; customers supply raw material and handle community management. We have not added another blogging retainer to that package. The advertising row comes from a Google Ads management provider's mid-tier offer. The €490 is the management fee. The advertising budget is paid separately. A €2.000 media budget would therefore make that part of the bill €2.490, not €490. The automation row is an AI-automation consultancy's ongoing partner offer, from €1.490 monthly with a 12-month term. The same provider lists operation and maintenance from €290 monthly, and an automation sprint from €4.900 once. Those are different jobs. Use the lower maintenance fee only when you already have the automation and need that narrower service. ##### What does SharpOS replace in the software budget? SharpOS is included with SharpHaw, with no separate workspace subscription. It brings the work queue, documents, approvals, creative assets, forms and reporting into the workspace used to deliver the service. That can remove the need to buy separate tools for those particular jobs. For example, **SharpOS Pages and Boards** can hold the marketing brief, decisions, tasks and content calendar that a small team might otherwise keep in Notion. The content workflow can handle review and supported publishing needs that might otherwise require a separate scheduler. **Forms** can collect website enquiries, while **Studio and Media Center** keep approved creative and source assets alongside the work. These are replacements for defined workflows. A company using Notion across finance, hiring and product development may still need Notion. A specialist publishing integration or form feature may also justify keeping its current tool. [See the SharpOS workspace](https://sharphaw.com/sharp-os) and check the actual workflow before cancelling anything. Here is a small optional software basket, using monthly billing: | Separate subscription | Assumption | Monthly cost | |---|---|---:| | [Notion Plus](https://www.notion.com/pricing) | Three paid members at €11,50 each | €34,50 | | [Buffer Team](https://buffer.com/pricing) | Three channels at $12 each | About €31,00 | | [Tally Pro](https://tally.so/pricing) | One paid forms workspace | €25,00 | | **Potential avoidable software spend** | Only if all three subscriptions can be retired | **About €90,50** | Buffer's $36 is converted using the [ECB reference rate for 8 September 2026](https://www.ecb.europa.eu/stats/shared/pdf/eurofxref.pdf?ec0baba70b01eb1e6d99a12c35f18d69=), €1 = $1.1614, and rounded to €31 for this model. Your invoice exchange rate can differ. All three providers have free options. This basket assumes a team already needs their paid collaboration, approval or branding features. If free tools cover your needs, the saving is zero. If the content supplier already provides the scheduler without a separate client bill, remove Buffer from the sum. **A tool is a saving only when its bill goes away.** ##### How does the total compare with SharpHaw? At the selected providers' published prices, the four-service basket costs €4.254 monthly. Adding the optional €90,50 tool basket takes it to approximately €4.344,50. SharpHaw's Growth fee covers the four service areas and the shared SharpOS workspace together. | Monthly budget | Separate-service example | SharpHaw Growth | SharpHaw Scale | |---|---:|---:|---:| | Services | €4.254 | €2.500 | €4.000 | | Illustrated tool subscriptions | €90,50 | SharpOS included | SharpOS included | | **Monthly total** | **€4.344,50** | **€2.500** | **€4.000** | | **Difference from this example** | — | **€1.844,50 less** | **€344,50 less** | SharpHaw fees are plus VAT, no annual contract. Foundation, at €1.000/month, is not in this table because it is the website on its own: built to an agreed scope, hosted and kept up to date, with small text and photo changes on request, a blog you write in, and SharpOS. Set it against the website row, not the four-service basket. Custom, for separate software built around your operations, is scoped on the call. Growth's fee is about **42% lower than this assembled monthly budget**. Without any software saving, it is still €1.754 lower than the selected service subtotal. Those are price differences between the stated offers, not proof that every deliverable or provider is interchangeable. Growth includes the website and ongoing upkeep, one new landing page per month, four blog posts per month, management of up to three channels, ads management, and AI automation work within the agreed priorities. SEO and GEO reporting, monitoring and improvements are part of the service. Social publishing cadence is agreed with the strategy; the plan does not promise the example provider's 25–30 posts across five channels. Scale increases blogging to two posts per week, takes content and channel coverage beyond three channels, and supports e-commerce and deeper analytics. All four service areas are already in Growth. Moving to Scale is about greater volume and scope. The work is prioritised together through SharpOS. A request queue does not mean every website change, campaign and automation runs simultaneously. [Compare the current plans](https://sharphaw.com/plans) against the output your business will actually use. ##### What will you pay over the first year? To compare the first year, multiply recurring fees by 12 and add setup charges once. That prevents a low monthly website rate from hiding an upfront build cost, and prevents a one-off automation project from being charged twelve times in your spreadsheet. Using the same basket and holding its rounded software cost constant: | Twelve-month component | Separate-service example | SharpHaw Growth | SharpHaw Scale | |---|---:|---:|---:| | Recurring services and illustrated tools | €52.134 | €30.000 | €48.000 | | Listed website and content setup | €3.380 | €0 setup fee | €0 setup fee | | **Total of these known components** | **€55.514** | **€30.000** | **€48.000** | Foundation over the same 12 months is €12.000, with no setup fee. The €3.380 is the website and content setup already identified. The automation partner's page does not settle every potential onboarding charge, so obtain a quote for the exact work. The example is a planning calculation, not an offer to buy all four services for a guaranteed total. SharpHaw has no setup fee, minimum term or annual commitment. The 12-month figure assumes you choose to stay for 12 months. Ad spend goes directly to the platforms. Support AI usage through the client's OpenAI or OpenRouter account is separate, as are any other agreed external usage charges. Applicable taxes and migration costs are outside this comparison. Ownership also changes the purchase. With SharpHaw, you own your domain, brand, content and advertising accounts; the website source code remains SharpHaw's. After cancellation, the website stays live for two months while we assist with exporting your content and data. A static HTML export is available by agreement. Buying an independently owned codebase is a different requirement and should be priced as such. ##### When is a monthly agency bundle worth the cost? A bundle makes the strongest financial case when you need the website, content, ads and automation work on an ongoing basis. The value comes from buying the combination you will use, with a shared place to manage it. SharpOS can then reduce the separate software bill as well. If you only need Google Ads management, a focused €290 or €490 service from the example above may cost less than a €2.500 bundle. If your website is the only problem, Foundation at €1.000/month is the plan to compare, not the bundle. If your website is already maintained, you publish internally and your automations need occasional care, the €4.254 basket overstates your needs. Some providers also sell lower-priced bundles; adding separate suppliers is only one way to buy. Before comparing quotes, write down your monthly requirement: how many articles, which channels, what website work, which campaigns and what automation changes. Ask each supplier to price that same list. Then add setup, media, usage charges and the software subscriptions you would still retain. That gives you a useful answer to “how much does a marketing agency cost per month?” For a business that needs our four service areas within Growth's scope, **SharpHaw is €2.500/month plus VAT, no annual contract, with SharpOS included**. [Book a 30-min call](https://sharphaw.com/contact) to compare that scope with the work and subscriptions you are paying for today. --- ### Website maintenance: what are you actually paying for? [Read on sharphaw.com](https://sharphaw.com/blog/website-maintenance-what-are-you-actually-paying-for) · Website · published 2026-09-08T11:00:00Z > Learn what a website maintenance fee should cover across hosting, technical care, content changes and conversion improvement. > **TL;DR:** A useful website maintenance agreement names four separate jobs: hosting, technical care, content changes, and conversion improvement. Each needs an owner, cadence, evidence, and boundary. If the scope only says “maintenance”, you are buying availability without a clear promise of what will change. “Hosting and maintenance” is one of the most expensive vague phrases in a service agreement. It can mean somebody keeps the server online. It can mean updates, backups, content edits, analytics, landing pages, or a monthly report nobody reads. Two providers can use the same label while selling entirely different responsibilities. That ambiguity creates the familiar question: what am I actually paying for? The answer should fit on one page. Split the work into four jobs, then make each job accountable. ##### 1. Hosting keeps the website available Hosting is the infrastructure the site runs on. It usually covers the server or platform, bandwidth, certificates, deployment infrastructure, and basic availability monitoring. The accountable version names: - where the site is hosted; - who owns the account and billing relationship; - how uptime is monitored; - who responds when the site is unavailable; - what recovery path exists if a deployment fails. Hosting does not automatically include fixing application bugs, updating content, improving page speed, or changing a form. Those are separate jobs. Ownership matters here. Your business should be able to leave a supplier without losing its domain, content or data, and it should know before signing who owns the code. Our [website plans](https://sharphaw.com/plans) put that line in writing: the domain, brand, content and data are yours; the code stays SharpHaw's. ##### 2. Technical care keeps the system healthy Technical care starts where hosting stops. It covers the work required to keep the website secure, compatible, recoverable, and technically sound. Depending on the stack, that can include: - dependency and platform updates; - security patching; - backup checks and restoration tests; - broken-form and broken-link monitoring; - performance checks; - error investigation; - accessibility regression checks; - DNS, certificate, and integration maintenance. The word “updates” is not enough. A useful scope defines how often checks happen, what gets fixed without approval, what requires a separate decision, and how completed work is shown. A report that says everything is green is weak evidence. A short change log is better: what was checked, what changed, what failed, what remains open, and who owns the next action. ##### 3. Content changes keep the website accurate A technically healthy website can still be commercially wrong. Services change. Team members leave. Offers become clearer. Proof ages. A launch announcement stays on the homepage for six months. Content maintenance exists to keep the site aligned with the business buyers meet today. This job needs an operating rule, not an unlimited-edits promise. Define: - what counts as a content change; - where requests enter the queue; - who supplies and approves the source material; - the expected turnaround; - the number of active requests; - what becomes a new page, feature, or project. The request system matters as much as the allowance. Work disappears when it lives across email, chat, documents, and calls. A shared queue, such as the one we use in [SharpOS](https://sharphaw.com/sharpos), leaves one visible record of the request, decision, draft, and approval. ##### 4. Conversion improvement makes the website earn its keep Conversion improvement is the job most often implied by a maintenance fee and least often specified. It is not the same as keeping the site online. It means finding and shipping changes intended to help more qualified visitors take the next useful action. That can include: - clarifying an offer or call to action; - improving a high-intent service page; - reducing friction in a form; - creating a campaign landing page; - adding missing proof; - fixing a mobile journey; - testing a meaningful page change; - connecting website behaviour to sales feedback. This work needs a hypothesis and a decision, not just activity. Every change should say what problem it addresses, what was shipped, what evidence will be watched, and when the result will be reviewed. That is the difference between a maintained brochure and a [conversion-first website](https://sharphaw.com/services/conversion-first-websites) that continues to adapt. ##### Put one accountability line under each job An honest scope can use the same four fields for every job: | Field | Question it must answer | | --- | --- | | Owner | Who notices and acts without being chased? | | Cadence | When does this work happen? | | Evidence | How can the client see what changed? | | Boundary | What is included, and what triggers a new decision? | Applied to the four jobs, the agreement becomes much easier to inspect: | Job | Accountable promise | | --- | --- | | Hosting | Keep the site available and own incident response | | Technical care | Check, patch, test, and document system health | | Content changes | Ship approved updates through one visible queue | | Conversion improvement | Propose, release, and review commercial changes | If a supplier cannot fill those cells, the fee is not necessarily unfair. It is simply undefined. ##### Separate care from improvement There is a useful line between preserving the current system and improving its commercial performance. Care prevents deterioration. Improvement creates a reason for the site to get better. Bundling both can work, but the agreement should still show the allocation. Otherwise urgent fixes consume the entire month while improvement remains an implied future benefit. The client sees a recurring invoice; the supplier sees an endless support queue; neither can say whether the site is moving forward. One simple operating model is: 1. technical risks enter a care queue; 2. business requests enter a content queue; 3. one conversion opportunity is chosen at a time; 4. shipped work and open decisions are visible in the same workspace; 5. the next priority follows evidence, not whoever sent the last message. This is close to how SharpHaw structures a senior-led [growth subscription](https://sharphaw.com/plans): one queue, visible work, and continuous shipping across the website and the marketing around it. ##### Some websites only need two jobs A small brochure site with stable information and little qualified traffic may only need reliable hosting and periodic technical care. Paying for monthly conversion work would be theatre if nobody will use the evidence or approve changes. The right scope depends on the role the site plays in the business. If it is a contact card, preserve it. If it is expected to generate enquiries, support sales, launch offers, or answer buyer objections, it needs content and conversion ownership too. That is the strongest reason not to buy a broad maintenance package by default. Buy the jobs the website actually has. ##### Audit the next maintenance invoice Take the last month of work and sort every item into the four jobs. Then ask: - Which job received no work? - Which job has no named owner? - Which job produced no visible evidence? - Which requests waited because the boundary was unclear? - Which commercial improvement shipped? If the answers are hard to find, the next conversation should not start with the fee. Start with the scope. Name the jobs. Name the owner. Name the evidence. Then decide whether the arrangement is worth continuing. If your website is meant to support growth but its maintenance scope only preserves the status quo, [talk to SharpHaw](https://sharphaw.com/contact) about a clearer operating model. --- ### Gemini 3.8 Flash changes the model-routing question [Read on sharphaw.com](https://sharphaw.com/blog/gemini-3-8-flash-model-routing) · Automations · published 2026-09-05T08:00:00Z > Gemini 3.8 Flash changes model routing: default reversible, testable work to Flash, then escalate ambiguity, blast radius, and costly verification at runtime. Gemini 3.8 Flash is a sensible default for routine, reversible AI work. It is not a reason to send every task through one model. The release changes the model-routing question from “Which model is smartest?” to “Which mistakes can this step afford?” That distinction matters more than a benchmark win when an agent can send an email, update a database, publish copy, or change production code. **TL;DR:** Route Gemini 3.8 Flash to work that is routine, reversible, and cheap to verify. Escalate when the task is ambiguous, the blast radius is high, or checking the answer costs more than using a larger model. Measure rework and escaped errors, not token price alone. ##### What changed with Gemini 3.8 Flash? Google released Gemini 3.8 Flash as a generally available model on 2 September 2026. The company positions it for long-horizon software engineering, autonomous agents, and complex enterprise workflows, not only low-latency chat. That is the important shift: the “Flash” label no longer means “small jobs only”. The model accepts text, images, video, audio, and PDFs, with a 1,048,576-token input limit and a 65,536-token output limit. It supports function calling, structured output, code execution, search grounding, and low, medium, or high thinking levels. Medium is the default; minimal is not supported. Those details come from Google’s [Gemini 3.8 Flash model page](https://ai.google.dev/gemini-api/docs/models/gemini-3.8-flash) and [latest-model guide](https://ai.google.dev/gemini-api/docs/latest-model). The launch price sharpens the temptation to standardise on it. Through 31 December 2026, Google lists Gemini 3.8 Flash at $0.75 per million input tokens and $3.75 per million output tokens. Standard pricing begins on 1 January 2027 at $1.50 and $7.50 respectively. Useful. Still not a routing policy. ##### Should Gemini 3.8 Flash replace a Pro model? Gemini 3.8 Flash should replace a larger model only where the workflow makes failure cheap, visible, and recoverable. A model can be excellent on average and still be the wrong choice for a step whose single bad output creates a large clean-up job. That is why the launch-day community question — “Is Pro still viable?” — is too broad. One developer may be generating testable code inside a branch. Another may be letting an agent email a customer, alter a contract, or delete records. The same model quality produces very different business risk. Google’s own [model card](https://deepmind.google/models/model-cards/gemini-3-8-flash/) still names familiar foundation-model limits: hallucinations, occasional slowness or timeouts, and higher token use at higher effort levels. General availability means a stable production target. It does not remove the need for controls around the target. I use a simpler distinction when thinking about [AI automations](https://sharphaw.com/services/ai-automations): default work and exception work. Default work is frequent, well-specified, reversible, and easy to check. Exception work is ambiguous, consequential, or expensive to verify. Flash should win much more of the first category now. It has not abolished the second. ##### How should you route work between Flash and a larger model? Route each step by its error economics, not by the model’s place in a leaderboard. Five questions usually expose the right path. 1. **Can the result be reversed?** A draft can be rewritten. A published price, sent contract, deleted record, or production migration may not be easy to undo. 2. **How large is the blast radius?** One internal summary is different from 40,000 personalised emails. 3. **Is the task unambiguous?** Clear inputs and acceptance tests favour Flash. Conflicting objectives and incomplete context favour escalation. 4. **How expensive is verification?** A cheap first pass becomes expensive when a senior operator must inspect every line. 5. **Can the workflow stop safely?** Checkpoints, dry runs, approval gates, idempotency, and rollback paths make a faster model much safer. This produces a router that is deliberately boring. Routine extraction goes to Flash. A confidence failure, policy conflict, missing input, or high-risk side effect moves the job to a larger model or a person. The model is only one control. The workflow carries the rest. ##### Which jobs belong on Gemini 3.8 Flash by default? Gemini 3.8 Flash is a strong default where correctness can be checked mechanically or the output remains a draft. Good candidates include: - classifying enquiries into an existing taxonomy; - extracting structured fields from documents with schema validation; - drafting internal summaries that link back to their sources; - generating first-pass code behind tests and a review gate; - rewriting copy within fixed brand and length constraints; - comparing records and flagging exceptions for a person; - running tool-based research where every factual claim retains a source. The shared feature is not that these jobs are easy. It is that they have boundaries. This is also why a one-model agent often underperforms a smaller system of explicit steps. Planning, extraction, drafting, checking, and acting do not carry the same risk. Split them before choosing the model. Our earlier guide to [building a content pipeline with specialised agents](https://sharphaw.com/blog/from-40-hours-to-4-automating-your-marketing-content-pipeline-with-ai) applies the same principle: one workflow can contain several jobs without pretending they need identical judgement. ##### When should a workflow escalate from Flash? Escalation should happen before a risky action, not after a bad result reaches a customer. I would route to a larger model or human review when any of these conditions appears: - the instruction conflicts with policy, brand, legal, or security rules; - the agent must infer intent from incomplete or contradictory context; - the next tool call changes money, permissions, customer data, or public content; - the task crosses several systems and rollback is uncertain; - the output cannot be checked with tests, schemas, source links, or a short review; - a retry repeats the same uncertainty instead of reducing it. Thinking level is useful here, but it is not a safety system. Raising Gemini 3.8 Flash from low to high may improve difficult reasoning, yet it does not create authorisation, validation, or rollback. It may also increase token use. Use thinking level to tune the model’s effort inside a route. Use workflow controls to decide whether the route is safe. That separation keeps the system legible. It also matches SharpHaw’s [tooling rule](https://sharphaw.com/values): AI where it multiplies output, software where it removes drag, and a person where judgement is the work. ##### How do you know the routing policy works? Token cost is the easiest number to collect and one of the weakest numbers to optimise alone. A cheap model can produce an expensive workflow if it creates retries, longer reviews, customer-facing mistakes, or silent bad data. Track four numbers per route: - **first-pass acceptance rate:** how often the output clears its defined checks; - **review minutes:** how much human time each accepted output still consumes; - **escalation rate:** how often the router sends work to the larger model or a person; - **escaped-error rate:** how often a bad result passes the gate and reaches the next system. Then compare total cost per accepted result, not price per token. If Flash cuts inference spend but doubles review time, the route is not cheaper. If it handles 80% of a queue and escalates the difficult 20% cleanly, the design is doing its job. The exact split will differ by workflow, but the measurement should make the trade visible. ##### Use the exception list as your routing policy Start with Gemini 3.8 Flash for a bounded task. Write the exception list before you connect the next tool: what must stop the run, what must escalate, what needs approval, and what evidence proves the step worked. The release raises the baseline for fast, cost-efficient agents. That is good news. It also makes lazy architecture harder to excuse. “Use the best model everywhere” is expensive. “Use the cheapest model everywhere” is brittle. A short routing policy turns model choice into an operating decision you can test and improve. [Map one recurring workflow on a 30-minute call](https://sharphaw.com/contact). Bring the steps, side effects, and current review time. You will leave with a clearer default path and an explicit exception list. --- ### Framer or Webflow template vs conversion-first service [Read on sharphaw.com](https://sharphaw.com/blog/framer-webflow-template-vs-conversion-first-service) · Website · published 2026-09-04T08:00:00Z > Compare a Framer or Webflow template with a conversion-first website service across strategy, tracking, ownership, iteration and ongoing work after launch. A Framer or Webflow template can be a sensible way to launch a website. You get a polished structure, responsive layouts and a visual system without beginning from a blank canvas. If your offer is already clear and you are happy to write, connect, test and maintain the site yourself, that may be all you need. The choice changes when the site has to produce enquiries, bookings or sales. Then you are not comparing two ways to draw pages. You are comparing a website template with a service that owns the decisions around those pages. > **TL;DR:** Buy a template when you have a clear offer, simple requirements and someone who can own the setup and upkeep. Buy a conversion-first website service when the site is tied to revenue and you need strategy, copy, tracking, QA and ongoing improvement to have a named owner. ##### What does a Framer or Webflow template actually buy? A template buys a head start. Framer says its free marketplace alone contains more than 2,000 customisable, responsive templates. Its own quality checklist covers audience fit, page hierarchy, mobile behaviour, CMS structure, accessibility and performance. That is substantial raw material, especially for a small brochure site or a focused landing page. [Framer's marketplace](https://www.framer.com/marketplace/templates/categories/free-website-templates/) and [template checklist](https://www.framer.com/help/articles/template-best-practices/) make the case well. Webflow describes templates in similar terms: a template becomes a new site that you can customise as much or as little as you want. The trade is that you still need to understand the Designer, the template's structure and any complex interactions it contains. Some templates also require paid Site or Workspace plans. [Webflow's template overview](https://help.webflow.com/hc/en-us/articles/33961270477971-Webflow-templates-overview) is explicit about that learning curve. Neither product is a toy. Both can produce a fast, responsive, professional website. A good template can remove days of layout work and give a non-designer a coherent starting point. What it cannot do is know your business. ##### Can a website template convert visitors into clients? Yes. A template can convert if the decisions inside it are good. The builder is not the limiting factor. Framer now supports funnels and built-in A/B tests around link clicks, form submissions and page visits. Webflow publishes a full conversion rate optimisation process built around data, blockers, hypotheses, variations, QA and an experimentation roadmap. [Framer's A/B testing guide](https://www.framer.com/help/articles/how-to-run-an-a-b-test-on-your-framer-site/) and [Webflow's CRO guide](https://help.webflow.com/hc/en-us/articles/34217155451539-Conversion-rate-optimization-CRO-best-practices) both show that serious optimisation can happen on either platform. The missing piece is not a feature. It is the person making the call. A template cannot decide which buyer the homepage should prioritise. It cannot tell whether "Book a call" is too large an ask for a visitor who still needs pricing, proof or scope. It cannot know that a form submission should become a qualified enquiry in your CRM rather than an unread email. It cannot decide whether this week's problem is the headline, traffic quality, a broken handoff or the offer itself. Those are conversion decisions. Someone still has to own them. ##### How does a template compare with a conversion-first website service? The clean comparison is not template versus bespoke design. It is asset versus responsibility. | Decision | Framer or Webflow template | Conversion-first website service | |---|---|---| | Starting layout | Included | Chosen or built around the job | | Positioning and page promise | You decide | The service works it through with you | | Copy | You write or commission it | Written as part of the conversion path | | Analytics and events | Tools are available | Events are defined, connected and reviewed | | Forms and handoff | You configure the destination | The path from click to enquiry is part of the build | | Quality assurance | You test devices, states and integrations | QA has a named owner | | What changes next | You inspect the data and choose | The site enters a continuing improvement queue | | Ongoing maintenance | You, a freelancer or platform support | Part of the operating relationship | SharpHaw's [Conversion-First Websites service](/services/conversion-first-websites) is built around that right-hand column. It covers the full site, landing pages, copy, speed, SEO, conversion tracking and weekly improvement. The launch starts the loop rather than ending the project. That is also why comparing prices without comparing responsibilities is misleading. A template fee is the price of the starting asset. A service fee pays for senior judgement, implementation and a continuing queue of decisions. They are different purchases. ##### When is a template the better choice? Choose the template when all of the following are true: - Your offer and audience are already clear. - The site is small and the content will not change often. - You can adapt the copy instead of forcing your business into placeholder sections. - Someone can configure forms, analytics, metadata, accessibility and responsive states. - You are comfortable learning the builder or paying for help when it breaks. - You do not need a weekly optimisation cadence. This is a strong fit for a portfolio, event page, early validation site or a local business whose website mainly needs to make basic information easy to find. There is one procurement detail worth checking on Webflow. Paid marketplace templates use a single-use licence, and support for template-specific problems belongs to the template creator rather than Webflow. The template can still be customised heavily, but the licence continues to apply to that implementation. [Webflow's template licence](https://webflow.com/templates/template-licenses) explains the boundary. Framer has a different risk. Its own template best-practices page says those recommendations are optional and that templates can be published without manual review. That does not make the marketplace unsafe. It means the buyer still has to inspect the template rather than treating marketplace presence as quality assurance. ##### When does the conversion-first service make more sense? Choose the service when the site is part of how the business sells and nobody inside the company should have to become its full-time operator. The strongest signals are operational: - You have traffic but cannot explain why enquiries are weak. - Sales conversations keep revealing objections the site does not answer. - New landing pages wait behind a freelancer's availability. - Form submissions disappear into inboxes with no qualification or follow-up path. - Analytics records activity but nobody turns it into a decision. - The last redesign launched, looked good and then stayed untouched. In that situation, another starting layout is unlikely to solve the constraint. The business needs an owner for the complete path: promise, page, action, handoff, measurement and next change. SharpHaw keeps that work visible in one weekly loop. You can inspect the model on the [plans page](/plans), see the standard of build in [Cases](/cases), and decide whether the operating relationship is worth more to you than owning the work yourself. ##### Does the platform matter at all? It matters, but later than most comparisons suggest. Framer is attractive when a visually strong marketing site needs to move quickly. Webflow gives teams a mature visual development and CMS environment. A coded stack makes sense when the site needs deeper product logic, integrations or control. Each choice has real implications for maintenance, content and portability. But a platform cannot rescue an undecided offer. It cannot make superficial copy specific. It cannot define a useful conversion event or decide what to do with an inconclusive test. Start with the operating question: who will make those decisions after launch? Then choose the platform that makes that person's work easier. ##### Questions to ask before you choose Ask these before buying either option: 1. What is the one business action this site should produce? 2. Who writes the copy and approves its claims? 3. Where does a form submission go, and who owns the next step? 4. Which events will show whether the page is working? 5. Who tests mobile layouts, error states, metadata and integrations? 6. What is the first change scheduled after launch? 7. Who owns the domain, content, data, analytics and implementation when the relationship ends? If you can answer all seven and have the time to execute them, a template may be the efficient choice. If the questions expose work with no owner, you are not short of a layout. You are short of an operating model. ##### Frequently asked questions ###### Is a Framer template enough for a business website? It can be. A clear offer, a small page set and an operator who can write, configure and maintain the site make a Framer template a practical choice. The template provides the structure. Your business still has to supply the positioning, proof, conversion path, analytics and ongoing decisions. ###### Is a Webflow template better than a custom website? Neither is automatically better. A Webflow template is efficient when its structure closely fits the job and someone can customise it properly. A custom approach earns its cost when the content model, integrations, user journeys or brand system would otherwise be forced into a structure designed for a different business. ###### Will a conversion-first service use Framer or Webflow? The service model and the implementation platform are separate decisions. A conversion-first process can work with an existing foundation, a visual builder or a coded stack. The correct choice depends on what the site needs to do, who maintains it and how much control the business needs. ###### What am I paying for beyond the website design? You are paying for the decisions and the ownership around the pages: positioning, copy, conversion paths, event tracking, form handoff, responsive QA, performance, search foundations and the next round of improvements. The design is visible. The operating work is what keeps it useful after launch. **Audit the decision before you buy:** [book a 30-minute site call](/contact) and leave with a direct answer on whether your current site needs a template-level fix, a rebuild or an ongoing conversion loop. --- ### AI chatbot disclosure: 5 checks beyond the label [Read on sharphaw.com](https://sharphaw.com/blog/ai-chatbot-disclosure-checks) · Product · published 2026-09-03T08:00:00Z > EU chatbot transparency rules now apply. Use five practical checks for visible AI disclosure, bounded answers, honest fallback, review and ownership. The EU AI Act’s chatbot transparency rule now applies. If an AI system talks directly to people, the person should know it is AI from the start of the first interaction. For a business owner, that makes the disclosure line the first check, not the whole audit. A visible “AI assistant” label can sit above a system that invents answers, hides uncertainty, sends people into a dead end and has nobody reviewing what goes wrong. **TL;DR:** Check five things in every website chatbot: the AI identity is visible from the first interaction; answers stay inside approved knowledge; uncertainty produces an honest fallback; conversations can be reviewed; and one named owner controls changes. SharpOS Support builds these operating choices around the label rather than treating it as compliance theatre. ##### What changed for website chatbots on 2 August 2026? Article 50 of the EU AI Act applies from 2 August 2026. The European Commission’s guidance says providers of AI systems that directly interact with people, including chatbots and AI agents, must design them so people are informed they are interacting with AI unless that fact is obvious. The notice should appear from the start of the first interaction, be clear and distinguishable, and follow accessibility requirements. The Commission also says the “obvious” exception should be interpreted restrictively because it removes transparency from the person using the system ([European Commission Article 50 FAQ](https://digital-strategy.ec.europa.eu/en/faqs/transparency-obligations-under-article-50-ai-act)). There is an important role distinction. The legal duty in Article 50(1) is framed around the **provider** of the AI system. A provider develops the system, has it developed, or puts it into service under its own name or trademark. A business using another company’s system under its authority may instead be a **deployer**. The facts of the implementation decide the role, so this article is an operational audit, not legal advice. That distinction does not make the customer experience someone else’s problem. The visitor is on your website, asking about your offer and deciding whether to trust your answer. Even when a vendor carries the provider duty, the business owner still needs to verify that the disclosure actually appears, the assistant behaves honestly and failures reach a useful next step. ##### Is an “AI assistant” label enough? No. It addresses identity, but not the quality of the interaction. Use these five checks together. ###### 1. Identity is visible before the first answer Open the widget as a new visitor. Do not rely on the assistant introducing itself after the person has already typed a question. The interface should identify the system as AI in a place that does not disappear when the welcome message changes. Test it on a small phone, at 200% zoom, with keyboard navigation and with a screen reader. A muted label below the fold is technically present and practically hidden. ###### 2. Answers stay inside approved knowledge Disclosure does not excuse invention. The useful test is not whether the chatbot sounds fluent. It is whether it recognises the edge of its evidence. A confident answer about an unavailable service is worse than a short admission that the information is missing. Knowledge also expires. Assign an owner to every source, record when it changed and remove obsolete claims. Otherwise the assistant can repeat an answer that was once approved and is now wrong. ###### 3. Uncertainty produces an honest fallback Many chatbot flows use “human handoff” as a reassuring phrase when no person is waiting. Test what happens when the assistant cannot answer. Does it invent a likely response? Promise that “someone will be with you shortly”? Create a ticket nobody owns? Or does it say that it lacks a confident answer and point to a real contact route? An honest fallback can be simple: - name the limit; - provide the correct email, phone or WhatsApp route; - say what the visitor should include; - avoid promising a response time the business has not operationally guaranteed. AI-only support is not inherently dishonest. Pretending an unattended queue is live human support is. ###### 4. Conversations can be reviewed If nobody reads the conversations, the business will not know which questions the website failed to answer. Review should cover more than sentiment or message count. Sample unanswered questions, low-confidence replies, repeated objections and suggestions from visitors. Separate a knowledge gap from a product gap: sometimes the assistant needs a better source; sometimes the offer itself is unclear. The useful output is a change queue. Update a support answer, rewrite a service page, clarify a price, fix a broken contact route or decide that a requested capability is outside the offer. ###### 5. One person owns the system Ask five operational questions: 1. Who can change the assistant’s instructions? 2. Who approves knowledge sources? 3. Who reviews failures and suggestions? 4. Who checks the contact fallback? 5. Who can disable the assistant during an incident? If every answer is “the vendor”, the business is exposed. If every answer is “the founder”, the process will eventually stall. Name an accountable owner and a backup, then make the review cadence proportionate to volume and risk. ##### How should the fallback work when the chatbot does not know? Start by rejecting a false binary. The choice is not “perfect AI” or “24-hour human team”. Most owner-operated businesses have neither. The better pattern is bounded automation with a truthful exit. For common, well-documented questions, the assistant can answer immediately in the visitor’s language. For anything outside the approved knowledge, it should stop, state the limitation and direct the person to a contact channel the business actually monitors. Test that exit like a form: confirm the address or number is current, the destination works on mobile, the visitor knows what happens next and the business can see how often the fallback appears. This is where support becomes part of the website’s conversion system. A chatbot that handles routine questions but loses every complex enquiry may reduce visible workload while quietly losing the most valuable conversations. ##### Who should review conversations and change the knowledge? Keep the loop small. For a lower-volume service business, a weekly review is often enough. Pull the questions that produced no useful answer, group them by theme and make one of four decisions: - add or update approved knowledge; - improve the relevant website page; - change the fallback route; - decline to answer because the question is outside scope or too sensitive. Measure useful signals: answer coverage, fallback frequency, recurring question themes, contact-route clicks and accepted suggestions. Do not inflate the report with total messages if message volume has no connection to resolved questions or qualified enquiries. ##### What does this look like in SharpOS Support? SharpOS Support is the AI support feature included with every SharpHaw subscription. It is designed as AI-only support, not a disguised live-chat desk. The widget carries a permanent disclosure line: **“AI assistant · May make mistakes.”** The AI label links to a transparency page, and the disclosure is part of the product shell rather than an organisation setting that can be switched off. Each assistant answers from an approved knowledge base, can respond in multiple languages and can be instructed to state its limits rather than fill gaps. When it cannot help confidently, the fallback can point to a real email, WhatsApp or phone route. It does not pretend a human has joined the chat. Inside SharpOS, the business can review conversations, capture visitor suggestions, see usage and update the knowledge that grounds future answers. This is an implementation pattern, not a claim that installing one feature proves compliance with every part of Article 50. The wider rules also cover areas such as marking certain generated content, deepfakes and public-interest text. The voluntary Commission Code supports parts of those obligations but does not replace the Act or official guidelines ([European Commission Code of Practice](https://digital-strategy.ec.europa.eu/en/policies/code-practice-ai-generated-content)). For a website owner, the immediate work is narrower and more practical: make the AI identity impossible to miss, constrain what it can claim, give uncertainty an honest exit, review what people ask and put one person in charge. That is the difference between a label and an operating system. [See how SharpOS Support works inside the shared workspace](/sharp-os). ##### FAQ ###### Does every website chatbot need an AI label? Article 50(1) covers AI systems designed for genuine, direct two-way interaction with people, unless it is obvious that the person is interacting with AI. The legal obligation is framed around the provider, and the exact provider/deployer role depends on how the system is built and offered. Get legal advice for your implementation. ###### When did the EU AI chatbot transparency rule start? Article 50 applies from 2 August 2026. The Commission says people should be informed from the start of the first interaction in a clear, distinguishable and accessible way. ###### Is a disclaimer enough for AI chatbot compliance? No single interface line proves compliance. A visible disclosure is one requirement. Businesses should also verify role allocation, accessibility, knowledge governance, fallback behaviour, review access, data handling and any other AI Act or privacy duties that apply. ###### Does SharpOS Support hand conversations to a human agent? No. SharpOS Support is AI-only. When it cannot answer confidently, it can point the visitor to a real contact route such as email, WhatsApp or phone. The interface should not promise a live human handoff that does not exist. ###### What should an owner review in chatbot conversations? Review unanswered questions, low-confidence replies, repeated objections, suggestions and fallback use. Turn each pattern into a knowledge update, website change, contact-route fix or explicit decision not to answer. --- ### Claude Fable 5.1 for founders: five jobs to hand it, three to keep [Read on sharphaw.com](https://sharphaw.com/blog/claude-fable-5-1-for-founders-five-jobs-to-hand-three-to-keep) · Automations · published 2026-09-02T07:00:00Z > Claude Fable 5.1 shipped on 1 September. The five founder jobs to hand it this week, the three to keep, and the rule that sorts them: what a wrong answer costs. Anthropic shipped Claude Fable 5.1 on 1 September, and by lunchtime my feed was benchmarks. Terminal-Bench scores, cache prices, a new map of Venus. None of it answers the question a founder actually has, which one owner put to Reddit in April: "I use Claude daily to run my small business. What am I missing?" The honest answer sits on a page most people skip, Anthropic's own release notes, which list what the model got better at and, further down, how it now behaves differently without you changing a thing. Read both lists together and the founder's job list writes itself: five things to hand Claude Fable 5.1 this week, three things to keep, and the one rule that sorts them. **TL;DR:** Claude Fable 5.1 is worth handing the jobs that end in a draft or a read: the month-end pulse, contract review, sourced research, enquiry follow-ups and internal tools. Keep anything that sends, posts or pays on its own, research run at low effort, and customer data until retention terms are written down. Sort by what a wrong answer costs. ##### What is Claude Fable 5.1 actually better at? Claude Fable 5.1 is better than its predecessor at work that does not finish in one prompt: long coding sessions that run unattended, research that takes several steps, and document, spreadsheet and slide work, according to Anthropic's release notes. The headline price is unchanged, cache reads cost a quarter of what they did, and Anthropic claims that at Low or Medium effort the new model matches Fable 5 at full effort for a good deal less. The partner quotes in the launch post say the same thing from different angles. MongoDB let it run for hours overnight on a prototype. Millennium says it found the cause of a crash their engineers had chased for years. Canva says the writing follows their house guidance better than before. That is the capability list. Founders read it and reach for the hardest problem in the business, because that is what the list invites. It is the wrong sort key. The question that decides what to hand a model is not "can it do this" but "what does a wrong answer cost, and who catches it first". A wrong month-end read costs you a second look. A wrong invoice reminder sent to the wrong client costs you the client. Same model, same capability — different job. ##### Which jobs should a founder hand Claude Fable 5.1 this week? Hand it the work that ends in a draft or a read. Every job below is something you already do badly at 11pm, and every one still lands on your desk before it leaves the building. 1. **The month-end read.** Export last month from the bank and from the invoicing tool, drop both files in, and ask for the position: what came in, what is overdue, what the next thirty days look like, and reminder emails drafted for the three oldest invoices. Anthropic's own small-business package runs this workflow against QuickBooks and PayPal; a European stack does it with two CSV exports and gets the same read. The check: you approve every reminder before it goes. 2. **Contract review before you sign.** The supplier agreement, the platform terms, the agency proposal with the twelve-month minimum. Ask for the clauses that bind you past the first month, the ones that let them raise the price, and the ones that decide who owns the work. One launch partner that measures contract redlining reports its first-turn score doubled against Fable 5. The check: the signature stays yours, and so does the lawyer for anything above your comfort line. 3. **The sourced market read.** Who else sells what you sell in your three markets, what they charge, what changed this year. Run it at High effort with search on and ask for the source next to every claim. One finance partner says the model went straight to the earnings call transcript where other models leaned on secondary coverage, which is the behaviour you want. The check: open three sources at random. If one does not say what the memo says, the whole memo goes back. 4. **Enquiry follow-ups, drafted into a queue.** The reply to Tuesday's enquiry, the quote follow-up, the "we haven't heard back" note. Give it your last twenty sent emails as the voice sample and let it draft into a folder, never into the outbox. That Reddit owner, who runs a one-person lighting installation business, lists sales follow-ups among the things they hand Claude every day. The drafts are the win — the autopilot is not on offer. 5. **The internal tool nobody would pay a developer for.** The quote calculator living in a spreadsheet with macros, the booking-slot checker, the script that renames the site photos. The same lighting installer had Claude build them a web app that visualises fixture placement on a building: one user, cheap to break, nothing a customer touches. Claude Fable 5.1 will run for hours on this kind of job and fix the underlying cause rather than the symptom, which is the documented improvement over Fable 5. The check: the code sits in a repository you own, with a second person who can read it. The moment a customer touches the tool, it moves to the other list. ##### What should you keep away from Fable 5.1? The obvious keep-list is "anything important". That is wrong, and it is why founders end up using the best model on the planet to reword LinkedIn posts. The month-end read is important. "Keep a human in the loop" is the advice every guide gives and nobody can act on. The actionable version is structural: does the job end in a draft, or in a send? The real keep-list is three jobs where the model's own behaviour, as Anthropic documents it, makes the wrong answer expensive. **Anything that sends, posts or pays without you.** Anthropic built its own small-business package so that "you approve before anything sends, posts, or pays", and that is the vendor talking. The agent that emails two hundred prospects on its own is fast on the tedious part and exposes you on the one email that quotes a claim you never made. Drafts into a queue, always. Sends from a human, always. The line does not move because the model got smarter. **Research you would act on that ran at low effort.** This one is in the release notes and almost nobody will read it: at low effort, Fable 5.1 answers from memory more often and calls search less. The default in Claude Cowork and on claude.ai is Medium, so the quick question you ask between meetings gets a confident answer that may be a year old. For anything with a date, a price, a regulation or a competitor's name in it, raise the effort or tell it to search and show its sources. There is a second note in the same list: when summarising documents, the model is more likely to reproduce passages without marking them as quotations. If you publish a summary it wrote, check it for lifted sentences first. **Customer data, until the retention terms are written down.** Anthropic's zero-retention arrangement, Enterprise Frontier Safeguards, arrives in phases from this autumn and is aimed at enterprise customers. Until then, eligible customers can ask for zero data retention and the rest of us are on whatever our plan's standard terms say. The safeguard checks also read everything the model reads, including uploaded files and connected tools, and a flagged request gets re-run on a different model. That is no argument for staying out. Write down which data goes in, under which account, kept for how long, before the first customer record does. If you are in Europe, that page is the audit trail a data-protection query will ask for, and it is the first thing we write on any [AI Automations](https://sharphaw.com/services/ai-automations) engagement. ##### How do you run Fable 5.1 without burning your plan? The 249-upvote complaint in June was that Fable 5 ate a Max plan at two percent a minute. The plan mechanics have not changed with 5.1. On Max plans and premium seats it is included up to half your weekly limit and draws that limit down faster than other models. On Pro it runs on usage credits from the first message. What changed is the dial. Anthropic says Fable 5.1 at Low or Medium effort produces results comparable to Fable 5 at full effort, Claude Code defaults to High, and Cowork and claude.ai default to Medium. So the operating rules for a founder are short. Leave the default for drafts and reads. Raise the effort for the sourced research and the contract review, where you want it to search and to think. Keep one long conversation per job with the documents inside it rather than starting fresh each time, because re-reading context it has already seen is now the cheap part of the bill. And look at the usage page on Friday, not when the plan locks on Wednesday. Treat the plan like an ad budget: the platform will happily spend it for you. ##### How does SharpHaw use Fable 5.1? This post was drafted by Claude Fable 5.1 on the day it shipped, inside the same pipeline that writes every SharpHaw post. I read it in [SharpOS](https://sharphaw.com/sharp-os) before it left the review column, and the card records which model wrote it, as every card on this blog does. Anthropic's watermark now travels with every sentence Fable 5.1 writes, so the disclosure would be forced anyway. Here it is simply the operating model, and it was before the watermark existed. The model is the cheap part. The read is the job. The same split runs through the client work. When we [map a founder's five biggest time sinks and automate them](https://sharphaw.com/services/ai-automations), the automations that survive are the ones that end in a queue a human clears: the enquiry triaged and drafted, the report assembled, the document filed. Almost none of the time they save comes from removing the human. They came from removing the blank page and the copy-paste. Fable 5.1 makes the drafts better and the long jobs cheaper. It does not change who signs. ##### Frequently asked questions Is Claude Fable 5.1 worth it for a small business? Yes, for the jobs that end in a draft or a read: the month-end pulse, contract review, sourced research, follow-up drafts and internal tools. It is not worth it as a chatbot for quick questions, where Opus 5 answers as well for less. Sort your jobs by what a wrong answer costs before you sort them by capability. Should a founder use Claude Fable 5.1 or Opus 5? Use Opus 5 as the default and Fable 5.1 for long unattended work, dense documents and research where you want it to keep digging. Anthropic's own guidance says to start with Opus 5 and move to Fable 5.1 when your results on Opus at higher effort still fall short of what the job needs. Does Claude Fable 5.1 count against my Claude plan? On Max plans and premium Team seats, Fable 5.1 is included up to half of your weekly usage limit and draws it down faster than other models. On Pro plans and standard seats it runs on pay-as-you-go usage credits from the first message. Check the usage page weekly rather than when the plan locks. Is text written by Claude Fable 5.1 detectable? Yes. Every piece of text Fable 5.1 produces carries Anthropic's statistical watermark, invisible to readers and readable by a detection tool Anthropic is opening to regulators, media and fact-checkers under the EU AI Act's transparency code. It does not change the text. It does make publishing unread AI output a bad idea. ##### Hand it the drafts, keep the sends Anthropic's list tells you what Claude Fable 5.1 can do. Your list should be sorted by what a wrong answer costs and who catches it. Hand it the drafts and the reads this week, with the effort dial at the default. Keep the sends, the spends, the low-effort facts and the customer records until the rule for each is written down. Then read what it gives you before it leaves the building, every time. [Book a 30-minute fit check](https://sharphaw.com/contact): bring the one job you would hand Fable 5.1 first, and leave knowing which list it belongs on and what the review step will cost you each week. If you would rather read the numbers first, [see the plans](https://sharphaw.com/plans). --- ### AI website builder checklist: 7 tests after launch [Read on sharphaw.com](https://sharphaw.com/blog/ai-website-builder-checklist-after-launch) · Website · published 2026-09-01T08:00:00Z > Use this seven-part AI website builder checklist to test editability, lead delivery, measurement, recovery, portability and handover after launch. AI website builders are finally good enough to produce a convincing launch. That is the wrong test. A polished homepage can be assembled in hours. Six months later, the business may still be unable to change a price safely, explain where an enquiry went, restore a failed deployment or give another operator everything they need. **TL;DR:** Judge an AI-built website by what happens after the demo. Test whether the business can edit it, receive and trace enquiries, own search and analytics access, recover a failed release, export the whole operating system and hand it to another competent operator. Launch speed matters. Dependence matters more. ##### The real question is not “Can AI build this?” It can. AI can now generate a credible marketing site, connect common services and iterate on a design quickly. For a founder who needs to validate an offer, that is useful progress. But a business website is not only the pages a visitor sees. It is also a set of operational promises: - the owner can change an offer without calling the original builder; - enquiries reach the right place and failures are visible; - search, analytics and consent settings remain under business control; - a bad release can be reversed; - code, content, data, domains and credentials can move; - another competent operator can take over. That is why “the AI built it” tells me almost nothing about production readiness. The useful distinction is between a fast artefact and an operable business system. This AI website builder checklist tests the second one. ##### Test 1: change one price without the builder Pick a real, low-risk change: a service price, an opening hour, a team member or the wording of the primary offer. Ask someone inside the business who did not build the site to make the change. Give them the access and documentation that would exist on an ordinary Tuesday. Do not let the original builder guide them over a call. The test passes when they can: 1. find the source of truth; 2. preview the change; 3. publish it without breaking another page; 4. see who changed what; 5. reverse it if necessary. If the content is trapped inside generated code, an unfamiliar visual editor or a prompt history only one person understands, the site is not easy to operate. It is easy to demo. The right editing model depends on the business. A small brochure site may only need a clear repository and deployment path. A site with frequent offers, locations or articles probably needs structured content. The standard is not “use a CMS”. The standard is “the intended operator can make the intended change safely”. ##### Test 2: trace one enquiry from click to owner Submit the contact form using a recognisable test address. Then follow the enquiry. Where was it validated? Where was it stored? Who was notified? What happens if the email provider rejects the message? Does a duplicate submission create noise? Does the success page load only after the system accepts the lead? On SharpHaw’s own site, the form path is explicit: server-side validation, a honeypot, defined handling for rejected, duplicate and rate-limited submissions, and a separate success route after acceptance. That plumbing is less exciting than a generated hero section. It is also closer to the sale. A useful [conversion-first website](/services/conversion-first-websites) treats the enquiry path as part of the product. If nobody can explain that path, the site has not passed launch. ##### Test 3: prove the business owns search access The business should control the domain, DNS and search property. It should also know how pages are discovered. Google recommends a Domain property in Search Console where possible. Its documentation also points site owners to URL Inspection for individual pages and the Sitemaps report for submitted sitemaps ([Google Search Console](https://support.google.com/webmasters/answer/10351509?hl=en)). Run a simple check: - Can the owner add and remove Search Console users? - Does the property cover every protocol and subdomain that matters? - Is there a sitemap, and can someone explain which routes belong in it? - Can the team inspect a new or changed URL without asking the vendor? - Are canonical URLs intentional? “It is indexed” is a moment in time. Search ownership is the ability to diagnose what happens next. ##### Test 4: reconcile the analytics event with reality Open the analytics tool, submit the form and confirm the event that represents the outcome you care about. Do not stop when a button click appears. A click can happen before validation fails. A form can report success while the lead never reaches its owner. A booking widget can load while no appointment is completed. For the SharpHaw site, the primary website conversion is tied to the success route rather than the initial form interaction, and analytics loading is consent-aware. That is a design choice: measure the accepted outcome, not the optimistic gesture. The test passes when the team can connect one real test action to one recorded conversion and one received business outcome. If those three records disagree, the dashboard is not evidence yet. This is also where performance belongs. Core Web Vitals are useful experience signals, with Google’s current good thresholds at 2.5 seconds for LCP, 200 milliseconds for INP and 0.1 for CLS at the 75th percentile ([web.dev](https://web.dev/articles/vitals)). They do not replace the enquiry test. A fast form that loses the lead is still broken. ##### Test 5: recover one bad release “We have backups” is not a recovery plan. Restore something. Create a safe failure in a non-production environment or use a known previous release. Then ask the operator to return the site to a working state. You are testing four separate things: - the source is versioned; - a known-good release can be identified; - deployment access belongs to the business; - recovery steps are documented and rehearsed. The exact mechanism can be simple. A small site may only need a previous deployment and a database export. A content-heavy or transactional site needs more. What matters is that recovery does not depend on one person remembering a private sequence of clicks. ##### Test 6: export the system, not only the pages Ask for an export and list what did not come with it. Code export is useful, but it can create a false sense of portability. Webflow, for example, documents that an exported site can include HTML, CSS, JavaScript and assets while excluding CMS content and functionality, user accounts, ecommerce, localisation, form processing and site search ([Webflow export documentation](https://help.webflow.com/hc/en-us/articles/33961386739347-How-do-I-export-my-Webflow-site-code)). That is one platform’s documented boundary, not a criticism of every builder. It illustrates the question to ask everywhere: what part of the business system remains behind? Inventory at least: - source code and build instructions; - content and uploaded assets; - form submissions and customer data; - environment variables and external service accounts; - domain and DNS control; - analytics, search and advertising properties; - deployment history and backups; - licences and paid integrations. If the answer is “we can export the code”, keep going. A static bundle is not the same thing as a runnable business system. ##### Test 7: hand it to another competent operator This is the strongest test because it combines the other six. Give a competent developer or operator who was not involved in the build: - the repository; - the access map; - the content source; - the environment-variable inventory without exposing secrets in documentation; - the deployment and recovery notes; - the ownership list for every external service. Ask them to run the site, make one content change, identify how a lead moves through the system and describe how they would roll back a bad release. The test should not require them to prefer the original stack. It should only prove that the system is legible enough to take over. This is the practical version of ownership. A contract can promise transfer. A handover rehearsal proves it. ##### Run the cancellation-day test There is a shorter way to expose hidden dependency: > If the builder, platform or subscription disappeared today, which parts of the website would still work tomorrow? The honest answer may include trade-offs. A managed platform can be worth depending on because it removes maintenance. A specialist integration can be better than rebuilding a commodity service. Portability is not the absence of dependencies. It is knowing which ones you chose, what they control and how you leave. At SharpHaw, [code and content ownership](/values) is explicit, while [SharpOS](/sharp-os) gives the work a shared operational home. The important part is not pretending dependencies do not exist. It is making them visible and movable. ##### A slower launch can still be the faster decision These checks add work. A throwaway validation page does not need the same handover package as a revenue-critical site. Building every recovery path on day one can be wasteful. Scope the standard to the risk: - **Experiment:** publish quickly, use reversible tools, avoid collecting data you cannot govern. - **Operating website:** own access, trace enquiries, measure accepted outcomes and document recovery. - **Revenue-critical system:** rehearse restoration, export data and complete an independent handover. AI has reduced the cost of producing the visible layer. That makes operational quality more important, not less, because more sites can now look finished before the business underneath is ready. Use the seven tests before choosing a builder, before approving launch and again six months later. If the site passes, it is not merely AI-built. It is business-owned. If you want a website designed around measurable enquiries, weekly improvement and a clean exit path, [show us what you are working with](/contact). ##### FAQ ###### Are AI website builders good enough for a business website? They can be, especially for simple marketing sites and fast offer validation. Production readiness depends on editability, lead delivery, measurement, recovery, portability and handover, not only the quality of the generated pages. ###### What should I own when using an AI website builder? At minimum, the business should control its domain and DNS, source or exportable site files, content and assets, customer data, analytics and search properties, deployment access, external service accounts and recovery materials. ###### Is exporting website code enough? Usually not. Confirm whether the export includes structured content, form handling, user data, ecommerce, localisation, search, environment configuration and deployment instructions. A code bundle may reproduce pages without reproducing the operating system behind them. ###### How often should I run this website checklist? Run it before platform selection, before launch, after any major integration change and at least every six months. Repeat it whenever the original builder or internal owner changes. ###### Does portability mean avoiding managed platforms? No. Managed platforms can be a sensible trade-off. Portability means the business knows what the platform controls, owns the surrounding accounts and data, and has a realistic handover or exit path. --- ### Should you replace WordPress? Ask who maintains it first [Read on sharphaw.com](https://sharphaw.com/blog/when-to-replace-wordpress) · Website · published 2026-08-31T08:00:00Z > Thinking of replacing WordPress? The platform is rarely the problem — an unmaintained plugin stack is. When migration is worth it, and when it isn't. The third plugin update this quarter broke your checkout. The one before that took the contact form offline for a weekend before anyone noticed. You're in wp-admin at 11pm, counting nine red update badges across twenty-four plugins, and you've decided you want to replace WordPress. Fair. But before you price a migration, sit with one uncomfortable question. The platform didn't install those twenty-four plugins, and it didn't skip the updates. Something else did — or rather, nobody did. Most founders who want off WordPress are running from a maintenance problem, and a maintenance problem follows you to the next stack. This is about telling the two apart: when the platform is genuinely the ceiling, and when you're about to spend five figures to feel decisive. **TL;DR:** Replacing WordPress rarely fixes a slow, broken, or leaking site, because the real problem is usually that nobody has been maintaining it — and neglect follows you to any platform. Leave WordPress when it's a proven ceiling and someone competent already runs it weekly. Otherwise, fix ownership first. ##### What people actually mean when they say they want off WordPress Almost no one is angry at WordPress the software. They're angry at what their site became on it: slow, fragile, and stacked with plugins whose names they no longer recognise. One owner-operator described their build in a review as "an expensive nightmare... there were numerous glitches & errors." The platform is taking the blame for an outcome it did not cause on its own. Here is the distinction that matters. WordPress is a content management system used by roughly 40% of the web. That makes it neither a fringe risk nor a badge of quality. It is just common. What most founders actually bought was a specific WordPress site: assembled by a freelancer or agency, held together by a dozen third-party plugins, then left alone. The day it shipped, it started ageing, and no one was assigned to keep it current. "Off WordPress" is shorthand for "off this specific neglected thing." Naming it correctly changes what you do next. ##### It's almost never the core. It's the stack nobody patched. Look at where the risk actually lives. In the first half of 2025, Patchstack's security researchers recorded roughly 6,700 new vulnerabilities across the WordPress ecosystem. About 89% were in plugins. Exactly one was in WordPress core. The 2024 figures told the same story: thousands of plugin flaws, seven in core. The engine you're blaming is one of the most-scrutinised, best-patched pieces of software on the web. The danger is in the parts you bolted on and stopped updating. That reframes the whole complaint. A site running twenty-four plugins is running twenty-four separate codebases, each maintained by a different third party on its own schedule, and roughly three in five of 2025's flaws could be exploited by a stranger with no login at all. Every plugin you don't update is a door left open. This is an ownership failing before it is a WordPress failing: someone has to watch that surface every week, and on most small-business sites, no one is paid to. Move to a new platform and you inherit a smaller version of the same duty. The framework changes. The job doesn't. ##### Why moving platforms won't fix a site nobody owns "But the new stack is faster and more secure." True, on day one. A modern build on a framework like Next.js or Astro will out-score a plugin-heavy WordPress site on almost every performance metric the morning it launches. The question is what it looks like on day 400. A website is a surface that decays the moment attention stops, and migrating without changing who tends it buys you a faster car for the same driver who never books a service. We see this pattern often. A business replatforms to escape maintenance, the new site launches beautifully, and eighteen months later it is stale for the exact reason the last one was. Content nobody refreshed. Forms nobody tested. Dependencies nobody upgraded. The migration felt like progress because it produced a visible artefact — a new site — while quietly recreating the invisible problem underneath. That is the cost nobody prices in: a replatform buys you a fresh start and a fresh maintenance bill, and if you only pay the first, you land back where you began, poorer. The businesses that stay fast are the ones where someone senior owns the site every week and [the work is visible](https://sharphaw.com/sharp-os), not the ones with the newest framework. ##### When replacing WordPress is the right call Sometimes the platform really is the constraint, and staying is the expensive choice. Three situations make replacing WordPress the right call — and each assumes someone has actually been maintaining the current site, so you know the limit is real and not neglect wearing a WordPress costume. First, a proven ceiling. You've pruned the plugins, moved to good hosting, and the site still cannot hit the load times or the editorial workflow your business needs. That is a wall you've tested, not one you've assumed. Second, you've outgrown the model. You need a web app, a customer portal, internal tooling, or custom functionality that WordPress can only fake with more plugins, which is the same bolt-on sprawl that caused the trouble. Building it properly on a codebase you own is the sane move. Third, the migration comes with a new operating model, not just a new framework. If replatforming is how you finally put a senior person in charge of the site every week, the platform change is almost incidental; the ownership change is the actual upgrade. Notice what unites the three. None of them is "I'm frustrated." Each is a specific, tested limit with a plan for who runs the result. ##### A five-minute test before you replatform Before you approve a migration budget, run four checks. They take an afternoon, and they tell you whether you're fixing the platform or running from the upkeep. - **Has anyone actually maintained this site in the last year?** Open the plugin list and the update log. If the honest answer is "not really," you haven't tested WordPress — you've tested neglect. Put someone in charge for three months, then re-judge. - **Is the ceiling proven or assumed?** Name the one thing WordPress cannot do that your business needs. If you can't say it in a sentence, it's frustration, not a limit. - **Who owns the new site on launch day plus one year?** If the answer is "no one yet," stop. You are about to rebuild the same problem in a new language. - **Can you leave cleanly?** Confirm you own the domain, the code, the content, and the analytics, and that you can take all of it with you. If a vendor controls any of it, ownership is your first fix — on any platform. ##### Frequently asked questions **Will moving off WordPress hurt my SEO?** It can, if you mishandle the cutover. Rankings drop when URLs change without redirects, content gets thinner, or load times regress during the move. A migration that maps every old URL to its new one, preserves the content, and keeps metadata intact usually holds rankings, and can improve them when speed gets better. **What should a small business replace WordPress with?** There is no single answer, and anyone who gives you one is selling a platform. Simple marketing sites do well on modern frameworks or hosted builders; sites that need custom features are better as a codebase you own. Choose on what the site must do and who will maintain it, not on which tool is fashionable this year. **Is WordPress secure enough for a business site in 2026?** The core is; the plugins are the risk. Patchstack attributed about 89% of 2025's WordPress vulnerabilities to plugins and one to the core. A WordPress site kept lean and patched weekly is safe for most businesses. A WordPress site carrying two dozen abandoned plugins is not, whatever the year. ##### The decision underneath the platform WordPress didn't break your site. A year of nobody owning it did. The platform is plumbing — worth replacing when it's a proven ceiling, and a distraction when it isn't. Before you price a migration, decide who is going to run this site every week, because that decision outlives any framework you choose. If you want a straight answer on which problem you're facing, we'll look at your site and your plugin stack and tell you plainly: platform, or ownership. That's the read. Where we can help beyond it, it's a conversion-first website someone senior improves every week, under a [month-to-month subscription](https://sharphaw.com/plans) you can leave with your domain, content and data, on terms written down before you sign. [Start with the review](https://sharphaw.com/contact). --- ### Founder-market fit can expire. Run the overlooked job audit [Read on sharphaw.com](https://sharphaw.com/blog/founder-market-fit-job-audit) · Founder · published 2026-08-30T08:00:00Z > Founder-market fit can expire as your role changes. Audit insight, access, energy and ownership, then decide what to keep, learn, partner on or hand off. Founder-market fit can expire when the company starts asking you to win through work that no longer matches your edge. You may still understand the buyer better than anyone. Yet Tuesday is now pricing approvals, a Meta ads review, two hiring interviews, a homepage rewrite and five calls you no longer want to be on. The company grows, but the founder's calendar gets even more packed. That pattern is easy to misread as poor discipline or fading conviction. Sometimes the market still fits. The job does not. This founder-market fit audit separates the advantage that only you hold from work you can learn, share or remove from your queue. Run it before you hire another specialist, buy another tool or decide you are the problem. **TL;DR:** Founder-market fit changes as a company grows because the founder's job changes with it. Audit your current week for unique market insight, decision risk, repeatability and blocked work. Keep the judgement only you can supply. Learn, partner on or hand off the rest before your early edge becomes the bottleneck. ##### What founder-market fit actually measures Your CV is only one input. [Startups.com defines founder-market fit](https://www.startups.com/lexicon/founder-market-fit) through background, network, expertise and genuine interest in the market. That is a useful start, but the operating version needs four separate assets: - **Insight:** you see a buyer constraint, tradeoff or failure pattern that an outsider would miss. - **Access:** the right buyers take your call, answer the awkward question and tell you what happens after the demo. - **Credibility:** buyers believe you understand the risk because you can name it precisely and show your work. - **Appetite:** you can sustain the daily motion the business needs, after the launch story stops feeling new. Those assets move at different speeds. Customer interviews can deepen insight. A useful body of work can earn credibility. Partnerships can widen access. Appetite can fall when the business changes from product work into constant selling, recruiting or support. That is why the usual “why you?” story is incomplete. It records the founder's advantage at one moment. It says little about the job the company will create next. Industry tenure can also cut both ways. It gives you vocabulary and pattern recognition, then tempts you to treat old constraints as permanent. One founder in a recent discussion put the risk plainly: experience can fog judgement when it turns into an outdated bias. The corrective is evidence from current buyers, not a more polished origin story. ##### Why founder-market fit changes as the business grows “The skills, motivations, and behaviors that make a good entrepreneur are not the same as those required to lead a high growth organization.” That line comes from James Picken's [founder-to-CEO research](https://www.sciencedirect.com/science/article/pii/S0007681316300921), and it names the part most founder-market-fit checklists skip. At the start, the founder's job may be to notice a problem, build the first version and persuade ten buyers to try it. Later, the job can become hiring, allocating cash, setting priorities, reviewing distribution, resolving ownership gaps and keeping a team pointed at the same outcome. The title barely changes. The work does. Picture a Thursday afternoon. A customer says one sentence on a sales call that should change the offer. The founder hears it, opens the homepage draft, rewrites the hero, messages the ads contractor and adds three tasks to the content queue. By Friday, four people are executing four interpretations of the same insight. The founder supplied the market judgement and accidentally became the routing system. Three kinds of fit now sit on the table: - Product-market fit asks whether the offer solves a problem people will pay to solve. - Founder-market fit asks whether the founder holds a useful advantage in that market. - Founder-job fit asks whether the current role uses that advantage without routing the whole company through one person's attention. The company can keep fitting the market while the founder stops fitting the job. That is a role-design problem before it is a verdict on the founder or the business. ##### Four ways a founder's edge turns into drag The same behaviour can help at one stage and hurt at the next. Look for the switch, not the trait. ###### Insight hardens into assumption Early buyer knowledge lets a founder move before the spreadsheet catches up. Trouble starts when the founder's memory outranks current evidence. Open the last ten sales-call notes. If the page copy still repeats language buyers stopped using six months ago, domain experience has become a stale source. Keep the judgement, but reconnect it to live calls, lost-deal reasons and the phrases sitting in the CRM. ###### Access becomes dependence Personal trust can open the first doors. It becomes fragile when every serious enquiry needs the founder's inbox, personal LinkedIn account or presence on the call. The test is simple: take one week away. Can a qualified buyer understand the offer, inspect credible proof and get a useful reply without waiting for you? If the answer is no, the business has access through the founder rather than access it can keep. ###### Speed becomes interruption Founders often move quickly because they carry the full context. A growing team experiences the same habit as a stream of exceptions. Look at the approval queue. Seven cards marked “Founder review” do not prove high standards. They prove nobody knows which decisions are reversible, which need a second check and which belong to the founder alone. The result feels busy because work starts everywhere and ships nowhere. ###### Craft becomes a bottleneck The founder who wrote the first landing page may still be the best person to call out a weak promise. Rewriting every paragraph is a different job. Open the version history on the last page, ad or email. Did the founder change the commercial decision, or polish the implementation? A changed audience, offer or proof claim deserves founder attention. A tenth round of sentence edits needs a clearer brief and an owner. ##### Run the weekly-work audit before you hire around the problem Use four weeks of real artefacts: your calendar, CRM, approval queue and shipped-work trail. Memory will flatter the interesting work and hide the repeated work. For each responsibility, write down five answers: | Audit question | Evidence to inspect | | --- | --- | | Did this work reveal buyer truth only I could reach? | Call notes, lost-deal reasons, support threads | | Would a wrong decision be expensive or hard to reverse? | Spend, legal exposure, offer changes, public claims | | Do I need to learn this once so I can judge it well? | First review, measurement plan, decision criteria | | Has the same task appeared twice in four weeks? | Calendar blocks, repeated comments, recurring cards | | How long did work wait for my input? | Card history, hand-off timestamps, missed publishing dates | Do not score the answers out of ten. A neat number hides the decision. Mark the work instead: - **Keep** work that uses scarce buyer judgement and carries serious decision risk. - **Learn** work you need to understand well enough to set the standard and read the evidence. - **Partner** where judgement matters, depth is missing and the work must keep moving every week. - **Hand off** repeatable execution with stable rules, visible quality checks and a clear owner. Then inspect the pattern. A calendar full of “keep” tasks may mean the company still relies on founder judgement. A queue full of repeatable approvals means the system is underdesigned. Those are different problems and they need different fixes. ##### Choose complementarity without giving away the company A 2023 [Scientific Reports study of 21,187 startups](https://www.nature.com/articles/s41598-023-41980-y) found companies with three or more founders were more than twice as likely as solo-founded companies to meet its success definition. The researchers defined success narrowly as acquisition, acquiring another company or an IPO, and the dataset over-represents funded technology companies and founders active on Twitter. Treat the number as evidence for complementarity, not a command to find two co-founders. The researchers put it plainly: “founding a startup is a team sport; therefore, diversity and complementarity of personalities matter”. No founder needs to become excellent at every job the company creates. Match the help to the work. Paid acquisition that changes every week needs a named operator, tracking and stop rules. A compliance question that appears twice a year may need one expert review. The buyer insight that shapes the offer should stay close to the founder, even when somebody else turns it into pages, ads and follow-up. [SharpHaw is built around one version of that choice](https://sharphaw.com/about). Gabriel keeps senior engineering and commercial judgement at the table. Website, ads, content and AI automations move through one prioritised weekly queue instead of four disconnected vendor relationships. [SharpOS keeps the work, assets, reporting and context visible](https://sharphaw.com/sharp-os), so the founder does not need a status call to discover what shipped. That model still asks the founder to make hard decisions. It removes the need to route every implementation detail through the founder's calendar. Somebody else will write a line, place a bid or build a workflow differently from you. Accept that variation, then keep control over the buyer, offer, proof and stop rules that should remain yours. ##### Renew the fit before the wrong job becomes the company Set the trigger now: run the audit again whenever the company changes stage, adds a channel or creates a recurring responsibility. Do it sooner when the calendar fills, decisions slow or work keeps returning after you thought you handed it off. Keep the market judgement that only you can supply. Build enough fluency to judge important work. Add complementary depth where the gap repeats. Hand off execution once the rules and evidence are visible. If your audit shows that website, ads, content and automations keep returning to your queue, [request a 30-minute fit call](https://sharphaw.com/contact). Bring the last four weeks of your calendar and the work that stalled. Leave with a keep, learn, partner or hand-off decision for each one. --- ### Founder dependency hides in your marketing approval queue [Read on sharphaw.com](https://sharphaw.com/blog/founder-dependency-marketing-approval-queue) · Founder · published 2026-08-29T08:00:00Z > Founder dependency survives hires and SOPs when marketing still waits for you. Run the two-week test and build three decision lanes that keep work moving. About 75% of owners in a 2026 survey kept reading and answering email while they were away. Around a third kept taking calls. The founder left. The approval queue followed. Founder dependency often looks this ordinary. A Google Ads change waits in one tab. A homepage claim waits in another. A serious enquiry sits in the CRM because everyone wants the founder to choose the reply. The dashboards stay active while the decisions stop. Hiring more people will not clear that queue by itself. Neither will a library of process documents. Marketing can run without your constant approval when the team knows which moves are reversible, which need a second check, and which genuinely require you. There is one reliable way to find out: disappear for two working weeks and inspect what waits. **TL;DR:** Founder dependency in marketing exists when safe work cannot continue without founder approval. Hiring and SOPs do not remove it. Split work into green, amber, and red decision lanes, then run a two-week no-contact test. Keep irreversible calls with the founder. Let reversible work move without them. ##### What founder dependency looks like in marketing [Eurostat's 2025 EU Labour Force Survey](https://ec.europa.eu/eurostat/statistics-explained/SEPDF/cache/85131.pdf) found that 32.2% of self-employed people worked at least 45 hours in the reference week. The employee figure was 6.4%. Long hours do not prove founder dependency, but they show how much extra load European owners already carry before a marketing approval queue lands on top. The queue rarely announces itself. It appears as reasonable messages: > Can you approve this headline? > Should we pause the ad set? > Is this result safe to publish? > Which lead should we call first? One question is harmless. Fifty questions turn the founder's attention into infrastructure. Picture a founder on the third day of a family trip. The out-of-office reply is on, but three tabs are still open on a phone: the ad account wants a budget decision, the website board has a proof line marked "needs review", and the CRM holds an enquiry from a buyer who asked a hard question about ownership. Nobody is idle. Work has been done. Movement still depends on one pair of thumbs. That is the useful definition. Founder dependency in marketing exists when a safe next action cannot happen without the founder being reachable. The founder may still set direction, appear in content, join important sales calls, or make the hard commercial decisions. Visibility is fine. Required availability is the risk. A marketing system that needs your thumbs-up is still running on your attention. ##### Why another hire and a folder of SOPs do not fix it "The docs get written, nobody reads them, and the founder still gets the call." That line from a recent [small-business discussion](https://www.reddit.com/r/smallbusiness/comments/1t8stn0/when_does_a_business_actually_stop_depending_on/) catches the failure better than most operating manuals. An SOP can explain how to publish a page. It rarely settles whether the claim on that page is supported, whether the audience is the right one, or whether the change can go live without another round of review. Those are judgement calls. When the judgement remains tacit, the process ends with the same step: ask the founder. Hiring moves tasks faster into that final step. A new marketer writes the email, builds the landing page, prepares the audience, checks the links, and schedules the send. Then the whole job waits for approval because nobody recorded what a safe send looks like. The founder now has more output to review and less time to review it. This is why a capable team can make founder dependency feel worse. More capacity produces more decisions. If authority does not grow with it, the approval queue expands. The correction is smaller than a grand delegation programme. Put the rule beside the work, where someone has to act. A content brief should say which sources may support a claim. An ad task should carry a clear exposure limit and pause condition. A lead-response workflow should name the owner and the cases that need escalation. The team should not have to search a 40-page playbook while a buyer waits. Documentation matters. Placement matters more. The decision rule has to appear at the decision. ##### Split the approval queue into green, amber, and red work The fastest way to shrink founder dependency is to stop treating every decision as equally dangerous. Most marketing teams use one invisible category: founder approval required. Replace it with three visible lanes. | Lane | What belongs there | How it moves | | --- | --- | --- | | Green | Reversible work inside an approved brief: headline variants, internal links, routine negative keywords, layout corrections, scheduled distribution | The named owner decides and ships. The founder can inspect the decision trail later. | | Amber | Bounded commercial exposure: a budget move inside an agreed range, a new proof source, a reply to a high-value enquiry, or a material change to page emphasis | A second qualified person checks the evidence and the boundary. Work moves without waiting for the founder. | | Red | Hard-to-reverse decisions: a new offer, a pricing-policy change, a public claim with legal or reputation risk, entry into a new market, or a commitment outside the agreed scope | The founder or a named deputy decides. The task carries a deadline and a default safe action if neither is reachable. | The colours are less important than the separation. Green work should never sit behind a red-work approval habit. Amber work needs a real boundary, not "use your judgement" followed by punishment when the judgement differs from the founder's taste. Red work should stay rare enough that the founder can give it proper attention. Take a homepage rewrite. Changing "request information" to a clearer action may be green when the page brief already defines the buyer and next step. Adding an early-engagement result from an approved proof register may be amber because another person should confirm the framing. Repositioning the business around a different category is red. One page. Three levels of consequence. This model asks the founder to accept a trade. Someone else will occasionally choose a headline you would not have chosen. A reversible miss may ship. You gain a business that can keep learning without waiting for your taste to become available. ##### Run a two-week founder dependency test A long weekend is too easy to fake. People can hold decisions until Monday, and the founder can clear the queue from a phone before breakfast. [Vistage surveyed more than 200 owners and CEOs in 2026](https://vistage.com/research-center/personal-development/exit-planning/unplug-exit-planning/) about time away and what happened inside their companies. More than three-quarters of those who took time away limited it to a single week. The report argues that five business days lets teams wait; two consecutive weeks forces the system to show what it can carry. Treat that finding as a stress-test design, not a promise of causation. The survey was self-reported and the fully disconnected group was small. Even so, the contrast is useful: among owners who completely disconnected, 90% reported sound employee decisions and 80% reported uninterrupted work. Owners who stayed connected reported more escalations and stalled work. Availability can hide the thing you are trying to measure. Run the test in four moves. 1. Pull the last 20 marketing approvals that reached you. Mark each green, amber, or red. If most are red, your definitions are too vague or your team lacks a second checker. 2. Set the lane, owner, evidence, deadline, and safe default on every active item. Do this in the working queue, not in a separate document. 3. Become unreachable for ten working days. No email replies, Slack reactions, call-ins, or quiet edits from a hotel room. A genuine emergency uses one named route and a narrow definition. 4. On return, inspect the residue. Which decisions waited? Which moved badly? Which escalations were justified? Change the boundary that failed, then run the test again. The test is allowed to expose mistakes. That is its job. Run it before a crisis, acquisition discussion, illness, or overloaded quarter makes the absence compulsory. One founder in a current community thread put the private fear plainly: "Taking time off feels impossible because I don't know who can actually run the business without me." The test replaces that fear with evidence. You stop guessing what might break and get a list of what did. ##### What should still come back to the founder Some marketing decisions should wait. Early positioning, a major offer change, a sensitive public response, and a promise that could bind operations all carry enough consequence to justify founder attention. The informed objection is fair: founder judgement may be the commercial advantage. In an early company, the founder hears the objections, knows which compromises the product can support, and spots a bad-fit buyer faster than a new hire. Removing that input in the name of scale can produce polished work that misses the market. Keep the input. Remove the queue. The founder defines the red decisions, records the reasoning after making them, and reviews patterns on a fixed cadence. They do not approve every green choice to prove that standards still matter. Senior attention goes to the few calls where experience changes the outcome. The same distinction applies when you use an outside partner. Direct access to the senior person doing the work has value. A partner who asks the founder to choose every headline, chase every update, and arbitrate every routine exception has handed the work back with nicer formatting. At SharpHaw, the useful standard is simple: the senior operator owns movement across the agreed queue, while the founder keeps the decisions that change the business. That is what senior-led should mean. It should reduce the founder's management load without hiding who is accountable. ##### Build a decision trail beside the work A status label saying "waiting for approval" tells you almost nothing. Good marketing operations record the decision that has to happen, the evidence available, the person who owns it, and what happens if the deadline passes. Use five fields on any material item: - Decision: the exact choice, written as a question someone can answer. - Lane: green, amber, or red. - Evidence: the source, customer phrase, metric, policy, or approved proof that supports the choice. - Owner and deadline: one person and one time, without a committee-shaped escape hatch. - Result and next check: what moved, what happened, and when the decision will be revisited. Imagine the Wednesday content queue. A founder article has a claim about customer behaviour. The writer links the source. The claim is amber, so a second reviewer checks its scope and date. The page ships. Two weeks later, Search Console and the CRM provide the next evidence. Nobody waits for a vague "looks good" because the system already says what good requires. That is also why every SharpHaw subscription includes [SharpOS as one shared workspace](https://sharphaw.com/sharp-os) for work, assets, reporting, and client context. Its useful part is seeing the task, decision, evidence, owner, and next move together. Visibility should help work move. A dashboard that merely shows the queue getting longer is report theatre with better colours. ##### Audit the approvals before you add more work Open the last ten marketing tasks that needed your sign-off. Count how many were truly red. For every green or amber item, write the missing rule that would have let someone else decide. Put that rule into the live queue. Then book the two-week test. Founder dependency will not disappear because the founder becomes less important. It falls when the business can use that judgement without demanding constant access to the person who formed it. If your marketing still comes back to you as a stack of approvals, [bring the queue to a focused fit check](https://sharphaw.com/contact). SharpHaw will show you which decisions need a senior operator, which need a boundary, and which should have shipped without you. No theatre. Just the operating model. --- ### How to name a company: why I chose SharpHaw [Read on sharphaw.com](https://sharphaw.com/blog/how-to-name-a-company-why-i-chose-sharphaw) · Founder · published 2026-08-28T08:00:00Z > How to name a company that guides real decisions. See why Gabriel chose SharpHaw, then run the same practical constraint test on your shortlist before launch. A good company name should make the next bad decision easier to reject. If you are working out how to name a company, you will find plenty of advice about brainstorms, domains and trademarks. All of that matters. None of it tells you what the name should do once the business is running. I chose SharpHaw because it carries my surname and sets a standard for the work. “Espinheira” translates to thorn or haw: nature's edge. The name is meant to have one. It should stop me publishing soft copy, hiding behind vague timelines or accepting work that cannot be shipped properly. That is the useful test for a name: not whether everybody likes it in a survey, but whether it still helps you make a decision five years later. **TL;DR:** To name a company well, choose a name that is memorable, usable and legally clear, then ask what it will force the business to do. A strong name leaves room to grow while giving you a standard for voice, offers and behaviour. If it cannot reject anything, it is only decoration. ##### Why most company naming advice stops too early Most naming advice treats the decision as a funnel: generate a long list, filter it, check availability, test the survivors and register one. That process can prevent an avoidable mistake. It cannot tell you whether the winner will be useful after launch. Official UK guidance recommends a name that is simple, memorable, easy to spell and broad enough for future ambitions. It also separates a company's legal name from a trading name and explains the checks that sit around both. That is sound guidance for UK founders, and the [full naming rules are worth reading](https://www.business.gov.uk/support/ideas-planning-strategy/naming-your-business/). They are gates, though. Passing them means a name is possible. It does not mean the name is right. The common mistake is to judge a shortlist by attraction alone. Which option sounds biggest? Which one looks best in a wordmark? Which one wins a poll among people who will never have to use it in a difficult sales call? Add a second kind of test: rejection. A name becomes useful when it makes some choices feel plainly wrong. That is where positioning stops being a slide in a deck and starts affecting the work. ##### What does SharpHaw mean? SharpHaw comes from something I already own: my family name. [“Espinheira” is my surname](https://sharphaw.com/about), and it translates to thorn or haw — nature's edge. The meaning gave the company a language for the standard I wanted to keep. The point is not that every founder needs to translate a surname. The point is that the origin should create pressure. “Sharp” means a homepage cannot open with a fog of empty claims. “Edge” means the work needs a decision, not another round of polite options. “Haw” keeps the story personal enough that I cannot pretend the company is a faceless machine when I run the strategy and engineering myself. That pressure reaches beyond copy. SharpHaw runs work as a weekly loop inside [SharpOS](https://sharphaw.com/sharp-os), where plans, changes and decisions stay visible. A name built around a pointed edge would ring false if the operation underneath it were vague. This is not mystical brand theory. It is quality control. When the name, offer and operating model disagree, one of them needs to change. ##### Can a company name reject a bad decision? It should, within limits. A company name cannot replace positioning, legal advice or judgement. It can compress those decisions into a phrase that is difficult to ignore. Imagine reviewing a new homepage. The first draft says the company “does everything for every business”. Nothing is technically false. Nothing is useful either. SharpHaw gives me a reason to reject that draft before debating font sizes: it has no edge, no named buyer and no decision. Use the same pressure on your own shortlist. For each candidate, finish these two sentences: - We are **[name]**, so we always ______. - We are **[name]**, so we never ______. Weak names produce answers such as “do good work” or “care about customers”. Those lines fit a bank, a bakery and a plumbing firm. A useful name produces a constraint tied to your actual business: which buyer you serve, how you behave under pressure, what you refuse to sell or what standard the work must meet. If the sentence only explains the logo, keep looking. If it changes a real choice, the name has started earning its place. ##### How do you pressure-test a company name before committing? Put the name into ordinary business situations before you put it on a mood board. A clever word can survive a presentation and still sound ridiculous on an invoice, in a referral or during a complaint. Take the strongest three candidates and use each one in four places: the opening line of a sales call, the subject of an invoice, a job advert and the announcement of a future service you have not built yet. Say every version aloud. Ask someone unfamiliar with the idea to spell it back to you. Then run the two-sentence constraint test above. You are looking for friction, but not zero friction. One sentence of explanation can buy distinctiveness and a useful story. Five minutes of correction every time somebody hears the name is a tax. A name tied so tightly to today's service that it breaks when you expand is another tax. Only after that should the clearance work begin. Search company registers, relevant domains and social handles. Use the [WIPO Global Brand Database](https://www.wipo.int/en/web/global-brand-database), then check the national or regional intellectual property registers for the markets where you plan to trade. WIPO itself notes that its database does not replace those local searches and suggests consulting a trademark attorney. An initial search is evidence for a shortlist, not legal clearance. ##### Does the exact domain name need to be available? An exact domain is useful, but it should not rescue a weak name or kill a strong one by itself. The domain must be easy to say, type and remember. It does not need to dictate the company's meaning. The market is crowded. The [Domain Name Industry Brief](https://www.dnib.com/) reported 401.6 million registrations across all top-level domains at the end of Q2 2026. That figure includes many kinds of registrations, so it does not mean every good address is gone. It does explain why the most obvious one-word options often lead founders into distorted spellings, stray hyphens or a costly purchase. Treat domain availability as a filter. If the exact address is unavailable, check whether a short, natural modifier works without confusing the spoken name. If the only available version requires you to explain three missing vowels and a fashionable suffix, the name has failed the practical test. Your future customers will forgive a sensible domain. They will not enjoy hunting for a company they cannot spell. ##### Should a business name explain what the company does? A descriptive name gives you immediate clarity and can become a cage. A non-literal name gives you room and creates an explanation bill. Neither option is free. SharpHaw does not announce “website, ads, content and AI automation” in the name. I accepted that cost because a list of current services would age faster than the standard behind them. The name can still fit if the mix of work changes. What it cannot survive is soft, vague work. That trade is worth making only when you can state the missing explanation cleanly. If your invented word needs a paragraph before anybody understands the category, it is probably self-indulgence. If one plain sentence places the company and the name then adds a memorable reason to care, the distinctiveness is doing work. This is also why the [website has to convert the name into a clear promise](https://sharphaw.com/services/conversion-first-websites). The name opens the door. The first screen must tell the right buyer what is behind it. ##### Frequently asked questions **How do I know if a company name is taken?** Check the company registry in the country where you will register, trademark databases covering the markets and classes you need, relevant domains and social handles. Similar names can matter even when the exact wording differs. Treat your search as initial screening and use a qualified trademark professional for legal clearance. **Do I need to trademark my business name?** That depends on the jurisdictions, goods and services involved, and the protection you need. In the UK, official guidance distinguishes a registered legal company name from a trading name and says trademark registration is needed if you want to protect that trading name. Get jurisdiction-specific advice before filing. **Does my business name need to match my domain?** No. A close, natural match can work if it is easy to say, type and remember without creating confusion. Avoid domains that require a verbal instruction manual. The exact domain is one practical filter among several; it should not outweigh legal clearance, distinctiveness or the name's fit with the business. **Can I change my business name later?** Usually, but the work extends far beyond a new logo. Registrations, contracts, invoices, email, domains, search visibility and customer memory may all need attention. The exact process depends on the country and legal structure. That is why testing the name against future services and real operating situations is worth doing early. ##### The test worth keeping If your company name cannot rule out a bad decision, it is only decoration. Clear the legal and practical gates, but do not stop there. Choose a name that can still make a demand of the business after the launch energy has gone. SharpHaw asks for pointed work, visible decisions and a week that ships. Your name should ask something equally specific of you. If the promise in your name and the promise on your website have drifted apart, [book a focused 30-minute call](https://sharphaw.com/contact). Bring the current homepage. I will tell you where the story loses its edge and what I would change first. --- ### Keyword cannibalisation is why your blog plateaued past 50 posts [Read on sharphaw.com](https://sharphaw.com/blog/keyword-cannibalisation-blog-plateau) · Content Engine · published 2026-08-27T08:00:00Z > Past 50 posts, your pages compete for one query and split your rankings. Find keyword cannibalisation in Search Console and fix it by cutting, not publishing. Open Search Console, filter to the one query your blog should own, and there they are: three of your own URLs, splitting the impressions between them. Positions eight, twelve, nineteen. None of them on page one. You weren't outranked by a competitor — you were outranked by yourself. This is keyword cannibalisation, and it's the quiet reason a lot of founder blogs stop growing right around the point they should be compounding. You published consistently. You, or an agency, shipped post after post. And somewhere past fifty of them the traffic went flat — not because you ran out of demand, but because your posts started competing for it. Here's how to see it in your own data, and why the fix is almost never another post. **TL;DR:** Keyword cannibalisation is when two or more of your own pages compete for the same query, splitting clicks and rankings so none of them wins. It usually surfaces once a blog passes roughly 50 posts. Find it in Search Console, then fix it by merging, redirecting, or cutting pages — not by publishing more. ##### Your own posts are competing, and Google isn't confused The popular explanation is that Google "gets confused" when two of your pages target the same keyword. It doesn't. Google is perfectly capable of choosing one page — the trouble is it keeps choosing a different one week to week, or a weaker one, because you handed it five mediocre options instead of one strong one. Every post you add on a topic you've already covered doesn't bring a fresh slice of traffic. It divides the authority — links, relevance, engagement history — across more URLs. Your tenth post on the same subject doesn't add a tenth of the traffic; it takes a slice from the other nine. The page that used to sit at position four drifts to eight, the new one lands at twelve, and the query you were winning becomes a query you split three ways. The nuance that matters: cannibalisation only bites when the pages chase the same intent. Two posts on Meta ads — one a beginner explainer, one a budget-pacing teardown — coexist fine, because a searcher wants different things from each. Two posts both trying to be the definitive "how to run Meta ads" cannot. If you've ever muttered "we've done the content, why aren't we showing up?", this is usually the reason. ##### Find it in Search Console before you touch anything You can diagnose this in an afternoon, with a tool you already have and already pay nothing for. In Search Console, open the Performance report, click a query you should be ranking for, then switch to the Pages tab. If two or more of your URLs pull meaningful impressions for that single query, they're competing for it. The tell isn't subtle once you know the shape: one query, several of your own pages, none in the top three. Sort your queries by impressions and work down the top twenty. Most blogs find the whole problem lives in three or four clusters — a handful of topics where you've published repeatedly and split yourself every time. Write down the query, the competing URLs, and each one's position and clicks. That list is the entire audit. You're not guessing which posts overlap or trusting a plugin's opinion — you're reading the collision straight off your own data, which is the only way to make the next decision without flinching. ##### The fix is a decision, not another post In February 2025, HubSpot removed around 3,000 pieces of outdated content from its blog, nearly all of them indexed but drawing essentially no traffic. It wasn't the only change they made, but the mechanics moved one way: crawling dropped, fresh pages started getting indexed in minutes instead of days, and authority consolidated onto the pages that actually earned it. The lesson isn't to go delete 3,000 posts. It's that on a large content library, subtraction can be a growth move, not a loss — the opposite of what almost everyone selling content will tell you. Once you have your list of competing clusters, each one gets exactly one of five decisions: - **Leave it.** The pages genuinely serve different intent and both earn clicks. Do nothing. - **Differentiate.** The overlap is fixable — re-angle one page to a distinct intent, rewrite its title and opening, and re-point its internal links. - **Redirect.** One page clearly wins. 301 the weaker one into it so its links and history flow to the survivor. - **Merge.** Two half-good posts become one strong page at a single URL, and you redirect the other into it. - **Cut.** No traffic, no links, nothing worth saving. Remove it and let the crawl budget go to pages that earn. One caution, because the mistake runs both ways: don't cut on age or a slow week alone. Google's own Search Liaison has said plainly that old content isn't inherently harmful and Google doesn't tell you to delete it. Check traffic, backlinks, and the query data before you remove anything. A page can look dead and still hold a single backlink that's quietly carrying half your topic's authority — cut it blind and you'll wonder why the survivor slid too. ##### Why "publish more" quietly made it worse The advice that created this problem is the same advice you'll be handed to fix it: publish consistently. For the first stretch of a blog's life that's right — you're claiming ground you don't own yet, and volume is how you claim it. Past a point, usually somewhere north of fifty posts, "just keep publishing" stops compounding and starts colliding, because you run out of genuinely new angles and quietly begin re-covering ground you already hold. It gets worse when the content was outsourced by the brief. An agency paid per post has every incentive to keep shipping and none to tell you that post forty-one is competing with post twelve. You end up with a library that looks productive on a spreadsheet and performs like a traffic jam you caused — and the posts you'd have to cut are the ones you paid for, which is exactly why nobody cuts them. We run our own [blog](/blog) in public, well past 130 posts, and keeping it compounding takes this discipline every week: a content engine is a governed library, not a volume machine. Every new post has to earn its place against the ones already there. Some weeks the most valuable thing we ship isn't a new post — it's a merge that finally lets one page win the query five were fighting over. ##### In 2026, one strong page beats five thin ones Cannibalisation used to cost you a few positions. It costs more now, because of where search is heading. Google's December 2025 core update pushed further in a direction it's held for years: it rewards pages that show real experience and depth, and demotes thin, near-duplicate content. Five overlapping posts on one topic are, by definition, thinner than the single page you could have written with the same effort. AI search raises the stakes again. When an answer engine cites sources, it pulls very few pages per site — Semrush puts it at roughly one page per domain in ChatGPT responses. If you want to be the page ChatGPT or a Google AI Overview quotes on your topic, you need one obvious candidate to be that source, not five splitting the signal between them. Consolidation stopped being housekeeping. It's how you become the page worth citing. ##### Frequently asked questions **How do I find keyword cannibalisation in Google Search Console?** Open the Performance report, click the query you want to rank for, then open the Pages tab. If two or more of your URLs earn impressions for that one query, they're competing. Repeat for your highest-impression queries — the clusters where several of your pages appear, none in the top three, are your problem areas. **Should I delete old blog posts, or redirect them?** Redirect when a page has backlinks, traffic, or history worth keeping — a 301 passes that value to the surviving page. Delete only when a page has no traffic, no links, and nothing worth merging. Check the data first; a page can look dead while quietly holding a link that carries real authority. **Do canonical tags fix keyword cannibalisation?** Rarely. Canonical tags are for near-identical pages you deliberately keep, like a print version or a parameter variant. They don't resolve two genuinely different posts competing for one query — for that you merge, redirect, differentiate, or cut. Put a canonical on real overlap and Google treats it as a suggestion it often ignores. ##### What to do next A blog that stalled past fifty posts rarely needs a forty-first article. It needs someone to open Search Console, find the three clusters where your own pages are fighting each other, and make five decisions. The traffic you're missing is already yours — it's just spread across pages that should have been one. Want a second read on yours? Book a 30-minute call, bring the query your blog should own and can't crack, and leave with a merge-redirect-cut list for it. It's the kind of work our [content engine](/services/content-engine) does every week — in the open, where you can watch it ship inside [SharpOS](/sharp-os). --- ### AI customer research: automate the notes, not the doubt [Read on sharphaw.com](https://sharphaw.com/blog/ai-customer-research-automate-notes-not-doubt) · Founder · published 2026-08-26T08:00:00Z > AI customer research can scale interviews without scaling judgement. Use this founder-led loop to test assumptions, inspect evidence and make sound decisions. AI customer research should automate repeatable interviews, transcription and first-pass synthesis. The founder still owns the hypothesis, the doubtful evidence and the decision that changes. That split matters because scale can improve one part of the work while weakening another. In a [2025 experiment with 1,800 participants](https://arxiv.org/abs/2504.13908), AI follow-up questions produced more detailed and informative open-ended answers. They also produced a slightly worse respondent experience and a small increase in false positives linked to acquiescence bias. This is the useful tension. AI can help a founder hear from more people. It cannot decide which answer should make the company change course. Picture the Monday dashboard: 50 completed interviews, six themes and a neat summary saying buyers want speed. The founder cannot name one buyer who meant onboarding speed, one who meant time to first result, or one who would pay to solve it. Nobody knows whether the homepage, product or offer should change. The research produced activity. It did not produce a decision. **TL;DR:** Use AI customer research to run repeatable interviews, transcribe conversations, retrieve evidence and make a first pass at patterns. Before the first interview, write what would change your mind. Personally inspect raw, negative and outlier evidence. Then record the commercial decision, its confidence and the next test. If the output stops at a summary, you have automated research work without doing customer discovery. ##### Where does AI customer research earn its place? AI is strongest where the work benefits from consistency, volume and retrieval. It can ask the same core questions across many interviews, branch into approved follow-ups, transcribe calls, label passages, group similar answers and return every quote related to a buying objection. It can also prepare a human conversation by showing where the evidence is thin or contradictory. That is useful plumbing. A founder who has spoken to five customers can inspect 30 more conversations without reading every transcript from the first line. A team can search the raw evidence instead of relying on whoever took notes. Repeated questions become easier to compare. Consistency has real value. In a blind assessment of masked transcripts across three countries, [Ipsos scored out-of-box AI and human moderators equally for consistency: four out of five](https://www.ipsos.com/sites/default/files/ct/publication/documents/2025-12/ipsos-views-mind-or-machines.pdf). On rapport, unscripted new questions and adapting communication style, the same AI scored one or 1.5 while human moderators scored 4.5 or five. The lesson is narrower than “humans good, AI bad”. A repeatable interview about a known workflow is different from a conversation where the real issue appears as hesitation, contradiction or an unexpected story. Match the method to the uncertainty. Use AI for reach and organisation. Use a person when the value of the conversation depends on noticing what was never in the guide. ##### Which parts of customer discovery stay with the founder? Three responsibilities should remain close to the founder. ###### 1. Define what would change your mind “Learn about onboarding” is a topic, not a research decision. A usable hypothesis names the current belief, the evidence that would weaken it and the decision at stake. For example: > We believe owner-operated service businesses delay a website rebuild because coordinating specialists feels riskier than the old site. If at least five qualified buyers describe budget as the real blocker without prompting, we will test a narrower entry offer before rewriting the coordination message. The numbers are not universal rules. They make the founder's standard visible before flattering answers arrive. Without this step, an AI system can generate a polished version of the founder's existing opinion. The prompts, tags and summary all inherit the original framing. ###### 2. Inspect the evidence that does not fit Do not review only the top themes. Read or watch a sample of raw conversations, every strong counterexample and the answers the system marked as unclear. Look for three things: a follow-up the moderator missed, two participants using the same word to mean different things, and an answer that agrees with the hypothesis too easily. The academic study above found a slight increase in false positives from acquiescence. Agreement deserves inspection, especially when the question made agreement easy. This is where a founder's commercial context matters. “We need it faster” may describe an implementation delay, a slow internal approval process or anxiety about paying before seeing progress. A theme label hides that distinction. The next decision depends on it. ###### 3. Own the commercial consequence An insight is not the end of the workflow. State which buyer, offer, message, product behaviour or priority changes because of it. Steve Blank's customer-discovery advice remains blunt: [“The founders need to do this.”](https://stvp.stanford.edu/av/acting-customer-discovery) A researcher or AI system can improve the evidence. Neither carries the founder's responsibility for the bet that follows. If the output is a folder of transcripts, you automated research activity. If a commercial assumption changed for a stated reason, you did customer discovery. ##### How do you run an AI-assisted customer research loop? Use a five-step loop: **Question → Collect → Inspect → Decide → Record**. | Step | AI can help with | Founder owns | | --- | --- | --- | | Question | Turn the research goal into a draft guide, remove compound questions and suggest neutral probes | The belief being tested, the decision at stake and what would change the belief | | Collect | Run repeatable text or voice interviews, branch into approved follow-ups and transcribe human calls | Participant fit, consent, sensitive topics and the conversations that need a person | | Inspect | Retrieve quotes, cluster answers, compare segments and flag contradictions | Raw-session sampling, negative evidence and missed follow-ups | | Decide | Draft options and connect each option to supporting passages | The commercial choice, confidence and acceptable risk | | Record | Keep the evidence, reasoning, owner and review date together | The final decision and the condition that will reopen it | Start small. Run the guide with two or three people before asking AI to repeat it at scale. Check whether the questions are understood, whether follow-ups stay neutral and whether the answers can affect the named decision. Fix the guide while the mistake is cheap. Then mix methods deliberately. An AI-moderated round can map common language and expose areas of disagreement. A founder-led round can explore the most consequential or confusing threads. Another AI pass can retrieve every related passage without pretending that frequency makes the conclusion true. This loop also improves human interviews. Instead of walking into the next call with a generic list, the founder arrives with a live contradiction: six people described setup as simple, three abandoned it at the same point, and two used “setup” to mean something else. That is a sharper conversation. ##### How do you know an AI insight is strong enough to act on? Ask five questions before changing anything expensive. 1. **Can we trace it?** Every claim should link back to raw words, not only an AI summary. 2. **Did the guide lead it?** Read the question immediately before the answer. Agreement after a loaded question is weak evidence. 3. **Who said it?** A frequent complaint from poor-fit participants should not steer an offer built for a different buyer. 4. **What contradicts it?** Record the strongest counterexample and explain why it does or does not change the conclusion. 5. **What decision follows?** Name the smallest commercial change that would test the insight. Frequency is not the same as importance. One buyer describing an unknown compliance barrier may matter more than 20 people preferring a different button label. Ten mentions of “speed” remain ambiguous until the company knows what buyers wanted to happen sooner. Confidence should affect the size of the next move. Weak evidence can justify another interview or a reversible message test. It should not quietly become a complete repositioning. The aim is not certainty. It is a visible chain from a question to evidence to a proportionate decision. ##### When should a human run the interview? Choose a human-led conversation when the cost of a missed signal is high or the subject needs trust. That includes early discovery, unfamiliar markets, emotionally loaded problems, sensitive personal or commercial information, complicated buying groups and conversations where body language or silence carries meaning. It also includes the first few sessions of any new guide. A founder should hear how real people interpret the questions before automating them. AI moderation is a better fit when the subject is bounded, the guide has already been tested, participant volume matters and the possible answers are useful without rich non-verbal context. It can be particularly useful between human rounds: widen the sample, find language patterns, then return to a person for the knots. There is a trade-off. Human interviews take time and vary with the interviewer. AI interviews are more consistent and easier to scale, but they can miss the unexpected turn that changes the whole model. A sensible research plan uses each where its weakness is least costly. The founder does not need to moderate every interview. The founder does need enough direct contact with the evidence to recognise when the summary has sanded off the useful doubt. ##### Keep one decision record, not another research archive End each research round with a short decision record: - the belief you tested; - the participants and method; - the evidence for and against it; - the raw passages that mattered; - the decision made and its owner; - the smallest next test; and - the date or signal that will reopen the decision. Keep that record beside the work it changes. When a website message, paid-search exclusion or onboarding step moves, the reasoning should be easy to find. The next round can build on the previous one instead of rediscovering its context. That is how AI customer research compounds. Faster notes are useful once every research round leaves the company with better questions, clearer evidence and one visible decision. SharpHaw uses AI as plumbing across content, websites and automation, with the commercial decision kept in view. Work ships weekly through SharpOS so the evidence, change and next observation stay in one trail. [Send SharpHaw one customer assumption and the evidence behind it](https://sharphaw.com/contact). You will get a straight fit check on the smallest research loop worth running and which part should stay human. --- ### Your bounce rate went down. Your site got worse. [Read on sharphaw.com](https://sharphaw.com/blog/bounce-rate-went-down-site-got-worse) · Analytics · published 2026-08-25T08:00:00Z > In GA4, bounce rate is the inverse of a 10-second dwell timer, not a quality score. A lower one can mean a worse website — here is what to track instead. A visitor lands on your services page, reads the one line that tells them you fix their exact problem, and taps your phone number nine seconds later. Google Analytics files that visit as a bounce. Now hold that next to the report your last agency sent: bounce rate down 14%, engagement up, three green arrows in a row. Both things can be true at once — a lower bounce rate and a website that sells less than it did last quarter. In GA4, the number and the outcome are not the same thing, and sometimes they move in opposite directions. Here is the part most founders never get told. A bounce in GA4 is not "someone hated your page." It is "someone didn't cross an arbitrary line" — a ten-second timer, a second pageview, or one tracked action. Miss all three and you bounced, whether you left happy or furious. So on the pages that actually matter to your business, bounce rate tells you who lingered. It says nothing about who bought. Optimise it directly and you can make your site worse. ##### What GA4 actually counts as a bounce [Google's own documentation](https://support.google.com/analytics/answer/12195621) defines an engaged session as one that "lasts longer than 10 seconds, has a key event, or has 2 or more screen or page views." Bounce rate is the mirror of that: "the percentage of sessions that were not engaged." Engagement rate and bounce rate always add up to 100. Read the criteria again, because they are doing something quiet. Nothing there asks whether the visitor got what they came for. A session clears the bar by sitting open for eleven seconds. No scroll, no click, no reason — just time on the clock. It was not always this loose. In the old Universal Analytics, which stopped processing data on 1 July 2023, a bounce meant a single-page session with no interaction at all. One and done. Google's former analytics evangelist, Avinash Kaushik, once described that bounce from the visitor's side as "I came, I puked, I left." Crude, but clean: it meant the page failed to earn a second move. GA4 kept the word and changed the meaning. Bounce rate was cut from GA4 at launch, then brought back in July 2022 after enough people complained — rebuilt as the inverse of that ten-second engagement timer. So if your monthly report runs one "bounce rate" line straight across mid-2023, it is splicing two different metrics into one chart and calling the wiggle a trend. That is a graph pretending its own y-axis never moved. ##### A bounce is a shrug, not a verdict The instinct is hard to shake: high bounce bad, low bounce good. It is wrong often enough to be dangerous. Bounce rate measures inaction, not dissatisfaction, and those are not the same event. Picture two visitors. The first reads your whole pricing explainer, finds the single answer they needed, and closes the tab satisfied. The second lands, sees a stock photo above a wall of jargon, and leaves annoyed. GA4 can log both as bounces. The fastest, cleanest win on your site and its most useless visit look identical in the report. This is why "what's a good bounce rate?" is the wrong question, even though every benchmark post answers it — usually with a range around 40 to 55% and a shrug about context. A glossary page, a contact page, a blog post that fully answers one question: each can run a bounce rate north of 70% while doing precisely its job. The number carries no meaning until you know what the page was for. ##### You can lower your bounce rate by making the page worse Here is the part that should make you suspicious of the green arrow. Because the default engaged-session bar is a ten-second timer, the easiest way to "improve" your bounce rate is to make people stay longer. Staying longer is not the same as buying. Autoplay a background video and engaged sessions climb, because the tab sits open past ten seconds while the clip runs. Bury your phone number three scrolls down and people spend longer hunting for it, so the timer clears the bar before they give up. Slow your page load and the visitor waits, staring, technically engaged. Every one of those changes lifts your engagement rate. Every one of them is worse for the person trying to hire you. So when a report says "we reduced your bounce rate," the honest follow-up is one word: how? A clearer headline and a faster path to the enquiry is a real win. A hero video and a longer page is not — you paid to make the metric prettier and the sale harder. This is the report theatre owners describe when they say they "stare at reports full of jargon, green arrows, and charts that don't really mean anything." The green arrow is not lying about the data. It is lying about what the data means. ##### Measure who acted, not who stayed Retire the site-wide bounce number as a scoreboard. Put one question in its place: did the people who were supposed to act, act? That needs a real conversion event on every page that matters — a call placed, a form sent, a booking made — tracked from click to client, not click to dashboard. On a service page the number is enquiries, not engagement. On a checkout it is completed orders. On a booking page it is calls held. If a change lifts that number, it worked. If it doesn't, it didn't, however green the engagement chart looks. Then read it by intent. Ten seconds means one thing for a buyer on your pricing page and something else for a reader who wandered in from a two-year-old post. Separate the traffic that was meant to convert from the traffic that never would, and judge each page against its own job. One honest conversion number, split by why the visitor came, beats a tidy engagement percentage every time. ##### When bounce rate is still worth a glance None of this makes the metric useless. It makes it something to investigate, never something to trust. On a content page where you would expect people to read and click through, an engagement rate scraping the floor can be a genuine smoke alarm — the wrong audience found you, the page loads too slowly, or the headline promised something the page doesn't pay off. That is worth a look. The rule is the direction of the arrow. Use a bad engagement number to ask "what's broken here?" and go find out. Never use a good one to conclude "this page is working." A page is working when it produces the action it exists for. The rest is weather. The metric that judges your website should be the one your business actually runs on. Not a dwell-time percentage a slower page can inflate. An enquiry. A booking. A call you can answer. That is the whole test — and it is why "I want results, not reports" is the most reasonable thing a founder can say to anyone running their site. The next time a chart shows a metric improving, ask the one thing that cuts through it: which real outcome moved with it? If nothing did, the metric was never the point. ##### FAQ **What is a good bounce rate in GA4?** There isn't a universal one. GA4 bounce rate is only the share of sessions that didn't last ten seconds, trigger an action, or reach a second page, so a "good" figure depends entirely on the page's job. A blog post can sit above 70% and still work; a checkout at 70% is a fire. Judge each page against the action it exists to produce, not a benchmark. **Why did my bounce rate change when I moved to GA4?** Because the definition changed. Universal Analytics counted a bounce as a single-page session with no interaction. GA4 counts it as any session that fails its engagement test — under ten seconds, no key event, fewer than two pageviews. They measure different things, so a bounce rate that "improved" across the 2023 switch may reflect the new maths, not a better site. **Is bounce rate a Google ranking factor?** No, and Google has said so for over a decade. Search Advocate John Mueller called it "a bit of a misconception that we're looking at things like the analytics bounce rate when it comes to ranking," and Gary Illyes put it plainly: "we don't use analytics/bounce rate in search ranking." Chasing bounce rate for SEO chases a number Google never sees. --- ### Founder-led sales is wasted if the calls die in your notes [Read on sharphaw.com](https://sharphaw.com/blog/founder-led-sales-buyer-language) · Founder · published 2026-08-24T09:00:00Z > Founder-led sales should produce more than closed deals. Use five call fields to turn buyer language into stronger pages, content and a safer handoff. Seven founder-led sales calls can produce roughly 42,000 spoken words, then collapse into seven CRM notes that say little more than "follow up Friday." [Gong estimates a typical sales conversation at about 6,000 words](https://www.gong.io/blog/revenue-teams-arent-ready-for-ai-heres-why-and-how-you-can-prepare). The useful phrases, awkward pauses and proof requests stay buried in the recorder. Founder-led sales is supposed to teach you how the market thinks before you ask someone else to sell into it. If those calls change your pitch but leave your homepage, service pages and content untouched, most of the learning still lives in your head. You recorded the conversation. You did not build an asset from it. **TL;DR:** Founder-led sales becomes transferable when recurring buyer language, objections, proof requests and outcomes change specific sales and marketing assets. Capture five fields from each call, keep the source and commercial outcome attached, then test whether another person can use that evidence without asking the founder to explain the market again. ##### Founder-led sales earns its value through the learning loop Pete Kazanjy gives the clean definition: ["Founder Led Sales is the process by which startup founders discover, refine, and scale their product's initial sales motion"](https://www.foundingsales.com/). The founder runs the early conversations because the motion does not exist yet. Each call helps define the buyer, trigger, promise, proof, price and path to a decision. Founder presence still matters. A founder can answer an odd technical question, change the product promise, admit a limitation or reject a bad-fit deal without asking three departments for permission. A new salesperson cannot borrow that authority from a script. That is exactly why a founder's close rate can hide a weak system. The deal may move because the buyer trusts the person in the room, while the message that moved them never becomes visible anywhere else. The next prospect lands on the website and sees the old positioning. The new salesperson opens a playbook full of approved phrases but no record of which buyer used them, what they were worried about or whether the deal closed. The goal is to preserve the reasoning behind the founder's performance. Charisma does not transfer. Evidence can. ##### Your call summary throws away the part marketing needs A typical call contains about 6,000 words. Gong says a hand-written summary usually keeps 40 to 60, which means [roughly 99% of the conversation disappears](https://www.gong.io/blog/revenue-teams-arent-ready-for-ai-heres-why-and-how-you-can-prepare). That compression is useful for administration. It is brutal for marketing. Picture the CRM after a 45-minute demo. The note says: "Good fit. Concerned about migration. Send security document. Follow up Friday." The buyer's actual language has gone. So has the moment they explained why the last migration failed, the comparison they made to their current tool, and the exact evidence that made them lean forward. Marketing needs that detail. A homepage promise written from "concerned about migration" will sound like every software website. A service-page section built from "we cannot lose another Friday rebuilding room allocations before check-in" has a buyer, a scene and a cost. The second line can only ship when the product really solves it, but at least there is now a claim worth checking. Listening matters too. [Gong's 2025 analysis of 326,000 sales calls](https://www.gong.io/blog/talk-to-listen-conversion-ratio) found that sellers in closed-won calls spoke for 57% of the conversation, compared with 62% in lost deals. Treat the five-point gap as a reminder rather than a magic target: the buyer's words are part of the work. A founder who spends the call presenting and the summary recording their own pitch has built a feedback loop with no feedback. AI can extract exact phrases faster than a founder can replay ten recordings. It still needs a brief. Ask for "key takeaways" and it will produce polite mush. Ask for the buyer's trigger, exact language, objection, requested proof and outcome, with timestamps, and it can build something a person can inspect. ##### What should you capture from every founder-led sales call? The useful artefact is a buyer-evidence ledger. Each row ties one signal to the call, the buyer segment, the commercial outcome and the public surface it may change. Five fields keep it small enough to review every week. | Field | What to record | What it can change | | --- | --- | --- | | Trigger | The event that made the problem urgent now | Homepage or service-page problem framing | | Exact phrase | The buyer's words, with a timestamp | Headline, content brief or sales language | | Objection | The reason they hesitate or say no | FAQ, comparison page, qualification rule or article | | Proof requested | The evidence needed to keep evaluating | Demo, technical note, policy, case evidence or product page | | Outcome | Won, lost, stalled or disqualified, with the reason | Whether the signal deserves promotion, another test or no action | Keep the recording link or transcript timestamp beside every row. Add the segment, call stage and owner of the next decision. The quotation supplies the language; the outcome supplies the weight. You need both before changing a page that every prospect will read. A useful row might read: trigger, current agency renewal in 21 days; exact phrase, "I don't want to be locked in again" at 18:42; objection, ownership after cancellation; proof requested, written clause and export process; outcome, qualified but stalled pending review; destination, Plans FAQ. The row tells the next person what to verify, where to answer it and how to judge whether the answer helped. One articulate buyer can still be wrong for the segment. Do not rewrite the website because a single prospect found a memorable way to complain. Review calls in comparable batches: the same buyer type, similar stage, with wins and losses included. Flag a signal when it repeats across separate qualified conversations and the outcomes support it. Park vivid one-offs until another call earns the change. This is where most call libraries fail. One founder on Reddit described ["500 hours of calls sitting there"](https://www.reddit.com/r/SaaS/comments/1rvfxuu/what_do_you_actually_do_with_recorded_sales_calls/) while the tools returned talk ratios and sentiment scores. The archive was full. The decision trail was empty. ##### Which marketing asset should the call change? Start with the buyer's job, then route the evidence to the smallest surface that can answer it. A call insight does not automatically deserve a new article. Sometimes it needs one sentence on a page. Sometimes it should change qualification before another bad-fit lead reaches the calendar. Take a hospitality software founder whose homepage says the product "centralises operations." Four hotel operators explain that the night manager cannot adopt another dashboard during check-in. That pattern may justify a sharper first screen about the existing workflow and how the product fits it. The call supplies the language. The product and support evidence decide whether the claim is true enough to publish. Now take an owner-operated services business replacing an agency. Three prospects ask what happens to the website and accounts if they cancel. That is not a closing-script problem. It belongs on the Plans page or service FAQ, backed by the real ownership and exit terms. Leaving it for the call forces every buyer to carry the same doubt through the website. The same rule applies to a loss. If companies without a connected CRM repeatedly reach the demo and fail the same implementation check, tighten the form, service-page boundary or ad qualification. More enquiries would make the problem worse. The call evidence has identified who should never have entered the sales conversation. At [SharpHaw](https://sharphaw.com/about), this is the standard I want the [Content Engine](https://sharphaw.com/services/content-engine) to meet. A call can create a content brief, but the brief must keep the buyer phrase, source, objection, proof constraint and destination attached. The article then answers a real decision instead of filling a slot on a calendar. ##### When is founder-led sales ready to leave the founder's head? A sales playbook proves that another person can follow the sequence. A cross-surface handoff proves they understand why the sequence works and which public assets must change when the market moves. Run a harder test before the founder steps back. Give the new owner three buyer-evidence rows from recent calls. Ask them to name the buyer segment, explain why the signal matters, find the page or sales asset it affects, and propose the next test. Then ask what evidence would make them leave the asset alone. If they can recite the discovery questions but need the founder to interpret every answer, the motion has not transferred. If they can close the call but cannot tell marketing that the same proof request has appeared in four qualified deals, the learning loop is still broken. There is a fair exception. A simple, low-cost product with stable positioning may need a sales script and little else. The public message can remain steady while the team improves conversion inside the call. Complex B2B offers work differently. Buyers research before the conversation, bring several stakeholders and carry questions back to people who never meet the founder. The website and proof library take part in the sale whether the founder manages them or not. If the call changes your pitch but not your page, the lesson still lives in your head. ##### Record the evidence without building a call graveyard European founders need a data rule before they need a transcription tool. A recording may contain names, voices, commercial details and information the buyer never expected to become raw material for marketing. The [European Commission's GDPR guidance](https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/principles-gdpr_en) requires lawful and transparent processing, a stated purpose, data minimisation, storage limits and appropriate security. The [European Data Protection Board](https://www.edpb.europa.eu/contact/frequently-asked-questions_en) says callers should be informed about the purpose of recording, who receives it, and their rights to object and access the recording. That means the ledger needs boundaries. Decide the lawful basis and check the call-recording rules that apply in each relevant country. Tell participants what you record and why. Keep only the excerpt and context needed for the stated purpose. Restrict access. Set a retention period. If a third-party AI tool processes the file, include it in the data review rather than treating the upload as invisible. Buyer language can usually be used without publishing the buyer's identity. Remove names and details that could reveal the person or company unless you have a separate, valid reason and permission to attribute them. Get local legal advice for the markets you operate in. A clever content system does not excuse careless data handling. ##### Run the ten-call test Choose ten recent calls from one buyer segment and one stage. Include wins, losses and stalled deals. Extract the five fields with source links, group the repeated signals, and park the phrases that appear only once. Then change one asset. Tighten the homepage promise, add the missing proof answer, reject a bad-fit enquiry earlier or brief one article around the recurring objection. Record the commercial signal you expect to move. Review the next ten comparable calls before you keep, revise or reverse the change. One batch only begins the evidence trail. Its value is the operating habit: market learning leaves the founder's memory, changes an inspectable asset and returns to the next sales conversation as a test. [SharpOS](https://sharphaw.com/sharp-os) gives the work one shared home. SharpHaw's Content Engine turns the evidence into pages and content that buyers can inspect before the call. Digital work that compounds. If your best buyer language is trapped in call notes, [bring the last ten transcripts to a focused fit conversation](https://sharphaw.com/contact). We will map one recurring trigger, objection and proof request to the first asset that should change. --- ### A custom marketing proposal never proves how work ships [Read on sharphaw.com](https://sharphaw.com/blog/custom-marketing-proposal-operating-model) · Founder · published 2026-08-23T09:00:00Z > A custom marketing proposal can describe the work but not prove it. Use five checks for price, ownership, cadence, exit terms and week one. An 11-page custom marketing proposal can map the next six months and still tell you nothing about Monday morning after you sign. [Proposify's 2026 dataset of more than 740,000 proposals](https://www.proposify.com/state-of-proposals-2026) found that winning proposals average 11 pages and losing proposals average 13. That may help a seller tighten the document. It does not answer the founder's harder question: "What specifically am I buying?" A proposal can describe a senior strategist, a weekly rhythm and a tidy list of outcomes. It cannot prove who opens the account, who owns the first decision, where the work lives or what you keep when the relationship ends. Use the proposal to understand the offer. Use the operating model to decide whether to trust it. **TL;DR:** A custom marketing proposal can explain an offer, but it cannot prove how the work will run after signing. Before you treat it as evidence, inspect the public price, named owner, work queue, ownership terms, exit route and first decision that will move into production. ##### What is a custom marketing proposal actually for? The document exists to win the sale. One current proposal guide puts it plainly: ["It's a sales asset, not a creative brief"](https://www.propal.io/blog/marketing-proposal-template). Its job is to show that the seller understands the problem, recommend an approach, frame the scope, state the price and make acceptance easy. That is useful. It is also narrower than many buyers assume. The proposal is written before the relationship starts, by the side trying to close the relationship. Even an honest one presents the cleanest version of the future. The timeline has no delayed approvals. The channel plan has no broken tracking. The named senior people are all available. Every dependency fits neatly inside a page labelled "scope." The marketing plan has a different job. It changes as the team finds bad data, a weak offer, a landing-page leak or a sales handoff nobody owns. A competent operator expects the order of work to move when the evidence changes. A sales document that pretends to know every action six months ahead is either vague enough to survive anything or precise enough to become wrong. The mistake is not receiving a proposal. The mistake is treating persuasive detail as proof of how the work will operate. ##### Why proposal polish proves so little after signing Page six introduces the senior strategist. Their biography is excellent. On Monday, a new account coordinator opens the thread, asks for the goals you explained on the sales call and sends a blank onboarding questionnaire. Nothing in the proposal had to be false for this to happen. The senior strategist may still join quarterly. The agency may still intend to follow the scope. But the operating model has already changed the buyer's experience: context has been handed off, the person who sold the judgement is no longer close to the work, and the founder is briefing the account again. Proposal polish cannot reveal that handoff. Neither can the number of case studies, the quality of the mock-ups or the elegance of the timeline. Those things show that the seller can produce a persuasive document. They do not show how the organisation behaves when tracking breaks on Thursday, the homepage claim needs legal review, or the best next move is outside the original sequence. The proposal is a promise about the work. The operating model is the machinery that keeps it true. Inspect the machinery. Ask who makes the weekly priority call. Ask whether that person will still be in the thread after the first invoice. Ask where a changed decision is recorded and how you will see the actual page, ad, article or automation that moved because of it. If the answer is another reporting deck, you are still inspecting promises. ##### What should be public before the first call? In a 2025 B2B buyer survey, [74% of respondents wanted clear and detailed pricing upfront](https://9230071.hs-sites.com/hubfs/PDF%20downloads/B2B%20Research%20Report_2025_Final_Linked.pdf). A named buyer in another 2025 study explained the reason in nine words: ["You want to be in control as a buyer"](https://www.chilipiper.com/post/2025-b2b-buyer-first-report). Control starts before a custom PDF arrives. A repeatable marketing offer should make its core shape inspectable on the public site: who it is for, what sits inside the service, where the boundaries are, how pricing works, who leads the work, whether there is a minimum term, what the buyer owns and how either side can end the relationship. The fit conversation can then deal with the buyer's situation instead of rationing basic commercial information. When every serious fact appears only inside a personalised proposal, comparison becomes hard on purpose. One agency calls a line item strategy. Another calls it account management. A third bundles both into a monthly fee. The buyer has three polished documents and no stable unit of comparison. Public information removes some of that theatre. It also forces the seller to make decisions before learning the buyer's budget. The price cannot stretch quietly. The cancellation rule cannot become friendlier only after an objection. The identity of the person doing the work cannot change between the website and the signature page without becoming visible. That is why SharpHaw publishes its [current Plans and operating terms](https://sharphaw.com/plans). The point is not that every business needs the same priority. It is that the core commercial model should not be reinvented around each prospect. ##### Which promises must survive the signature? The same 2025 buyer research found that [90% of respondents said post-purchase support or relationship management influenced their vendor choice](https://9230071.hs-sites.com/hubfs/PDF%20downloads/B2B%20Research%20Report_2025_Final_Linked.pdf). Buyers choose the proposed strategy and the working relationship around it. They are deciding what it will feel like to get a decision, see progress and recover when something goes wrong. Six promises deserve evidence before they carry any trust. 1. The named owner stays close to the work. You should know who makes the next priority decision, not merely who attends the pitch. 2. The first decision is already visible. "Onboarding" is not a decision. A real first step names the bottleneck, the evidence needed and what can ship when the evidence is good enough. 3. The work has a shared home. An actual queue beats a paragraph saying communication will be transparent. You should be able to see the priority, blocker, owner and latest change without booking a status call. 4. Evidence links to the thing that changed. A green arrow in a report is not enough. The work trail should point to the page, ad account change, published article, automation run or measurement fix behind it. 5. Ownership is written down. Domains, website code, content, ad accounts, analytics, creative source files and automation credentials need named owners before the relationship ends. 6. The exit works on an ordinary month. Notice, exports, access removal and unfinished work should not become a hostage negotiation after trust has already broken. Inside [SharpOS, a SharpHaw subscription makes the work visible](https://sharphaw.com/sharp-os): assets, reporting and client context share one operating surface. A workspace does not guarantee good judgement. It does make silence, handoffs and missing evidence harder to disguise. ##### When does a custom marketing proposal earn its pages? Formal proposals are not useless. In [Responsive's 2025 survey of 350 B2B buyers](https://www.responsive.io/blog/what-buyers-look-for-rfp), 81% said the RFP had the greatest influence on the final vendor decision. Forty-one per cent used RFPs when the purchase was high-risk or highly visible. An RFP is not the same document as a small agency proposal, but the exception tells us when extra pages earn their place. A bespoke proposal is appropriate when several stakeholders must compare different approaches, procurement needs a common evidence format, regulated work carries specific controls, or the work is genuinely custom. A multi-country launch with legal review, data migration, custom software and several internal teams cannot be reduced to a package card and a short call. The buyer needs assumptions, responsibilities, dependencies and acceptance criteria in writing. SharpHaw's Custom work is scoped on a call for the same reason. Custom AI agents, internal tools, larger ecommerce systems and multi-market work contain real variance. The proposal should explain that variance. It should not be used to hide the stable parts of the relationship, such as who owns the work, how decisions are made or what happens when the buyer leaves. The test is simple: does the document resolve complexity the buyer genuinely has, or manufacture complexity the seller can charge and negotiate around? ##### What should a productized subscription give you instead? A growth subscription should move from fit to evidence faster than a traditional one-off sale. The buyer still needs written terms. They do not need a miniature strategy engagement performed for free and dressed as certainty. I built SharpHaw around a simpler sequence. The [Plans page](https://sharphaw.com/plans) explains the tier structure and current commercial terms. A direct fit conversation deals with the actual bottleneck. The agreement records obligations, ownership and exit. Then the first priority moves into a visible SharpOS queue where the buyer can see what changed and why. That sequence gives up one thing: the emotional effect of a document that appears to have solved the business before anyone has opened the analytics, CRM, ad account or CMS. Good. That effect is flattering, but it is not evidence. The productized model also creates a harder standard for the provider. The offer must be clear enough to publish. The boundaries must survive comparison. The senior owner must remain close enough to change the queue when reality contradicts the sales-call hypothesis. And the buyer must be able to leave without losing the digital surface they paid to improve. Personalisation still belongs in the priorities. It does not need to infect the price, ownership model, communication standard or exit route. ##### Five questions to ask before you sign Use these questions on the proposal, the sales call and the contract. Each answer should point to an artefact you can inspect. 1. What can I verify without asking the salesperson? Look for the public offer, pricing model, boundaries, named operator, ownership policy and cancellation terms. 2. Who owns Monday morning? Get the name of the person making the first priority call and confirm how directly you will work with them after signing. 3. Where will I see work before the report? Ask for the queue or workspace that connects a decision to the live page, account change, published asset or automation run. 4. What do I own if I leave? Check the domain, code, content, accounts, analytics, source files, credentials and exports. "We'll sort that out" is not an ownership policy. 5. How does an ordinary exit work? Read the minimum term, notice period, access handoff and final work rules before urgency makes them feel standard enough. If the seller answers with another promise, keep asking. If the answer is a public page, a written clause, a named person or a live work surface, you are finally looking at evidence. A custom marketing proposal can still help you understand an approach. It should not carry trust that the operating model has not earned. The safer buying decision is less flattering and more useful: inspect what is public, what survives the signature and what you can take with you when the relationship ends. SharpHaw is a senior-led growth subscription built around public Plans, direct ownership and visible weekly work in SharpOS. Digital work that compounds. [Read the current Plans](https://sharphaw.com/plans), then [send the one fit question the page does not answer](https://sharphaw.com/contact). You should not need a custom deck to find out whether the model fits. --- ### AI vendor due diligence: 7 checks before customer data moves [Read on sharphaw.com](https://sharphaw.com/blog/ai-vendor-due-diligence-checklist) · Founder · published 2026-08-22T09:00:00Z > Run AI vendor due diligence before customer data moves. Use seven evidence checks to approve, restrict, pause or reject an AI tool. The AI demo took 18 minutes. The vendor now wants permission to import your customer records. The assistant will read the CRM, draft replies and update deal stages. It looks useful. The salesperson points to a security badge, says the platform is GDPR compliant and opens the connection screen. This is where procurement actually starts. **AI vendor due diligence is the evidence check you complete before a tool receives customer data, system credentials or authority to act.** For an owner-operated business, it does not need a committee or a 90-page questionnaire. It needs a risk tier, seven checks and a written decision: approve, restrict, pause or reject. The import button is a trust decision wearing the clothes of a product setting. ##### Why the usual vendor check is too shallow A normal software review asks whether the supplier is financially credible, secure and contractually accountable. AI adds questions that a generic security page may not answer: - Can prompts, files or outputs be used to train or evaluate a model? - Does the tool create embeddings, traces or support copies that live somewhere else? - Can the model or its behaviour change without notice? - Can it only suggest an action, or can it send, edit, delete or pay? - What happens when the output is confidently wrong? In one current procurement discussion, the inherited process was described as **“fill out security questionnaire, get SOC 2, done.”** The people in the thread were already finding the gap: controls at company level do not prove that a particular model is suitable, stable or correctly bounded for your use. ([Reddit](https://www.reddit.com/r/procurement/comments/1r3kbj9/how_do_you_actually_assess_ai_vendor_risk/)) A certification can be useful evidence. Check its scope three ways: does it cover the vendor organisation, the exact service you will use and the configuration you intend to run? A badge alone cannot answer all three. The urgency is real, but the numbers need context. Cisco's 2026 privacy benchmark surveyed 5,200 privacy-responsible technology and security professionals across 12 markets. Ninety per cent said AI had driven an expansion of their privacy programme, while only 12% described their AI governance body as mature. This is vendor-sponsored global research, not a measure of European small businesses, but the direction is worth noticing: spending can move faster than operating discipline. ([Cisco](https://investor.cisco.com/files/doc_news/AI-Fuels-Surge-in-Data-Privacy-Investments-and-Redefines-Governance-Cisco-Reports-2026.pdf)) ##### Tier the use before you review the vendor Do not send every supplier the same questionnaire. First decide what the tool will touch and what a mistake could do. | Tier | Example | Starting position | |---|---|---| | 1. Public | Drafting from public website copy with no account connection | Light review; no customer data | | 2. Internal | Summarising non-sensitive notes or searching approved internal guidance | Standard review; named owner and access limits | | 3. Customer data | Reading CRM records, support tickets, calls or contracts | Enhanced privacy, security and contract evidence before a live test | | 4. Consequential action | Hiring, credit, health, payment, legal or autonomous changes in customer systems | Specialist legal and security review; strong human control; possibly reject | The EU AI Act also takes a use-based, risk-based approach. As of August 2026, it is generally applicable and certain transparency duties apply, while many obligations for high-risk systems have later application dates in 2027 or 2028. Employment, credit and access to essential services are among the use cases that can fall into the high-risk category. Classify the intended use before assuming the vendor's general statement covers it. ([European Commission](https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai)) This is an operational checklist, not legal advice. Personal data, employee records, health, credit or other high-impact uses deserve advice from a privacy, security or legal specialist who understands the jurisdiction and facts. ##### The seven AI vendor due diligence checks Each check has three parts: the question, acceptable evidence and a red flag. A confident answer is not the same thing as proof. ###### 1. Map every place the data goes Start with your data, not the vendor's architecture diagram. List the fields and files the tool receives. Then trace prompts, outputs, logs, embeddings, evaluation traces, backups, support exports and connected-system data. Note who can see each copy and where it is stored or processed. The UK National Cyber Security Centre recommends recording supplier information flows, subcontractors, assessment dates and assurance evidence so supply-chain risk can be understood and revisited. It also recommends contract terms for incident notification, audit rights, necessary data transfer, segregation and supplier access. ([NCSC](https://www.ncsc.gov.uk/sites/default/files/pdfs/publication/mapping-your-supply-chain.pdf)) **Acceptable evidence:** a product-specific data-flow diagram or written schedule that includes every storage and processing layer you will use. **Red flag:** “Your data stays in Europe” with no distinction between storage, model processing, support access and backups. If the path cannot be mapped, test with synthetic data. Do not solve uncertainty by uploading real records to see what happens. ###### 2. Separate storage, training and purpose Ask three different questions: 1. Is our data stored, and for how long? 2. Is any input, output or trace used to train, fine-tune, evaluate or improve a model or product? 3. For which purposes may the vendor or its model provider process it? A “no training” setting may not cover human review, abuse monitoring, evaluation or a third-party model provider. It may also differ between consumer and business accounts. **Acceptable evidence:** product terms, a data-processing schedule and administrator settings that agree on training, evaluation and secondary use. **Red flag:** the salesperson says no, the privacy policy says “improve our services” and the contract never resolves the difference. Under GDPR Article 28, a controller should use **“only processors providing sufficient guarantees”** and put the processing duties into a binding contract. That does not make a generic “GDPR compliant” statement a substitute for understanding your own purpose, data and configuration. ([EUR-Lex](https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1510829288571&uri=CELEX%3A32016R0679)) ###### 3. Prove retention and deletion “We delete your data” is incomplete. Ask when, from which systems and what happens to logs, backups, embeddings and support copies. Set a retention period that fits the use. Confirm whether an administrator can delete an individual record, an account or the full workspace. At contract end, decide whether data is returned, deleted or retained under a stated legal requirement. **Acceptable evidence:** a retention schedule, deletion procedure, administrator controls and a contractual deletion or return commitment. **Red flag:** deletion applies to the visible chat history but not to derived data, logs or connected stores. The UK ICO's current AI audit framework calls for detailed processor contracts and clauses requiring personal information to be deleted or returned at the end of the contract unless the law requires storage. The page is UK guidance and is marked as under review, but its evidence discipline is practical beyond a checkbox. ([ICO](https://ico.org.uk/for-organisations/advice-and-services/audits/data-protection-audit-framework/toolkits/artificial-intelligence/contracts-and-third-parties/)) ###### 4. Expose subprocessors, locations and transfers The vendor on the invoice may not be the only company touching the data. Model providers, cloud hosts, observability tools, transcription services and support platforms can sit underneath it. Request the current subprocessor list. Ask what each one does, where it processes data, how changes are announced and whether you can object. If personal data leaves the EEA or another protected jurisdiction, ask which transfer mechanism applies and have the answer reviewed where necessary. **Acceptable evidence:** a dated subprocessor register linked to the service, change-notification terms and a clear transfer schedule. **Red flag:** the vendor names its cloud host but will not identify the model or logging providers behind the feature. ###### 5. Test access, security and incident controls Encryption is a starting point. The practical questions are who can get in, what they can do and whether you can reconstruct an incident. Check multi-factor authentication, role-based permissions, tenant separation, support access, API-key handling and audit logs. For an AI agent, list every tool it can call. Mark calls as read-only or changing data. Ask for a replay of one allowed action, one blocked action and one action that required human approval. OWASP identifies sensitive-information disclosure as a material LLM application risk and recommends sanitisation, least-privilege access, restricted data sources and transparent retention, use and deletion policies. It also warns that prompt-only restrictions can be bypassed. ([OWASP](https://genai.owasp.org/llmrisk/llm022025-sensitive-information-disclosure/)) **Acceptable evidence:** access-control documentation, audit-log samples, recent relevant testing, incident contacts and a notification commitment. **Red flag:** the agent can send emails, change records or trigger payments using a broad shared credential, with no approval trail or kill switch. ###### 6. Make the contract match the product The DPA, order form, security schedule and product settings should describe the same service. Record the processing purpose, data categories, instructions, confidentiality, security measures, subprocessor rules, assistance with individual rights, incident duties, audit evidence, retention and end-of-contract handling. Add notification or review rights for material changes to models, terms or data handling where the risk justifies it. **Acceptable evidence:** signed terms that name the service and resolve gaps found in the review. **Red flag:** an enterprise security page makes a promise that the order form excludes or the administrator cannot configure. A DPA allocates obligations. It does not prove the product behaves as described. Test important controls before approval and keep screenshots or exports with the decision record. ###### 7. Bound the use, the human decision and the exit Vendor due diligence cannot make a poor use case safe. Decide what the tool is allowed to do, who checks its output and which event stops it. For customer-facing or consequential work, define the acceptable error, the human review point and the record you keep. Decide what happens when the model changes, quality falls, an integration fails or the vendor changes a subprocessor. Then test the exit: export the data, revoke credentials, delete the workspace and run the process manually if needed. **Acceptable evidence:** a named business owner, an approved-use statement, permission limits, review samples, stop conditions and an exit test. **Red flag:** “human in the loop” means somebody could notice a bad action after it has already reached the customer. ##### Turn the review into a one-page decision Do not end with a folder of documents and no answer. Record: - the tool, use case and owner; - the data and system access requested; - the risk tier; - evidence received for each of the seven checks; - unresolved gaps and compensating restrictions; - the decision: approve, approve with restrictions, pause for evidence or reject; - the next review date and events that reopen the decision. Restricted approval is useful. A tool may be acceptable for public-copy drafting but not CRM access. It may work with redacted tickets but not full call recordings. It may suggest replies but not send them. That is not indecision. It is giving the useful part permission without giving the unknown part customer data. A shared operating record in [SharpOS](/sharp-os) can keep the evidence, access decision, owner and next review together. The point is not more administration. It is being able to answer one calm question later: why did we trust this tool with this data? ##### Five reasons to stop before connecting Pause the purchase or pilot when: 1. the vendor cannot map where your data goes; 2. training, evaluation or secondary use remains ambiguous; 3. deletion excludes important stores or cannot be tested; 4. tool permissions exceed the approved job; or 5. the contract and product settings contradict each other. No supplier will remove every risk. The decision is whether the remaining risk is visible, owned and proportionate to the value of the use. Small companies do not need enterprise theatre. They need to connect fewer things by accident. Before adding another AI tool to your [business systems](/services), decide what it may see, what it may change and what proof earns that access. If the workflow cannot be explained on one page, it is not ready for production data. If you want AI automation that removes work while keeping the data path, permissions and human decisions visible, [talk to SharpHaw](/contact). We can help you design the operating loop before the import button becomes somebody else's problem. --- ### When to stop a marketing campaign: decide before launch [Read on sharphaw.com](https://sharphaw.com/blog/when-to-stop-a-marketing-campaign) · Founder · published 2026-08-21T09:00:00Z > Learn when to stop a marketing campaign using an evidence floor, exposure ceiling and decision date set before the first euro or founder hour is spent. You are looking at a campaign that has spent enough to be annoying, but not enough to make the answer obvious. One more week might rescue it. One more week might also buy you a slightly more expensive version of the same bad news. This is where founders usually ask: *How long should a marketing campaign run before I stop it?* The useful answer is not three days, three weeks or three months. The useful answer should have been written before the campaign began. Every marketing bet needs two boundaries: a minimum amount of evidence before you judge it, and a maximum amount of exposure before it must earn another round. Without both, “give it more time” becomes a recurring invoice. ##### The decision gets worse after you spend Before launch, you can be reasonably calm. You have a hypothesis, a budget and several other things competing for attention. After launch, the bet becomes personal. Someone argued for the channel. Someone wrote the copy. You have already spent money, held meetings and checked the dashboard far too often. Stopping now feels like admitting the work was wasted. So the standard quietly moves. The original goal was qualified enquiries. Then the campaign produced clicks, so clicks became encouraging. Then it produced a few weak leads, so the conversation moved to “learning”. Nothing has technically failed because nothing was defined well enough to fail. Founder time makes this worse. In a recent discussion about moving from organic to paid marketing, one founder put it neatly: “[My hours are the budget, and they’re maxed](https://www.reddit.com/r/founder/comments/1uvgcw2/at_what_point_do_you_stop_milking_free_marketing/).” Free distribution is not free when the owner is the production system. The answer is not to become ruthless with every weak number. It is to remove as much improvisation as possible from the decision. ##### A stop condition is a decision contract A stop condition is not “pause if ROAS is below two”. That may be one threshold inside it, but a useful condition says more: - what you believe; - what business result would support that belief; - which early signal is worth watching; - how much evidence you need before judging it; - the most money and time you will expose; - when the decision will be made; - who can make it. Write those points before the first euro or founder hour is spent. That is the contract. It protects the budget, but it also protects a decent bet from a nervous Tuesday afternoon. ##### Set an evidence floor and an exposure ceiling These are different controls. You need both. The **evidence floor** is the earliest point at which the result is credible enough to influence a decision. It could be a number of qualified conversations, a full buying cycle, a defined volume of searches, or enough traffic to observe a meaningful conversion pattern. The **exposure ceiling** is the most you will risk before the bet must justify more. Count cash, founder hours, team capacity, opportunity cost and any reputational risk. If you only set the ceiling, you can kill a good idea on noise. If you only set the floor, an inconclusive bet can keep feeding indefinitely. Advertising platforms make this distinction in their own way. Google Ads sets initial durations of **2–12 weeks** for several experiment types and advises advertisers to keep the rules stable between the test groups. Its reporting also explains that a result may remain unclear because the test lacked time, traffic or a large enough split—not because the idea was proved bad. ([Google Ads experiment guidance](https://support.google.com/google-ads/answer/6318731?hl=en-GB), [reporting guidance](https://support.google.com/google-ads/answer/6318747?hl=en-GB)) Optimizely uses product-specific minimums too. For binary metrics, it requires at least **100 visitors or sessions and 25 conversions in both the variation and baseline** before it declares a winner. Those numbers are not targets for your business. They are evidence that even tools built for testing refuse to call a result before their own floor is met. ([Optimizely statistical significance guidance](https://support.optimizely.com/hc/en-us/articles/4410284003341-Statistical-significance)) Your evidence floor will depend on the bet. A local service business testing a new offer has a different data problem from a high-volume shop testing a checkout button. False precision is still false. ##### Write these seven fields before launch Keep the document short enough that people will actually use it. ###### 1. The belief Write one sentence that can be wrong. > We believe owners of multi-location clinics will respond to a fixed-scope website assessment because they suspect their current site is losing enquiries. “We should try LinkedIn” is not a belief. It is an activity looking for a reason. ###### 2. The business outcome Name the result that would matter outside marketing. Qualified enquiries, booked assessments, accepted proposals, repeat purchases or recovered staff time all count. Impressions do not become revenue because the chart is colourful. ###### 3. The early signal Some outcomes take too long to observe directly. Choose an earlier signal with a credible connection to the outcome: visits from the right search terms, replies from the target buyer, completed diagnostic forms or sales conversations that mention the tested problem. An early signal earns more observation. It does not get promoted to revenue. ###### 4. The evidence floor Define what must happen before the team is allowed to judge the bet. Use the buying cycle and available volume, not a borrowed internet rule. For low-volume work, this may be a set of ten well-targeted conversations and the objections heard in them. For a paid campaign, it may be enough spend to give the target acquisition cost a fair test, across a full conversion delay. For content, it may be a consistent publishing window plus evidence of the right readers arriving. ###### 5. The exposure ceiling State the maximum in plain units: - cash; - founder hours; - team hours; - calendar time; - customer or brand risk. One consultancy recommends reserving **5–10% of the marketing budget** for controlled experimentation, with a hypothesis, owner, cap, metric, timeline and stop-loss rule. Treat that percentage as a reference point, not a commandment. The useful part is separating experimental money from the core engine and capping it before launch. ([Pedowitz Group](https://www.pedowitzgroup.com/how-much-should-i-reserve-for-experimentation)) ###### 6. The decision date Put the review in the calendar now. “We monitor continuously” usually means everybody watches and nobody decides. The date can include an exception: review earlier if the exposure ceiling is hit, tracking breaks, or the activity creates a material customer risk. ###### 7. The owner and possible next states One person owns the call. Their options are: 1. **Scale** because the result cleared the success condition. 2. **Continue** because the evidence floor has not been met and the ceiling has room. 3. **Change one variable** because the diagnosis points to a specific weakness. 4. **Pause** because the environment or measurement is unreliable. 5. **Stop** because the hypothesis lost or the likely upside no longer justifies the exposure. “Keep tweaking” is not a sixth state. ##### Three bets, three different stop conditions The framework stays stable. The numbers should not. | Marketing bet | Evidence floor | Exposure ceiling | Decision signal | |---|---|---|---| | Test Google Search for an urgent local service | A full conversion-delay window and enough relevant clicks to inspect search intent and conversion behaviour | Fixed media spend plus the landing-page work already approved | Qualified enquiry cost and evidence that the queries match the service | | Publish founder-led LinkedIn posts around one buyer problem | A consistent run across several weeks, with every post aimed at the same buyer and problem | A fixed number of founder and editing hours | Replies, profile visits and conversations from recognisable target buyers—not total reactions | | Change the main promise on a service page | Enough qualified traffic to compare behaviour without changing acquisition at the same time | One copy and implementation cycle | Movement in qualified form completions, backed by sales-call language | Notice what is missing: a universal number of days. A direct-response ad can produce an early commercial signal. A positioning change may need repeated exposure and sales conversations. A search-led article can take time to be discovered. Treating them as the same test makes the spreadsheet tidy and the decision useless. ##### Do not confuse a losing hypothesis with a broken test A clean test can show that the idea was wrong. That is a useful result. A broken test tells you very little. Tracking failed. The offer changed halfway through. Sales did not follow up. Three variables moved at once. The target audience never saw enough of the work. Calling that a failed channel is convenient, but inaccurate. At the review, ask two questions in this order: 1. **Was the test credible?** Check execution, tracking, audience, timing and whether the agreed evidence floor was met. 2. **Did the belief hold?** Compare the result with the success and stop conditions written before launch. If the first answer is no, fix the test only when the remaining upside justifies another capped round. Poor setup does not create an automatic right to more budget. ##### The 15-minute pre-launch ritual Before the next marketing activity begins, open a blank page and complete this: > **We believe:** > **The business outcome is:** > **The earliest useful signal is:** > **We will not judge it before:** > **We will not expose more than:** > **We decide on:** > **The decision owner is:** > **If it stops, the learning we keep is:** If the team cannot complete the page, it is not ready to spend. It may be ready to research, interview customers or fix measurement. That is different work. Store the brief next to the work and its results. A system such as [SharpOS](/sharp-os) makes the useful part visible: the original decision, the work in progress and the evidence used at review. The point is not another dashboard. It is stopping the rationale from being rewritten after the result arrives. ##### Marketing patience should be chosen, not improvised Good marketing often needs time. That is not an argument for open-ended activity. Choose the time. Name the signal. Cap the exposure. Then let the bet run without a founder changing direction every time the chart moves. The discipline cuts both ways: weak work loses the right to continue, and credible work gets the room it was promised. If your marketing still depends on late-night judgement and moving targets, [talk to SharpHaw](/contact). We build and run the website, [advertising](/services/ads-management), content and automations inside one visible operating rhythm—so the next decision is already clear before the spend begins. --- ### Growth debt: every marketing promise creates an operations bill [Read on sharphaw.com](https://sharphaw.com/blog/growth-debt-marketing-promises) · Founder · published 2026-08-20T13:00:00Z > Find the growth debt hiding in your marketing promises. Use a six-part promise ledger to protect capacity, margin and customer trust before buying more demand. A strong marketing promise can win the sale and weaken the business on the same day. The landing page says quotes arrive within 24 hours. Enquiries rise. The owner now spends every evening pricing work after being on site all day. Replies slip. Margins get guessed. The promise still converts, so nobody wants to touch it. That is growth debt. The phrase is often used for the data, measurement and capital-allocation systems that fall behind as a company scales. That is a useful definition. For an owner-operated business, there is an earlier version worth inspecting: **the gap between the promise that creates demand and the operation that must keep it.** Every promise creates work. If the work is not priced, owned and repeatable, the business pays interest through founder evenings, rushed handoffs, rework, thinner margins and disappointed customers. ##### What is growth debt in an owner-operated business? Think of growth debt as a deliberate or accidental claim on future capacity. Marketing issues it when the business promises speed, access, personal attention, choice or an outcome. Operations repays it each time a customer expects that promise to be true. Exactius uses the term for the gap created when execution scales faster than the data and capital-allocation system supporting it. Its symptoms include contested attribution, rising acquisition costs and unclear investment decisions. This article uses a narrower operating lens: what happens when the promise itself scales faster than the business behind it. ([Exactius](https://exacti.us/blog/what-is-growth-debt)) Debt is not automatically bad. A business may accept a period of manual work to test a market, learn a new service or establish a valuable position. The problem begins when temporary effort becomes permanent architecture and the accounts still treat founder rescue as free. The invoice is paid in founder evenings long before it appears in the accounts. ##### How marketing creates an operations bill The bill is issued at the moment a reasonable buyer forms an expectation. It does not wait for a signed contract. “Reply within one business day” requires an intake path, a qualified owner, calendar cover and a fallback when that person is unavailable. “Everything handled for you” requires somebody to coordinate access, assets, decisions, approvals and exceptions without handing the management back to the client. “Built around your business” creates variation. Variation creates discovery, judgement, review and rework. If the price and schedule assume a standard job, the promise borrows from margin. “More leads” creates a downstream requirement to answer, qualify, quote, follow up, onboard and fulfil. A form submission is not the end of the system. It is where the expensive part starts. This is why a demand metric without a fulfilment counter-metric is incomplete. Enquiries up 40% can be good news. Enquiries up 40% while quote time doubles and accepted-job margin falls is a different result wearing the same green arrow. ##### What growth debt costs after the sale Customers experience the gap before the finance report names it. PwC’s 2025 Customer Experience Survey found that **52% of US consumers surveyed had stopped using or buying from a brand after a bad experience with its products or services**, while 29% cited poor online or in-person customer experience. In the same study, 70% of executives said customer expectations were changing faster than their organisations could adapt. The research covered 5,511 US consumers and 406 executives, so it is context rather than a European benchmark—but the commercial risk is not subtle. ([PwC](https://www.pwc.com/us/en/services/consulting/commercial-excellence/library/2025-customer-experience-survey.html)) For a service business, the interest usually appears in six places: - **Founder intervention:** the owner steps back into quoting, checking, fixing or calming the client. - **Rework:** rushed discovery and unclear handoffs create a second pass. - **Response drag:** the first reply is fast because marketing measures it; the useful answer is slow because nobody owns it. - **Margin erosion:** extra calls, exceptions and revisions do not appear in the original estimate. - **Team fatigue:** people absorb a promise they did not design and cannot change. - **Trust loss:** the buyer has to renegotiate expectations after buying. In a recent discussion about selling project-based work while operations was stretched, one salesperson described raising capacity risks as “[protecting the customer, margin and long-term relationship](https://www.reddit.com/r/sales/comments/1vd9j81/sales_being_told_to_keep_selling_while_operations/).” That is not sales getting in the way of growth. It is somebody noticing the interest rate. ##### Five promises that commonly create growth debt The words vary by industry. The operational patterns repeat. ###### 1. Speed without a queue Fast quotes, same-day replies and short turnaround times can be valuable. They also require a clear queue, priority rules and cover. If every urgent request goes straight to the founder, the promise is attached to a person rather than a system. ###### 2. Personal attention without a capacity limit “Work directly with the founder” converts because buyers want judgement and accountability. It stops working when founder access is sold more times than the week contains. The honest version may be founder-led, not founder-present in every task: the founder sets direction, reviews the important work and owns the decision, while a visible system carries the routine movement. ###### 3. Choice without a variation price Every extra option creates more diagnosis, explanation and approval. A broad menu feels generous on the website and behaves like unfinished product design after the sale. Narrowing the offer is not a failure of service. It can be the reason the valuable part happens reliably. ###### 4. Outcomes without controlled inputs Revenue, rankings, leads and time savings depend on inputs the provider may not control: market demand, sales follow-up, customer data, budget, approvals and competitive movement. Strong marketing can still name the intended commercial outcome. It should also state the work, the evidence and the customer responsibilities that make the outcome plausible. ###### 5. Simplicity outside, chaos inside The best service often feels simple to buy. That simplicity is expensive to produce. It needs a defined intake, one source of truth, named decisions and clean handoffs. If “one partner” means the client stops coordinating five vendors but the founder quietly coordinates five disconnected tools and freelancers, the debt has merely moved out of sight. ##### Build a promise ledger before buying more demand A promise ledger turns copy into an operating decision. It can be one page. | Customer-facing promise | Operational proof | Capacity assumption | Early failure signal | Owner | Recovery path | |---|---|---|---|---|---| | Quote within one business day | Qualified request enters one queue and receives a priced response | Estimator has two protected review blocks each day | Oldest qualified request exceeds four working hours | Commercial owner | Confirm receipt, state the review time, reroute overflow | | Weekly progress visible to the client | Work, decision and next step are updated in the shared workspace | Every active account has a fixed weekly review slot | Update depends on asking three people for status | Account owner | Publish what moved, name the blocker, reset the next decision | | Founder-led strategic direction | Founder reviews the brief and high-impact decisions | Review time is capped per active account | Routine approvals wait more than two working days | Founder | Delegate routine rules; reserve founder time for exceptions | The exact numbers belong to the business. The columns do not. For each promise, ask: 1. What must happen operationally for this to be true? 2. Which capacity assumption is hidden inside it? 3. What is the earliest sign that repayment is slipping? 4. Who can change the queue, scope or expectation? 5. What does the customer hear when the business misses? If those questions cannot be answered, more traffic is premature. The website may be ready. The business is not. ##### Measure demand and fulfilment in the same weekly view Marketing reports tend to stop at the handoff. Operations reports start after it. The customer experiences one company. Put one demand measure next to one fulfilment measure for each important promise: - qualified enquiries **and** time to useful reply; - accepted proposals **and** promised start dates met; - jobs won **and** contribution margin after rework; - onboarding started **and** time until the customer knows what happens next; - content or ads shipped **and** sales capacity to handle the response; - customer volume **and** founder hours required per active account. This is not a request for a larger dashboard. Five paired measures that cause a weekly decision beat fifty numbers that explain last month. A shared workspace such as [SharpOS](/sharp-os) can keep the promise, current work, blocker and next decision together. The useful feature is not visibility for its own sake. It is making hidden interest difficult to hide. ##### How do you repay growth debt? Hiring is one option. It is rarely the only one, and it is often the most expensive place to start. ###### Change the promise Replace a broad or absolute claim with a narrower one the business can defend. “Instant quote” may become “reply within one business day with the next step”. The second promise can be stronger because the buyer knows what will happen. ###### Narrow the customer or job The same team can handle more work when the work has less variation. Tighten the geography, project type, minimum scope or problem the offer accepts. ###### Remove a handoff Many capacity failures are coordination failures. Give one person authority over intake through the first useful outcome, with a clear rule for exceptions. ###### Standardise before automating Automate stable, repetitive movement: acknowledgements, reminders, routing, status updates and record creation. Do not automate a process the team still argues about. That produces faster confusion. ###### Price the capacity honestly If the valuable work requires senior judgement, include that time in the offer. Underpricing does not make capacity disappear. It only prevents the business from funding it. ###### Pace demand Reduce spend, narrow targeting, add qualification or create a waiting list when fulfilment is at risk. This is not surrender. It is protecting the next customer from a promise the current system cannot keep. ##### Planned growth debt can be rational The answer is not timid marketing. A promise should still be specific enough to matter. There are times to carry debt: launching a new offer, entering a market, learning where human judgement matters or filling capacity that is already funded. The rule is to write the repayment plan at the same time as the promise. Set the period. Cap the founder intervention. Name the process that will replace it. Track whether margin and customer experience recover as volume rises. Founder heroics are useful as research. They are dangerous as a business model. ##### Make the promise smaller than the system behind it The strongest businesses do not make the biggest claims. They make claims their operation can prove again on a bad week. Before the next [marketing push](/services), audit the promise that will receive the demand. Check the queue, capacity, handoff, margin and recovery path. Then decide whether to increase capacity, narrow the offer or change the words. If every new customer still pulls the founder back into the work, [talk to SharpHaw](/contact). We build the website, content, advertising and automations around one visible weekly operating loop—so the promise that wins the enquiry is the one the business is set up to keep. --- ### Why I cap my client list instead of scaling like an agency [Read on sharphaw.com](https://sharphaw.com/blog/why-i-cap-clients-instead-of-scaling-an-agency) · Founder · published 2026-08-20T09:00:00Z > The senior who pitched you rarely does your work; that's the agency leverage pyramid. Why I cap my client list instead of scaling, and how to test 'senior-led'. Three months into the contract, you're staring at work that doesn't look like the pitch. The senior strategist who won you over is nowhere in the thread. Someone junior you've never spoken to now runs your account, asking you to re-share context you explained in the sales meeting. Your last agency wasn't being sloppy. It was doing exactly what its business model is built to do. I watched that pattern for years from [inside large software teams](https://sharphaw.com/about), and I built SharpHaw to break it. The reason is unglamorous: to keep a senior on your account every week, I cap how many clients I take. I don't scale a marketing agency the way you're supposed to. That constraint is the product, not a limitation I'm apologising for. **TL;DR:** Agencies grow by stacking low-cost juniors under a few senior partners — the leverage pyramid that has run professional services for decades. It means the senior who sells the work rarely does it. A senior-led subscription can't grow that way without breaking its one promise, so capping the client list is what keeps the person you hired on your account. ##### The pyramid is the whole business, not a side effect Open almost any agency's org chart and you find a triangle: a few partners at the top, a wide base of juniors and analysts underneath. David Maister named the economics in *Managing the Professional Service Firm* back in 1993, and they haven't moved since. "Leverage" is the ratio of junior to senior staff on the work. The more juniors you stack under each senior, the lower your effective hourly cost and the higher the partners' margin. That structure underpinned growth across law, consulting, and accounting firms for four decades. Read it again, because it explains your last four agencies. A firm wins your business by putting its most impressive, most expensive people in the room. It makes its margin by handing the actual work to its least expensive people. The distance between those two facts isn't a scandal. It's the operating model. Seniority is the sales tool. Junior labour is the product. So when the strategist disappears after you sign, nothing has malfunctioned. The pyramid is working. ##### "We're growing the team" is the moment you become a smaller account Vendor growth reads like a trust signal. They must be doing something right — look, they're hiring, they won an award. Flip it. Every senior in a pyramid firm gets spread across more accounts as the firm grows, so each account gets a thinner slice of the person who sold it. Growth doesn't deepen your relationship with the senior. It dilutes it. Steve Boehler, who advises brands on choosing agencies, quoted the client reaction after one pitch: "We'll never see these people again." He describes a single large agency sending the same senior pitch team to three different prospects inside six months, then losing two of them once buyers did the maths. Those buyers weren't being cynical. They were being accurate. Client churn at agencies isn't really a marketing problem. It's what happens when the person who earned the trust is structurally pulled off the work, again and again, at scale. ##### Why I cap the number of clients I take I only take on the number of clients I can personally ship for, every week. That is the constraint, and it's chosen on purpose. There is no account manager sitting between you and me, because the day I add that layer to fit more clients in, you lose the precise thing you paid for: the engineer who builds it is the one you talk to next week. This is where a subscription can beat the pyramid, but only if it refuses to grow like one. The work stays visible in [one shared workspace](https://sharphaw.com/sharp-os), so you see what shipped without booking a call to ask. The cadence is weekly, so context compounds instead of resetting to zero every quarter. The person reading your analytics on Friday is the person who wrote the page on Monday. None of that survives a leverage model. All of it depends on me staying close enough to the work to do it, not just sell it. I turn away business to hold that line. Sometimes that means a wait for a slot. I would rather tell you that plainly than turn you into someone else's junior project. ##### What you give up when the founder is the cap Honesty first: this model has a ceiling, and the ceiling is me. You can't hand ten parallel workstreams to a one-person-led subscription and expect a team of twelve to absorb them by Thursday. A national launch across six markets, on a fixed deadline, needing deep specialist bench strength in each discipline — that is precisely the job a larger agency's pyramid is built for, and I'll say so rather than pretend otherwise. The trade is simple. You give up raw parallel capacity. You get a senior who actually knows your account, weekly, with no handoff and no re-briefing. For an owner-operated business burned by the last agency's disappearing act, that trade is usually the right one. For a company that genuinely needs a bench of twenty, it isn't — and working out which one you are is worth more than any pitch deck. ##### How to tell if "senior-led" is real or just the pitch line Every agency will now tell you it's senior-led. The phrase is free, so pressure-test it, and run the same test on me. Ask who does the weekly work, by name, and get it written into the contract. Ask what happens to your account the week they sign their next three clients. Ask to see where the work lives between meetings — a real trail you can open, not a monthly PDF. Ask what you keep and how fast you can leave if it stops working. I'll be straight about my own gap: SharpHaw doesn't have a wall of named client case studies yet, and I won't borrow proof I haven't earned. So don't take "senior-led" on faith from me either. Judge it by one question — is the person who pitched you still the person doing the work in month four? That question sorts the model from the marketing, mine included. ##### The version where growth can't cost you A pyramid firm's growth and your results sit on opposite ends of the same seesaw: the bigger it gets, the further the senior drifts from your account. A capped, senior-led subscription is the version where that can't happen, because growth by headcount was never the plan. The price is real capacity limits and the occasional wait. The return is a partner who stays close enough to ship every week, and who answers for the work because they did it. If you've been on the wrong end of the pitch-and-vanish before, book a 30-minute call, bring your worst-performing page, and leave with a fix-it list whether or not we work together. You can read the terms, including the fact that there's no annual lock-in, on the [plans page](https://sharphaw.com/plans). --- ### AI agents won't run your marketing. Here's what they can run. [Read on sharphaw.com](https://sharphaw.com/blog/ai-agents-wont-run-your-marketing) · Automations · published 2026-08-19T08:00:00Z > Gartner expects over 40% of agentic AI projects cancelled by 2027. Here's the three-question test for what an AI agent can safely run in your marketing. No, an AI agent is not going to run your marketing while you sleep. The demo makes it look inevitable. The research says otherwise: [Gartner expects more than 40% of agentic AI projects to be cancelled by the end of 2027](https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-predicts-over-40-percent-of-agentic-ai-projects-will-be-canceled-by-end-of-2027), and [a July 2025 study from MIT's Project NANDA](https://mlq.ai/media/quarterly_decks/v0.1_State_of_AI_in_Business_2025_Report.pdf) found that 95% of enterprise generative-AI pilots produced no measurable return at all. Those are not fringe numbers. They describe the middle of the market. Here is the part that gets skipped. Those projects did not fail because the models were stupid. They failed because someone handed an agent a job it had no business doing alone. The interesting question is not whether AI agents work. It is which tasks you can safely let one run without watching — and that line is sharper, and further down the funnel, than the sales deck suggests. ##### What an "AI agent" actually is, once you strip the costume An automation follows a fixed recipe: when this happens, do that. It does the same steps every time, and you can read the steps. An agent is different in one specific way — it decides its own steps. You give it a goal, it plans a path, calls tools, reacts to what it finds, and keeps going until it thinks it is done. The autonomy is the feature. It is also the risk. That distinction matters because most of what gets sold to founders as an "agent" is not one. Gartner has a name for the gap: "agent washing" — taking a chatbot, a rules-based automation, or a support assistant, and re-labelling it agentic without any real autonomy underneath. Of the thousands of vendors claiming agentic products, [Gartner reckons only around 130 are the real thing](https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-predicts-over-40-percent-of-agentic-ai-projects-will-be-canceled-by-end-of-2027). So the first tension is not "should I trust an agent." It is "is this even an agent, or a dressed-up macro wearing a new word." Neither one is bad. A rules-based automation that never surprises you is often exactly what a small team needs. The problem starts when you pay agent prices, and take agent risks, for a task that a boring automation would have handled with none of the exposure. ##### Why 40% of these projects get quietly cancelled Gartner's Anushree Verma put the cause plainly: "Most agentic AI projects right now are early-stage experiments or proof of concepts that are mostly driven by hype and are often misapplied." Misapplied is the operative word. The cancellations are not a technology verdict. They are an aim verdict. The MIT finding points the same direction. Ninety-five percent of pilots returning nothing is not a story about weak models — the same report notes the models are fine, and the gap is organisational: the tool never learned the workflow, nobody owned the output, and the pilot stalled between "impressive demo" and "thing the business actually runs on." A generative model that dazzles one person can still fail a company, because a company needs the work to be repeatable, checkable, and owned. For an owner-operated business the maths is unforgiving. You do not have a data-science team to babysit a misbehaving agent. If it goes wrong, it goes wrong on your name, your inbox, your ad account. So the bar for letting one run unattended has to be higher for you than for a company that can absorb a bad quarter. ##### The three questions that decide if an agent can run alone Before you let any agent act without a human reading its work first, put the task through three questions. If the answer to all three is yes, it is a good candidate for autonomy. If any answer is no, keep a person in the loop. **Is the scope bounded?** Can you draw a hard line around what the agent is allowed to touch? "Draft replies to inbound enquiries in this one inbox" is bounded. "Manage our outreach" is not — it has no edge, so the agent invents its own, and its idea of the edge is not yours. **Is every action reversible?** If the agent gets it wrong, can you undo it before anyone notices? Tagging a lead is reversible. Sending 400 cold emails, changing live ad bids, or publishing to your site is not. Irreversible actions are where autonomy stops being efficiency and starts being a liability you cannot see until it lands. **Is the output measured?** Is there a number that tells you within days whether the agent is helping or quietly drifting? If you cannot measure it, you cannot manage it, and you will find out it went wrong the way most people do — from a customer. An agent that can act without you can also fail without you, quietly, at scale, in your name. The three questions are how you keep the speed and lose the landmine. ##### What that actually leaves an agent running Plenty, once you frame it right. Run the test and the safe zone becomes obvious: bounded, reversible, measured work where the agent does the volume and a human owns the outcome. Picture the difference. An "AI SDR" pointed at your pipeline, told to "book meetings," emails hundreds of prospects on its own and, three weeks later, a reply lands quoting a claim about your service that you never made and is not true. It did the work. It also manufactured a problem you only discover from the outside. Now the same model, bounded: it drafts every one of those emails into a review queue, you approve or bin them in a ten-minute pass, and nothing leaves without a human behind it. Same speed on the tedious part. None of the exposure. That is the shape of AI work that pays off — and it is the only shape we ship. At SharpHaw the rule is that AI is plumbing, not magic: a named job, a bounded scope, a number to judge it by, and a senior person who owns what goes out. The agent triages, drafts, enriches, and monitors; the human still decides. Unglamorous, and it holds. The point is not handing the business to an agent. It is taking the repetitive first draft off a founder's plate and keeping the judgement where it belongs. The fantasy the market is selling you is "set it and forget it." The version that survives contact with a real business is "set it, bound it, and check the number." One of those has a 40% cancellation rate attached. The other one just quietly gives you your Tuesday back. ##### FAQ **Are AI agents worth it for a small business in 2026?** For bounded, reversible, measurable tasks, yes — drafting, triage, data enrichment, monitoring. For anything that owns an outcome you cannot undo, such as live ad spend or outbound sending, keep a human in the loop. The tool is worth it; unattended autonomy over risky tasks usually is not. **What is the difference between AI automation and an AI agent?** An automation follows a fixed set of steps you can read. An AI agent is given a goal and decides its own steps, calling tools as it goes. The agent's autonomy is more flexible and more useful — and riskier, because you cannot always predict what it will do next. **Why do most AI agent projects fail?** Not because the models are weak. Gartner and MIT both trace it to misapplication: agents deployed without a bounded scope, without governance, and without a number to judge them by. The failure is in the task chosen and the ownership, not the intelligence. ##### Before you buy the demo If a vendor is selling you an agent that "runs your marketing," ask which specific task it runs unattended, whether that task is reversible, and what number proves it is working. A real answer is a good sign. A tour of the dashboard instead of an answer is the tell. If you want a second read on where AI genuinely fits in your stack — and, just as usefully, where it does not — that is a fit check we are happy to run. Bring the workflow you are tempted to automate. Leave knowing whether an agent should touch it at all. --- ### Content operations after 131 posts: the queue beats the calendar [Read on sharphaw.com](https://sharphaw.com/blog/content-operations-131-posts-queue-beats-calendar) · Content Engine · published 2026-08-18T13:00:00Z > Content operations fail when the calendar becomes the system. See the seven queue fields SharpHaw used across 131 published posts to stop repeat work. "Volume is easy now. Sameness is the new problem." That line came from a [content marketer trying to sustain eight posts a month](https://www.reddit.com/r/content_marketing/comments/1vo1rx3/publishing_8_posts_a_month_how_do_you_stop_them/). After 131 published SharpHaw posts, it names the content operations problem better than another calendar template ever could. At the start of this run, the live Blog board held 131 Published cards, two in Review and two Rejected. The dates helped pace the work. They did not reject a repeated promise, challenge a weak source or decide who should act after reading. The queue did that. **TL;DR:** Content operations is the system that decides what earns a place in the queue, which proof it needs, who owns the next move and what happens after publication. An editorial calendar can show when work is due. It cannot make those decisions, prevent near-duplicates or maintain the archive. ##### What content operations means after the calendar is full For an owner-operated business, content operations is one repeatable work trail from reader problem to maintained page. It should survive even if every publication date disappears. That distinction sounds fussy until the calendar fills up. A blank square creates pressure to publish something. A queue record asks a harder set of questions: Who is this for? What job will it do? Which existing page comes closest? What proof can survive review? Who owns the next decision? Where does the reader go if the post helps? Take the board review behind this article. There was room for another post. There were also several plausible ideas about AI automation, marketing handovers and email delivery. Each could have produced a tidy headline. Each collided with work already in the archive, so the ideas were rejected or narrowed before research began. The calendar would have accepted all three. It had open dates. This is why content operations is larger than scheduling and smaller than an enterprise department. The useful system does not need an operations manager, a wall of swimlanes or another subscription. It needs one place where the decisions travel with the work from brief to review to publication and, eventually, update or retirement. ##### Why faster content production raises the bar for the queue The [2026 B2B Content and Marketing Trends report](https://contentmarketinginstitute.com/b2b-research/b2b-content-marketing-trends-research) makes the speed-versus-value gap hard to ignore. CMI and MarketingProfs surveyed 1,015 B2B marketers. Among those using AI for content creation, 87% reported better productivity and 80% reported better operational efficiency. Only 39% reported better content performance. AI helps teams type faster. It does not choose the reader tension, notice that last month's post already made the same promise, or refuse a statistic whose original source cannot be found. Production gets cheaper while judgement becomes more valuable. The same research found that 61% of marketers said their content strategy had improved. Among that group, 74% credited strategy refinement, while 51% credited new technology. Robert Rose's summary is sharper: "Strategy beats scale." That is not an argument against AI. SharpHaw uses it inside the work. It is an argument for putting the difficult decisions before the draft, where speed cannot bury them. If the brief contains a generic audience, an unsupported premise and no commercial next step, faster writing produces the wrong page sooner. The private fear is usually "I've tried to write blog posts and gave up." More tools feel like the answer because the visible struggle is drafting. At 131 posts, drafting is rarely the binding constraint. Admission is. The operation has to say no before the model turns one repeated idea into 1,800 polished words. ##### What every content queue card must prove A publishable card needs seven fields. The names can change. The decisions cannot. 1. **Reader tension.** Use the sentence the reader would say, not an audience label. "Founder" is a segment. "I've tried to write blog posts and gave up" is a problem a post can solve. 2. **Reason and intent.** State why the page should exist now and whether it must diagnose, compare, teach or help someone decide. A target keyword alone does not supply a job. 3. **Closest existing work.** Name the nearest cards and explain why the new promise produces a different outline, reader or next step. A new adjective does not make a new post. 4. **Proof.** List the first-party fact, primary research, approved quote or documented method the draft may use. If the load-bearing claim has no source, the card is not ready for drafting. 5. **Owner and status.** One person owns the next move. Backlog, Review and Published should describe actual states, not become decorative labels every card carries forever. 6. **Commercial path.** Decide what the reader should understand or inspect next. The CTA must follow the article's job rather than arrive as a sales paragraph pasted onto the end. 7. **Maintenance cue.** Record what would make the page stale: a policy change, product update, new dataset, expired example or competing page in the archive. Those fields turn a coloured rectangle into an operating record. They also make review faster. An editor can test the premise without rereading a planning document, a writer can see the proof boundary, and a future owner can understand why the page exists before changing it. If your calendar tool stores all seven, good. The software is not the argument. The queue underneath that date view is doing the operational work. Inside [SharpOS](https://sharphaw.com/sharp-os), the board is visible with the work around it. That matters because accountability hidden in a private spreadsheet is still hidden from the person paying for the work. ##### How the queue stops the 132nd idea becoming a repeat On a Monday board pass, a new title can look excellent and still deserve rejection. The test is not whether the words are new. It is whether the reader, intent, promise and likely section structure are materially different from the closest card. Suppose the archive already contains a post about automations silently failing and another about the approvals required before an AI action runs. "Build an AI exception queue" sounds fresh. Its likely sections cover failure paths, human review, recovery and ownership. The title is new; most of the article is already there. A distinct angle would need to change the actual job. It might address finance teams reconciling failed invoice actions, or compare reversible and irreversible workflows for a decision-stage buyer. If the outline and CTA remain the same, changing the persona in the title is camouflage. This is where the archive begins to compound. Old posts stop being finished files and start acting as topic memory. They narrow the next brief, expose cannibalisation and force a sharper promise. The 132nd published idea only matters if the first 131 can tell it no. That sentence carries a tradeoff. Sometimes the date stays empty. Publishing one fewer post can look like a failure when cadence is the headline metric. It is usually cheaper than researching, drafting, designing and distributing a page that competes with work you already own. ##### Who owns content operations when there is no content team "Without defined accountability, operational work becomes fragmented," [Contentful writes in its 2026 guide](https://www.contentful.com/blog/what-is-content-operations/). The guide describes repeatable, transferable processes rather than work built around one campaign. That principle still holds when the "team" is a founder and one senior partner. One operator should own the queue. Subject experts contribute facts, objections and corrections. The operator decides whether the card moves, returns for proof or stops. A committee can provide context; it cannot share one next action. Picture a founder replying to a draft review at 22:40 with two notes: make it broader, then cut 400 words. A calendar reports that the article is late. An owner resolves the conflict against the recorded reader and intent, explains the cut, and moves the card once. The artefact preserves that decision for the next post. This is also where a [Content Engine](https://sharphaw.com/services/content-engine) differs from a folder full of generated drafts. The operation owns the research, proof boundaries, duplicate check, review state and maintenance trail. The words are one stage in that system. ##### How to measure content operations without worshipping output Post count proves that work shipped. It does not prove the work produced demand, enquiries or revenue. SharpHaw can verify the 131 published cards. It should not pretend that the count caused a commercial result without evidence connecting the two. Measure the operation closer to the decisions it controls: - **Safe work shipped:** cards that cleared proof, voice and duplicate checks before publication. - **Overlap stopped:** ideas rejected or re-angled before they consumed a draft. - **Review time:** how long a card waits for one named decision, not how long it sits coloured green. - **Maintenance closed:** pages updated, consolidated or retired when their trigger fires. - **Commercial path present:** every published page points to a useful next step that fits its reader and stage. - **Outcome evidence:** qualified enquiries, sales conversations, assisted journeys or other business evidence attributed carefully, without forcing a straight line from read to sale. The first five tell you whether the content operation works. The sixth tells you whether the content earns its commercial place. Keep them separate long enough to avoid crediting a workflow for revenue it did not create. This is evidence over assertion in practice. "I want results, not reports" does not mean ignoring the work trail. It means the trail must show decisions and connect to outcomes, rather than hiding behind activity volume. ##### Run this test before you add another date Open the next card in your editorial calendar and ignore its deadline for five minutes. - Can you quote the reader tension in their own words? - Does the card name its closest existing page and explain the difference? - Is every load-bearing claim tied to an approved or external source? - Can one person state the next decision without calling a meeting? - Does the CTA follow the reader's stage rather than the sales target? - Is there a condition that will trigger an update, consolidation or retirement? Three missing answers mean the date is doing more work than the brief. Six missing answers mean you have a schedule, not content operations. Digital work that compounds. The queue is where that promise becomes inspectable. Our content engine isn't a pitch deck. It's our blog. Read it before you buy it. The operation behind that public sample also includes rejected ideas, review states and source checks before a card reaches Published. If you want that system running without managing every handoff yourself, [bring your current content queue to a 30-minute fit call](https://sharphaw.com/contact). We will show you where the calendar ends and the operation needs to begin. The scope and month-to-month model are public on the [Plans page](https://sharphaw.com/plans). --- ### Google Ads location targeting: the map cannot prove the leak [Read on sharphaw.com](https://sharphaw.com/blog/google-ads-location-targeting-map-cannot-prove-leak) · Ads · published 2026-08-17T17:00:00Z > Google Ads location targeting can look wrong in analytics. Prove the paid click, user location and serviceable sale before you change the campaign setting. Put two tabs side by side. One shows a Google Ads campaign targeted to the Netherlands. The other shows website visits from the US, Italy and Romania. The owner wants real, local customers. The map gives them no idea why those visits appeared. The obvious verdict is that Google ignored the target. The obvious fix is to switch the campaign to Presence, exclude more countries and call the leak closed. That may be the right change. The map has not proved it. Google Ads location targeting is an inference built from several signals. Your analytics map contains traffic from several sources. Your service area may not match the buyer's location when they start searching. Treating those as one fact can remove wasted reach, or remove a buyer who plans to travel, relocate or purchase remotely. ##### TL;DR Before changing Google Ads location targeting, prove the visit came from a paid ad, compare Google's user location with its matched location, define where a qualified sale can be fulfilled, and check the lead in your CRM. Presence is useful for strict service areas. It is not a universal repair. ##### Why the wrong-country map is not enough A session replay or analytics map answers a useful question: where did this website visit appear to come from? It does not, by itself, answer whether Google Ads paid for that visit. A red dot in Microsoft Clarity can be an organic visitor, a referral, a bot or a click bought through another network. Clarity does not attach the Google Ads invoice to the replay. One recent r/PPC answer put it cleanly: [“clarity is not evidence here”](https://www.reddit.com/r/PPC/comments/1vi77l5/google_ads_targeting_north_carolina_but_microsoft/). If you change location targeting before isolating the paid source, you can spend an afternoon fixing the wrong system. Start with the traffic record. In a linked Google Analytics 4 property, check source, medium, campaign and source platform. Google Ads [auto-tagging](https://support.google.com/google-ads/answer/3095550?hl=en) normally adds a GCLID to the landing URL, which helps Google connect the click with the visit. Consent settings can limit the identifier available to you, so the absence of a visible GCLID is not conclusive. The point is to establish paid source from the available evidence, not to hunt for one magic field. Run a fresh test through the ad's final URL as well. Confirm that redirects, cookie tooling and the landing page preserve the query string. A broken redirect can strip tracking before analytics sees it, leaving a real paid click labelled as something else. The map is a clue. The paid click is the evidence. ##### What Google Ads location targeting actually matches Google's own accuracy warning is blunt: [“100% accuracy is not guaranteed in every situation”](https://support.google.com/google-ads/answer/1722038?hl=en). The system infers geography. It does not observe a clean digital border. Google currently gives most campaigns two positive location modes: - **Presence or Interest:** people in, regularly in, or who have shown interest in the targeted location. - **Presence:** people in or regularly in the targeted location. [Presence or Interest is the default](https://support.google.com/google-ads/answer/1722038?hl=en). A person outside the target can therefore be eligible because their search, recent behaviour or viewed content suggests an interest in that place. Google says it may infer location interest from search terms, previous searches, past physical locations, Maps activity and page context. Physical location is inferred from signals such as IP address, device data, GPS and Wi-Fi. This matters when reading reports. A location can be the user's physical location or the place they showed interest in. Google also warns that its geographic reporting may differ from third-party analytics because the systems use different IP data and update it at different times. Some older guides still describe Search Interest as a third positive option. Current [Google Ads API documentation](https://developers.google.com/google-ads/api/docs/targeting/location-targeting) marks it as deprecated and no longer settable for most campaign types. Build the audit around the two options the account can actually use. ##### When Presence is safer, and when it blocks real demand In a [2022 internal experiment](https://support.google.com/google-ads/answer/1722038?hl=en), Google found 5% more conversions among travel, real estate and education advertisers that moved from Presence to Presence or Interest. That is old, limited first-party evidence from three destination-oriented verticals, not a forecast for your account. It is enough to disprove the lazy rule that broader location interest is always waste. Presence is the defensible choice when the offer depends on the buyer being physically inside a hard service area. Think of a dentist in Porto that cannot treat someone in Bristol, or a same-day home service that only dispatches within a fixed radius. Interest in Porto does not make the lead serviceable. In that situation, broader reach gives the sales inbox work it cannot turn into a customer. The same rule fails for destination demand. A couple in Manchester may search for a wedding venue in Lisbon months before travelling. A buyer may research property before relocating. A student may compare courses before arriving. A B2B service may fulfil the work remotely even when the owner wants customers in a particular market. Write the commercial rule before touching the advertising rule: > From which locations can this person become a qualified customer, and must they be there now? If the answer is “inside our dispatch area today”, Presence fits. If the sale can begin before arrival, or be fulfilled remotely, location interest may be valuable. If different offers have different answers, separate them into campaigns with distinct geography rather than forcing one account-wide compromise. ##### The four-part geography audit The audit should end in one sheet that a founder can inspect. Four columns are enough. | Evidence | What to inspect | What it settles | | --- | --- | --- | | Paid source | GA4 source, medium, campaign and source platform; GCLID when available; final URL redirects | Whether the suspicious visit came from the campaign | | User location | A Google Ads custom report with `Country/Territory (user location)` | Where Google placed the person who received the ad | | Matched location | The account's geographic or matched-location view | Whether physical presence or location interest created eligibility | | Qualified outcome | CRM country, serviceability, lead status and eventual sale | Whether the geography can produce a customer the business can serve | Google documents the `Country/Territory (user location)` dimension in its guidance for [viewing the jurisdictions where ads were served](https://support.google.com/google-ads/answer/9750227?hl=en-AU). Use it alongside the matched-location report. A campaign can match interest in Lisbon while the person is physically in London; those are different facts and should occupy different columns. Then add the fulfilment rule. Mark each lead serviceable, unserviceable or unresolved. Do not count every form submission as proof that the geography works. A spam enquiry, a job application and a buyer outside the delivery area are all conversions in some dashboards. None is a qualified sale. Small accounts will not produce a neat statistical answer after a handful of leads. That does not make the audit useless. The CRM still defines which locations the business can serve, while the ad report shows where reach occurred. Review individual leads until enough evidence accumulates; do not disguise a thin sample with a confident percentage. If the evidence shows paid clicks from places with no serviceable demand, change one variable. Switch the affected campaign to Presence or add explicit exclusions for locations the business cannot serve. Keep the ads, landing page and bidding strategy stable long enough to judge the location change on its own. ##### What to measure after the switch Fewer impressions are not the result. Neither is a cleaner analytics map. Measure the share of paid leads that are serviceable, the cost per qualified serviceable lead and the sales outcome by user location. Compare those with the previous period while noting seasonality, budget changes and any material difference in demand. If a strict Presence setting lowers reach but improves qualified customer economics, it is doing useful work. If it removes destination buyers and raises the cost of a sale, the cleaner map has made the account worse. Check the search terms and network breakdown at the same time. A geography complaint can coexist with weak query matching or unsuitable partner inventory. Location targeting cannot repair an unrelated source of poor traffic. This is where [SharpOS](https://sharphaw.com/sharp-os) matters. The campaign change, location report and lead outcome should live in one operating trail. SharpHaw Ads is tracked from click to client, not click to dashboard. That is the only level at which the location setting can be judged honestly. ##### Google Ads location targeting FAQ ###### Should I use Presence or Interest in Google Ads? Use Presence when a buyer must already be inside a strict service area. Keep Presence or Interest when people can buy before travelling, relocating or receiving the service remotely. If the offers have different fulfilment rules, split them into separate campaigns. ###### How accurate is Google Ads location targeting? Google calls it a best-effort system. Physical location and interest are inferred from several signals, and Google does not guarantee complete accuracy. Judge patterns across Google's user-location report and qualified lead records, not one surprising session or one isolated day. ###### How do I see where Google Ads clicks came from? First isolate Google Ads traffic in GA4 using source, medium, campaign and source platform. Then build a Google Ads custom report with `Country/Territory (user location)` and compare it with the matched location for the same period. The two dimensions answer different questions. ###### How often should I review location targeting? Review it when the business changes service areas, launches a new offer, separates destination demand, inherits an account or sees a material shift in user location or qualified lead geography. Stable accounts still need a periodic check, but the trigger should be a commercial change or evidence shift rather than an arbitrary weekly toggle. ##### Make the geography answerable Google Ads location targeting is not a border control. It is a decision about which inferred locations and intentions the business is willing to buy. Define the serviceable sale, prove the paid source and make the report answer to the CRM. If the lead cannot be served, the click was outside the market even when Google got the map right. SharpHaw builds and runs senior-led growth systems for owner-operated businesses. [Review SharpHaw Ads Management](https://sharphaw.com/services/ads-management), then [request a Google Ads fit check](https://sharphaw.com/contact) if you want one senior operator to trace the account from location setting to qualified enquiry. Digital work that compounds. --- ### Why one request at a time ships more than ten in progress [Read on sharphaw.com](https://sharphaw.com/blog/one-request-at-a-time-ships-faster) · Product · published 2026-08-17T13:00:00Z > “Unlimited requests, one at a time” sounds generous. It’s the one setting that makes a real weekly shipping cadence possible — here’s the queueing maths. The last agency kept ten things "in progress." Six months later, none of them had shipped. The dashboard stayed busy — green arrows, a burndown chart, a status column three cards deep — and the business hadn't moved a millimetre. If you've run an owner-operated company for a while, you've lived some version of this: plenty of motion, nothing you can point to. So when a subscription says it works one request at a time, it sounds like a downgrade. It isn't. That single-active-request limit is the reason work ships at all, and there's ordinary maths behind why. **TL;DR:** "Unlimited requests, one at a time" isn't rationing your capacity. Working a single active request is the only way a subscription can promise a real weekly cadence, because queueing maths (Little's Law) says the way to ship faster is to hold less in progress, not more. The limit is the product. ##### What "unlimited requests" actually promises Read the small print on any "unlimited" plan and the word is doing a lot of quiet work. Unlimited describes how many requests you can stack in the queue and how many revisions each one gets. It says nothing about how many run at once. One task is active; everything else waits its turn. The design and creative subscriptions that popularised this model sell it exactly that way — unlimited requests, worked one at a time, with a rough turnaround on each. The queue is the mechanism that lets one senior operator serve several clients without lying about capacity. Most write-ups explain that from the provider's side: the queue protects the agency's margin. True enough. What almost nobody tells the buyer is that the same constraint is protecting them. ##### The maths says more in progress ships slower In 1961, an MIT professor named John Little published the proof for a formula that now governs serious production queues everywhere: average cycle time equals work in progress divided by throughput. Rearrange it and the awkward part surfaces. With throughput fixed, the more you hold in progress, the longer each item takes to finish. Throughput is how much a team can actually complete in a week. A [senior-led subscription](https://sharphaw.com/about) has one senior partner and a tight contractor stack, so throughput is real but bounded. "Unlimited requests" can't raise it. All the phrase can raise is work-in-progress — and by Little's Law, that lengthens the time every request spends in the system. You feel productive because ten cards are inching forward. Each one lands later than it would have if you'd run them in sequence. A queue capped at one active request is the shortest honest path from "asked for" to "shipped." ##### Ten open tasks cost more than they look Splitting attention isn't free, and the bill is larger than most founders budget for. David Meyer, whose team ran the landmark task-switching experiments published in 2001, has put the cost of flipping between jobs at up to 40% of productive time. That figure is his own extrapolation rather than a line in the paper, and it's worth saying so plainly — but the direction isn't in dispute. Every switch reloads the problem, and complex creative and engineering work reloads slowly. So ten live requests don't hand the operator 10% each. They get less than that, because the switching between them burns hours that never touch the actual work. One active request removes the switch. The person building it holds the whole problem in their head until it's done, then picks up the next one clean. ##### A queue you can watch is the honest version Most agency relationships feel like a black box because the work in progress lives somewhere you can't see. You get a monthly report instead — "reports full of jargon, green arrows, and charts that don't really mean anything," as one owner described it. A green arrow is not shipped work. SharpHaw runs the queue in the open, inside [SharpOS](https://sharphaw.com/sharp-os). Every request moves through four columns you can watch: Backlog, In Progress, Review, Published. One card sits in In Progress at a time. You can see what's active, what's next, and what landed this week without booking a status call. That visibility only works because the limit exists. A board with forty things "in progress" is a to-do list pretending to be a plan. "I want results, not reports" is the whole design brief. ##### What one at a time forces you to decide The real work the limit does happens upstream of the shipping: it makes you rank. When only one request can be active, "do everything" stops being an option and "what matters most this week" becomes a question you have to answer out loud. That's the trade. You give up the comfortable sense of everything moving at once. In return you get a weekly conversation about priority — the one a fat retainer lets an agency avoid, because looking busy on ten fronts is easier than choosing. A good queue is ruthless about sequence: the landing page leaking enquiries goes before the blog refresh that can wait a fortnight. If your gut says all ten are urgent, that gut is exactly what stalled the last engagement. ##### When one at a time is the wrong fit This model has a real edge, and naming it is only fair. If you genuinely need five separate workstreams running in parallel, each with its own owner and deadline, a single senior queue is not your tool. You want a team sold by the hour or a set of in-house hires, and you should buy that structure with your eyes open. The one-at-a-time queue fits the owner-operator who has more marketing ideas than time, no internal marketer to run them, and wants one senior partner accountable for both sequence and outcome. For that owner, the limit is the difference between a two-year backlog and a weekly habit. ##### Frequently asked questions **Does "one request at a time" mean the work is slow?** Usually the opposite. Because only one request is active, it moves start to finish without queueing behind nine others. Total output is set by the team's weekly throughput, not by how many tickets sit open, so a single active request is the fastest route from asked to shipped. **Is an unlimited-requests subscription worth it?** It's worth it when you have a steady backlog of marketing work, no one internal to run it, and a provider who's honest that "unlimited" means queue depth rather than simultaneous output. It's poor value if you expected ten things built at once — no subscription gives you that from one senior operator. **How many requests actually get done in a month?** As many as the team's weekly throughput allows, shipped in priority order. The useful question isn't "how many can I submit" but "what's the weekly shipping rate, and can I see it?" A visible queue answers both; a monthly report answers neither. **What counts as one request?** One shippable change with a clear finish line: a new landing page, an ad set rebuild, a month of content, an automation. Vague, open-ended asks get split into sequenced requests so each has a real "done" — which is what keeps the queue moving instead of clogging it. ##### What to do next A subscription that runs one request at a time is making a promise it can keep: the next thing on your list ships this week, and you can watch it happen. "Unlimited" makes a promise about the queue. One-at-a-time makes a promise about output. Pick the one you can see. Want to test it? Book a 30-min call, bring the three changes you'd want shipped first, and we'll rank them into a queue you can watch — the terms, and the exit, are already on the [Plans page](https://sharphaw.com/plans). --- ### Why your conversion rate can fall while every segment improves [Read on sharphaw.com](https://sharphaw.com/blog/conversion-rate-average-hides-segments) · Analytics · published 2026-08-15T13:00:00Z > Your conversion rate can fall while every segment improves. See how a blended average and traffic-mix shifts mislead you, and how to read it by segment. Your conversion rate was 3.1% last month. This month it is 2.4%. Nobody touched the homepage. Same product, same prices, same checkout. So you open the dashboard on Monday, see the drop, and start hunting for what broke. Here is the uncomfortable part. It is possible that nothing broke. It is possible that every kind of visitor you get converted *better* this month than last, and the single number on your dashboard still fell. That is not a glitch in the analytics. It is arithmetic doing exactly what it does. A blended conversion rate is an average. Averages hide things — and the thing they hide most often is that your traffic changed while your site stayed still. **TL;DR:** One site-wide conversion rate is a weighted average of very different visitors. When your traffic mix shifts — more mobile, more cold ad clicks, more first-timers — the blended number can fall even if every individual segment improved. Before you redesign anything, split the rate by device, by new-versus-returning, and by source. Read the segments, not the blend. ##### An average is one number pretending to be the whole story Your site does not have "a" conversion rate. It has dozens, stacked on top of each other and flattened into one figure for the dashboard. Desktop buyers convert at one rate. Phone browsers convert at another. People who already know you convert far better than strangers who clicked an ad thirty seconds ago. Someone arriving on a branded search is a different animal from someone caught by a cold display banner. Each of these groups has its own rate, and each group is a different size every single week. The number you stare at is a weighted average of all of them. "Weighted" is the word that matters. Each segment pulls the blended rate towards its own value in proportion to how much traffic it sent. Change the proportions — send more of the low-converting kind, less of the high-converting kind — and the average moves on its own. Your page never got a vote. This is why the Monday-morning panic is usually aimed at the wrong target. The founder blames the new hero section. The real culprit is a campaign that started dumping cheap, curious, low-intent clicks into the top of the funnel. Same site. More tyre-kickers. Lower average. ##### Berkeley watched a rate reverse in 1973 The cleanest proof that an average can betray you did not come from marketing. It came from a university. In the autumn of 1973, UC Berkeley looked like it was rejecting women. Across the graduate school, 44% of the 8,442 men who applied were admitted, against 35% of the 4,321 women. That is a wide gap across nearly 13,000 applications — far too wide to write off as noise. Then three researchers split the data by department. Bickel, Hammel and O'Connell [published the result in *Science* in 1975](https://doi.org/10.1126/science.187.4175.398), and the correction was blunt: the departments showed "a small but statistically significant bias in favor of women." Not against. In favour. Both facts were true at once. Women were admitted at a *higher* rate in most individual departments, yet at a lower rate overall. The trick was where people applied. Women applied in larger numbers to the most competitive departments — the ones that rejected almost everyone, men included. Men clustered in departments that waved most applicants through. The aggregate number reversed the truth of every department underneath it. Statisticians call this Simpson's paradox: a pattern that holds inside every group can flip when you mash the groups together. Berkeley is the textbook case. Your conversion dashboard is the same maths wearing a marketing costume. ##### Watch it happen with your own traffic Numbers make this concrete faster than any explanation. Take a shop with two sources of traffic and follow it across two months. | Segment | Month 1 | Rate | Month 2 | Rate | | --- | --- | --- | --- | --- | | Branded search (warm) | 50 sales / 1,000 | 5.0% | 30 sales / 500 | **6.0%** | | Cold display (chilly) | 10 sales / 1,000 | 1.0% | 45 sales / 3,000 | **1.5%** | | **Blended** | 60 / 2,000 | **3.0%** | 75 / 3,500 | **2.1%** | Read the segment rows first. Branded search improved, 5.0% to 6.0%. Cold display improved, 1.0% to 1.5%. Every visitor type got *better* at converting. You could not have asked for a cleaner month. Now read the blended row. It fell from 3.0% to 2.1%. Nothing on the site got worse. A display campaign in Month 2 poured 3,000 cold clicks on top of a much smaller warm pool, and cold clicks convert low by nature. The mix moved. The average followed the mix, not the page. If you had spent that week rewriting the homepage to "fix conversion", you would have been treating a healthy patient — and you would have congratulated yourself when the campaign eventually ended and the number floated back up. ##### Three splits move your blended rate more than your page does You do not need a statistics degree to catch this. You need three cuts, and they take about ten minutes in any analytics tool. **Device.** Desktop and mobile do not convert alike. A seasonal swing towards phone traffic, or an Instagram push that lands mostly on mobile, drags the blended rate down while both device rates hold perfectly steady. **New versus returning.** Returning visitors convert well above first-timers. So a burst of top-of-funnel reach, a viral post, or a fresh awareness campaign floods you with new visitors and pulls the average down. That is growth showing up as a "problem" on the dashboard. **Source intent.** A branded search click and a cold retargeting impression are not the same buyer at different speeds. They want different things and convert an order of magnitude apart. Shift budget from search to display and the blended rate drops on contact — before a single visitor has judged your offer. Device, intent, recency. When the site-wide number moves and you have not shipped a change, one of these three moved first almost every time. ##### What to do before you touch the page The fix is a habit, not a tool. When the blended rate jumps or drops, run the diagnosis before the redesign. Segment the same rate three ways — device, new versus returning, and source or channel. Compare each segment to its own past self. Comparing segments against each other tells you nothing; a segment is only interesting when it moves. If every segment is flat or up and only the blend fell, stop. The mix moved, and the site is fine. Go look at what changed in your traffic: a campaign that launched, a channel that spiked, a season that turned. If a *specific segment* dropped — mobile cratered, or returning visitors fell off — now you have something real to chase, and you know exactly where to point. That is a page problem, or a checkout problem, or a broken flow on one device. It is fixable because it is located. The average didn't lie to you. You asked one number to do the work of four. ##### When the blended number is still worth watching None of this makes the site-wide rate useless. It makes it a smoke alarm, not a diagnosis. A moving blended rate is a fine trigger to go and look. It tells you *something* shifted. It never tells you *what*, because it cannot separate a worse page from a different crowd. The alarm has one job: get you to open the segment view. Everything useful happens after that. The trade is real, and worth naming. Segments mean smaller samples, and smaller samples are noisier — a 40% mobile conversion rate off ten sessions is a rounding error, not a finding. You give up the comfort of one clean figure for three or four honest, wobblier ones. That is the correct trade. A single confident number that points the wrong way is more expensive than four modest numbers that point where the problem actually is. At SharpHaw we treat conversion as the only brief worth having — but the first move is always to read the number properly before reaching for the page. Diagnose, then build. If your conversion rate just moved and nobody can tell you which segment moved it, that is the conversation to have before anyone opens the site editor. [That is the kind of read we do in the open.](https://sharphaw.com) ##### Common questions **Why did my conversion rate drop right after I got more traffic?** More traffic is usually more *new* and more *cold* traffic, and both convert well below your site average. The extra visitors drag the blended rate down even when your existing audiences convert exactly as before. Check the new-versus-returning split first — a growth spike often looks like a conversion fall. **Is a falling conversion rate always a bad sign?** No. If every segment is holding or improving and only the blended number fell, the mix changed, not your site. That can even mean a successful awareness push. A falling rate is only a real problem when a specific segment — a device, a channel, a returning audience — falls on its own. **How do I segment my conversion rate?** Any analytics tool will do it. In GA4, compare conversion rate across device category, then across new versus returning users, then across session source or channel. Look at each segment against its own history, not against the others. The goal is to find the one segment that moved, or to confirm that none did. --- ### Contact form thank-you page: the missing reply contract [Read on sharphaw.com](https://sharphaw.com/blog/contact-form-thank-you-page-reply-contract) · Website · published 2026-08-14T12:00:00Z > Fix your contact form thank-you page with a reply contract covering receipt, ownership, response time, fallback and measurement. Run this ten-minute audit. [Zuko Analytics' 2025 benchmark](https://www.zuko.io/blog/25-conversion-rate-statistics-you-need) found that only 38% of people who interact with a contact form successfully submit it. The few who press **Submit** deserve more than “Thanks, we'll be in touch.” A contact form thank-you page should work like a reply contract. It confirms that the enquiry arrived, says who owns the response, gives an honest timeframe and provides a fallback if the reply never appears. Without that, the form has captured data but the buyer is still guessing. A founder reads your service page, sees a promising fit and explains the problem in a form. The browser replaces their careful message with one line: > Thanks! We'll be in touch soon. The browser says success. The buyer still does not know who replies, when or where to look if nothing arrives. By tomorrow, they may submit again or contact somebody else. That is a broken hand-off. **TL;DR:** A contact form thank-you page should confirm receipt, identify the request, name the response owner, give an honest timeframe and provide a monitored fallback. Put those five parts before any extra sales action, then test the real submission and measure the reply rather than relying on a page view. ##### What should a contact form thank-you page actually promise? The page has one primary job: make the hand-off legible. The [GOV.UK Design System's confirmation pattern](https://design-system.service.gov.uk/patterns/confirmation-pages/) recommends telling users what happens next and when, with a reference number and contact details where those are useful. A small service business can turn that principle into five fields. ###### 1. Receipt Confirm that the submission reached the system. “Form sent” describes an interface event. “We received your website enquiry” describes the buyer's outcome. If you issue a reference number, show it here and include it in the confirmation email. Do not invent one for decoration. It is only useful when somebody can find the enquiry by that number later. ###### 2. Scope Restate the type of request so the buyer can catch mistakes. This might be “conversion-first website enquiry” or “support request for order 1842”. Avoid printing sensitive form answers back onto a shared screen. This matters when one form handles several services. The buyer should know that the right route received the request without needing four nearly identical thank-you pages. ###### 3. Owner Say who is responsible for the next move. A named person is useful when that person really owns the inbox. A role such as “our senior web partner” is better when coverage rotates. This line looks like copy, but it forces an operational decision: who notices the enquiry, and who is accountable when nobody replies? ###### 4. Clock Give an honest response window. “Within one working day” is clear. “As soon as possible” is not. If weekends or public holidays change the window, say so. An honest two-day promise is better than “shortly” followed by silence. The former may look slower, but the buyer can plan around it. The latter makes the firm look disorganised before the first conversation. ###### 5. Fallback Tell the buyer what to do if the promised window passes. Give one monitored email address or phone number and mention the sender name or domain they should look for. The fallback is not pessimistic. Email filters fail, automations break and people get ill. A credible service path accounts for that. Put together, a stronger confirmation could read: > We received your website enquiry. A senior web partner will review it and reply from an @example.com address within one working day. If you have not heard from us by then, email hello@example.com and mention reference 1842. Adapt the role, timing and route to the process you can actually run. Do not paste a faster promise onto a slower operation. ##### Should confirmation stay inline or open a new page? Either can work. The choice depends on what the buyer needs after submitting, not which setup makes the analytics dashboard tidier. An inline message suits a short, low-stakes form when the full reply contract fits beside it. It keeps the buyer in context and avoids an extra page load. The implementation still has to make the state obvious. The [W3C Web Accessibility Initiative](https://www.w3.org/WAI/tutorials/forms/notifications/) puts it plainly: “Success messages are also important to confirm task completion.” A visual colour change alone is not enough for everybody to notice. A separate confirmation page earns its place when the buyer needs a durable reference, detailed next steps, a document or a clear fallback route. It can also give the state a stable URL for support and quality checks. Test both versions on a slow connection and with the browser's back and refresh controls. A success message that vanishes, appears below the fold or creates a duplicate enquiry on refresh is not a success state. This is one of the small but consequential details behind a [conversion-first website](https://sharphaw.com/services/conversion-first-websites): the interface must carry the buyer cleanly through the action, including the quiet state after it. ##### Why another sales pitch is the wrong next step Most thank-you-page guides recommend using the space for an upsell, referral request, newsletter, social follow or stack of resources. That advice is not automatically wrong. It is simply secondary. The buyer has just asked for human attention. Answer that need before asking for another action. A useful secondary link reduces uncertainty. A short explanation of the review process, a relevant service page or a way to add a confirmed appointment to a calendar can help. Five unrelated articles and three social buttons make the page feel like leftover landing-page inventory. Use this order: 1. Confirm the enquiry. 2. Explain the reply. 3. Provide the fallback. 4. Offer one optional next action if it helps the buyer wait or prepare. The discipline is especially important for firms selling senior judgement. If the page immediately pushes another download, it suggests that the funnel owns the moment and nobody owns the person. ##### Measure the hand-off, not just the page view A dedicated thank-you URL used to be the convenient way to count form conversions. It should not be the only evidence that an enquiry worked. Google Analytics' current event guidance recommends [`generate_lead`](https://developers.google.com/analytics/devguides/collection/ga4/reference/events) when somebody submits a form or request. Its [enhanced-measurement guidance](https://support.google.com/analytics/answer/9216061?hl=en-IE) also documents the `form_start` and `form_submit` events. That means the successful action can be measured whether the interface uses an inline message or a separate page. Automatic tracking still needs verification. Submit a real test enquiry and check that: - one submission creates one analytics event; - the enquiry reaches the system that somebody monitors; - the confirmation state appears on mobile and desktop; - a failed submission does not fire a success event; - refreshing the page does not create a second record. Then measure the operational hand-off. How long did the first useful reply take? How many enquiries were duplicates? Which ones became qualified conversations? A page view cannot answer those questions. For SharpHaw work, the visible trail matters as much as the event. The website captures the enquiry; [SharpOS](https://sharphaw.com/sharp-os) keeps the work and decisions visible after it arrives. The point is not another report. It is knowing what changed, who owns the next move and whether the path still works. ##### Run the ten-minute reply-contract audit Open your live contact form in a private browser window and submit a realistic test enquiry. Then answer these questions with yes or no: - Does the page explicitly confirm receipt? - Does it identify the request without exposing private details? - Does it say who or which role replies? - Does it give an honest working-hours timeframe? - Does it provide a monitored fallback route? - Does the analytics event match the real submission exactly once? Fix the first **no** before redesigning the page. Receipt comes before styling. Ownership comes before an extra call to action. A working fallback comes before clever nurture. Run the same test on a phone and ask somebody outside the business to read the confirmation. If they cannot tell what happens next without guessing, the contract is incomplete. A generic “Thanks” can hide a surprising amount of operational fog. The repair is small, but it demands real answers from the business behind the form. SharpHaw builds those answers into the path: one accountable senior partner, visible work and a measured hand-off. Digital work that compounds. [Send the live form and its current reply path](https://sharphaw.com/contact) for an honest fit check. You will know which part of the hand-off needs fixing first. --- ### AI automation GDPR: audit every copy the workflow leaves [Read on sharphaw.com](https://sharphaw.com/blog/ai-automation-gdpr-data-copy-audit) · Automations · published 2026-08-13T15:00:00Z > AI automation GDPR starts with the data copies your workflow leaves. Map retention, access and deletion before customer data enters the flow. A customer fills in your enquiry form. The record appears in the CRM, an AI step labels the request, and someone on your team gets an alert. It looks like one tidy transaction. It may have created six copies of the same personal data. Practical AI automation GDPR work starts by naming every place the data persists, why it is there, who can see it, when it disappears and how you would delete it. Vendor security pages are evidence, but they cannot answer those questions for the workflow you configured. Before an automation touches customer data, run a data-copy audit. Map the source, execution history, AI provider, destination, retry path and human notification. Then give every stored copy a purpose, an owner, a retention rule and a tested deletion route. A green tick in the run history proves the workflow ran. It does not prove the data trail is controlled. **TL;DR:** One AI workflow can leave personal data in more places than the CRM shows. Audit each copy, pass only the fields a step needs, shorten or disable unnecessary histories, and test deletion across the whole chain before live customer data enters it. ##### Where does an AI automation copy customer data? Take a common lead-routing flow: 1. A visitor submits a name, email address, company and free-text message. 2. The form platform stores the submission. 3. An automation platform reads the payload and keeps a run history. 4. An AI service classifies the enquiry by service and urgency. 5. The CRM creates a contact and opportunity. 6. A failed step enters a retry queue, or the full message is pasted into an email or team chat alert. The information can pass through even more places: webhook logs, test runs, spreadsheets, exported histories, error-monitoring tools and backups. Some copies last seconds. Others persist until somebody changes a default setting. That difference matters. Data moving through memory for a specific step is not the same operational risk as a payload stored in a searchable history. Your first job is to distinguish transit from persistence. If one enquiry creates five stored payloads, deleting the CRM record deletes one copy. This is why the audit starts with the workflow you actually built, not the diagram from a vendor's homepage. Open a real execution. Inspect the input and output at each step. Search for the same email address in every connected system. The result is usually less tidy than the boxes and arrows suggest. ##### Why a successful run history becomes a shadow database Run histories are useful. When an automation fails at 02:13, the engineer needs enough context to find the bad step and repair it. The problem begins when the easiest debugging setting is “save everything forever”. A history that stores names, emails, messages and AI outputs is functionally another customer database, even if nobody calls it one. It has records, search, access rules and a retention period. It also tends to receive less scrutiny than the CRM. The settings are often configurable. [n8n's execution-data documentation](https://docs.n8n.io/deploy/host-n8n/configure-n8n/scaling/manage-execution-data/) shows that teams can avoid saving successful runs, keep error runs and prune older executions. Its documented default age at the time of writing is 14 days, with exceptions including waiting and annotated runs. That is a product default, not a GDPR rule. [Zapier's run-history documentation](https://help.zapier.com/hc/en-us/articles/8496291148685-View-and-manage-your-Zap-history) says it guarantees up to 60 days of run data and displays up to 10,000 runs. It also makes an important distinction: deleting the record of a completed run does not undo the action already taken in another system. The sensible trade-off keeps the smallest useful diagnostic record. Keep the error code, step name, timestamp and internal record ID where those are enough. Do not keep a full customer message merely because it made the first build easier to debug. Third parties deserve attention too. Verizon's [2025 Data Breach Investigations Report](https://www.verizon.com/business/resources/T16f/reports/2025-dbir-data-breach-investigations-report.pdf) found third-party involvement in 30% of the breaches it analysed, up from roughly 15% in the prior report. The figure covers third-party involvement generally, not AI tools specifically. Every extra service and stored copy expands the system you must understand and protect. ##### What AI automation GDPR work actually asks you to prove The [GDPR's Article 5](https://eur-lex.europa.eu/legal-content/EN/AUTO/?uri=celex:32016R0679) sets the operating principles. Personal data should be limited to what is necessary for the purpose, kept identifiable for no longer than necessary, and protected with appropriate measures. Article 25 extends that thinking to data protection by design and by default, including the amount collected, the extent of processing, storage time and access. Those principles expose three weak answers that often survive a technical review: - “The vendor is GDPR compliant.” A supplier's controls do not document the workflow you configured. - “We keep logs in case we need them.” “In case” is not a retention purpose or a deletion trigger. - “The AI only classifies the message.” That says what the step does, not which fields it receives or what the provider stores. The GDPR does not set one universal number of days for every automation log. Retention has to make sense for the purpose and the risk. A failed payment workflow may need a different diagnostic window from an enquiry classifier. Write the reason down. Set a date or event that ends it. Give someone responsibility for checking that the setting still matches the policy. Using a processor does not outsource the whole decision. The [European Data Protection Board's small-business guide](https://www.edpb.europa.eu/sme/learn-the-basics/data-controller-or-data-processor_en) says the controller generally retains overall responsibility, while the controller-processor relationship must be governed by a contract that documents the processing. Article 28 also covers sub-processors, support for individual rights and deletion or return of copies when the service ends. A data processing agreement belongs in many supplier relationships. The workflow map belongs beside it. ##### Run a six-field data-copy audit The ICO's practical [AI and data-minimisation guidance](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/artificial-intelligence/guidance-on-ai-and-data-protection/how-should-we-assess-security-and-data-minimisation-in-ai/) starts with understanding and mapping every process where personal data may be used. For a small workflow, that map can be one table. Create one row for every place data can persist and fill in six fields: | Field | What to record | Bad answer | |---|---|---| | Copy | System and exact storage location | “In the automation” | | Fields | Personal data stored there | “Form details” | | Purpose | Why this copy must exist | “Just in case” | | Owner and access | Named owner plus roles that can view it | “The team” | | Retention trigger | Days, state change or contract event | “Platform default” | | Deletion route | Exact action and last test date | “Vendor handles it” | For the enquiry flow, a useful first pass might look like this: | Copy | Fields kept | Purpose | Retention and deletion | |---|---|---|---| | Form submission | Name, email, company, message | Recover a failed hand-off | Delete after CRM creation is confirmed and the recovery window closes | | Successful run history | Internal record ID, step status | Diagnose recent faults | Do not store the full payload; prune on a short schedule | | AI request | Enquiry text or reduced features | Classify service type | Check provider settings, contract, region and retention; remove fields the model does not need | | CRM lead | Contact and enquiry record | Manage the commercial conversation | Apply the CRM retention and deletion process | | Error alert | Run ID and error summary | Tell the owner where to look | Redact the customer message; expire the alert with the incident record | | Retry queue | Minimum payload needed to retry | Recover a temporary failure | Delete on success or when the retry window ends | Do this with a real run, not a recollection of how the workflow was meant to work. Defaults change. A test node can be left active. A colleague can add a spreadsheet export that never appears on the original diagram. The audit is complete only when someone other than the builder can follow the deletion route. If the answer depends on one person's memory, you have documented a bus factor, not a control. ##### What to delete, redact or stop logging Start at the first unnecessary field. An AI classifier deciding “website”, “ads”, “content” or “automation” may need the message and perhaps the current page. It probably does not need the person's phone number, billing address or full CRM history. Then reduce persistence step by step: - Pass internal record IDs between systems instead of copying the full record where possible. - Disable successful-run storage when a timestamp and status counter are enough. - Keep error context, but redact free text and direct identifiers from team alerts. - Separate production histories from test data and restrict debugging access. - Delete exports after the investigation or migration they were created for. - Check the model provider's retention, training-use, region and sub-processor terms against the actual account configuration. - Test a deletion request with a seeded record and record the result. The deletion test is the part most teams skip. Create a test enquiry with a unique address. Let the entire flow finish. Delete it through the normal process, then search the form platform, workflow history, AI traces where available, CRM, alert channel, retry queue and exports. You may find that one deletion route is manual. That is not automatically a reason to abandon the workflow. It is a reason to name the owner, write the steps and decide whether the response time is acceptable. If the volume grows, automate the deletion process only after the operating rule is clear. This is how [AI automation](https://sharphaw.com/services/ai-automations) should enter a business: as a maintained data path with visible decisions, not an impressive demo held together by hidden histories. ##### When the workflow needs privacy counsel, not another setting The copy audit is an engineering and operating check. It does not choose your lawful basis or certify compliance. Bring in your privacy counsel or data protection officer when the flow handles special-category data, monitors people systematically, profiles them at scale, involves children, sends personal data across uncertain jurisdictions, or makes decisions with legal or similarly significant effects. Get advice too when nobody can state the lawful basis clearly or when a data protection impact assessment may be required. Do not hide those questions inside a build ticket. A platform toggle cannot decide whether the business should process the data in the first place. The same rule applies to procurement. A polished security page is useful evidence, but you still need to inspect the contract, sub-processors, retention controls, deletion support and the settings available on your plan. If a vendor cannot answer where data goes or how it is removed, the workflow is not ready for live customer records. ##### The release test before you switch it on An AI workflow is ready for customer data when the owner can answer yes to these questions: - Can we list every system where a payload or identifiable output persists? - Does every stored field have a specific purpose? - Is each retention period intentional rather than inherited from a default? - Can we remove one person's data across the whole chain? - Has somebody other than the builder watched that deletion test pass? Keep the audit with the rest of the operating record in your workspace. At SharpHaw, that kind of decision trail lives in [SharpOS](https://sharphaw.com/sharp-os), beside the work rather than in a forgotten policy folder. The useful finish line is “we can explain its data trail, operate it and delete it”. That is what “Digital work that compounds.” means when the work is an AI automation. If you have a recurring workflow worth automating, [book a focused call](https://sharphaw.com/contact). We will map the smallest useful version, including the copies and controls it needs before customer data enters the flow. --- ### An AI receptionist won't save the calls you're losing [Read on sharphaw.com](https://sharphaw.com/blog/ai-receptionist-wont-save-calls-youre-losing) · Automations · published 2026-08-13T12:00:00Z > An AI receptionist stops the ring-out but rarely wins the client. See why the missed-call fix is a text-back and a callback, not a synthetic voice. An AI receptionist will answer the call you're about to miss. It just won't get you the client. That gap between answered and won is the part the sales pitch skips. Missed calls are a real leak. If you run a service business in Europe and the phone rings while you're on a roof, in a chair, or three tabs deep in a client's ad account, some of those callers are buying today and calling your competitor tomorrow. The instinct to plug the leak is right. The instinct to plug it with a synthetic voice that pretends to be your front desk is where founders lose the plot. Here's the honest version of the trade before you spend a cent. ##### The number that sells AI receptionists was built to scare you Every AI-receptionist pitch opens with the same stat: 62% of calls to small businesses go unanswered during business hours (411 Locals, 2024). It gets paired with "85% of callers won't try again" and a headline about the tens of thousands you're bleeding a year. The numbers aren't fabricated. They're just quoted almost entirely by the companies selling you the robot. That should slow you down, not speed you up. A frightening figure attached to a product is a marketing asset, not a diagnosis. The retention industry does the same thing with its "5% loyalty lift" folklore. The missed-call industry does it with 62%. So take the leak seriously and ignore the cure being sold with it. The real question isn't "how do I answer every call?" It's "what actually turns an inbound call into a booked client — and which part is a machine good at?" ##### Answering the phone was never the hard part Picture the call you're worried about. Someone found you, had enough intent to dial, and got voicemail or a ring-out. Roughly 80% of those callers won't leave a message, and around 85% won't ring back. The lead didn't go to voicemail. It went to whoever picks up next. An AI receptionist answers, sounds pleasant, and takes a message. Feel the shape of that: you've replaced a missed call with a message you still have to act on. The caller now believes they've spoken to your business. If you don't follow up fast, you've converted a cold miss into a warm disappointment — worse, because they expected a call back that a script promised. A robot reading your script in a calm voice isn't answering the phone. It's buying you time you then don't use. The evidence on speed is brutal and old. Harvard Business Review found that firms responding within an hour were about seven times likelier to have a real conversation with a decision-maker (2011). The Lead Response Management Study put a 5-minute reply at roughly 21 times more likely to qualify the lead than a 30-minute one (Oldroyd, 2007). The bottleneck is never the greeting. It's the callback that arrives after the buyer already hired someone else. ##### What actually recovers the money The fix that works is boring, which is exactly why nobody sells it to you with a countdown timer. When a call comes in and you can't pick up, three things need to happen in the next sixty seconds, and only one of them is talking: - **An instant, honest text goes out.** "This is Gabriel at [business] — I missed your call, I'll ring back within the hour. Or reply here and I'll sort it now." No pretending a human answered. The caller who won't leave voicemail will happily reply to a text. - **A task lands where you'll actually see it.** Not a voicemail box you check twice a day — a logged item in the system you already work from, with the number, the time, and a due-by. - **The follow-up is owned.** Someone (you, a contractor, or a genuinely narrow AI step) closes it before the buyer's patience runs out. Notice what the machine is doing here. It's not impersonating your receptionist. It's sending a reliable message and creating a record. That's automation doing what it's good at: the same small job, every time, without forgetting. AI is plumbing here, not a personality. The judgement (what this caller needs, whether they're a fit, what to quote) stays with a person, because that's the part a synthetic voice fumbles the moment the call goes off-script. ##### When an AI voice actually earns its place This isn't a blanket no. There's a narrow case where an AI voice agent is the right tool, and it's worth naming so you can test yourself against it honestly. An AI voice earns its place when your call volume is high enough that texts-back and callbacks can't keep up, the calls are repetitive and structured (booking a slot, confirming an address, checking opening hours), and a wrong answer is cheap to correct. A dental clinic fielding forty "can I move my appointment" calls a day is a real fit. The system has one job, the caller expects a transaction, and nothing subtle is being sold. You fail the test when the call is where the sale is actually made — a founder ringing about a project, a homeowner describing a leak, a buyer deciding whether to trust you with money. There, the caller is reading your competence and your character in the first thirty seconds. Hand that to a script and you've automated the exact moment you were trying to win. So the fit test is one line: **is the phone call the transaction, or the sale?** Automate the transaction. Never automate the sale. ##### The uncomfortable part for founders Most people shopping for an AI receptionist don't have a phone-answering problem. They have a follow-up problem, and the robot is easier to buy than the discipline. If your missed calls turn into un-returned callbacks, an AI voice will not save you — it'll just miss them more politely. The 62% stat isn't lying about the leak. It's lying about where the leak is. It's rarely in the greeting. It's in the hour after, the day after, the "I'll get to it" that never gets got to. A synthetic voice papers over the first ten seconds of a problem that lives in the next twenty-four hours. Fix the follow-up and most of the panic-buying reason for an AI receptionist disappears. What's left is a small, specific automation (missed-call text-back, logged task, owned callback) that costs a fraction of a per-minute voice bot and doesn't put words in your mouth. ##### FAQ **Do I need an AI receptionist for my small business?** Probably not first. Most missed-call revenue is lost in the follow-up, not the greeting. An instant text-back plus a logged callback task recovers most of it at a fraction of the cost. Consider an AI voice only when call volume is high and the calls are repetitive, structured transactions rather than sales conversations. **What's the difference between a missed-call text-back and an AI receptionist?** A text-back sends the caller an honest message ("I missed your call, I'll ring back within the hour") and logs a task — it never pretends to be human. An AI receptionist holds a synthetic voice conversation on your behalf. The first automates a reliable message; the second automates the sales moment, which is exactly the part a script tends to fumble. **Won't an AI receptionist stop me losing leads to voicemail?** It stops the ring-out, but not the loss. If the callback still arrives after the buyer has hired someone faster, you've converted a cold miss into a warm disappointment. Speed of the human follow-up is what recovers the lead — HBR found responding within an hour makes a real conversation about seven times likelier. ##### The next step that isn't a robot If your phone is leaking clients, the answer isn't a voice pretending to be you. It's mapping where the calls actually die (greeting, callback, or the day-after silence) and shipping the smallest automation that plugs it. Usually that's a missed-call text-back wired into the system you already work from, plus a callback someone genuinely owns. That's the kind of work we ship weekly at SharpHaw: name the leak, automate the boring reliable part, leave the sale to a person. If you want a straight read on whether an AI voice would help you or just cost you, bring us your call setup — you'll leave knowing which part to automate and which part to never hand to a machine. --- ### Your domain authority score is a number Google never reads [Read on sharphaw.com](https://sharphaw.com/blog/domain-authority-not-a-google-ranking-factor) · Content Engine · published 2026-08-12T17:00:00Z > Domain authority is Moz's third-party score, not a Google ranking factor. See what the 2024 Google leak really proved and what to measure instead. Domain authority is not a Google ranking factor. It never has been. That one sentence quietly deletes a slide from a lot of monthly SEO decks — the slide where a number climbs from 28 to 34, a green arrow points up, and nobody in the room can tell you what changed in the inbox. If you have ever paid for "link building to raise your domain authority" and wondered why the enquiries never followed the number, here is the reason. You were watching a score Google never reads. Domain authority is not Google's metric. It belongs to Moz, an SEO software company, and it runs on a 1-to-100 scale that Moz built to *predict* ranking. Ahrefs sells its own version called Domain Rating. Both are estimates of your backlink profile, calculated by a private vendor — not a signal the search engine consults when it decides where you land. Moz states it plainly in its own documentation: Domain Authority "is not a Google ranking factor." When the company that sells you the number tells you Google ignores it, that is worth reading twice. **The short version:** Domain authority (and Ahrefs' Domain Rating) is a third-party guess at how strong your backlinks are. Google does not use it. The 2024 Google documentation leak showed the search engine keeps its *own* site-level trust signal — but it is earned by being worth citing, not bought by moving a vendor's needle. Measure enquiries and real mentions, not DA. ##### Where the number in your report actually comes from Someone built the domain authority in your report by reverse-engineering Google, not by reading anything Google publishes. Moz crawls the web, counts linking root domains and total links, runs a machine-learning model, and outputs a tidy score. Ahrefs does the same and calls it something else. Useful as a rough gauge. Fine as a proxy. But a proxy is the map, not the ground. Here is where it goes wrong. The report treats the proxy as the target. "Let's get you to DA 40" becomes the goal, so the work becomes acquiring whatever Moz counts — links — regardless of whether those links do anything for a buyer or for Google. You end up paying to improve a private company's estimate of your website. That is not a ranking strategy. That is optimising the reflection. ##### Google has said the same thing for a decade This is not a contrarian take. It is the boring official record, repeated until the people saying it sounded tired. Gary Illyes, from Google's search team, said back in 2016: "We don't really have 'overall domain authority'." John Mueller, also Google, was blunter in 2020 — Google does not use domain authority "at all in our algorithms" — and said it again in 2022. Not "we weight it lightly." Not "it's one of two hundred factors." At all. You can dislike the messenger. But there is no version of the last ten years where Google quietly used a Moz number and forgot to mention it across dozens of public answers. The score in your deck and the algorithm ranking your pages have never been the same thing. ##### The 2024 leak didn't rescue domain authority — it buried it In May 2024, roughly 14,000 internal Google Search documents — 2,596 modules — spilled onto GitHub and were surfaced by Rand Fishkin and Mike King. For about a week, every SEO forum declared victory: one of the leaked fields was called `siteAuthority`. See — Google *does* have domain authority. Read the actual documents and the story flips. Yes, Google appears to keep a site-wide trust signal. That is real, and it matters. But `siteAuthority` is Google's own internal measure, computed from signals Google has never handed anyone a dial for. It is not Moz's DA, it is not your report's number, and there is no field in there labelled "buy links, watch it rise." There was, however, another field in the same leak: `BadBackLinks`. Sit with that. The exact link packages an agency sells to lift your domain authority are the kind of pattern Google has a named signal for on the *negative* side. Google's spam systems devalue manipulative links algorithmically now — most sites never need the disavow tool at all. So the vendor's number and Google's real signal can move in opposite directions at the same time. You can buy your way to a higher DA and a quieter site. ##### Why the score still climbs alongside your rankings Two things can climb together without either one lifting the other. That is exactly what happens with domain authority and your rankings — both are driven by the same underlying cause, and neither one causes the other. When you publish something genuinely worth referencing, real sites link to it and real readers cite it. Google notices the usefulness. Moz notices the links. Rankings move; DA moves; they move together because the actual work moved both. The number is a *lagging mirror* of value you already created. Agencies sell you that mirror as if it were a lever — as if painting a higher number onto the glass would change what stares back. It doesn't. Domain authority is a mirror. Your agency sells it as a lever. This is the same trap as the report "full of jargon, green arrows, and charts that don't really mean anything" that every burned founder eventually describes. A metric that only ever goes up, disconnected from the thing you sell, is not evidence. It is decoration with a decimal point. ##### What to measure instead of domain authority Swap the vendor's number for three figures that touch the business. **Qualified enquiries.** Did a real, right-fit person fill the form, book the call, or send the email? This is the only number that survives a recession. "We've done SEO… why aren't we showing up?" is a fair complaint — but showing up is a means, and enquiries are the end. Track the end. **Real mentions and citations.** Are relevant publications, suppliers, and now AI answers referencing you by name? When ChatGPT or Google's AI answers name you as an option, that is site trust doing its job — the thing `siteAuthority` gestures at, earned honestly. One editorial citation from a source your buyer already reads outweighs fifty directory links. **Rankings on queries that precede a sale.** Impressions and positions on the searches a buyer runs the week before they choose someone — not vanity head terms with no intent behind them. Links still matter, to be clear. But the links that matter are earned: a real site references you because you said something worth referencing. That is the only kind that lifts Google's real signal *and* your DA at once — and it is the opposite of a bought package. Everything else marketed as "link building" is theatre with an invoice. This blog is the working example. Every post here is written to be worth citing, because that is the only durable way any authority signal, Google's or Moz's, actually moves. ##### When domain authority is still worth a glance Not never. Domain authority is a fine *rough* gauge when you are sizing up a market or a prospect — a five-second read on whether a competitor has been around and earning links, or a quick triage before deeper work. Glance at it the way you glance at a thermometer. What it is not: a goal, a service line, or a line on your own progress report. The moment "raise your DA" becomes something you are paying for, you are buying the thermometer instead of turning on the heat. ##### FAQ **Is domain authority a Google ranking factor?** No. Domain authority is a 1-to-100 score created by Moz, a third-party SEO tool, to predict ranking. Google representatives have said for years that Google does not use it. Moz's own documentation confirms it is not a Google ranking factor. **What is a good domain authority score?** There is no universal good score, because it is relative to your competitors and controlled by a private vendor, not Google. A DA that is higher than the sites you compete against tells you something rough about link profiles. It tells you nothing certain about where you will rank or how many enquiries you will get. **Does the 2024 Google leak mean Google uses domain authority after all?** No. The May 2024 leak revealed Google keeps its own internal `siteAuthority` signal — but that is Google's private measure, not Moz's DA, and Google has never exposed a way to buy or set it. The same leak also named a `BadBackLinks` signal, which is bad news for anyone purchasing links to raise a score. **Should I pay for link building to raise my domain authority?** Not as a goal in itself. Paid link packages target the vendor's number, not Google's, and can trip the exact spam patterns Google devalues. Earned references from relevant, credible sites are worth pursuing; a monthly invoice to lift a DA figure usually is not. ##### The number was never the point A score that always climbs and never explains itself is the easiest thing in the world to sell and the least useful thing to own. Domain authority is a mirror of work you either did or didn't do. Stop paying to repaint the glass. If your last SEO report leaned on a domain authority number, send it over. I'll tell you which figures on it map to enquiries and which are there to fill a slide. That is how we run everything at SharpHaw — one senior partner, weekly shipping, and a shared workspace in SharpOS where you can see what actually changed, not a number that only points up. Book a fit call through the [contact page](/contact); the plans are [priced in public](/plans). --- ### Marketing change log: what changed before the graph moved [Read on sharphaw.com](https://sharphaw.com/blog/marketing-change-log-before-results-move) · Marketing · published 2026-08-12T16:02:00Z > Build a marketing change log that records the decision, expected signal and rollback point behind every result, before the next graph moves, and act on it. A marketing change log should already hold the decision before the graph moves. A conversion graph moves on Tuesday. By Friday, nobody can say whether the cause was the new homepage, a Google Ads budget edit, the campaign email or a tracking break. That is the job of a marketing change log. It records each meaningful change before it ships, along with the owner, expected signal, date to review and condition for rolling it back. Native platform histories can tell you who clicked which setting. They cannot preserve the cross-channel decision that connected the work to the business result. If the dashboard moved and the decision is missing, you have a graph, not an explanation. **TL;DR:** A marketing change log records what changed, why it changed, who owns it, which metric should move, when to judge it, what must not get worse and when to reverse it. Keep one cross-channel record because Google Ads, Meta, GA4, your website and your CRM each preserve only part of the story. ##### Why a graph cannot explain its own movement A dashboard can show the exact hour a number moved. It cannot tell you which decision deserves credit or blame. Picture the Monday review. Website enquiries fell last week. Google Ads still reports conversions. GA4 shows a dip on the pricing page. The CRM shows fewer qualified opportunities, but nobody tagged the reason. Meanwhile, the homepage headline changed, a form field was removed, automated bidding adjusted spend and the cookie banner was replaced. Four systems changed. One graph moved. The review starts with the question founders already ask in operator communities: "What do you check first?" Without a work trail, the honest answer is experience plus gut. That is where report theatre begins. Someone opens the tab they own, finds a flattering metric and builds a story around it. The web person blames traffic quality. The ads person blames the page. The analytics person blames consent. All three may be partly right, but none can show the decision that came before the result. The founder's worry is simpler: perhaps the weekly "optimisation" is activity first and explanation later. A marketing change log removes that escape route. It gives every review a dated starting point before anyone chooses a narrative. ##### What a marketing change log should record At 10:14 on Tuesday, the homepage CTA changes from a vague contact prompt to a fit-check request. A weak log records: "Updated CTA." That line will be useless in three weeks. A decision record needs seven fields: 1. **Change:** the exact setting, page element, audience, workflow or tracking rule that changed. 2. **Reason:** the observed problem that justified touching it. 3. **Owner:** one named person responsible for the decision and the review. 4. **Expected signal:** the primary metric or behaviour that should move if the decision is sound. 5. **Judgement window:** the earliest date when there is enough data to review it. 6. **Guardrail:** the number or buyer outcome that must not get worse while the primary signal improves. 7. **Rollback condition:** the threshold or failure that triggers a reversal. The CTA example now reads differently: > Changed the homepage CTA from "Contact us" to "Request a fit check" because high-intent pricing-page visitors were reaching the form but abandoning before submission. Expect completed fit-check requests to rise over 21 days. Watch qualified-opportunity rate as the guardrail. Revert if completion rises but qualification falls for two weekly reviews. Owner: Gabriel. That entry is inspectable. It also forces the hard conversation before the button changes: which result is this supposed to move, and what would make the team admit the change was wrong? The artefact can live in a table, a Board or a plain document. The tool is the cheap part. Discipline comes from creating the record before the change ships and linking it to the live page, ad, automation or analytics version. ##### Why native change histories are not a marketing record In 2026, [Google Ads keeps account changes for two years and lets you undo most reversible changes for 30 days](https://support.google.com/google-ads/answer/2454137?hl=en). That is useful audit history. It is still only one room in the building. [Meta Ads Manager activity history](https://www.facebook.com/help/messenger-app/289211751238030) records who changed an ad, what changed and when. [GA4 now allows up to 1,000 annotations per property](https://support.google.com/analytics/answer/15884203?hl=en), with notes attached to line-graph dates or written through the Admin API. On 5 May 2026, [Shopify added automatic analytics annotations](https://changelog.shopify.com/posts/annotations-bring-store-event-context-directly-to-your-analytics) for product events, store changes and system events. These are good controls. Use them. They still preserve different fragments: - Google Ads knows a budget changed, but not that the sales team rejected the last five enquiries. - Meta knows an audience changed, but not that the landing-page promise changed that morning. - GA4 can hold a note, but not the agreed rollback condition unless someone writes it. - Your CMS knows a page was published, but not which qualified outcome the page was meant to improve. - The CRM knows whether the lead became an opportunity, but rarely knows which exact site or ad decision preceded it. The marketing change log sits above those histories. It links the decision to the native evidence and the business outcome. It should not duplicate every automated event. Record the changes that could plausibly alter buyer behaviour, spend, measurement, compliance or the route to a sale. A [shared workspace for the work, assets, reporting and client context](https://sharphaw.com/sharp-os) earns its place when the decision stays attached to the work it changed. Otherwise, it is another place to upload files. ##### How to connect a change to a result without inventing causation The dangerous leap is simple: the number moved after the change, so the change caused the movement. Sequence is evidence worth investigating. It is not proof. Start with the judgement window you set before shipping. A homepage-message change may need several weeks of qualified traffic. A broken conversion tag should show a technical correction quickly. An SEO title change may take longer to be recrawled and settle. Using one review cadence for all three guarantees bad calls. Then inspect four things: - **Direction:** did the expected signal move the way the record predicted? - **Guardrail:** did lead quality, revenue, consent rate or another protected outcome get worse? - **Outside events:** did seasonality, an outage, a competitor move, a stock problem or a platform change arrive in the same window? - **Repetition:** does the pattern hold across another comparable page, audience or period? Use an experiment or holdout when the traffic, risk and platform make one practical. Otherwise, say what the evidence can support: "This change aligns with the improvement and survived the guardrail" is honest. "This change caused the improvement" needs more. That distinction protects the founder twice. It stops a partner claiming credit for every green arrow, and it stops the team reversing useful work because one noisy week looked bad. Consider a Google Ads example. A budget rises on Monday. Form submissions rise by Friday, but qualified opportunities stay flat and cost per qualified opportunity worsens. The platform graph looks positive. The change log says the guardrail failed. Keep the evidence; reverse the budget decision. The dashboard did its job. The pre-written rule made the decision. ##### When to keep, reverse or repeat a marketing change Three choices are enough at review time: keep, reverse or repeat under a cleaner condition. "Wait and see" is allowed only with a new review date and a reason. Keep the change when the expected signal improves, the guardrail holds and no stronger outside explanation appears. Record the outcome and leave the original prediction intact. Editing the prediction after the result destroys the trail. Reverse it when the rollback condition fires. Do not soften the threshold because the work took a week or the new design looks better. Sunk effort is not a metric. Repeat it when the result is promising but ambiguous. Apply the same decision to a comparable service page, a second region or another audience while holding the rest steady enough to learn. Aim for a better next decision than the one you would make from memory. Perfect laboratory causality is rarely available here. There is a tradeoff. A good change log makes simultaneous unlabelled changes uncomfortable. The work may look slower because one person can no longer change the page, the bid strategy and the lead-routing automation in the same afternoon without explaining how the review will separate them. Take that trade. Busy accounts create impressive activity feeds and terrible explanations. ##### The weekly habit that keeps the log alive Derrick Reimer described the Marketing Changelog he and Rob Walling used while building Drip: ["It was nothing fancy, just a Google Sheet with timestamps and descriptions of various marketing activities."](https://www.derrickreimer.com/changelogs/) The sheet worked because they used it when metrics changed. The stronger version adds the decision fields before the activity. Keep the weekly habit small: 1. Open the change log before the work review. 2. Add records for changes scheduled to ship that week. 3. Review entries whose judgement date has arrived. 4. Link the native history, page version, creative, automation run or CRM view that carries the evidence. 5. Choose keep, reverse, repeat or wait with a dated reason. Ten disciplined minutes beats an hour of reconstructing four platforms after the number moves. One owner should protect the format, but everyone who can change the site, ads, content, tracking or automation should be able to add a record. The log also sharpens prioritisation. If a proposed change has no expected signal, guardrail or review date, it is probably an opinion wearing a task label. Either define the decision or do not ship it yet. That is how weekly work compounds. The next review inherits the reasoning, not only the output. ##### Frequently asked questions **What is a marketing change log?** A marketing change log is a dated record of meaningful changes to websites, ads, content, analytics and automations. A useful entry includes the reason, owner, expected signal, judgement window, guardrail and rollback condition, so later performance movement can be investigated against a decision made before the result appeared. **What should a marketing change log include?** Record the exact change, the problem it addresses, one owner, the metric or behaviour expected to move, the earliest fair review date, a protected guardrail and a rollback condition. Link the native platform history or live artefact. Add the final keep, reverse or repeat decision without rewriting the original prediction. **Does GA4 have annotations?** Yes. Google Analytics 4 supports annotations on reports with line graphs and through the Admin API. Google says each property can hold up to 1,000 annotations. Use them for dated context inside GA4, then keep the cross-channel decision and rollback rule in the main marketing change log. **How long does Google Ads change history last?** Google Ads shows account and campaign changes from the past two years. Most change types that support undo can be reversed for 30 days. Keep a separate marketing change log for longer-term memory and for the reason, expected business outcome, guardrail and CRM result that Google Ads does not store. ##### Turn the work trail into a decision trail A marketing change log does not make every result explainable. It makes guessing visible. That alone changes the quality of the review. Record the decision before the page, ad, article or automation changes. Set the signal, guardrail and rollback point while nobody knows the outcome. Then let the evidence argue back. Every SharpHaw subscription includes [SharpOS](https://sharphaw.com/sharp-os), one shared workspace for the work, assets, reporting and client context. [See the current Plans](https://sharphaw.com/plans), or [request a focused fit call](https://sharphaw.com/contact). Bring one result nobody can explain. Leave with the first version of the change log that should have existed before it moved. Digital work that compounds. ## Blog: index only The 124 older posts past the cap above. Full text at each URL. - [Why I built a marketing subscription, not another agency](https://sharphaw.com/blog/marketing-subscription-vs-agency-product-team): A marketing subscription should preserve context, ship weekly and keep one senior owner close. See the five product-team choices behind SharpHaw. - [Accessibility overlay: the widget cannot fix your sale](https://sharphaw.com/blog/accessibility-overlay-widget-cannot-fix-sale): An accessibility overlay cannot prove your checkout or enquiry path works. Use this release test to fix the code, forms and errors buyers actually touch. - [Your reviews are aging out of the ones buyers trust](https://sharphaw.com/blog/online-reviews-recency-buyers-trust): Your star average is a gate you clear once. After that, recency and replies win buyers and Google. See why fresh reviews beat a pile of old five-star ones. - [Marketing agency access: make every admin temporary](https://sharphaw.com/blog/marketing-agency-access): Marketing agency access should be owned, named, scoped and reviewed. Use this six-field audit to remove access debt, protect attribution and keep work moving. - [Buyers ask AI who to hire. Your name doesn't come up.](https://sharphaw.com/blog/get-recommended-by-ai-buyer-shortlists): Buyers ask AI who to hire, and it names only businesses it can verify. See why your name is missing and how to get recommended by AI. Check yours today. - [Google Ads Target CPA: the old number becomes the rule](https://sharphaw.com/blog/google-ads-target-cpa-old-number-becomes-rule): Google Ads Target CPA rules change on 17 August 2026. Learn which campaigns are affected and how to audit targets before the rollout. - [AI Max for Search can choose routes. Only you define the sale.](https://sharphaw.com/blog/ai-max-for-search-route-audit): AI Max for Search can change the query, ad and landing page. Run this four-part route audit before September, then judge every conversion in your CRM. - [Human-in-the-loop AI: what every approval must reveal](https://sharphaw.com/blog/human-in-the-loop-ai-approval-action-receipt): Human-in-the-loop AI needs more than an Approve button. See the action receipt, risk tiers and rollback test every consequential workflow should use. - [Your AI customer support knowledge base needs an expiry date](https://sharphaw.com/blog/ai-customer-support-knowledge-base-expiry-date): Learn how to keep an AI customer support knowledge base accurate with owners, expiry dates, change triggers, release tests and clear human handoffs. - [Your AI-built website looks done. It just doesn't sell.](https://sharphaw.com/blog/ai-built-website-looks-done-but-doesnt-sell): Your AI-built website looks finished but gets no enquiries. The reason isn't the copy or the design. It's three decisions the AI can't make. Here's the fix. - [The European Accessibility Act: exempt isn't the same as safe](https://sharphaw.com/blog/european-accessibility-act-exempt-small-business): The European Accessibility Act took effect in June 2025, but most small EU businesses are exempt. Here's why an inaccessible site still costs you customers. - [ChatGPT ads are live. Most European founders can't buy them yet](https://sharphaw.com/blog/chatgpt-ads-europe-the-founders-buy-in-test): ChatGPT ads reached six markets in 2026 and no EU country is one of them. The three questions to answer before you spend, and the free version you can run today. - [Every spam lead you count trains your ads to fail](https://sharphaw.com/blog/spam-leads-training-your-ads-to-fail): Spam leads don't just clog your inbox — every junk form-fill you count as a conversion teaches Meta and Google to buy you more. Here's the fix. - [AI crawlers: block the training bots, feed the ones that cite you](https://sharphaw.com/blog/block-ai-crawlers-training-bots-vs-answer-bots): Block AI crawlers the right way: stop the training-only bots like GPTBot, but let the answer bots cite you. Why llms.txt won't help and robots.txt isn't a wall. - [Automation monitoring: how to know your automations still work](https://sharphaw.com/blog/automation-monitoring-silent-failures-small-business): Automations fail without warning and keep failing until a customer notices. Automation monitoring (a heartbeat, an alert, an owner) catches the break first. - [Should you add WhatsApp to your website? Depends where you sell](https://sharphaw.com/blog/should-you-add-whatsapp-to-your-website): Should you add WhatsApp to your website? For European service businesses the answer splits by market. A decision guide, with GDPR and reply speed. - [Core Web Vitals INP: test the click that earns the sale](https://sharphaw.com/blog/core-web-vitals-inp-test-click-earns-sale): Core Web Vitals INP can fail while Lighthouse shows 99. See which click, tap or keypress slows buyers, then fix the action instead of chasing the score. - [Google Search Console hides your best queries. On purpose.](https://sharphaw.com/blog/google-search-console-hides-your-best-queries): Google Search Console omits your lowest-volume, highest-intent queries by design. Here is what the report gets right, and what expires after 16 months. - [Marketing prioritisation: fix the bottleneck, not the channel](https://sharphaw.com/blog/marketing-prioritisation-fix-the-bottleneck-not-the-channel): Marketing prioritisation should start with the bottleneck. Map the route to qualified enquiries, find the broken handoff, and choose the next repair. - [Service area pages SEO: publish only where you can prove work](https://sharphaw.com/blog/service-area-pages-seo-prove-city-before-publishing): Service area pages SEO works when each city has real proof, lead routing and measurement. Use the six-field check before you publish another page today. - [Meta ads learning phase: why weekly tweaks are backwards](https://sharphaw.com/blog/meta-ads-learning-phase-weekly-tweaks-backwards): Meta ads learning phase resets hide inside weekly tweaks. See which edits matter, audit the work trail, and know when leaving it alone is the senior move. - [Marketing attribution for small business only works with receipts](https://sharphaw.com/blog/marketing-attribution-for-small-business-evidence-trail): Marketing attribution for small business starts with a six-field receipt. Build a source-to-revenue trail before another dashboard tries to claim the sale. - [Website security isn't a plugin. It's a job nobody owns.](https://sharphaw.com/blog/small-business-website-security-maintenance-ownership): A hacked small-business site rarely looks hacked. Website security is a maintenance job someone must own, not a plugin you buy. Here's the 15-minute check. - [A marketing knowledge base should store decisions, not files](https://sharphaw.com/blog/marketing-knowledge-base-decisions-not-files): A marketing knowledge base should preserve approved decisions, proof and priorities so every new hire, freelancer or partner can act without a fresh briefing. - [Your LinkedIn company page was never going to work](https://sharphaw.com/blog/linkedin-company-page-vs-founder-led-posting): Buyers check the founder before they book a call. Why a LinkedIn company page can't build that trust — and the one-post-a-week founder system that can. - [Service page copy has one overlooked job: say no](https://sharphaw.com/blog/service-page-copy-overlooked-job-say-no): Learn how service page copy can qualify better-fit buyers, reduce vague enquiries, set clear boundaries, and turn form fills into useful sales calls now. - [You bought AI automation. You still don't have your hours back.](https://sharphaw.com/blog/ai-automation-didnt-give-you-your-hours-back): AI automation isn't saving you time because the tool is only 10% of the job. Here's the 70% that actually gives an owner-operated business its hours back. - [EU AI Act labelling: what marketers must disclose in August](https://sharphaw.com/blog/eu-ai-act-labelling-marketing-content-august-2026): EU AI Act labelling starts in August 2026. See which marketing assets need disclosure, who owns the decision, and the five-field review trail to build now. - [Your first marketing hire won't take marketing off your plate](https://sharphaw.com/blog/your-first-marketing-hire-wont-take-marketing-off-your-plate): Your first marketing hire won't take marketing off your plate — it makes you the manager. The real cost, the risk, and how EU founders should decide. - [SEO content brief: the 6 decisions most templates miss](https://sharphaw.com/blog/seo-content-brief-decisions-templates-miss): An SEO content brief needs six founder decisions before writing starts. Approve the reader, thesis, proof, CTA and success measure before the first draft lands. - [Should you pause your ads in August? Not the way you think](https://sharphaw.com/blog/should-you-pause-your-ads-in-august-europe): Thinking of pausing your ads in August? For European founders, going dark costs more than it saves. What to cut, keep, and fix for September. - [Voice of customer interview questions before a homepage rewrite](https://sharphaw.com/blog/voice-of-customer-interview-questions-before-a-homepage-rewrite): Use voice of customer interview questions to find buying triggers, objections and proof, then turn five interviews into a sharper homepage brief that converts. - [Internal linking strategy: connect every post to the offer](https://sharphaw.com/blog/internal-linking-strategy-connect-every-post-to-the-offer): Build an internal linking strategy that helps Google find pages and guides buyers from useful content to the right offer, proof, or next step. See the system. - [Call tracking only works after the phone rings](https://sharphaw.com/blog/call-tracking-only-works-after-the-phone-rings): Call tracking is not a call counter. See the five-field handoff that connects Google Ads, phone enquiries and real sales without recording every call. - [Content distribution checklist: stop shipping posts into silence](https://sharphaw.com/blog/content-distribution-checklist-stop-shipping-posts-into-silence): Content distribution checklist for founders: turn every post into email, social, sales follow-up, links, and measured next actions. - [Google Tag Manager audit: stop trusting old tags](https://sharphaw.com/blog/google-tag-manager-audit-stop-trusting-old-tags): Google Tag Manager audit guide for founders: find stale tags, duplicate events, consent gaps, and false ad signals before reports steer your spend. - [Booking page conversion: the highest-intent page you never test](https://sharphaw.com/blog/booking-page-conversion-the-highest-intent-page-you-never-test): Booking page conversion is your highest-intent, least-audited number. Fix the two leaks losing your best calls: friction and no-shows. - [Homepage hero copy: stop making buyers decode your offer](https://sharphaw.com/blog/homepage-hero-copy-stop-making-buyers-decode-your-offer): Homepage hero copy should clarify the offer, buyer fit, proof, and next step before visitors scroll. Use this first-screen audit before a redesign. - [Referrals aren't luck. You just never built the system](https://sharphaw.com/blog/referrals-aren-t-luck-you-just-never-built-the-system): Customer referrals are your cheapest, best-converting channel. Most founders run them on luck. Build the trigger, asset, and tracked destination that gets more. - [Agency renewal: check the work trail before you sign again](https://sharphaw.com/blog/agency-renewal-check-the-work-trail-before-you-sign-again): Agency renewal guide for founders: inspect shipped work, ownership, decisions, numbers, and the next plan before you sign again. - [Why Performance Max looks like it's working — and probably isn't](https://sharphaw.com/blog/why-performance-max-looks-like-it-s-working-and-probably-isn-t): Google Performance Max can show a strong return and still lose you money. Why it flatters small budgets, cannibalises brand search, and when to avoid it. - [A website chatbot is a promise to reply. Most sites break it](https://sharphaw.com/blog/a-website-chatbot-is-a-promise-to-reply-most-sites-break-it): A website chatbot is a promise to reply, and most sites break it. See when live chat or an AI support assistant helps, when it hurts, and what to do instead. - [About page copy: stop hiding the person buyers trust](https://sharphaw.com/blog/about-page-copy-stop-hiding-the-person-buyers-trust): About page copy should prove who is responsible, how work happens, and what buyers should do next before they trust you enough to book a call. - [First-party data marketing: stop renting customer memory](https://sharphaw.com/blog/first-party-data-marketing-stop-renting-customer-memory): First-party data marketing works when CRM, website, ads, email, and consent data form one owned customer-memory loop. See the checks. - [Website audit report: the PDF is not the work](https://sharphaw.com/blog/website-audit-report-the-pdf-is-not-the-work): A website audit report should become a fix queue with owners, evidence, and retests, not a PDF full of scores. See what to demand before you pay. - [Your link preview is the ad you never designed](https://sharphaw.com/blog/your-link-preview-is-the-ad-you-never-designed): The link preview that unfurls when someone shares your URL is your most-shared marketing, and usually broken. What Open Graph needs, fixed in ten minutes. - [CRM hygiene: stop losing leads after the form](https://sharphaw.com/blog/crm-hygiene-stop-losing-leads-after-the-form): CRM hygiene guide for founders: keep source, owner, status, and next action clear so website, ads, and content leads do not vanish after the form each week. - [Your Google Business Profile outsells the website you obsess over](https://sharphaw.com/blog/your-google-business-profile-outsells-the-website-you-obsess-over): For local searches your Google Business Profile wins the call in the map pack, not your homepage. How Google ranks it and the weekly work that keeps you there. - [UTM naming convention: stop trusting broken campaign data](https://sharphaw.com/blog/utm-naming-convention-stop-trusting-broken-campaign-data): UTM naming convention guide for founders: fix source, medium, campaign, and CRM handoffs before broken reports steer your spend. - [Brand consistency: why your ads and website disagree](https://sharphaw.com/blog/brand-consistency-why-your-ads-and-website-disagree): Brand consistency fails when ads, website, content, proof, and CTA disagree. Use this founder-ready audit before buying more traffic. - [Marketing asset library: stop losing files between vendors](https://sharphaw.com/blog/marketing-asset-library-stop-losing-files-between-vendors): Marketing asset library guide for founders: keep approved files, source assets, versions, permissions, and handoffs clear before vendors change. - [Your website has a bug only a session recording will show you](https://sharphaw.com/blog/your-website-has-a-bug-only-a-session-recording-will-show-you): Your analytics show that visitors leave, not why. See how session recordings and heatmaps reveal the conversion bugs costing your site enquiries. - [Website navigation audit: stop hiding your best offer](https://sharphaw.com/blog/website-navigation-audit-stop-hiding-your-best-offer): Run a website navigation audit that shows buyers your offer, proof, price, and next step before the menu costs you enquiries. - [Negative keywords are sales inbox work, not cleanup](https://sharphaw.com/blog/negative-keywords-are-sales-inbox-work-not-cleanup): Negative keywords should improve Google Ads lead quality, not just tidy reports. See the weekly search-term and inbox loop founders should ask for. - [AI meeting notes automation: turn calls into shipped tasks](https://sharphaw.com/blog/ai-meeting-notes-automation-turn-calls-into-shipped-tasks): AI meeting notes automation should turn calls into owned tasks, deadlines, and visible work. Use the founder-ready workflow before buying another tool. - [Marketing approval process: why weekly shipping stalls](https://sharphaw.com/blog/marketing-approval-process-why-weekly-shipping-stalls): Fix the marketing approval process that stalls weekly shipping. Learn how one owner, one review place, and one deadline keep work moving. - [Lead quality vs lead quantity: stop bad-fit enquiries](https://sharphaw.com/blog/lead-quality-vs-lead-quantity-stop-bad-fit-enquiries): Lead quality vs lead quantity for founders: stop bad-fit enquiries by measuring fit, intent, source, outcome, and the next fix before you scale spend. - [Ad account ownership: the exit clause founders miss](https://sharphaw.com/blog/ad-account-ownership-the-exit-clause-founders-miss): Ad account ownership guide for founders: see who controls Google Ads, Meta, pixels, billing, and data before you sign with an agency. - [FAQ page SEO: answer buyers before the call](https://sharphaw.com/blog/faq-page-seo-answer-buyers-before-the-call): FAQ page SEO in 2026 is a buyer-trust job. Learn how to answer real questions, use schema safely, and turn FAQs into booked calls. - [Your website copy won't convert by swapping 'we' for 'you'](https://sharphaw.com/blog/your-website-copy-won-t-convert-by-swapping-we-for-you): Swapping 'we' for 'you' won't fix website copy that doesn't convert. The real fix: write your homepage in your buyers' own words — here's how to harvest them. - [Content refresh strategy: fix posts that should still sell](https://sharphaw.com/blog/content-refresh-strategy-fix-posts-that-should-still-sell): Content refresh strategy for founders: use Search Console, CRM, and offer fit to refresh posts that still deserve enquiries before publishing more. - [Consent Mode v2: the ads data gap European founders miss](https://sharphaw.com/blog/consent-mode-v2-the-ads-data-gap-european-founders-miss): Consent Mode v2 affects Google Ads measurement in Europe. Learn the checks founders should run before bad consent signals hide real enquiries. - [Website trust signals founders need before testimonials](https://sharphaw.com/blog/website-trust-signals-founders-need-before-testimonials): Website trust signals for founders without testimonials: show process, proof, ownership, and next-step clarity so sceptical buyers keep reading and book. - [Domain ownership: the login that can take you offline](https://sharphaw.com/blog/domain-ownership-the-login-that-can-take-you-offline): Domain ownership is not the same as owning your website code. See who really controls your domain and DNS, and how to check before site and email go dark. - [Meta ads creative fatigue: the quiet budget leak founders miss](https://sharphaw.com/blog/meta-ads-creative-fatigue-the-quiet-budget-leak-founders-miss): Meta ads creative fatigue explained for founders: spot tired winners, check the right metrics, and refresh creatives before budget leaks. - [Prices on your website: hide them, keep the wrong buyers](https://sharphaw.com/blog/prices-on-your-website-hide-them-keep-the-wrong-buyers): Should you put prices on your website? For most owner-operated European businesses, hiding your price loses serious buyers and wastes your time. The senior fix. - [SharpOS data after cancellation: what founders keep](https://sharphaw.com/blog/sharpos-data-after-cancellation-what-founders-keep): SharpOS data after cancellation explained: what founders should keep, export, and own before they trust any marketing workspace. - [Cookie banner: the most expensive checkbox on your site](https://sharphaw.com/blog/cookie-banner-the-most-expensive-checkbox-on-your-site): Your cookie consent banner quietly costs you conversions, hides 30-60% of your analytics, and is probably still non-compliant. The senior fix for European sites. - [Email deliverability: why one in six emails never arrives](https://sharphaw.com/blog/email-deliverability-why-one-in-six-emails-never-arrives): About one in six emails never reaches the inbox — and your subject line isn’t why. The email deliverability records to fix first, and what changed in 2024–2025. - [Marketing subscription first 30 days: what should ship](https://sharphaw.com/blog/marketing-subscription-first-30-days-what-should-ship): Marketing subscription first 30 days explained: see what should ship, what can wait, and which warning signs to catch before month two. Use the checklist. - [A/B testing needs traffic you don't have. Fix this first.](https://sharphaw.com/blog/a-b-testing-needs-traffic-you-don-t-have-fix-this-first): A/B testing needs more traffic than most small European sites have. Why split tests stall before they prove anything - and the senior move that lifts conversion instead. - [Multilingual website: more languages don't mean more markets](https://sharphaw.com/blog/multilingual-website-more-languages-don-t-mean-more-markets): A multilingual website only helps when each language is fully localised. See which European markets earn a real site and which should stay in clean English. - [Agency client portal: what clients should see weekly](https://sharphaw.com/blog/agency-client-portal-what-clients-should-see-weekly): Agency client portal checklist for founders: see weekly proof, approvals, metrics, files, blockers, and next steps your agency should show before you sign. - [Conversion tracking: the dashboard says yes, the inbox says no](https://sharphaw.com/blog/conversion-tracking-the-dashboard-says-yes-the-inbox-says-no): Your ad dashboard says conversions are climbing; your inbox says otherwise. Here's how conversion tracking tied to real enquiries shows what actually works. - [Build an email list before Google stops sending you traffic](https://sharphaw.com/blog/build-an-email-list-before-google-stops-sending-you-traffic): Social reach is shrinking and most EU Google searches end without a click. The one audience you actually own is your email list - why it matters, and how to build one in Europe without becoming a spammer. - [Your contact form is where European enquiries quietly die](https://sharphaw.com/blog/your-contact-form-is-where-european-enquiries-quietly-die): European buyers want to message you, not fill in a contact form. Why the form leaks enquiries — and the conversion paths that actually win them. - [Retargeting in Europe: why the pixel playbook quietly died](https://sharphaw.com/blog/retargeting-in-europe-why-the-pixel-playbook-quietly-died): Retargeting for European businesses still works — but the pixel playbook broke under EU consent, Safari and iOS. The first-party version that still delivers. - [Marketing automation isn't saving you time. Kill this one.](https://sharphaw.com/blog/marketing-automation-isn-t-saving-you-time-kill-this-one): Most marketing automation mistakes aren't technical. Here's why automation steals time from small European teams, and the one automation to kill first. - [Marketing subscription vs freelancers: the hours no one bills](https://sharphaw.com/blog/marketing-subscription-vs-freelancers-the-hours-no-one-bills): Marketing subscription vs freelancers: the hidden coordination cost EU founders pay in hours, not invoices, plus 6 line items to add before you sign. - [Weekly shipping in a marketing subscription: what really lands](https://sharphaw.com/blog/weekly-shipping-in-a-marketing-subscription-what-really-lands): "Weekly shipping" in a marketing subscription should mean a live change every week — a page, an ad set, a post, an automation. Here's what really lands, and how to tell real shipping from busywork. - [AI-search content engine: 5 posts to publish as clicks shrink](https://sharphaw.com/blog/ai-search-content-engine-5-posts-to-publish-as-clicks-shrink): AI search cut organic clicks 61%. An AI-search content engine fixes it: the 5 post types ChatGPT and Perplexity cite, a weekly cadence, and a citation test. - [Landing page conversion audit: 9 checks before you blame ads](https://sharphaw.com/blog/landing-page-conversion-audit-9-checks-before-you-blame-ads): Clicks but no leads? Run this 9-point landing page conversion audit to find the post-click leak — message match, CTA, forms, speed — before you spend more on ads. - [Why your agency dashboard looks busy but proves nothing](https://sharphaw.com/blog/why-your-agency-dashboard-looks-busy-but-proves-nothing): Your agency dashboard looks busy, but impressions and optimisations are not progress. The four questions a marketing report must answer before you trust it. - [Why your Meta ads bleed budget: a 3-step founder's diagnostic](https://sharphaw.com/blog/why-your-meta-ads-bleed-budget-a-3-step-founder-s-diagnostic): Meta ads wasting budget? Diagnose the real leak in three steps — signal, structure, then your post-click offer — before you spend another euro. - [Lead response time: the 5-minute gap costing EU founders deals](https://sharphaw.com/blog/lead-response-time-the-5-minute-gap-costing-eu-founders-deals): Lead response time decides the deal: reply within 5 minutes and you're up to 100x more likely to connect than at 30. How EU founders close the 47-hour gap. - [The 5-hour AI marketing stack a solo European founder can ship](https://sharphaw.com/blog/the-5-hour-ai-marketing-stack-a-solo-european-founder-can-ship): AI marketing tools every solo European founder actually needs — four narrow-job tools, one weekly cadence, five hours of work, and the gaps the stack will not fill. - [Meta ads or Google ads: the pick-one test for EU founders](https://sharphaw.com/blog/meta-ads-or-google-ads-the-pick-one-test-for-eu-founders): Meta ads or Google ads? A three-question test for European founders, plus the budget math behind why splitting between both starves each platform. - [Marketing agency FAQ: 9 answers founders need before signing](https://sharphaw.com/blog/marketing-agency-faq-9-answers-founders-need-before-signing): Marketing agency FAQ for founders: check ownership, reporting, access, cancellation, AI use, pricing model, and weekly process before you sign. - [AI content agency: 6 checks before you outsource your blog](https://sharphaw.com/blog/ai-content-agency-6-checks-before-you-outsource-your-blog): Hiring an AI content agency? Use six checks to protect your blog, brand voice, sources, ownership, and search visibility before you sign. - [Modern business website in 2026: 7 patterns, 5 to delete](https://sharphaw.com/blog/modern-business-website-in-2026-7-patterns-5-to-delete): What a modern business website needs in 2026: 7 specific patterns to ship and 5 legacy elements to delete, anchored to AI search, conversion, and weekly shipping. - [Track AI-search traffic when GA4 calls it 'Direct'](https://sharphaw.com/blog/track-ai-search-traffic-when-ga4-calls-it-direct): AI-search traffic from ChatGPT and Perplexity often lands in GA4 as Direct. Four signals — channel groups, form questions, server logs, citation tracking — pull it back into view. - [Business website requirements: 7 checks before you rebuild](https://sharphaw.com/blog/business-website-requirements-7-checks-before-you-rebuild): Business website requirements for 2026: clarity, speed, accessibility, AI search, ownership, and measurement before you rebuild. - [Marketing agency pricing: why ours is public and most are not](https://sharphaw.com/blog/marketing-agency-pricing-why-ours-is-public-and-most-are-not): Marketing agencies that hide their pricing usually have three reasons — none benefit the buyer. Why we publish ours, and a 5-check pass for any agency page. - [Senior-led website agency: 5 changes after you sign](https://sharphaw.com/blog/senior-led-website-agency-5-changes-after-you-sign): Senior-led website agency guide for founders: see what changes in decisions, reports, ownership, and weekly website improvements, with a 5-check hiring test. - [Website project brief: stop becoming the project manager](https://sharphaw.com/blog/website-project-brief-stop-becoming-the-project-manager): Website project brief guide for founders: define goals, scope, content, approvals, technical guardrails, and change rules before your next build starts. - [Marketing agency case studies: 5 proof gaps to check](https://sharphaw.com/blog/marketing-agency-case-studies-5-proof-gaps-to-check): Marketing agency case studies can mislead. Check baseline, scope, measurement, fit, and work trail before you trust the result. - [Marketing agency reports: 7 questions when green arrows lie](https://sharphaw.com/blog/marketing-agency-reports-7-questions-when-green-arrows-lie): Marketing agency reports should prove shipped work, real movement, lead quality, and next steps. Use these 7 questions before you keep paying. - [3 AI ops automations every EU founder should ship this quarter](https://sharphaw.com/blog/3-ai-ops-automations-every-eu-founder-should-ship-this-quarter): Three AI ops automations to ship in 90 days for European founders — document triage, recurring reports, support intake. GDPR notes included. - [Marketing stack audit: 6 tools your agency should replace](https://sharphaw.com/blog/marketing-stack-audit-6-tools-your-agency-should-replace): Marketing stack audit guide for founders: review tool ownership, usage, data flow, and six agency systems worth replacing before you sign. - [Google Ads agency Europe: 7 checks before you sign](https://sharphaw.com/blog/google-ads-agency-europe-7-checks-before-you-sign): Google Ads agency Europe checklist for founders: check account access, tracking, reports, wasted-click controls, and exit terms before you sign. - [How to get ChatGPT to cite your blog post: 2026 GEO playbook](https://sharphaw.com/blog/how-to-get-chatgpt-to-cite-your-blog-post-2026-geo-playbook): AI engines cite specific blog posts using a tight set of writing patterns. Nine 2026 GEO patterns to make ChatGPT and Perplexity cite yours — with three tests. - [Marketing agency discovery call: 4 questions before you sign](https://sharphaw.com/blog/marketing-agency-discovery-call-4-questions-before-you-sign): Before you sign with a marketing agency, ask these 4 questions on the discovery call. They separate senior partners from vendors who go silent after invoice one. - [Marketing agency testimonials: 4 checks before you buy](https://sharphaw.com/blog/marketing-agency-testimonials-4-checks-before-you-buy): Marketing agency testimonials can mislead. Use four proof checks to inspect results, fit, gaps, and live work before you buy. - [How to fire your marketing agency without losing your work](https://sharphaw.com/blog/how-to-fire-your-marketing-agency-without-losing-your-work): A seven-step exit checklist for European founders: recover your domain, website code, content, ad accounts, and analytics before notice expires. - [Month-to-month marketing subscription: 5 terms that matter](https://sharphaw.com/blog/month-to-month-marketing-subscription-5-terms-that-matter): Month-to-month marketing subscription terms explained: ownership, cancellation, scope, access, and reporting — the 5 contract terms EU founders must check before signing. - [3 AI automations most EU founders haven't shipped yet](https://sharphaw.com/blog/3-ai-automations-most-eu-founders-haven-t-shipped-yet): Three AI automations (lead follow-up, content repurposing, client onboarding) that take repetitive admin off a European business owner's week. - [Agency pricing: fixed monthly beats hourly for EU founders](https://sharphaw.com/blog/agency-pricing-fixed-monthly-beats-hourly-for-eu-founders): Hourly, retainer, or fixed monthly — which agency pricing model fits EU founders? A plain-English breakdown of all three models, where each breaks, and how to choose. - [AI Overviews are costing European founders traffic: 3 fixes](https://sharphaw.com/blog/ai-overviews-are-costing-european-founders-traffic-3-fixes): Google AI Overviews cut 61% of organic clicks. European service businesses face the sharpest exposure. Three structural fixes — no full overhaul needed. - [Async marketing agency: weekly shipping without meetings](https://sharphaw.com/blog/async-marketing-agency-weekly-shipping-without-meetings): Learn how an async marketing agency replaces recurring meetings with weekly updates, dashboards, focused shipping, and clearer decisions for founders. - [How to Tell If Your Website Is Actually Selling: A 12-Point Conversion Audit for Founders](https://sharphaw.com/blog/how-to-tell-if-your-website-is-actually-selling-a-12-point-conversion-audit-for-founders): A 12-point website conversion audit founders can run in 30 minutes. Score yes/no, fix the no's first, and stop redesigning before diagnosing. - [Weekly Marketing Metrics: The 7 Numbers Founders Should Track (and the 12 to Stop Watching)](https://sharphaw.com/blog/weekly-marketing-metrics-the-7-numbers-founders-should-track-and-the-12-to-stop-watching): The 7 weekly marketing metrics that actually drive decisions for European founders — plus the 12 vanity numbers to stop watching this week. - [Website redesign vs continuous improvement: a founder's framework](https://sharphaw.com/blog/website-redesign-vs-continuous-improvement-a-founder-s-framework): When a full website redesign actually earns its cost — and when continuous improvement wins. A decision framework for founders tired of restarting every three years. - [AI automations for small businesses: five workflows that actually save time](https://sharphaw.com/blog/ai-automations-for-smbs-five-workflows-that-actually-save-time): Five AI automations every small European business should be running in 2026 — lead triage, support, invoice ops, meetings, and knowledge. GDPR notes included. - [Meet SharpOS: the shared workspace behind every SharpHaw subscription](https://sharphaw.com/blog/meet-sharpos-the-shared-workspace-behind-every-sharphaw-subscription): SharpOS is the shared workspace bundled with every SharpHaw subscription — Pages, Boards, Audits, Customers, Media Center, Analytics in one place. - [Subscription marketing agency vs project: which fits a European business](https://sharphaw.com/blog/subscription-marketing-agency-vs-project-which-fits-a-european-smb): Subscription marketing agency vs project: 12-month euro cost math, a 5-question decision matrix, and when to pick neither — for European small businesses. - [From 40 Hours to 4: Automating Your Marketing Content Pipeline with AI](https://sharphaw.com/blog/from-40-hours-to-4-automating-your-marketing-content-pipeline-with-ai): Learn how to automate your marketing content pipeline with AI and turn one idea into blog posts, social content, and distribution-ready assets faster. - [Why Your Beautiful Website Redesign Just Killed Your SEO (And How to Fix It)](https://sharphaw.com/blog/why-your-beautiful-website-redesign-just-killed-your-seo-and-how-to-fix-it): Did your traffic drop after a website redesign? Discover the 5 most common technical SEO mistakes designers make and the exact steps to restore your lost traffic. - [Programmatic SEO vs. Spammy AI Content: The Growth Strategy That Actually Ranks in 2026](https://sharphaw.com/blog/programmatic-seo-vs-spammy-ai-content-the-growth-strategy-that-actually-ranks-in-2026): Discover the critical difference between AI content spam and true Programmatic SEO (pSEO), and learn how to build a scalable, data-driven traffic engine that Google loves. - [Why Your Website Project Keeps Dragging On (And How to Fix It)](https://sharphaw.com/blog/why-your-website-project-keeps-dragging-on-and-how-to-fix-it): Website projects should not take six months. Discover why they drag on forever and how to fix your process for fast, reliable delivery. - [The True Cost of Cheap Website Design](https://sharphaw.com/blog/the-true-cost-of-cheap-website-design): A $500 website is not a bargain. Discover the hidden costs of cheap web design and why investing right the first time saves you money. - [Why Agencies Go Silent: The Ghosting Problem](https://sharphaw.com/blog/why-agencies-go-silent-the-ghosting-problem): Why do agencies go silent? Learn the real reasons behind agency ghosting, how it hurts your business, and what a better model looks like. - [How to Turn Your Website Into Your Best Salesperson](https://sharphaw.com/blog/how-to-turn-your-website-into-your-best-salesperson): Stop chasing traffic and start converting visitors. Learn how to turn your website into a sales machine that generates leads and sales on autopilot. - [Why Your Web Agency Is Wasting Your Money (And What to Do Instead)](https://sharphaw.com/blog/why-your-web-agency-is-wasting-your-money-and-what-to-do-instead): The traditional web agency model often wastes time and budget. Learn why it happens and what to do instead to get better results. - [What Happens to Your Business When Your Website Stays the Same for 2 Years](https://sharphaw.com/blog/what-happens-to-your-business-when-your-website-stays-the-same-for-2-years): An outdated website quietly hurts trust, rankings, and conversions. Learn what happens when your site stays unchanged for too long.