Why Pirros' hackathon blog mirrors its LinkedIn ads, but pitches a demo to a recruiting audience
Pirros runs a LinkedIn ad cluster that quotes its own engineering blog post about a 72-hour hackathon. The landing page is the same post, opened to the exact headline a reader just clicked. Match on copy is near perfect. The gap is what happens next: every conversion path on the page asks the engineer reader to book a product demo, even though both ad bodies end with we are hiring.
Primary click path
// Ad
Pirros
Promoted · LinkedIn ad sample 1
Last month the engineering team held our first ever hackathon and it truly changed the way we work.
Zhan Isaakian wrote the whole story on our blog. I'm not going to repeat it because he tells it better than I would.
What I want to focus on here is our team at Pirros. You can have a vision and you can have a roadmap. But the thing that actually determines whether you build something great is whether the people around you care as much as you do.
The culture Zhan is describing in his post didn't happen by accident. It happened because we hired people who think like owners and then actually let them own things.
What I saw during the hackathon, and what I see every week, is a team that cares about the outcome in a way that goes beyond their job description. The engineers here build things not because someone told them to but because they saw something that could be better and just fixed it.
I’m so grateful that I get to build alongside this team every day and have the opportunity to learn from them.
Read the full story on our blog: https://lnkd.in/gGtcAV2e
And if this is the kind of team you want to be part of, we're hiring. Link in the comments.
Show more
Last month the engineering team held our first ever hackathon and it truly changed the way we work. Zhan Isaakian wrote the whole story on our blog. I'm not going to repeat it because he tells it better than I would. What I want to focus on here is our team at Pirros. You can have a vision and you can have a roadmap. But the thing that actually determines whether you build something great is whether the people around you care as much as you do. The culture Zhan is describing in his post didn't happen by accident. It happened because we hired people who think like owners and then actually let them own things. What I saw during the hackathon, and what I see every week, is a team that cares about the outcome in a way that goes beyond their job description. The engineers here build things not because someone told them to but because they saw something that could be better and just fixed it. I’m so grateful that I get to build alongside this team every day and have the opportunity to learn from them. Read the full story on our blog: https://lnkd.in/gGtcAV2e And if this is the kind of team you want to be part of, we're hiring. Link in the comments.
We Took Three Days Off the Roadmap. It Forever Changed How We Build. We pulled ten engineers off the roadmap for three days. Twelve projects shipped. But the real outcome was a permanent shift in how our team builds, collaborates, and thinks about ownership. …see more
1388448636
// Landing page
The score.
// Overall score
- Headline match
- 9.8
- Offer continuity
- 8.5
- Visual + tone
- 8
- Scent + intent
- 8.5
The verdict
This is one of the cleaner message matches in our PostClickSignal sample. Pirros is running 2 unique copy variants from a larger 4-ad LinkedIn cluster, all pointing to its own engineering blog post titled We Took Three Days Off the Roadmap. It Forever Changed How We Build. The landing page H1 is the same string, the byline is the same engineer the ad bodies reference, and the article delivers every beat the ads promise: ten people, three days, twelve projects, a culture shift.
Where the audit drops from an A to a B+ is intent. The ads read like recruiting posts. Both bodies tell a culture story and close with we are hiring or a link to engineering roles in the comments. The blog post itself never offers that path inside the reading flow. The two CTAs on the page are Book a demo at the top and Schedule a demo at the bottom, both aimed at AEC teams evaluating Pirros as software, not at engineers thinking about joining.
The ads pointing here
// Ad cluster
LinkedIn copy variants scored.
Scored sample: 2 ads.
Learn more// Dominant headline
We Took Three Days Off the Roadmap. It Forever Changed How We Build.
PostClickSignal scored 2 unique copy variants from a larger 4-ad LinkedIn cluster. Both variants are organic-style LinkedIn posts written in the first person by Pirros team members, with image creative and a long narrative body. Both share the same headline and both link to the same blog post.
Variant one is told from the writer's seat. It reframes the hackathon as evidence of culture: a team that cares about the outcome beyond the job description, hired people who think like owners, and were given room to own things. It closes with a link to the blog and a hiring nudge in the comments.
Variant two is told from the founder seat. It frames the decision to stop the roadmap for three days, contrasts that with quarterly planning cycles that ship less in twelve weeks than ten people built in 72 hours, and ends with an explicit role: an Engineer's Engineer who does not need to be told why you give engineers freedom.
Both variants share the same dominant CTA, Learn more, which on LinkedIn deep-links into the blog post the ad is already quoting.
// Ads scored
More ad variants.
Pirros
Promoted · LinkedIn ad sample 2
A few weeks ago at Pirros, I said "what if we just stop working on the roadmap for three days and let engineers build whatever they want." So I put together a 72-hour hackathon.
No committee. No proposal. No six-week planning process to plan the three-day thing. That alone would've been a feat at most places I've worked.
I won't spoil what everyone built because I wrote about the whole experience on our blog. But I will say this: I've sat through quarterly planning cycles that shipped less than what ten people built between Tuesday night and Friday afternoon.
The thing I actually want to talk about is what it feels like to work here. Because the hackathon is a good story, but it's really just one example of something that happens all the time at Pirros.
You have an idea for how something should work. You say it out loud. And nobody says "put it in the backlog."
They say "go build it."
There's a version of startup life where "move fast" means you're always behind and everything is on fire. This isn't that. This is a team that actually trusts its engineers to make decisions, and then gets out of the way while they do.
If you're curious what ten engineers built in 72 hours: https://lnkd.in/gmavVYPj
We're looking for an Engineer's Engineer — someone who doesn't need to be told why you give engineers freedom. If that's you — link in the comments.
Show more
A few weeks ago at Pirros, I said "what if we just stop working on the roadmap for three days and let engineers build whatever they want." So I put together a 72-hour hackathon. No committee. No proposal. No six-week planning process to plan the three-day thing. That alone would've been a feat at most places I've worked. I won't spoil what everyone built because I wrote about the whole experience on our blog. But I will say this: I've sat through quarterly planning cycles that shipped less than what ten people built between Tuesday night and Friday afternoon. The thing I actually want to talk about is what it feels like to work here. Because the hackathon is a good story, but it's really just one example of something that happens all the time at Pirros. You have an idea for how something should work. You say it out loud. And nobody says "put it in the backlog." They say "go build it." There's a version of startup life where "move fast" means you're always behind and everything is on fire. This isn't that. This is a team that actually trusts its engineers to make decisions, and then gets out of the way while they do. If you're curious what ten engineers built in 72 hours: https://lnkd.in/gmavVYPj We're looking for an Engineer's Engineer — someone who doesn't need to be told why you give engineers freedom. If that's you — link in the comments.
We Took Three Days Off the Roadmap. It Forever Changed How We Build. We pulled ten engineers off the roadmap for three days. Twelve projects shipped. But the real outcome was a permanent shift in how our team builds, collaborates, and thinks about ownership. …see more
1388427896
What the page promises
The landing page is a Pirros blog post dated April 6, 2026, written by Zhan Isaakian, the same engineer named in one of the ad bodies. The hero shows the post title, the author photo, and a hackathon photo. There is no marketing module above the article and no sales banner inside it.
The article walks through why the team paused the roadmap, the setup of a 72-hour off-site, the three projects that stood out (an AI agent that reads Jira tickets and opens pull requests, a Revit web bridge, and an AutoCAD integration), a mid-hack realization about spec-driven development with Claude, and how the experience permanently changed how product and engineering collaborate at Pirros.
At the very bottom, after the article ends, a brand block appears with the line Get your details closer to design-ready than they've ever been and a Schedule a demo button. That is the only direct conversion path the page offers, and it speaks to AEC buyers, not the engineering audience the ads are addressing.
Dimension breakdown
The ad headline and the page H1 are the same sentence. A reader sees their own scent restated word for word in the first viewport.
The article delivers every story beat the ads tease, ten people, three days, twelve projects, a culture shift. What it does not deliver is the recruiting offer the ads imply at close.
Organic-style LinkedIn ads land on a long-form first-person article with hackathon photos. The product-style demo CTA at the bottom is a mild tonal jump for a culture-story reader.
Within the first viewport a reader knows they landed on the exact post quoted in the ad. The intent leak is downstream, where the only next step is a product demo.
Top fixes
Add an in-article recruiting CTA that matches the ad's hiring signal
Both LinkedIn variants close with a hiring beat, either we are hiring or a link to engineering roles in the comments. The post itself never offers that path inside the reading flow. A jobs CTA placed after the section To the Engineering Leader Who Says We Don't Have Time will catch the engineers the ads are actually targeting.
Schedule a demo
See open engineering roles at Pirros
Lead the end-of-post CTA with a culture or team next step before the demo ask
A reader who clicked a hackathon story is not in a buying mindset. The current closing block jumps straight to a product pitch, which weakens offer continuity for the recruiting audience. Replace it with a two-button block that offers a recruiting path first and a demo path second.
Get your details closer to design-ready than they've ever been
Want to build with this team? See open roles or read more from our engineers
Pull a one-line recruiting line into the hero or directly under the H1
The dominant ad bodies frame this as both a culture story and a hiring pitch. Echoing the hiring beat in the hero closes the loop on what the ad promised in the first scroll, before the reader has to scroll past the entire article to find any next step.
We pulled ten engineers off the roadmap for three days. We are also hiring more of them.
Rewrite preview
// Suggested hero
We Took Three Days Off the Roadmap. It Forever Changed How We Build.
Ten engineers, 72 hours, twelve shipped projects, and a new way of working at Pirros. If this is your kind of team, we are hiring.
FAQ
How many Pirros LinkedIn ads point to this blog post?
The LinkedIn Ad Library shows 4 ads in this cluster, which collapse into 2 unique copy variants after we deduplicate on headline, body, and CTA. All point to the same blog post URL.
Why did this audit score B+ instead of A?
Headline match is near perfect and the article delivers every story beat the ads tease, which earns a strong base score. The deduction is intent. The ads end on a recruiting note, but the only conversion path on the page is a product demo for AEC teams. The page does not give engineer readers a way to act on the hiring signal.
What is Pirros?
Pirros is a B2B SaaS product for AEC teams that helps architects and engineers manage and reuse construction details inside Revit. The company is based at pirros.com.
What would a reasonable next test be?
Run a split where one variant of the landing page surfaces a See open engineering roles CTA inside the article body and keeps the existing demo CTA at the bottom. Measure click-through to the careers page from LinkedIn ad traffic. If engineer readers are converting at a meaningfully higher rate on the recruiting CTA, the ads are recruiting ads and the page should follow.
Sources
- LinkedIn Ad Library: 2 unique copy variants from a 4-ad cluster pointing to the blog post
- Landing page: https://pirros.com/blog/we-took-three-days-off-the-roadmap
- Advertiser homepage: https://pirros.com
Want to see where your paid clicks drift?
Run a free PostClickSignal audit on one of your live ad-to-page pairs and get the same dimension breakdown and fix list we generated for Pirros.
Audit my ads