# Draft email to Tanya — onboarding requests To: tanya@culturefoundry.com Cc: rob@plusroi.com, nancy@culturefoundry.com, hans@culturefoundry.com Subject: Re: Meeting assets for Culture Foundry | Plus ROI are ready! (or: "Getting set up — access and a few details we'll need") --- Hi Tanya, Sorry I'm a bit delayed joining this conversation. I'm just sending through a few things we'll need to get set up. I've split this into what we need to get moving and what can follow over the next couple of weeks — please don't feel you need to solve it all at once. I've also noted where I suspect Hans or Nancy is the right person, so you can route rather than chase. ## 1. Google tools For now, myself, Rob, and Yulia (who you haven't met yet — she'll be doing much of the hands-on implementation) will be the primary people working on this. So we'll need access to the various Google tools for: * rob@plusroi.com * rian@plusroi.com * yulia@plusroi.com * and plusroi@gmail.com (our general company account) We'll be looking for the following. If you can't provide admin/full access, please provide what you're able: * **GA4** * **Google Search Console** — and if you know offhand whether it's set up as a domain property or just the https:// one, that's helpful * **Google Business Profile** — both the Seattle and Austin locations (access is granted per location, so it's two invitations) * **Bing Webmaster Tools** — worth adding to the list. Bing's index is what sits behind Copilot and a chunk of ChatGPT's search, so it matters more for the AI-visibility side of this work than most people expect * **GTM** (optional but nice to have for completeness. If shared, we'll have a quick look at what you have set up and whether we have any thoughts) * **Google Ads** (not needed, but if you want to share we'll have a look and make sure it's properly connected to the other tools for you, and see if anything stands out that should be fixed) Also worth knowing: any Looker Studio dashboards you already rely on, and whether you have subscriptions to any SEO tools (Semrush, Ahrefs, Moz, BrightLocal). I'd rather work with what you already trust than hand you a second set of numbers that disagrees with it. ## 2. One decision that unlocks a lot — your official name, address and phone This is the single most useful thing you can send back this week. A surprising amount of the checklist is waiting behind it — the citation cleanup, the profile updates, the footer, the location pages and the schema markup all have to match each other exactly, so we need one canonical version to work from: * **Business name** — you appear as both "Culture Foundry" and "Culture Foundry LLC" in different places. Which should we standardize on? * **Seattle address**, exactly as it should appear everywhere — including how you want the suite written (#200 vs Suite 200 vs Ste 200). We have 600 N 36th St #200. * **Austin address**, same thing — full street address and suite. * **Phone** — is 1-206-487-3330 the number for both, or does Austin have its own? * And just to confirm: the old Seattle address (5101 14th Ave NW) is fully retired, nothing still routing there? It sounds fussy, but inconsistent listings are actually worse than missing ones — they make Google unsure which version of you to trust. Locking this down is what lets the rest of the local work proceed. ## 3. Website and development — probably one for Hans Quite a lot of the checklist is development work, and as we discussed, your team will be doing the actual coding with us specifying and guiding. To do that well we need: * **CMS access** for myself and Yulia — individual logins rather than a shared one, if that's easy on your end. (I have site access already; mainly need to confirm it's admin-level and get Yulia set up.) * **A quick orientation to the stack.** We know it's a hybrid setup with Wagtail involved. What we really need to understand is what's editable in the CMS versus what's templated or hard-coded — specifically page titles, H1s, the footer, breadcrumbs, structured data, category page intros and author bios. That determines which items we can just do and which need to become tickets for your team. * **Staging environment** — URL and access, if there is one. * **How work should reach your developers.** Ticket system, who triages, and roughly what lead time we should plan around. I'd rather build our schedule around your team's real capacity than hand you a queue that outruns it. * Related: Nancy mentioned breadcrumbs not showing up. Anything your team already knows about why would save us some digging. ## 4. The urgent local items — a bit of legwork on your side Three things in the "do right away" tier depend on you more than on us: * **Reviews.** Seattle has one, Austin has none, and this is one of the strongest factors in whether a profile gets chosen. We'll write the wording and the process — what we need from you is a list of clients it's appropriate to ask, who's best placed to send the ask, and a heads-up on anyone who can't publicly endorse you for NDA or procurement reasons. We'd suggest a steady drip rather than a burst; a dozen reviews landing in one week looks manufactured. * **Photos.** Team, workspace and exterior shots for both offices. Seattle currently has one photo, Austin has none but the street view. If there's a brand asset folder we can pull from, even better. * **Existing directory listings.** Cleaning up the old Seattle address means editing listings across the web — Clutch, Yelp, BBB, LinkedIn, Crunchbase and so on. Wherever you already have a login for one of those, that access saves us weeks versus claiming each one from scratch. We'll also need an email address that's monitored for verification messages, and someone who can pick up the occasional verification phone call. Also, two quick confirmations: your profiles list you as open 24 hours on weekdays — is that intentional? (If it reflects support coverage rather than office hours, we should say that plainly on the site.) And Portland, Boulder and Sarasota are service areas with no physical office, correct? ## 5. Author bios — the biggest single opportunity, and it needs your people Cultivate already has named authors, archive pages and the underlying markup in place, which is further than most firms get. What's missing is real bios behind the bylines, and that's the largest credibility gap on the site for both Google and the AI tools. Could you pick the handful of people who'll be regular authors — three to six rather than everyone — and for each gather: specific expertise, credentials, years of experience, a photo, LinkedIn, and anything external like talks, published articles or certifications. The external links matter more than they look like they should; they're how the machines verify a person is real. While you're at it: **how many years have you been in business, and roughly how many clients or launches?** Concrete numbers like that aren't stated anywhere on the site right now, and they're one of the most quotable things you can give an AI tool. ## 6. The keyword conversation Rob mentioned wanting to sit down with you and Nancy on keywords before we get properly rolling. The main thing we need out of it is a business decision only you can make: **which services you most want to be found for.** Right now the site treats them fairly evenly, so nothing signals what you want to be known for. It'd also help to know which agencies you tend to lose to, so we can point the content work at the right targets. (And Hans, I haven't forgotten the "wagtail support" idea — I think there's something there.) Happy to get that booked whenever suits you both. ## 7. Housekeeping * Who approves published copy, and what turnaround should we plan for? Our timeline estimates assume reasonably quick approvals, so it's worth being realistic about it up front. * Do you want to work over email, or would a shared Slack channel be easier? * What cadence do you want for check-ins, and what day of the month works for the progress report? * Billing contact and any PO details, for the September invoice. * And on paperwork — Rob mentioned the email confirmation was enough for us, but if there's anything on your side you'd like signed, easier to sort now than mid-stream. One small request: for anything where there's genuinely only one shared login, please send it through a password manager share or a one-time secret link rather than in an email. We keep client credentials properly compartmentalized and it's much easier to do that from the start. That's a lot in one email — the genuinely time-sensitive pieces are the Google access, the name/address/phone decision, and getting the review and photo gathering started. Everything else can trickle in over the next couple of weeks. Rob will be sending through the workplan separately. Thanks Tanya — looking forward to getting into it. Rian