DEV Community: Harsha Kumar

From 0 to a real floor, what actually changed over the last month or so

Harsha Kumar — Tue, 04 Aug 2026 05:30:21 +0000

For a long stretch, XEdge sat around 2 to 3 active users a day, sometimes lower. Real product, real traffic sources, but the daily number stayed stubbornly low no matter what got posted.

Somewhere in the last few weeks that shifted. The floor now sits closer to 6 to 10 on a normal day, sometimes higher, without needing a big spike or a lucky post to get there. Worth being honest about what actually caused that, because it wasn't any single thing, and it definitely wasn't what I expected going in.

The first real unlock was fixing something boring that had been sitting broken for over a month. A checkout path from the product straight to the paid playbooks. Not complicated, just kept losing to whatever felt more urgent that week. Once it finally shipped, product page views picked up almost immediately, not because anything got more exciting, because something that was quietly broken stopped being broken.

The second thing was rotating content formats deliberately instead of chasing whatever spiked last. Stack posts, honest numbers updates, open interactive questions, each one works well on its own, and each one flattens fast if repeated too many days in a row. Once that became a conscious rotation instead of a reaction to yesterday's number, the whole week got steadier instead of swinging between big days and dead ones.

The third thing, and probably the one that mattered most, was replying fast and specifically to anyone who actually engaged. A single comment thread on Peerlist a few days ago, someone pointed out I'd been assuming features would announce themselves once shipped, they don't, and that one exchange reshaped how the whole week's content got planned.

None of this was a growth hack. No new platform, no automation, no clever trick. Just closing a few real gaps that had been sitting open too long, and paying attention to what the daily numbers were actually saying instead of guessing.

Still early, still a small floor in absolute terms, but the shape of the graph is different now than it was a month ago, and that's the part worth writing down before it's forgotten how it happened.

The no-code SaaS stack that actually gets to a paying user, not just a working demo

Harsha Kumar — Fri, 31 Jul 2026 05:29:38 +0000

Most no-code guides stop at "you can build this without code," which is true but incomplete. The harder part isn't building, it's getting someone to pay before the excitement of building it wears off.

Here's the stack in the order that actually matters.

Validation first, using Claude. Describe the idea plainly and ask it to argue against it, five real reasons it could fail. This costs nothing and catches the obvious problems before any time gets spent building around them.

Building, Bubble, free tier. Real database, real authentication, real workflows, genuinely no code required. The free tier is enough to validate demand, no reason to pay anything until real usage shows up.

Adding AI, through Bubble's OpenAI plugin. Roughly twenty minutes of setup, and it's the difference between a simple tool and something that feels like it has real intelligence behind it.

Charging, immediately, through Stripe connected to Bubble. Even a small amount. This is the step most people quietly avoid, waiting until the product feels more finished, more polished, more ready. It almost never actually needs to wait. Paying users behave differently from free ones from day one, and that behavior is the real signal, not analytics.

Finding users, inside communities that already exist around the problem being solved. Solve something real in a real thread first, mention the product only when it's genuinely relevant to what's being discussed.

Total cost across all of this, zero. A live product in a weekend is realistic. A first paying user in two to four weeks is realistic too, but only with daily, unglamorous outreach behind it, not a single launch post and silence after.

Full playbook with every prompt and every tool link at xedge.tech.

What actually shipped this week, and the retention question that started it

Harsha Kumar — Thu, 23 Jul 2026 05:06:34 +0000

A few weeks back I asked a Discord community a direct question. XEdge hit 750+ users organically, then flattened. 61 returning users out of that total. I wanted to know if that was a positioning problem, a UI problem, or something else.

Someone answered with a single question that reframed the whole thing. Is there an incentive to keep using your tool.

That's the actual gap. XEdge answers one question well, what AI stack fits your goal, and once someone gets that answer, there's no reason to open the tab again until they have a new goal. That's not a bug, it's just the nature of what a reference tool does. But it means nothing in the product was giving anyone a reason to return.

A friend who's been in these conversations for a while had already suggested the fix independently, before I even asked the retention question publicly. Real builders, their actual stack, a short honest quote, featured on a page that grows over time. Not a login system, not a notification engine, nothing structurally heavy. Just people and their real answers.

This week that shipped. It's called Builder Stories. First person featured is the friend who suggested it, which felt like the only honest way to open it, since the idea was his.

Two things stood out building it. First, the honest gap between what people say they use and what they actually open daily is bigger than expected. Second, the ask itself has to stay small, one sentence, no pitch, or the yes rate drops fast. Learned that the hard way testing different framings across a few days, an announcement post barely moved the number, a direct challenge asking people to drop their actual stack in the replies did.

Daily numbers this week bounced around more than usual, 7, then 3, then 2, then 8. Tracked cleanly against which angle was used that day, not luck. Repetition of the same framing three days running flattened it. A genuinely different hook, even on the same underlying feature, brought it back.

The honest lesson from the week isn't really about the feature. It's that consistency and honest specificity keep working, every time they're tried, and every time they're abandoned for something flashier, the numbers show it within a day or two.

xedge.tech/builders if you want to see where it landed.

This is what i planned in order of trying to get a spike in my traffic

Harsha Kumar — Sat, 18 Jul 2026 10:02:42 +0000

i've added a new feature section in my site xedge.tech where i show case builders and their opinion about tools like what tools they , why only that tool and many questions that begginers wanted answers for and we already got 2 builders in the showcase and they are highly experienced

this can help people to decide which tool to use for their project and also it clears up the confusion . the 2 guys i asked questions about they are experienced they are programming before the ai enhancements were added so their advice might help a lot and I'm gonna find more builders and tech enthusiasts to get more info about ai tools in their own perspective and including why they pay for that specic tool and a lot . so i want you guys to be stay tuned and check xedge daily about new builder stories and support it .

Why I built a page with no immediate growth upside, and shipped it anyway

Harsha Kumar — Thu, 16 Jul 2026 10:05:42 +0000

XEdge has a discovery problem that's already solved. Describe a goal, get a stack, done. What it didn't have was a reason for anyone to come back after that first answer.
A friend pointed this out plainly a few weeks ago, and independently, someone in a community I'm active in asked almost the same question from a different angle, is there any incentive to keep using this. Two people, no coordination, same gap named.
The fix didn't need to be complicated. Real builders, their actual AI stack, one short quote, a photo, a permanent page that grows over time. No login system, no notification engine, no new infrastructure.
It's live now. First person featured is the friend who suggested it, which felt like the only honest way to open something built on someone else's idea.
xedge.tech/builders, and if you want to be one of the next few featured, this post is an open invitation.

The newsletter stack that gets you to your first $50 — no audience required

Harsha Kumar — Wed, 15 Jul 2026 08:47:06 +0000

Most "start a newsletter" advice skips the order of operations. Here's the exact one, five tools, in sequence:
Perplexity for niche validation — search actual complaints in your space, not trend reports. Claude for the first five issues, written in one batch sitting, not live day-by-day. Beehiiv free tier for the platform — zero cost to start. One insight post daily for growth, subscribe link in the first comment so the post itself reads as value, not a pitch. First $50 from one manually-sold sponsored slot, before any subscriber threshold, because the first sale validates the model faster than waiting for scale.
$0 total cost. First subscriber same day you start.
Full playbook with every prompt used at xedge.tech.

What actually matters when someone asks you to "build a chatbot" for their business

Harsha Kumar — Sat, 11 Jul 2026 07:52:00 +0000

Got a real lead this week — small business owner wanting an AI chatbot for his site. Here's the honest breakdown of what that actually requires, since "chatbot" means five different things depending on who's asking.
Scope before building. Most small businesses don't need a custom-trained bot. They need their top 10-20 repeated customer questions automated well. Find that out first.
Platform over custom build. Tidio, Crisp, Intercom's lower tiers — pre-built AI chat widgets connect to a knowledge base fast. Custom builds are rarely worth it below a certain scale.
The bot is only as good as its input. Feed it real past customer conversations, not generic FAQ copy. Specificity is what makes it feel useful instead of annoying.
Always build the human handoff. A bot that traps a frustrated customer in a loop does more damage than having no bot. This is non-negotiable.
Test before launch. Twenty real customer-style questions, see what breaks, fix it before it's client-facing.
Full customer support AI stack at xedge.tech.

The no-code SaaS stack that actually gets you to a paying user

Harsha Kumar — Thu, 09 Jul 2026 05:32:28 +0000

No-code SaaS consistently surprises founders because the barrier to a real, working product is genuinely gone now. Here's the stack:
Validation: Claude — before touching a builder, describe the idea and ask Claude to steelman the 5 biggest reasons it fails. Cheapest possible filter.
Building: Bubble.io — real database, real auth, real workflows, no code. Free tier is enough to validate and launch a basic version.
AI features: OpenAI API via Bubble plugin — the unlock most no-code founders skip. Connects in 20 minutes, instantly makes the product feel more capable than it looks.
Payments: Stripe + Bubble — charge from day one, even a token amount. Paying users tell you the truth; free users tell you nothing.
Distribution: show up where your users already are — solve a real problem in a real thread first, link second.
Total cost: $0. Time to live product: one weekend. Time to first paying user: 2-4 weeks with real effort.
Full playbook at xedge.tech.

this is how I started Xedge from 0

Harsha Kumar — Sun, 05 Jul 2026 03:53:32 +0000

I'm Harsha and i'm from india , once i'm in college i was obsessed with this ai tool market when i tried to use them so many questions ,

which tool is better ?

-does hype really matches that output ?

is there any underrated tool that i'm missing

i just become from obsessed to overwhelmed and then i got an idea like what if there is a guide to tell me , but when i clearly did research there are already a bunch of tools directories out there like the futurepedia , there is an ai for that , etc . i noticed that all they do is like dumb a ton of tools and describe about them . that doesn't make any sense to me . i asked myself " is there a better way of organisation rather than dumping tools ?". then i thought about an ai ecosystem , where they'll get ai tools , stacks , professional prompts , automations , templetes , agents , api's , and i even imagined a interface within it where they can build their custom software by using open sources . they are not only going to buy the templetes from others they can build and sell them too . simply a places where people can access everything related to ai at one place where you can buy , sell and create custom for your own .

i think about it like an ai paradise . but at that point i really don't know how to code , i only know the c language . then just did some research got the elite sources to learn html , css and js i got the documentations in 1 tab and the videos in another and opened vs code for practice . in less than a month i've learned css , html , java script , python and MYSQL .

Then I heard about ai open source high end models writing code for free . Im like " damm i have to use this free 1 time usage " i explained almost everything related to xedge i imagined about and it just gave me a single vibe coded home page , i'm very dissapointed at that point because i thought it might build a whole website for me . then my inner voice kicked in and told me " you have the skills , just do it " , i used that same colour pallete generated by ai and created like 4 pages and learned a lot of stuff in that building phase , and it became very easy but time taking process , then i get to know about claude , gpt , and a bunch of other tools .

I used them to write code faster and after it done doing things i'll check all the code based on my knowledge and do corrections if i want , that is how i built the my ideas first prototype .

then i increased my connections mastered marketing certainly the organic marketing and the SEO game , i did a lot of research and learned a lot of stuff , the on i've been grinding on gaining knowledge among tech side and distribution side while building the product , i put all my efforts and now i have over 600+ users in my platform and i spent almost 0$ ( except for the domain ) .

even though i havent made a single penny from my skills or from my product , I'm really proud to myself for doing all this in less than 3 months and starting from 0 and spending 0 . And i believe i could really get my xedge to its final phase and gnerate the real revenue ,

How to validate any startup idea in 48 hours with $0

Harsha Kumar — Thu, 02 Jul 2026 08:18:10 +0000

Most founders skip validation because it feels like delaying the real work.
Validation IS the real work. Building the wrong thing for 6 months is the delay.
Here's the exact process:
Find real complaints: Perplexity
Search for people already expressing the problem you're solving — Reddit, review sites, forums. Copy the exact language they use. That's your marketing copy and your proof of demand in one step.
Size the market honestly: Claude
Describe your idea and ask Claude to calculate TAM/SAM/SOM using three different methods — top-down from industry reports, bottom-up from customer count, and value theory. If the three methods don't roughly converge, you don't understand your market well enough yet.
Map your real competitors: Claude + Google
Not just direct competitors — what do people do instead of your solution right now? That "instead of" answer is your real competition, and it's almost always more honest than a competitor matrix.
Test demand without building: Carrd
Free one-page landing page with a waitlist signup. If 20 strangers won't give you their email for something free, the idea has a messaging problem at minimum and a demand problem at worst.
Talk to 5 real people
Not friends. Not family. Strangers who actually have the problem. One conversation where someone says "I've been looking for exactly this" is worth more than any analytics dashboard.
Total cost: $0
Time investment: 48 hours
Time saved if the idea is wrong: months of your life
Full validation playbook with every prompt and template at xedge.tech
What idea are you sitting on right now that you haven't validated yet?

Why I stopped trying to grow and started trying to help — and what happened to XEdge's traffic

Harsha Kumar — Wed, 01 Jul 2026 05:02:04 +0000

For the first two weeks of building XEdge I didn't mention the product once.
I showed up in Discord servers, answered questions on Dev.to, replied to LinkedIn posts from bigger accounts — all without pitching anything. Just genuinely trying to be useful.
By the time I mentioned XEdge, people already knew I knew what I was talking about. The click-through rate on those first mentions was dramatically higher than anything I've posted since, because trust was already there before the ask.
700 users later, $0 marketing spend, I keep coming back to the same lesson: distribution isn't a numbers game, it's a trust game.
You don't need more reach. You need more trust density in the right rooms.
What room are you in right now where you've been lurking instead of contributing?

A month in, 0 sales, and what I think I actually got wrong

Harsha Kumar — Mon, 29 Jun 2026 03:45:02 +0000

Real numbers: XEdge has 700+ users, $0 revenue, and a $29 playbook that hasn't sold a single copy in a month, even with a free coupon code live.
Here's my honest read on why.
I assumed "real, lived experience" would sell itself. It doesn't. I wrote a genuinely specific document — actual TAM/SAM/SOM math from XEdge, the exact validation prompts I used, the pricing mistake I almost made — but my posts about it stayed vague. "Check out my playbook" doesn't tell anyone why it's different from the thousand other startup guides already out there.
Specificity is the thing I skipped. Generic hooks don't sell specific value.
So today I'm being as concrete as possible: this is the actual market sizing process for XEdge, shown step by step. These are the actual prompts, copy-pasteable. This is the actual pricing fear I almost gave into and how I avoided it.
If you're early-stage and stuck before you've even started, free with code FIRST50, or $29 otherwise.
The lesson: vulnerability gets attention. Specificity converts it. I had the first one. I was missing the second.