Suggesto.io

Seven days ago, this was just a concept and a fresh Next.js terminal. Today, Suggesto.io is officially launched and open for signups. We hit the goal!

Suggesto.io si live on ProductHunt and Uneed. Please upvote!!!

Day 6 Recap:
✅ Pricing finalized and payment integration complete.
✅ Landing page and SEO prepared.

Key Lessons Learned from the Sprint:

1. Scoping is Everything: The moment I tried to add a "nice-to-have" feature (like advanced reporting), I cut it. Sticking religiously to the core MVP was the only way to launch in 7 days.

2. Supabase: The biggest time-saver. Using its Auth and Edge Functions together reduced backend deployment time by at least 70%. Highly recommended for speed-to-market.

3. Feedback is Fuel: Sharing daily progress on IH and X provided immediate motivation and kept me accountable.

The challenge is over, but the work just began. I'm prioritizing the first post-launch feature based on early feedback. What is the single most important feature Suggesto.io must build next? (e.g., Tagging, Status/Roadmap updates). Let me know in the comments, or better yet, try Suggesto.io and give me feedback using my own widget!

The code is 95% feature-complete. Day 6 is focused on the business, marketing, and legal groundwork necessary for launch.

Day 5 Recap:
✅ Production-ready, tiny JavaScript SDK/Snippet.
✅ Anti-spam V1 deployed.

Day 6 Focus & Progress:

1. Polar Integration (Payments): Integrated Polar for simple, secure one-time payments for the Pro tier. This was chosen over Stripe Subscriptions to reduce complexity and minimize recurring revenue management headaches for the MVP.

2. Pricing Model Finalized:

• Free Tier: 1 Board, 50 Feedback items, Basic Voting.

• Pro Tier ($14.99 One-Time): Unlimited Boards, Unlimited Feedback, Email Notifications, Comments/Discussions (post-MVP).

1. SEO & Copywriting: Updated the landing page copy based on the main target keywords: "feedback widget," "dev-friendly," and "cost-effective." The goal is to clearly communicate value to the developer niche.

Why One-Time Payment?
For an initial launch, the $14.99 lifetime deal acts as a low-friction hook. It encourages early adoption, generates immediate cash flow, and lets me focus on the product without being shackled by monthly churn tracking. I can always pivot to MRR later.

I've settled on the $14.99 one-time payment. As an Indie Hacker, what is your gut reaction to this pricing model for a lightweight utility tool? Is it too cheap, or is the "lifetime access" angle compelling enough?

We are entering the final stages! Today's task was the hardest: building a robust, tiny, and non-breaking script that works everywhere.

Day 4 Recap:

✅ Public Feedback Board is functional.

✅ Core Upvote logic implemented and tested against simple abuse cases.

Day 5 Focus & Progress:

1. The SDK/Snippet: This is the product. The script must dynamically inject the React widget component into the client's page without causing conflicts. The final script size is ~8KB gzipped, which is incredibly fast.

2. Installation Guide: Created the copy-paste instructions in the developer dashboard. The instruction is literally: "1. Copy this script. 2. Paste it before the closing </body> tag."

3. Anti-Spam V1: Implemented server-side rate-limiting on the Supabase Edge Function to prevent immediate API flooding. I also added a simple Honeypot field to the widget form to catch basic bot submissions.

The Power of Simplicity
If the installation takes more than 5 minutes, developers abandon it. My focus on a clean JS injection and minimal configuration is directly aimed at maximizing the "time-to-first-feedback" metric.

I'm struggling with the default widget trigger text. Should it say "Feedback" (clear but generic), "Feature Request" (too specific), or "Suggest" (on-brand but less clear)? What would you, as a developer, prefer to see on your site?

Four days in, and the application is starting to look like a coherent product.

Day 3 Recap

✅ Magic Link developer authentication is live.

✅ Dashboard is ready for snippet generation.

Day 4 Focus & Progress:

1. Public Board View: I built the public-facing board (/board/[board_id]). This is where users see all submitted feedback. I focused on making it highly readable and fast to load.

2. Upvoting Logic: This was the main technical challenge today. The logic:

• Unauthenticated Voting: Users can vote without signing up, but we use an anonymous identifier (stored in localStorage and rate-limited by IP) to prevent simple ballot stuffing.

• Sorting: The default sort is "Top" (most votes), which is essential for feature prioritization. I used a simple query ORDER BY votes_count DESC.

1. UI Polish: Added basic search/filtering capabilities to the public board for developers.

Market Positioning
This board, even in its MVP state, offers the core functionality (collection + prioritization) that costs $50+/month on competitor platforms. That’s the value proposition: "90% of the functionality at 10% of the price."

The public board is key for prioritization. Beyond simple upvotes, do you find features like "Vote Decay" (where older votes lose weight) or "Comment Count" more useful for deciding what to build next?

We are at the halfway point, and today was focused on the developer experience. No product can be launched without a way for the user to manage their data.

Day 2 Recap

✅ Widget UI/JSX components finalized.

✅ Core POST /feedback API is functional and secure (RLS enabled).

Day 3 Focus & Progress

1. Magic Link Authentication: I implemented Supabase Auth with Resend for email delivery. I chose the "magic link" flow (passwordless) because developers hate creating yet another password. It's fast, secure, and improves the UX immensely. It took me less than 2 hours to get the full flow working—a huge win for the speed challenge.

2. Dashboard Shell: I built the primary dashboard layout using Shadcn UI components. The main feature is the "Create New Board" form, which automatically generates a unique board_id and the corresponding JS installation snippet.

First Lesson Learned
While Magic Link auth was fast, configuring the domain whitelisting for the Resend API (to prevent spam/abuse) took longer than expected. Little setup tasks always eat up time!

Your Feedback is Critical (CTA)
For B2B tools, I prefer passwordless/magic link authentication. Do you, as an Indie Hacker, prefer Magic Links, standard Email/Password, or OAuth (Google/GitHub) for new dev tools? If OAuth, which provider is a must-have?

Yesterday, I laid the foundation. Today was a successful race to the core MVP.

Day 1 Recap:

✅ Monorepo setup, Next.js dashboard initialized.

✅ Supabase database schema (Boards, Feedback, Votes) defined.

✅ Auth structure planned out.

Day 2 Focus & Progress
The most critical piece is the end-user widget itself. It has to be blazingly fast.

1. Widget UI Design: I designed a super minimal, floating button that opens a clean modal. The entire widget is rendered in a shadow DOM to avoid CSS conflicts with the host application.

2. Core API Endpoint: I built the first Edge Function in Supabase (/api/v1/feedback) to handle unauthenticated submissions from the widget. Crucial technical decision: I'm using RLS (Row Level Security) in Postgres to ensure one user's widget data can never accidentally query another's, even if they manipulate the request payload.

Technical Trade-off for Speed:
I initially wanted to include real-time vote updates via Supabase Subscriptions, but to hit the 7-day deadline, I'm delaying real-time features. MVP will use simple polling/refresh on vote submission. Done is better than perfect.

Your Feedback is Critical:
When you integrate a third-party script like this, what is your biggest concern about performance? Is minimal bundle size (under 10kb) more important to you than a rich UI, or is a great design worth a slightly larger payload?

Hello, Indie Hackers community! I'm kicking off an ambitious 7-Day Build-in-Public Challenge to launch a full SaaS product: Suggesto.io.

The Problem I'm Solving: Collecting user feedback shouldn't require complex integrations or expensive monthly fees, especially for solo developers and micro-SaaS founders. Tools like Canny or Nolt are great, but they often feel like overkill (and budget killers) for a simple feedback loop. Users shouldn't have to leave the app and sign up for a third-party platform just to tell you a button is broken.

The Suggesto.io Vision: A lightweight, universal JavaScript widget that can be installed in under five minutes with a simple <script> tag. It lets users leave feedback and vote on existing requests directly inside your application. Simple, fast, and cost-effective (I'm planning a low-cost, one-time payment Pro tier).

The Challenge Outline (What I must deliver in 7 days):

1. Widget SDK: The embeddable JS snippet.

2. Dashboard: For developers to create boards and grab the snippet.

3. Authentication: Simple Magic Link auth for developers.

4. Public Board: The upvote/downvote board.

Day 1 Progress & Decisions (The Foundation): Today was all about the tech stack, focusing on speed and maintainability:

• Frontend: Next.js (for the dashboard), Vanilla JS (for the widget).

• Database/Backend: Supabase (Postgres, Auth, and Edge Functions for API endpoints). This lets me move fast without setting up custom servers.

• Styling: Tailwind CSS + Shadcn UI (for rapid dashboard component building).

• Email: Resend (for Auth Magic Links).

I've already set up the initial monorepo structure and designed the core Supabase schema (Boards, Feedback, Votes).

Your Feedback is Critical: I'm relying heavily on Supabase for the entire backend. Have any of you successfully scaled a B2B SaaS with only Supabase? Any "gotchas" I should watch out for over the next 6 days? Let me know!