This is a past send for The Outpost, a weekly newsletter filled with realtime insights and tactics for building more impactful customer marketing programs. To get The Outpost in your inbox every week, subscribe right here.
Brayden again! Last week I told you a census survey has two moments that decide whether it was worth running. We covered the first one: everything that happens before you hit send.
This week, moment two: everything that needs to happen after the responses come in.
Our survey went live on June 30th. By July 6th, here’s what we’d shipped from the responses:
- 16 customer assets published in our library (dozens since that I’m still sifting through)
- 18 new G2 reviews, holding our 4.8 rating
- Enablement on new assets on our team all-hands
- 15 new hand-raisers for LinkedIn thought leadership
- 47 other advocates for webinars, referrals, customer stories, etc.
One week. And that’s what I want to dial in on. Week one culminates in a choice, one that makes or breaks all the effort you spent on getting folks to respond in the first place.
Do you bask in the glow of survey responses… or do you get to work?
Here’s the mindset shift: stop treating a census survey like a data pull. Data pulls end when the numbers come in. Campaigns, on the other hand, need a plan for the week after launch, not just launch day.
So, as my boss Alex put it to me in our 1:1 after the send: “what’s your plan of attack for this week”?
Here’s what I’d encourage:
Get proof into your evidence library fast, and make it searchable.
Uploading a batch of quotes is the easy part. Tagging them by product, use case, and persona so someone six months from now can actually find what they need is the element that makes the whole exercise worth it. This is also your moment to pull in anything sitting in adjacent tools, like new review-site activity. You (should have) just asked folks to complete a review as part of your survey, so it’s the perfect time to consolidate all your proof under one roof! We obviously drink our own champagne here and house everything in our UserEvidence library, but whatever tool you use, this is a step not to be missed.
Follow up on every advocacy signal while people still remember answering.
The last question of every customer survey we send out is:
Would you be willing to participate in any of the following advocacy activities?
Referrals, case study interest, thought leadership asks. These cool off fast, so hop to it! Just be sure to prioritize with intention: most advocates raise their hand for more than one activity (70% of our advocates did), so it’s on you to sequence the ask.
A referral that drives pipeline this quarter probably outranks a co-written blog post that can wait a month or two. Work the list with that lens.
And one last nuance I’d add: a soft yes still counts. If someone says they’d refer you but can’t name a person on the spot, that’s not a dead end. Follow up! Help them think through their own network. Or better yet, do that thinking for them. Pull up their connections on LinkedIn Sales Navigator and send them some names: “Looks like you know these five people who we can help. Any chance you’d introduce us?” That’s way easier than “who do you know who might be interested?”
You did the legwork. They just have to say yes.
Bring your team along as it happens, not after.
Share wins the week they land. This does not mean you have to wait until everything is perfectly curated and executed. It’s perfectly okay to tease out that more is a-comin’. A quick note in your team channel, a mention at your next all-hands, whatever fits your culture.
Two things happen when you do this: Your org sees customer marketing generating value in real time instead of hearing about it secondhand in a recap deck. And Sales and Product get reminded that new proof exists and is ready to use, right when it’s most useful to them.
Turn raw feedback into something leadership will actually read.
Confession time.
I started building the leadership readout the old fashioned way: spreadsheet open, copying and pasting responses into rows, tagging themes as I went. Twenty minutes in, I stopped cold and quite literally said out loud, “What the HECK am I doing?!” (a question we should all ask more often). I then took our full feedback set and handed it to Claude with a few prompts.
Two files came back.
First, an interactive HTML doc. One page, headline findings, charts, and clickable themes that drill straight down into the actual verbatims behind each one. No more toggling between a summary slide and a raw export trying to remember why a number looks the way it does.
Second, a companion Excel workbook with executive summary, theme tallies, investment-priority votes, full verbatim tabs so anyone can slice the data themselves, etc.
Nobody needs a medal for manually formatting a report leadership will skim in four minutes. Let AI do the busywork. Spend your saved time on the analysis and not the pivot tables.
Wrapping it up.
None of this requires a bigger team or more tools. It requires deciding, before your survey ever goes out, that the week after launch matters as much as launch day. Build that into your plan up front, and the survey stops being an annual chore and turns into one of the highest-leverage weeks your team runs all year.
If you’re building out your own survey and want a partner in thinking through the after, shoot me a message. Always happy to talk shop!
Talk soon,
Brayden
