2 builders who never spoke to each other

Republish the same piece into a second community

A long answer you typed into someone else's forum belongs on your own site afterwards, and a post that did well on your site is worth putting in front of a founder community weeks later. The second audience arrives with different feedback, and posts placed this way carry onward into much larger aggregators.

The method

1. 01

   When you write a long answer inside somebody else's mailing list, forum or Q and A site, republish it on your own site afterwards so the writing builds your archive rather than theirs.

2. 02

   Write up your first revenue milestone and cross-post it to a founder community, since that kind of post can carry onward into much larger aggregators.

3. 03

   Republish a piece that did well on your own blog to a founder community weeks later, because the second audience brings feedback and information the first did not.

What it returned

• 13

  Zue's first-dollar retro, cross-published to Indie Hackers, reached the Hacker News front page at position 13

• This piece started as a lengthy reply Hillman typed on his phone into the coworking Google Group while feeling unwell, and he then posted it on his own blog.

• A week after publishing it himself, Zue put SEO for Developers up on Indie Hackers, which brought a fresh round of comments and corrections

Sources

• “Open-plan offices were devised by Satan in the deepest caverns of hell” and other similar nonsense you might read about trends in the workplaceAlex Hillman · dangerouslyawesome.com · 2013-11-01
• Week 23 RetrospectiveCory Zue · coryzue.com · 2017-08-28
• Week 31 RetrospectiveCory Zue · coryzue.com · Comments · 2017-10-23