<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Udit Kapoor</title>
    <description>The latest articles on DEV Community by Udit Kapoor (@udit_kapoor).</description>
    <link>https://dev.to/udit_kapoor</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3898983%2F07040668-af66-47b6-aa38-7ba5ad98debc.jpg</url>
      <title>DEV Community: Udit Kapoor</title>
      <link>https://dev.to/udit_kapoor</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/udit_kapoor"/>
    <language>en</language>
    <item>
      <title>How to Track Your Startup Progress Without Losing Your Mind</title>
      <dc:creator>Udit Kapoor</dc:creator>
      <pubDate>Tue, 26 May 2026 03:30:00 +0000</pubDate>
      <link>https://dev.to/udit_kapoor/how-to-track-your-startup-progress-without-losing-your-mind-5ahp</link>
      <guid>https://dev.to/udit_kapoor/how-to-track-your-startup-progress-without-losing-your-mind-5ahp</guid>
      <description>&lt;p&gt;You are building a startup. Maybe even a SaaS. You have a product, some users, maybe some revenue.&lt;/p&gt;

&lt;p&gt;And somewhere between shipping features, talking to customers, and trying to grow, you are also supposed to be tracking your progress.&lt;/p&gt;

&lt;p&gt;Most developers handle this badly. Spreadsheets that never get updated. Notion pages that made sense three months ago but now nobody opens. Numbers scattered across five different tools.&lt;/p&gt;

&lt;p&gt;Here is a simple system that actually works.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why tracking feels like a chore and why that is a problem
&lt;/h2&gt;

&lt;p&gt;When you are deep in building mode, opening a spreadsheet to update your user count feels like a distraction.&lt;/p&gt;

&lt;p&gt;But when you do not track, you lose visibility. You stop seeing trends. You make important decisions based on gut feeling instead of actual data.&lt;/p&gt;

&lt;p&gt;Tracking is not admin. It is how you know if what you are doing is working.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to actually track
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;MRR&lt;/strong&gt; is the most important number for any subscription product. Track it weekly so you can see the trend, not just the monthly snapshot.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Active users vs total users&lt;/strong&gt; are two completely different signals. Total users is vanity. Active users tells you if people are finding real value. Define what active means for your specific product and track that number consistently.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;New signups per week&lt;/strong&gt; shows whether your discovery is working. Flat or dropping means a top-of-funnel problem.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Churn&lt;/strong&gt; tells you whether your product is actually solving a problem. High churn almost always means a product problem, not a marketing problem.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key milestones&lt;/strong&gt; are the qualitative markers worth documenting. First paying user. First ten users. First user from organic search. These do not show up in dashboards but they matter enormously.&lt;/p&gt;

&lt;h2&gt;
  
  
  The spreadsheet problem
&lt;/h2&gt;

&lt;p&gt;Spreadsheets work fine for numbers. The problem is they are private, static, and have no accountability mechanism.&lt;/p&gt;

&lt;p&gt;Nobody sees your spreadsheet. When tracking is private it is easy to skip a week. Then two weeks. Then six months later you have no idea what your user count was in March.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why public tracking works better
&lt;/h2&gt;

&lt;p&gt;When you track publicly something changes. You update your numbers because people are watching. Not out of pressure but out of accountability.&lt;/p&gt;

&lt;p&gt;Your audience follows the real journey. Potential users see you are actively building. And when you look back in six months you have a complete record instead of gaps.&lt;/p&gt;

&lt;h2&gt;
  
  
  The ten-minute weekly routine
&lt;/h2&gt;

&lt;p&gt;Every Monday morning, update five numbers. MRR, total users, new signups last week, active users, one milestone or event from the previous week.&lt;/p&gt;

&lt;p&gt;Write two or three sentences about what happened. What you shipped, what worked, what did not.&lt;/p&gt;

&lt;p&gt;Share it publicly somewhere.&lt;/p&gt;

&lt;p&gt;Ten minutes. Once a week. Done consistently for a year this builds something genuinely valuable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where to keep your tracking data
&lt;/h2&gt;

&lt;p&gt;Notion is good for private reference but bad for public sharing. Twitter threads disappear. Personal blogs require too much setup.&lt;/p&gt;

&lt;p&gt;BuildTrail was built specifically for this. One public page for your MRR, users, milestones, and updates. Your journey lives permanently in one place instead of scattered across tools and tweets.&lt;/p&gt;

&lt;p&gt;See how it works at &lt;a href="https://www.buildtrail.app" rel="noopener noreferrer"&gt;BuildTrail&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Start simple
&lt;/h2&gt;

&lt;p&gt;Start tracking one number this week. Just one. Update it every Monday. Share it somewhere public.&lt;/p&gt;

&lt;p&gt;That is the whole system. Add more over time. But do not wait for the perfect system before you start.&lt;/p&gt;

&lt;p&gt;The founders who win at this are the ones who started imperfectly and kept going.&lt;/p&gt;

</description>
      <category>buildinpublic</category>
      <category>saas</category>
      <category>productivity</category>
      <category>startup</category>
    </item>
    <item>
      <title>What Does "Building in Public" Actually Mean in 2026?</title>
      <dc:creator>Udit Kapoor</dc:creator>
      <pubDate>Mon, 11 May 2026 03:45:00 +0000</pubDate>
      <link>https://dev.to/udit_kapoor/what-does-building-in-public-actually-mean-in-2026-31oe</link>
      <guid>https://dev.to/udit_kapoor/what-does-building-in-public-actually-mean-in-2026-31oe</guid>
      <description>&lt;p&gt;If you've spent any time on developer Twitter, you've seen it.&lt;/p&gt;

&lt;p&gt;Founders posting their MRR. Sharing what broke this week. Documenting every step of building their product in real time.&lt;/p&gt;

&lt;p&gt;But what does building in public actually mean? And is it worth doing?&lt;/p&gt;

&lt;p&gt;This is the honest breakdown. No hype.&lt;/p&gt;

&lt;h2&gt;
  
  
  The simple definition
&lt;/h2&gt;

&lt;p&gt;Building in public means sharing your startup journey openly as it happens. Not after you've succeeded. Not in a polished case study. Right now, in real time, with the messy parts included.&lt;/p&gt;

&lt;p&gt;That means posting about your revenue even when it's zero. Sharing what broke last week. Telling people about the feature nobody used.&lt;/p&gt;

&lt;p&gt;It is the opposite of stealth mode.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it started
&lt;/h2&gt;

&lt;p&gt;The movement took off when founders like Pieter Levels started sharing everything publicly. Revenue screenshots. User counts. Failed experiments. Real numbers behind real products.&lt;/p&gt;

&lt;p&gt;People responded because it felt honest. In a world full of polished startup stories, "here's what my dashboard actually looks like" was refreshing.&lt;/p&gt;

&lt;p&gt;Indie Hackers built a community around it. Twitter's #buildinpublic tag became one of the most active founder spaces online.&lt;/p&gt;

&lt;h2&gt;
  
  
  What building in public is not
&lt;/h2&gt;

&lt;p&gt;It is not bragging. It is not a marketing strategy disguised as transparency. It is not just posting revenue milestones when things are going well.&lt;/p&gt;

&lt;p&gt;The founders who do it well share the whole picture. Bad months alongside good ones. Features that flopped alongside ones that worked.&lt;/p&gt;

&lt;p&gt;If you only share the good stuff, your audience will feel it. And they will stop trusting you.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why founders actually do it
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Accountability&lt;/strong&gt; is the biggest reason. When you tell the world you're going to ship something this week, you're far more likely to do it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Audience building&lt;/strong&gt; compounds over time. Every post reaches potential users, collaborators and supporters.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Feedback&lt;/strong&gt; helps you build something people actually want. When you share what you're building, people tell you what they think.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Community&lt;/strong&gt; is real. The build-in-public world is genuinely supportive. Founders help each other in ways that don't happen anywhere else.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem nobody talks about
&lt;/h2&gt;

&lt;p&gt;Here's the thing though. There's a real problem with how most founders build in public.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;All that content disappears.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;You post a milestone on Twitter and it gets buried in 48 hours. Six months of honest documentation of your journey just vanishes into the feed.&lt;/p&gt;

&lt;p&gt;There's no permanent record. No single place where someone can see your full story from the beginning.&lt;/p&gt;

&lt;p&gt;This is the gap that BuildTrail fills. A permanent public page for your entire startup journey. One link that tells the whole story.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to actually start
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Start with weekly updates.&lt;/strong&gt; Every Friday or Monday, write a short post covering three things. What you shipped. What you learned. What you're working on next.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Share real numbers from day one.&lt;/strong&gt; Even if those numbers are zero. Saying "zero users and zero revenue on week one" is more trustworthy than vague language about early traction.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Be consistent over being perfect.&lt;/strong&gt; One post every week for a year matters far more than ten posts in January and then silence.&lt;/p&gt;

&lt;h2&gt;
  
  
  The bottom line
&lt;/h2&gt;

&lt;p&gt;Building in public means sharing your real journey openly as it happens. It's not about looking good. It's about being genuine, staying accountable, and building trust.&lt;/p&gt;

&lt;p&gt;The founders who do it consistently and honestly are the ones who build audiences, get early users, and create products people actually care about.&lt;/p&gt;

&lt;p&gt;If you're ready to start documenting your journey properly, BuildTrail gives you one permanent public page for everything.&lt;/p&gt;

&lt;p&gt;Free to start at &lt;a href="https://www.buildtrail.app" rel="noopener noreferrer"&gt;buildtrail.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>buildinpublic</category>
      <category>saas</category>
      <category>startup</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Why I Built BuildTrail — A Public Home for Founders Who Build in Public</title>
      <dc:creator>Udit Kapoor</dc:creator>
      <pubDate>Mon, 27 Apr 2026 05:40:25 +0000</pubDate>
      <link>https://dev.to/udit_kapoor/why-i-built-buildtrail-a-public-home-for-founders-who-build-in-public-bo9</link>
      <guid>https://dev.to/udit_kapoor/why-i-built-buildtrail-a-public-home-for-founders-who-build-in-public-bo9</guid>
      <description>&lt;p&gt;&lt;em&gt;If you've ever posted a milestone on Twitter and watched it disappear two days later, this one's for you.&lt;/em&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  It started with a problem I couldn't unsee
&lt;/h2&gt;

&lt;p&gt;About a year ago, I was building ViewUs — my first real SaaS attempt.&lt;/p&gt;

&lt;p&gt;Like most founders trying to grow, I was doing the whole "build in public" thing. Posting on Twitter every few days. Revenue updates. User milestones. Lessons from features that flopped. The wins, the dead ends, all of it.&lt;/p&gt;

&lt;p&gt;And after a while, I started noticing something that nobody really talks about.&lt;/p&gt;

&lt;p&gt;All of it was disappearing.&lt;/p&gt;

&lt;p&gt;Not slowly. Fast. A tweet about hitting 50 users — buried in 48 hours. A thread about the biggest lesson from a failed launch — gone in a week. A revenue screenshot that took real courage to post — never found again.&lt;/p&gt;

&lt;p&gt;I'd scroll back through my own feed looking for something I wrote three months ago and spend ten minutes trying to find it. That's when it hit me.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;There's no place where a founder's journey actually lives.&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  The "build in public" movement has a blind spot
&lt;/h2&gt;

&lt;p&gt;Look at any founder you follow on Twitter who builds in public. They post consistently. Revenue milestones. User counts. Honest reflections. All of it valuable, all of it real.&lt;/p&gt;

&lt;p&gt;But here's the thing — if someone discovers them today and wants to understand their full journey, they have to scroll through hundreds of tweets across months or years. Most people won't bother.&lt;/p&gt;

&lt;p&gt;And for the founder themselves? There's no single answer to "how far have you come?" No timeline. No clean record. Just fragments scattered across a social feed that wasn't built to tell stories.&lt;/p&gt;

&lt;p&gt;I kept waiting for someone to build the solution. Nobody did.&lt;/p&gt;

&lt;p&gt;So I built it myself.&lt;/p&gt;




&lt;h2&gt;
  
  
  What is BuildTrail?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;BuildTrail is a public page for your startup journey.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Instead of your milestones living in tweets that disappear, they live on your BuildTrail — a clean, permanent, shareable page that tells the full story of what you're building.&lt;/p&gt;

&lt;p&gt;Here's what you can track and share:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Milestones&lt;/strong&gt; — every significant moment in your build, from first commit to first dollar&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Revenue&lt;/strong&gt; — your MRR or total revenue, updated as you grow&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;User count&lt;/strong&gt; — watch your number go up (and sometimes down — that's fine too)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Updates&lt;/strong&gt; — post like a public changelog, keep your audience in the loop&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Full control&lt;/strong&gt; — you decide exactly what's visible and what stays private&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One link. Your whole story.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why this matters more than you think
&lt;/h2&gt;

&lt;p&gt;Building in public isn't just a growth strategy. For most indie founders, it's accountability. It's the thing that keeps you going when nobody's watching.&lt;/p&gt;

&lt;p&gt;But accountability needs a record. Progress needs somewhere to live.&lt;/p&gt;

&lt;p&gt;When you have a BuildTrail, you can look back six months from now and see exactly where you started. Your followers can follow the real arc — not just the latest tweet. Future users can see you're the real deal before they hand over their credit card.&lt;/p&gt;

&lt;p&gt;It changes the question from &lt;em&gt;"what have you been up to?"&lt;/em&gt; to &lt;em&gt;"here's everything, in one place."&lt;/em&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  The honest part — where I am right now
&lt;/h2&gt;

&lt;p&gt;I launched BuildTrail two days ago.&lt;/p&gt;

&lt;p&gt;I have my first real users. I have my first real feedback. I have a site speed issue I fixed last night at midnight.&lt;/p&gt;

&lt;p&gt;Revenue: $0. Users: small but growing. Energy: very much alive.&lt;/p&gt;

&lt;p&gt;I'm using BuildTrail to track BuildTrail's own journey — which feels right.&lt;/p&gt;

&lt;p&gt;If you're building in public and your journey deserves more than a Twitter thread that disappears — come try it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Free to start. $9/mo for the full thing.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;First 50 founders get 40% off for 3 months with code &lt;strong&gt;EARLYTRAIL&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;👉 &lt;a href="https://www.buildtrail.app" rel="noopener noreferrer"&gt;buildtrail.app&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  One question for you
&lt;/h2&gt;

&lt;p&gt;What's the one thing missing from how you currently share your startup journey publicly?&lt;/p&gt;

&lt;p&gt;I'm genuinely building this for founders like you — every piece of feedback shapes what gets built next. Drop it in the comments, I read and reply to everything.&lt;/p&gt;

</description>
      <category>buildinpublic</category>
      <category>saas</category>
      <category>startup</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
