Over a decade doing search for technical B2B SaaS — the kind where the marketing site shares a repository with the product and ships when engineering ships. I work on two things, and both of them end in something written down.
Code review for the part of your site Google sees. Before each release I check whether it's about to cost you organic traffic and put the answer in writing — go, hold, or amend — then verify it in production within the hour.
See what's included →A senior organic function without hiring a growth team: strategy, technical search and GEO, landing pages that carry product weight, competitor intelligence, and reporting that says when something didn't work.
How it works →No case studies on this page. The work I've done for the last several years sits under other companies' names, and using their numbers to sell you something would tell you a lot about how I'd treat yours.
So instead: the method above, the actual deliverable format, a written kill condition on the pilot, and a conversation in which you can test whether I know your problem. When the first pilot produces a real record, it goes here — with permission, or not at all.