Building Quickly in Public: Week 1
We're building an AI reply tool and sharing everything. Here's what we learned in week one about voice analysis and Chrome extensions.
Quickly Team
@quicklyWe decided to build Quickly completely in public. Every win, every failure, every pivot. Here's week one.
The Problem We're Solving
Twitter engagement takes time. Good replies take thought. Most people either:
We wanted a middle ground: AI that sounds like *you*, generated in one click.
Week 1: Voice Analysis
The core challenge is capturing someone's "voice." We started by analyzing:
The breakthrough came when we stopped trying to categorize voices ("casual", "professional") and instead captured the actual patterns. Your voice isn't a category—it's a fingerprint.
Week 1: Chrome Extension
Building a Chrome extension for X.com is... interesting. The DOM changes constantly, class names are obfuscated, and you're fighting against a site that doesn't want you there.
Key learnings:
What's Next
Week 2 focus:
Follow along at @quickly. We'll share the code, the metrics, and the mistakes.