When I did log back into the twitter-o-sphere, my timeline was dominated by #Tweet100, Jay Clouse’s community project to encourage folks to tweet every day for 100 days. Proof is in the numbers as they say: over 600 participants
and hundreds of tweets everyday
At its center is a proper no-code stack: a landing page (built in Wordpress 🤷♂️), shoutout.so
for the tweet wall, convertkit
for email management, and Zapier, Airtable and Integromat glued together for tracking the leaderboard.
The #tweet100 leaderboard
which we built on the stream is one of the workflows I’m most proud of. It’s simple, elegant and extremely
Above all, it’s a true example of democratizing software creation in that the underlying tools enabled a workflow that would
not have otherwise existed.
I emphasize the word would
instead of could here because there were no technical limitations in what we built. All of it is relatively simple if you’re a developer: Twitter and Convertkit have APIs, websites can be built from scratch, hosting tweet metadata in databases is relatively easy. It’s feasible
, just not with Jay and I’s capacities. And without a leaderboard, I’m not sure #Tweet100
would exist—or be near as impactful.
Building this workflow and seeing the community that has formed around it got me thinking: what is our #tweet100? How do we succinctly (e.g. not in a one hour stream) show what they can do and get more folks onboard?
*Stephen O'Grady has since made it even better by making it update in real-time which was one of the flaws of the way I built it. He’s also migrated it to Integromat making it truly no-code!