FeedbackFlow

The problem

Website feedback usually arrives as a screenshot in Slack, a long email or a spreadsheet of "change the button on page 3". Developers lose time working out which element a comment is about, and clients lose patience repeating themselves. The idea behind FeedbackFlow was simple: let people click the exact spot on a live site and leave the comment there.

What we built

• Embeddable widget. A few lines of code add FeedbackFlow to any site or staging environment.
• Point-and-click comments. Comments are pinned to the element they are about, so there is no guessing.
• Threaded discussion. Teams and clients reply in context, resolve comments and get notified when something changes.
• Access control. Project-level passwords decide who can view and add comments.
• Custom branding. Colours and styling so the widget matches the client's product.
• Billing. A single Pro plan with a 14-day free trial, handled through Stripe.

The core loop comes first

FeedbackFlow was built on our 30-day MVP model, where one workflow has to work perfectly before anything else gets time. Here that loop is: install the widget, click an element, leave a comment, see it in the dashboard. Branding, notifications and access control only matter once that loop is solid. It is the same order we use on every MVP build.

What it shows

A focused SaaS with an embeddable script, multi-tenant projects and subscription billing fits the 30-day model when the scope is honest about version 1. If you are planning something similar, the week-by-week MVP timeline shows how we break it down, and the cost calculator gives you a price range in a minute.