You just got into YC. Or you are 2 weeks from Demo Day. The product is solid. The traction metrics tell a real story. But your LinkedIn presence? Your last post was a reshare of a TechCrunch article 4 months ago. Your headline still says "CEO at [Company]" with no indication of what you actually do or why anyone should care.
You have 14 days. Here is exactly what to do.
I have spent the past two years running marketing campaigns for 15+ B2B tech companies — physical AI, robotics, autonomous systems, industrial software, developer tools. The pattern I see over and over is this: the founders who treat Demo Day as a content event, not just a pitch event, walk away with 3-5x more follow-up meetings than those who show up with a great product and a dormant LinkedIn profile.
This is the exact 14-day sprint we run with founders. Not theory. Not "best practices." A day-by-day playbook built on 150+ validated content patterns across real B2B tech companies. The same framework that has generated enterprise pipeline for companies selling everything from LiDAR sensor fusion to autonomous inspection drones to real-time vehicle data platforms.
If you are a YC F25 or S25 founder, this is probably the most important marketing document you will read before Demo Day. I say that not because it is comprehensive, but because it is specific. Every template, every hook formula, every timeline recommendation is backed by data from companies that look like yours.
Why Demo Day Without LinkedIn Is Leaving Money on the Table
Let me give you the uncomfortable truth first: Demo Day generates awareness, not pipeline. The batch presentation, the investor meetings, the press coverage — those create a spike of attention. But attention without a conversion mechanism is just noise that fades.
LinkedIn is that conversion mechanism. Here is why it matters specifically for enterprise B2B:
Enterprise buyers research founders before taking meetings. This is not an opinion. According to LinkedIn's own B2B research, 72% of B2B buyers check a founder's LinkedIn profile before agreeing to a product demo. For enterprise deals — the kind where your ACV is $50K+ and the sales cycle involves 3-7 stakeholders — that number climbs higher. Your LinkedIn profile is not a social media page. It is the first page of your sales deck.
Demo Day creates the awareness. LinkedIn converts it to pipeline. When a VP of Engineering at a Fortune 500 sees your batch presentation, they are not going to fill out a contact form on your website. They are going to look you up on LinkedIn. What they find there determines whether they send you a connection request with a note that says "Let's talk" or move on to the next company in the batch.
After running campaigns for 15+ B2B tech companies, the pattern is consistent: founders who launch Demo Day with an optimized LinkedIn presence generate 3-5x more follow-up meetings than those who do not. That is the difference between leaving Demo Day with 8 warm enterprise conversations and leaving with 2.
The compounding effect is real. Demo Day attention decays fast. Within 72 hours, the spike is over. But if you have content in the feed during and after Demo Day, you are extending that attention window from 3 days to 30. Every post that lands during Demo Day week gets amplified by the ambient awareness your batch presentation created. Your content reaches people it never would have reached on a normal Tuesday.
The 14-Day Sprint Framework
This framework is designed to work backwards from Demo Day. If your Demo Day is on Day 14, you start this sprint on Day 1 — exactly two weeks out. If you have less time, compress Days 1-3 into a single day and prioritize the content production days.
The sprint has four phases: Positioning Foundation (Days 1-3), Content Production (Days 4-7), Distribution Engine (Days 8-10), and Demo Day Week (Days 11-14). Each day has one primary deliverable. No multi-tasking. Finish the deliverable, move on.
Days 1-3: Positioning Foundation
Everything falls apart without positioning. If you cannot articulate who you serve, what problem you solve, why now, and what proof you have — in language your buyer already uses — no amount of content will save you. Three days. Three deliverables.
Day 1: The 4-Question Positioning Exercise
Sit down with a blank document and answer these four questions. No jargon. No pitch-deck language. Write as if you are explaining it to a smart friend who works in a different industry.
- What do you build? One sentence. "We build real-time perception software for autonomous industrial robots." Not "We are an AI-powered platform leveraging proprietary deep learning architectures to enable next-generation autonomous systems." The first version is clear. The second is noise.
- Who cares? Name the specific buyer. Not "manufacturing companies" but "VP of Automation at automotive OEMs with 5+ factories running legacy pick-and-place systems they need to upgrade without halting production." The more specific you get, the more your content will resonate.
- Why now? What has changed in the market, the technology, or the regulatory landscape that makes your solution urgent? "New OSHA guidelines require automated safety inspections by 2027, and most factories do not have the sensor infrastructure to comply." That is a compelling "why now."
- What proof? Traction metrics, pilot results, design partners, patents, team credentials. Whatever you have. If you are pre-revenue, talk about design partners and pilot results. If you have revenue, lead with it. "3 automotive OEMs in production, 94% defect detection accuracy, $1.2M ARR."
Write your answers down. Print them out. Tape them to your monitor. Every piece of content you create in this sprint will pull from these four answers.
Day 2: Rewrite Your LinkedIn Headline
Your headline is the single most important line of text on your LinkedIn profile. It appears everywhere: in search results, in comments, in DMs, in connection requests. Most YC founders waste it on "CEO at [Company]" which tells a buyer absolutely nothing.
Use this formula: [What you do] for [who] | [credibility signal]
Here are five examples for B2B tech founders in physical AI, robotics, and automotive:
- Before: "CEO at RoboSense" → After: "Building real-time perception for autonomous forklifts | YC F25 | 3 OEMs in production"
- Before: "Co-founder, DriveAI" → After: "Cutting autonomous vehicle validation time from 18 months to 4 | YC F25 | Ex-Waymo"
- Before: "Founder & CEO" → After: "Replacing manual inspection in factories with computer vision | YC F25 | $1.2M ARR"
- Before: "CEO at SensorFusion Inc." → After: "LiDAR + camera fusion that actually works in rain and fog | YC F25 | 94% accuracy in production"
- Before: "Co-founder" → After: "Making industrial robots safe enough for humans to work next to | YC F25 | 3 patents, 2 design partners"
Notice the pattern: every headline answers "what" and "for whom" within the first few words, then adds a credibility signal. The "YC F25" badge is a credibility accelerator during Demo Day week — use it.
Day 3: Rewrite Your About Section
Your About section should follow a 4-paragraph structure. This is the exact framework we use across our client base:
- Paragraph 1 — Hook: A single sentence or question that makes a VP of Engineering stop scrolling. "Every automotive OEM will need real-time perception for their factory robots within 3 years. Most are not ready."
- Paragraph 2 — Problem you solve: Describe the problem in your buyer's language. Not your technical architecture. The business pain. "Factory automation teams spend 12-18 months integrating perception stacks for each new robot deployment. By the time the system is live, the production line has already changed. They need perception that adapts in real-time, not perception that requires re-training every quarter."
- Paragraph 3 — How you solve it: This is where you can be technical — your buyers are engineers. But lead with the outcome. "Our on-device perception engine runs at 12ms latency on standard industrial GPUs. No cloud dependency, no re-training. Deploy once, adapt continuously. Three automotive OEMs are running it in production today."
- Paragraph 4 — Proof + CTA: Traction, team credentials, and a clear next step. "Before starting [Company], I spent 6 years at [Credibility Company] building [relevant thing]. We are backed by YC and [other investors]. If you are evaluating perception solutions for industrial automation, I would like to show you what real-time adaptation looks like. Connect with me or visit [website]."
Days 4-7: Content Production Sprint
Four days. Four pieces of content. Each one serves a specific strategic purpose. Write all four before you publish any of them — you want a content bank you can deploy on a schedule, not a daily scramble to create something new.
Day 4: Write Your Origin Story Post
This is the post that answers: why does this company exist? What problem made you angry enough to leave a good job and build something? Enterprise buyers care about founder motivation because it signals commitment. A founder who started a company because they personally experienced the pain they are solving will build a better product than someone chasing a market opportunity they read about in a report.
Here is the template:
I spent [X years] at [Company] working on [specific problem].
Every [time period], we would hit the same wall: [describe the specific, concrete frustration].
The tools available were [describe inadequacy — be specific about what was broken].
In [month/year], I decided to build what I wished existed: [one-sentence product description].
[X months/years] later, [traction proof]: [specific metric].
The problem has not changed. But the solution finally works.
If you are dealing with [buyer's pain], I wrote about how we approached it differently: [link or CTA].
Keep it under 300 words. Be concrete. "We hit the same wall" is weak. "Every 3 months, we spent 6 weeks re-training our perception model because the lighting in the factory changed with the seasons" is strong. Specificity is what separates a founder post from a corporate announcement.
Day 5: Write Your Industry Truth Post
This is the post with the highest viral potential. It is the uncomfortable truth that everyone in your industry knows but nobody says publicly. The format works because it creates tension: the reader wants to know if you are going to say the thing they have been thinking.
The hook formula: "Most [industry] [companies/startups/teams] [negative outcome]. Here is why:"
Real examples from campaigns we have run:
- "Most robotics startups die waiting for their first enterprise contract. Here is why:"
- "Most autonomous vehicle companies will never reach Level 4. And it is not a technology problem."
- "Most factory automation projects fail within 18 months of deployment. The reason has nothing to do with the technology."
Then deliver 3-5 specific insights. Not opinions — observations backed by your experience. Each insight should make the reader nod and think "yes, that is exactly what I have seen." End with your contrarian take on how to solve the problem.
This post format consistently generates 3-5x more engagement than standard company update posts. Save it for Day 11 of the sprint — peak Demo Day week — where the amplification effect is highest.
Day 6: Create Your First Carousel
Carousels are the highest-reach content format on LinkedIn. Across our client base, carousel posts generate 11.2x more impressions than text-only posts. For Demo Day week, you want at least one carousel in your content bank.
Use this 8-slide structure:
- Slide 1 — Hook: A bold statement or question that stops the scroll. Large text, high contrast. "The 3 Things Every Enterprise Buyer Checks Before Taking a Meeting with a Startup."
- Slide 2 — Problem: Name the pain. "You built a 10x better product. Your demo is flawless. But the VP of Engineering still will not take your call."
- Slides 3-5 — Key Insights: One insight per slide. Each slide should have a headline and 2-3 supporting sentences. Be specific. Use numbers where you have them.
- Slide 6 — Proof Point: A specific result, case study, or data point that validates your insights. "After implementing this approach, one of our clients went from 0 to 3 enterprise pilots in 60 days."
- Slide 7 — CTA: What should the reader do next? "If you are preparing for Demo Day and want to turn attention into meetings, connect with me. I will send you our full sprint framework."
- Slide 8 — Close: Your name, title, one-line description, and a prompt to follow or connect.
Design tip: alternate white and dark backgrounds between slides. White slide, dark slide, white slide. It creates visual rhythm that keeps people swiping. Use a single accent color — not your full brand palette. One color plus black and white is enough.
Day 7: Write Your Technical Insight Post
This is the post that establishes you as a builder, not just a pitcher. Your target buyers — VPs of Engineering, CTOs, technical product managers — are drowning in pitch-speak. When they encounter a founder who can articulate a genuine technical insight, it immediately signals credibility.
The format: "What we learned building X" or "How we achieved [specific technical result]."
Examples:
- "How we reduced inference latency from 340ms to 12ms on edge hardware without model distillation"
- "The 3 architectural decisions that let us process 10,000 sensor frames per second on a $200 GPU"
- "Why we rebuilt our entire perception pipeline after a single factory deployment — and what it taught us about real-world edge cases"
Notice the specificity. "How we reduced inference latency from 340ms to 12ms" is 10x more compelling than "We are building AI for edge computing." Engineers love numbers. They love specific technical choices and their tradeoffs. Give them that.
Keep the post accessible — you are writing for technical leaders, not PhD researchers. Explain the problem, the approach, the result, and the insight. Under 400 words. If the reader wants more depth, they will reach out. That is the point.
Days 8-10: Distribution Engine
Content without distribution is a diary. These three days are about building the infrastructure that ensures your Demo Day week content reaches the right people.
Day 8: Map Your Target Buyer List
Open a spreadsheet. Create these columns: Company, Name, Title, LinkedIn URL, Connection Status, Priority.
Build a list of 50 accounts. Not 500. Fifty. These should be the companies where your product solves a real, current pain. For each company, identify the 1-2 decision-makers who would own the buying process for your product. Typically this is the VP of Engineering, Head of Automation, CTO, or Director of [relevant function].
Then start connecting. Send 15 connection requests per day. Keep the note short and non-salesy: "Hi [Name], I am building [one sentence about your product] and preparing for YC Demo Day. I have been following [Company]'s work on [something specific and genuine]. Would love to connect." That is it. No pitch. No ask. Just a human reaching out.
Day 9: Start the Engagement Loop
This is the most undervalued activity in the entire sprint. Spend 20 minutes per day commenting on posts from your target buyers. Not "great post!" — that is invisible. Add actual value:
- Share a relevant data point they might not have seen
- Add a specific example from your experience that supports or challenges their point
- Ask a thoughtful question that extends the conversation
Why this works: when you comment on someone's post, your name and headline appear in their notifications. If your headline is optimized (you did that on Day 2), they now have context for who you are. When you post your own content during Demo Day week, they are more likely to engage because your name is familiar. You are not a cold account showing up in their feed. You are someone they have seen contributing to conversations they care about.
Do this for 20 minutes every morning. Before Demo Day, you will have had 40-60 meaningful interactions with people at your target accounts. That warm context is worth more than 1,000 cold emails.
Day 10: Post Your Origin Story
You wrote it on Day 4. Now publish it. Share it in 2-3 relevant Slack communities (your YC batch Slack, relevant founder groups, industry communities). Do not spam. Share it once per channel with a short note about why it is relevant to that community.
This is your warm-up post. It gets your profile back in the feed after what may have been months of silence. It tells the algorithm you are active. And it gives your new connections (from Day 8-9) their first exposure to your story.
Days 11-14: Demo Day Week
This is where the sprint pays off. You have a positioned profile, four pieces of content in the bank, a connected target audience, and warm engagement history. Time to execute.
Day 11: Post Your Industry Truth Piece
This is your highest-viral-potential post. You saved it for peak Demo Day week intentionally. The YC batch is generating ambient attention across LinkedIn — investors, buyers, media, and other founders are all paying more attention to YC-adjacent content. Your industry truth post rides that wave.
Post it between 8:00-9:30 AM ET (when enterprise LinkedIn usage peaks). Respond to every comment within the first 2 hours — the algorithm rewards posts that generate conversation, and your responses count as engagement.
Day 12: Post Your Carousel
Carousels are visual anchors in a text-heavy feed. During Demo Day week, when dozens of YC founders are posting text updates about their companies, a well-designed carousel stands out. It stops the scroll. Each swipe is an engagement signal to the algorithm, which means your carousel will reach further than any text post.
Post it in the morning. In the accompanying text, use a hook from the list below — do not just describe the carousel. Tease the insight and tell people to swipe.
Day 13: Post Your Technical Insight Piece
By now, your target buyers have seen your origin story, your industry perspective, and your carousel. This post closes the loop by establishing you as a builder. After the noise of Demo Day announcements — "We raised $X! We are building the future of Y!" — a specific technical insight is a breath of fresh air for technical buyers.
This is the post that a VP of Engineering will screenshot and send to their team with "We should talk to these people."
Day 14: Demo Day
The day itself. Post a concise "What we are building and why" with a clear CTA for meetings. Keep it under 200 words. Direct. No preamble, no gratitude paragraph, no "excited to announce" filler.
Structure:
[One-sentence problem statement].
[One-sentence solution].
[2-3 traction proof points, each on its own line].
We are presenting at YC Demo Day today.
If you are evaluating [relevant solution category], I would like to show you what we have built: [calendar link].
That is it. Under 200 words. The simplicity is the point. Every other founder in your batch is writing 500 words about their "incredible journey." Be the one who respects the reader's time and gives them a clear path to the next step.
