DEV Community: Trishan Roy Roddur

I Built an AI Scope Generator in 2 Weeks

Trishan Roy Roddur — Fri, 17 Apr 2026 10:08:35 +0000

I just shipped Plannomial.

The problem: Every time I tried to build something, I'd spend 3 days overthinking the tech stack instead of actually shipping.
So I built something stupid simple — describe your idea, get a weekend MVP scope + tech stack + to-do list in 60 seconds.
The First Customer:
I shipped it on Twitter. A guy named Maks saw it, thought it was useful, and paid $19.
That's it. That's the whole story so far. But that $19 meant everything because someone I didn't know thought my idea was worth money.
What Changed After That:
Maks gave feedback: "I don't understand the tech stack you gave me. Can the AI explain it?"
So I built Plue — an AI assistant that lives inside Plannomial.

Now it can:

Explain any tech stack in plain English
Help you customize your MVP
Guide you through implementation

Shipped that in 2 days.
Current Status:

1 paying customer
~5 signups
Just improved the landing page based on feedback
0 regrets

What I've Learned:
Build fast. Listen to real feedback. Ship the simple version first. The ambitious stuff can wait.
If you're building a weekend project and want a clear scope without overthinking, try Plannomial: plannomial.netlify.app
Real feedback is gold right now. Tell me what sucked.

Built Plannomial in 6 Days. Here's What 43 Users Taught Me.

Trishan Roy Roddur — Fri, 03 Apr 2026 05:58:41 +0000

The Problem

Every developer has this moment:

You have an idea. You're excited. You sit down to code.

Then: "Wait. What exactly am I building?"

You could spend weeks planning. Or you could just describe the idea and get instant clarity.

That's Plannomial.

The Journey (6 Days)

Day 1: Started building
Day 2: Shipped MVP
Day 3: Got feedback ("UI is confusing")
Day 4: Rebuilt the UI based on feedback
Day 5: 43 users. Still growing.
Day 6: Just shipped v2

What 43 Users Taught Me

1. People hate feeling lost
Most feedback: "I didn't know what to do next"
Solution: Step-by-step flow instead of everything at once

2. PDF export matters
Users wanted to take roadmaps outside Plannomial
Built it. People love it.

3. Persistence beats perfection
v1 was confusing. v2 is clear.
Shipped v1 anyway. Got feedback. Improved.

4. Build for yourself first
I built Plannomial because I get stuck planning.
That's why it resonates with users.

What Plannomial Does

You input: Your project idea
You get (in 30 seconds):

Weekend MVP (what to ship in 48 hours)
6-month vision (full roadmap)
Tech stack suggestions
Step-by-step to-do list

The Monetization Question

43 users. $0 revenue.

Pro tier exists ($19/month for unlimited + PDF + organized history).

But 0 conversions.

Why?

Users get what they need from free version
They generate 1 roadmap and leave
No repeat use = no reason to upgrade

What's Next

Not more features. But:

Email capture (stay connected)
Usage tracking (who generates 2+ roadmaps?)
Targeted Pro messaging (upgrade when they need it)

The Real Lesson

Shipping > Planning.

I could have spent 2 months perfecting Plannomial.
Instead, I shipped in 2 days.

Got 43 users. Got real feedback. Improved based on reality, not assumptions.

That's worth more than any perfect product.

Try It

Free: plannomial.netlify.app

Feedback welcome. Especially on monetization — how would YOU price it?

# I Got 26 Users in 3 Days. Here's How (And What I Learned)

Trishan Roy Roddur — Tue, 31 Mar 2026 02:40:26 +0000

The Idea

Every developer has this moment:

You have an idea. You're excited. You open your editor.

Then: "What do I actually build?"

I built Plannomial to answer that question. You describe your idea → get a complete roadmap in 30 seconds.

The Timeline

Day 1: Started building
Day 2: Shipped MVP (conversational UI, Groq API integration, beautiful dashboard)
Day 3: Improved UX based on feedback
Day 4: 26 users

How I Got 26 Users

Honestly? I'm not entirely sure.

Could be:

X posts with #BuildInPublic hashtag
Dev.to articles (posted twice)
IndieHackers post
Discord communities (shared yesterday)
Reddit comments
Word of mouth
All of the above?

Lesson: Without UTM tracking, I can't attribute properly. Adding that next.

What Worked

1. Ship fast
Don't wait for perfect. Ship when it's good enough. Feedback will tell you what to fix.

2. Beautiful UI matters
People judge books by covers. Spent time on dark theme, animations, spacing.
Result: Users stuck around.

3. Solve a real problem
Scope anxiety is real. I feel it too. Built for myself first.
Result: Real users found it because it solved their actual problem.

4. Build in public
Shared progress on X, Dev.to, IH. Didn't hide mistakes.
Result: People are interested in the journey, not just the product.

5. Iterate immediately
First version had confusing UI. Users pointed it out.
I rebuilt in 24 hours with step-by-step flow.
Result: Better UX, better retention.

What's Hard

Attribution: Don't know where users came from
Retention: Have no way to contact them (yet)
Monetization: No paying customers yet (Pro tier tomorrow)

What's Next

This week:

Launch Pro tier ($19/month)
Add email capture (newsletter signup)
Add UTM tracking (future attribution)
Get first 5 paying customers

Month 2:

50-100 total users
$100+ MRR
Better analytics

The Real Lesson

Shipping beats planning.

I could spend weeks perfecting Plannomial. Instead, I shipped in 2 days.

Got real feedback. Improved. Got users.

The product isn't perfect. But it's real. And people are using it.

That matters more than perfect.

Try It

Free: plannomial.netlify.app

Feedback welcome (even brutal feedback helps).

What's stopping you from shipping your idea?

I Built Plannomial — Stop Scope Anxiety, Start Shipping

Trishan Roy Roddur — Sat, 28 Mar 2026 09:51:58 +0000

I Built Plannomial — Stop Scope Anxiety, Start Shipping

The Problem

You have an idea. You're excited. Then you get stuck.

"What features do I build first?"
"Can I actually ship this in a weekend?"
"Am I overthinking this?"

This is scope anxiety. It kills more projects than code bugs ever will.

The Solution

I built Plannomial to solve this in 30 seconds.

Describe your idea → Get 2 instant roadmaps:

⚡ Weekend MVP (48 hours, ruthlessly scoped)
🚀 6-Month Vision (full feature set)

How It Works

Type your project idea
Pick your timeline
Get structured roadmaps
Start building (not planning)

Why I Built This

I'm a developer. I get stuck here too.

I'd spend hours planning, then lose motivation. Or I'd start coding without a plan and scope crept to death.

So I built a tool to answer the ONE question that matters: "What's the smallest version I can actually ship?"

Try It

It's free. Takes 30 seconds.

plannomial.netlify.app

Honest feedback welcome — even if it feels boring or useless. That helps more than feature requests.

What's Next

Building in public. Shipping updates based on real feedback.

If you try it, let me know what breaks or confuses you.

SideProject #BuildInPublic #Productivity #DevTools

How do you plan a coding project before you start?

Trishan Roy Roddur — Fri, 27 Mar 2026 04:03:18 +0000

**I always get stuck between 'I have an idea' and 'I actually start coding.'
Do you:

Spend hours planning then lose motivation?
Just start coding and figure it out?
Something in between?

What actually works for you? Looking to figure out my best workflow.******