Our Plan to Build Transparently with Real-Time Developer Feedback

Your feature requests are essential. Your bugs will shape our roadmap. Your opinions will guide everything we build.

That's not corporate speak—it's exactly how we plan to operate over the next few months as we build our latest tool from absolute zero. No stealth mode, no grand reveals, just raw development happening openly with real developers guiding us on what's valuable and what's not.

Most "build in public" journeys are polished performances. Companies typically share carefully curated updates after decisions have been finalized. We're planning something different: genuinely letting our community drive our development in real-time, transparently, even if it gets messy.

Here's what we're planning to do:

Week 1-2: Starting From Absolutely Nothing

Our initial hypothesis is straightforward: technical marketers need better ways to track developer engagement across various touchpoints. No extensive market research, no investor presentations, just this simple idea.

Instead of developing in isolation for months, we plan to release a minimal viable product (MVP) after just two weeks. It might initially only track GitHub activity and basic blog engagement. It might look rough, possibly have UI issues on mobile, or even struggle with exporting data initially.

But we'll release it anyway.

We plan to initiate conversations wherever our potential users spend their time—not with sales pitches but with genuine questions. In growth engineering Slack channels, we'll ask: "What developer engagement metrics matter most to you?" On indie maker forums: "How are you currently tracking if your technical content is effective?"

We expect direct, unfiltered feedback. We'll document everything openly, and each piece of feedback will shape our shared public roadmap, highlighting exactly what we're considering, actively building, or dropping.

Community-Driven Development From the Start

Within weeks, we anticipate natural and organic feedback loops forming.

Our public roadmap will become the central hub, allowing users to upvote features, comment on priorities, and transparently follow our weekly progress—no marketing fluff, just straightforward updates like "Building authentication" or "Fixing a reported bug."

We expect surprising insights. Perhaps users might prioritize simple Slack notifications over complex analytics, or they may prefer webhook integrations pushing data into existing tools rather than another dashboard.

We plan regular public user interviews—brief sessions where we screen-share our staging environment, inviting users to test and critique live on our Discord. We anticipate immediate, actionable feedback:

• "This button could be clearer."
• "Why multiple clicks here?"
• "How can I act on this data effectively?"

Every week, we'll publish unfiltered changelogs, openly acknowledging issues:

"Added webhook support due to popular demand. Fixed mobile layout issues. Still working on API rate limiting problems."

Embracing Public Mistakes

We anticipate making mistakes publicly.

We might invest significant time into features that don't resonate. Instead of quietly removing these features, we'll share openly why they didn’t work, including genuine user feedback and lessons learned.

We'll be transparent even during performance challenges. If our API encounters issues, we'll openly discuss our challenges and solutions, inviting our community to contribute insights and advice.

Prioritizing User-Defined Wins

We aim to achieve early wins that matter deeply to users—perhaps saving someone hours in their workflow or clearly demonstrating the impact of their content.

Within months, we anticipate our community suggesting critical features we'd never imagined—SDK tracking, health monitoring integrations, or detailed cross-platform analytics.

We expect higher retention from engaged users who see their feedback actively shaping the product, fostering a sense of ownership and advocacy.

Keeping Honest with Public Retrospectives

Every week, we'll conduct and share honest retrospectives:

• What worked?
• What didn’t?
• What's next?

These will not be polished corporate updates but truthful reflections, inviting community participation and accountability.

Knowing our decisions will be publicly reviewed by knowledgeable users will guide us to make better, more intentional choices.

Our Commitment

Over the next several months, we commit to authentically building in public. Our goal is to grow a vibrant community of developers actively contributing feedback, reporting bugs, and suggesting ideas.

We expect our core features to achieve high adoption because they'll be directly driven by our community's genuine needs.

This approach won’t suit every product or team. It requires comfort with public experimentation, rapid iteration, and relinquishing tight control over the roadmap.

However, for technical products built for technical users, we believe this open, transparent, and community-driven approach will deliver the most meaningful results.

Want to follow our journey, contribute your ideas, or see your feedback become reality? Join our newsletter for weekly updates on what we learn and build based on your input.