Document in public on a “HQ” account
This playbook is about creating a 'HQ' account-a dedicated channel (like an X account or blog) to document your company's journey in public. It's not about marketing your product directly. It's about showing the process, the people, the wins, and the failures. You're building a brand around your brand, creating a loyal audience that is invested in your story, not just your features.
- Effort
- Medium
- Cost
- Low
- Time to first result
- 3-6 months
- Best for
- SaaS, Startups, Creator-led businesses
Save this strategy and send it to my inbox
Get the full playbook - scripts, tool stack and checklist - delivered as a single email you can act on today.
No spam. One email, and only what is worth reading.

Why Building in Public With a "HQ" Account Works
Trust is the currency of the internet. A polished corporate account tweeting marketing slogans builds very little of it. A 'HQ' account, showing the real people and the messy process behind the scenes, builds immense trust and authenticity. It proves there are thoughtful humans behind the logo. This human connection makes your brand more relatable, memorable, and defensible against competitors.
This strategy creates a powerful content flywheel that fuels your entire funnel. The stories you share attract talent, investors, partners, and, most importantly, customers. People who follow your journey are pre-sold on your mission and values before they even see a demo. This public documentation becomes a top-of-funnel asset that works for you 24/7, building a community of evangelists around your brand.
Three real examples
Buffer shares salaries, revenue, and diversity reports
Buffer is famous for its 'radical transparency'. They created a dedicated 'Transparency' dashboard on their site sharing everything from employee salaries and revenue numbers to diversity data and fundraising term sheets. This built a huge amount of trust and a massive audience who respected their openness, turning their blog into a major customer acquisition channel.
Source: BufferBasecamp (37signals) blogs about how they work
The founders of Basecamp have been blogging at 'Signal v. Noise' for over 20 years. They share their candid opinions on software, business, and design. They don't just sell project management software; they sell a philosophy of work. This thought leadership has established them as trusted voices, attracting customers who believe in their way of working.
Source: Signal v. NoiseLinear documents the details on X
Linear's X account is a masterclass in 'building in public' for a product-led company. They go beyond simple feature announcements, sharing the craft and obsession behind their decisions. By posting high-quality videos, changelogs, and insights into their design philosophy, they attract an audience of product builders who admire the quality of their work and, therefore, trust the quality of their tool.
Source: X.comThis playbook isn't just for founders. A Head of Product, Engineering, or Design can run their own 'HQ-style' account for their specific department to attract talent and build authority in their domain.
The step-by-step playbook
- 1
Step 1: Choose Your HQ Channel and Name
Decide on ONE primary channel to be your 'HQ'. X (formerly Twitter) is ideal for short-form updates and engagement. A blog is better for long-form thoughts. Name it something clear, like {YourCompany}HQ, or use the founder's personal account if they will be the main voice.
- 2
Step 2: Define Your Transparency Level
Hold a meeting and decide what you're willing to share. Will you share revenue (a la Buffer)? Product strategy? Team wins? Hiring processes? Technical challenges? Also, define what's off-limits (e.g., specific customer data, internal team disagreements).
- 3
Step 3: Create Content Pillars
Don't just post randomly. Define 3-5 content pillars. For example: 1) Weekly Metric Snapshot, 2) Product Behind-the-scenes, 3) A Lesson We Learned This Week, 4) Team Member Spotlight. This makes content planning easier.
- 4
Step 4: Document, Don't Create
The best content is already happening. Your job is to capture it. Take a screenshot of a funny Slack thread. Snap a photo of a whiteboard from a brainstorming session. Record a quick Loom video explaining a new feature. Don't invent content-just document your reality.
- 5
Step 5: Post Your 'Genesis' Post
Your first post should explain what you're doing. Announce that you're starting this 'build in public' experiment, what you'll be sharing, and why. This sets expectations and invites your first followers to join the journey.
- 6
Step 6: Engage Authentically
This is a two-way conversation. When people reply, answer them. Ask your audience questions. Thank people for their feedback. Block out 30 minutes every day just to reply and interact with people who are engaging with your story.
- 7
Step 7: Repurpose Your Content
A single public update can be repurposed in many ways. A long-form blog post about a failure can be turned into an X thread. Key quotes from the post can become standalone graphics for LinkedIn. A video of a product walkthrough can be chopped into short clips for social media.
Copy-Paste DM/Email to Invite Followers
Use this script to personally invite people you think would be interested in your journey. It's a low-pressure way to get your first true fans.
Subject: Following the {Your Company} journey
Hey {FirstName},
I saw you're interested in {Their Industry/Interest}. We're building {Your Company} to solve {Problem}, and we're documenting the entire journey in public-the wins, the losses, and the lessons.
We share everything from product-building insights to our growth metrics over at {Link to HQ Account}. Thought you might find it interesting to see how a startup is built from the inside.
Would be great to have you follow along.
Best,
{Your Name}Key Questions to Answer Before You Start
- What is our primary goal with this? (e.g., attract talent, build community, generate leads)
- Who is the 'person' behind the account? The founder? The marketing lead? A collective 'we'?
- What are our 'no-go' zones? What will we never share publicly?
- How will we handle negative feedback or public failures?
- What does success look like in 6 months? (e.g., follower count, sign-ups from this channel, inbound partner requests)
The most critical question is defining your 'no-go' zones. Setting clear boundaries early prevents difficult situations and protects your team and customers.
Recommended tools
Tally.so
Free, with paid plansUse this to create simple, beautiful forms to gather feedback, run surveys, or collect emails from your most engaged followers.
Screen Studio
$89 one-timePerfect for creating polished screen recordings of your product or internal processes to share as 'behind-the-scenes' content.
Jasper.ai
Starts at $39/moUse AI to help you turn raw notes, meeting transcripts, or data points into well-written threads, blog posts, or updates.
June.so
Starts at $79/moConnect June to your product to find interesting data and metrics (like 'most used feature' or 'power user habits') to share with your audience.
Prices are indicative and change - check the vendor before buying.
Do it faster with AI Prompts
To brainstorm content pillars
Act as a startup founder building a B2B SaaS product for {your_customer_persona}. We want to build in public on X. Our goal is to attract new users and build community. Brainstorm 5 content pillars (recurring themes) for our @{company_name}HQ account. For each pillar, provide 3 specific post examples.
To turn meeting notes into a public update
I'm the founder of a startup. Below are my messy notes from a product strategy meeting. Your task is to turn these notes into a concise, engaging, and transparent public update for our followers. The tone should be authentic and honest. End with a question to encourage discussion. Notes: ''' - We're behind on feature X. Team is a bit burnt out. - Debate: should we simplify the feature to ship faster, or delay to build it right? Decided to delay - quality is our main value. - User feedback on the beta is mixed. Some love it, some are confused by the UI. - Plan: pause new features next sprint, focus entirely on bug fixes and UI polish based on feedback. '''
To write an X thread about a failure
Write a 5-tweet X thread about a recent failure at our startup. The failure: we spent a month building a new feature that usage data shows nobody is using. The thread should be honest, share the lesson we learned, and explain what we're doing next. The tone should be humble, not defensive. Start with a hook that grabs attention.
Mistakes that kill this play
- Being too polished: Authenticity is the goal. If your 'behind the scenes' content looks like a professional marketing campaign, you've missed the point.
- Inconsistency: Building an audience requires showing up regularly. Disappearing for weeks at a time will kill your momentum.
- Broadcasting, not engaging: Don't just post and leave. The magic is in the replies and conversations with your audience.
- Sharing only the wins: This isn't a highlight reel. Sharing failures, struggles, and lessons learned builds more trust than just posting vanity metrics.
- Not having a clear voice: Decide if the account is the founder's voice, a team voice, etc., and stick to it. An inconsistent voice feels disjointed.
- Violating privacy: Get permission before you screenshot a team member's message or a customer's email. Set clear guidelines on privacy.
- Not linking back to the 'why': Always connect your journey back to the problem you're solving for customers. Context is everything.
Your First 7 Days
- Day 1: Choose your primary channel (e.g., X), create the account (e.g., @YourCompanyHQ), and write a clear bio explaining its purpose (e.g., 'The public journey of building {YourCompany}. The wins, losses, and lessons.').
- Day 2: Hold a 30-minute meeting with your team. Define your transparency boundaries and brainstorm your first 3-5 content pillars.
- Day 3: Write and post your 'genesis post'. Announce what you're doing, why you're doing it, and invite people to follow along for the ride.
- Day 4: Document something real from today. Take a screenshot of a piece of user feedback, a photo of a whiteboard, or a snippet of code. Post it with a short caption explaining the context.
- Day 5: Find one simple, interesting metric to share. It could be new users this week, website visitors, or even number of bugs squashed. Post it with a brief commentary on the number.
- Day 6: Dedicate 30 minutes to engagement. Reply to every comment you've received. Find 5-10 interesting people in your space and reply to one of their posts.
- Day 7: Review the engagement on your first week's posts. What resonated most? Use this insight to plan a few posts for the upcoming week.
Save this strategy and send it to my inbox
Get the full playbook - scripts, tool stack and checklist - delivered as a single email you can act on today.
No spam. One email, and only what is worth reading.