GiveFeedback: zero to paying clients in six weeks

GiveFeedback.dev went from nothing to paying clients in six weeks. It won the $100K grand prize at Lovable Shipped Season 1, finished #1 globally against 5,800 builders, and had revenue before the prize was even decided. I built it solo, in August 2025, as a deliberate test: take eight years of operating discipline out of a scaled company and see whether it survives contact with a hard deadline and no team.

This is the receipts page. If you are deciding whether to work with me, inspect this project first, because nothing about it can be attributed to anyone else.

Why I entered#

By 2025 I had spent eight years at Verto Health. Employee #2, helped scale it to 80 people, 100+ deployments across Canadian and US health systems, 10M+ patient journeys orchestrated on the platform. It reads well. It also has a known problem: a resume like that cannot tell you how much was me and how much was the machine around me. Companies at scale launder individual contribution. Everyone who was in the building gets to claim the outcome.

Lovable Shipped Season 1 was a way to un-launder it. Six weeks, money on the line, 5,800 other builders. No engineers to spec against, no sales team to hand leads to, no brand to borrow trust from. If the discipline was real, it would show up in the result. If most of it had been the machine, that would show up too. Either answer was worth having.

What got built#

GiveFeedback.dev is a feedback and task management product. It takes the messy stream of client feedback (emails, call notes, screenshots, "one quick thought") and turns it into structured, trackable work that both the client and the builder can see. I picked it because I had felt the pain directly in client work, and because it passed two tests at once: small enough to ship in six weeks, real enough that someone would pay for it.

That second test was the actual product decision. The competition scored shipping. I scored myself on revenue, because a prize judges a demo and a paying client judges a business. That one bar changed most of the downstream calls: what got cut, what got polished, and who I was talking to in the first week instead of the last one.

The operating decisions, in order#

I did not keep a tidy journal during those six weeks, and I distrust case studies that produce a clean day-by-day log months after the fact. What I can give you honestly is the sequence of decisions and roughly where each one landed.

Decide what it is not, first. The opening stretch went to scope, and the useful work was subtractive. One workflow, end to end: feedback in, structured task out, visible status. Integrations, analytics, anything resembling a permissions matrix went onto a list I agreed not to open until after the deadline. This is standard advice that almost nobody follows under competition pressure, because a public leaderboard rewards visible surface area and scope-cutting produces none. Years of product management are, in large part, training in taking that trade anyway.

Get it in front of people who could pay. As early as I could stand it, the product went into real client-work contexts rather than demo contexts. That is the only reason there were paying clients before the prize closed. Payment was the one test I could not grade myself on, which is exactly what made it worth optimizing for. A stranger's credit card is the least sentimental judge available.

Ship something every day the tool allows. Lovable compresses the build loop enough that the constraint stops being code and becomes judgment: what to build next, what to skip, which feedback to believe. I have more to say about where that compression is real and where it runs out in is Lovable good for real products, but the short version is that the tool moves the bottleneck. It does not remove it.

The fight I nearly lost. Here is the part I would quietly omit if this page were marketing instead of a case study. I nearly shipped a week late, and the reason was that the marketing site won a priority fight it should not have won. A marketing site is seductive work: progress is visible in hours, it demos beautifully, and it feels like distribution. Meanwhile the product's remaining work was grindy and invisible. I have watched that exact failure mode eat roadmaps for a decade, from the other side of the table, and I still walked into it with money on the line. The deadline did not protect me. Deadlines make attractive-but-wrong work more attractive, not less.

The rough parts#

The six weeks were rough, and I want that on the record next to the trophy. Solo means every stall is yours: no one to trade tasks with when you are stuck, no one whose optimism is fresh when yours is spent. The prize framing adds its own pressure, because the opportunity cost of one bad afternoon is visible on a leaderboard.

The other honest entry: I underestimated how much of the speed was the tool versus the discipline I brought. That is an uncomfortable sentence for someone whose whole pitch is operating discipline, so let me keep it precise. The discipline decided what to build, when to cut, and what revenue bar to hold. The tool decided how fast the building went. Both were necessary, and I had the ratio wrong going in. Getting the ratio right matters, because every estimate I now give a client depends on it.

The outcome#

The receipts, plainly:

• $100K grand prize, Lovable Shipped Season 1, against 5,800 builders.
• #1 globally for GiveFeedback.dev.
• Paying clients before the prize closed, which was my own bar for the six weeks.
• Same season, a second product: Lotso Travel finished #7 globally and now does roughly $200/day passively, across 195 countries.
• Vibe Coding L5: Diamond, Lovable's highest certification.

GiveFeedback did not end with the competition. It runs today as one of my ventures, in daily use on real client work, which is a longer and less glamorous test than any prize.

What transfers to any founder#

The competition details are trivia. Four things underneath them are portable, and none of them depend on Lovable.

Score yourself on revenue, not on whatever leaderboard you happen to be standing on. Every context hands you a default metric: the prize, the launch upvotes, the demo applause. The default metric is almost never the business metric, and choosing your own changes your daily decisions more than any productivity system will.

Scope is a decision you make once and then defend daily. Cutting features at the start is easy. The hard part arrives mid-build, when the cut feature would demo well and the remaining work is boring. Write the not-doing list down and treat reopening it as an event, not a mood.

Attractive-but-wrong work gets stronger near deadlines. My marketing site fight is the specific instance. The general rule is that visible, fast-feedback work will always out-lobby grindy, invisible work exactly when you can least afford it. If a task feels suspiciously satisfying during a crunch, audit it.

Know what the tool did versus what you did. Not for humility points. Your next estimate, your next hire, and your next client promise all depend on attributing speed correctly. I got this partly wrong and paid for it with a rough recalibration. It is cheaper if you do the accounting deliberately.

Where to go from here#

The fuller narrative of the six weeks, including the parts that did not fit a case study format, is in how I won Lovable Shipped. If you are a founder staring at a brief and wondering whether six weeks to shipped is realistic for your product, that number came from this project, and it is one of the engagement shapes I offer. A call makes sense if you want the honest version of whether your scope fits the clock. Skip it if starting anything requires three layers of approval.