What's going on, it's Jonathan.

You show someone an early app. They ask for chat, reminders, a dashboard, and three integrations.

It's tempting to put everything on the build list.

Pause and ask what they were trying to get done.

Imagine you're testing a simple tool for collecting client feedback. Someone asks for chat because they keep losing revision notes across email threads.

The underlying job is getting the feedback into one place. Chat is one possible approach.

Here's a simple way to turn that conversation into a focused first version.

Use the customer's words. For this example: Collect the client's revision notes in one list I can work through.

Keep that sentence at the top of your build brief.

Needed now: without it, the person can't finish that job.

Worth testing: it might help, but you need to see where someone gets stuck.

Later: useful for a different task or a future version.

A request can be reasonable and still belong on the later list.

In this example, the client submits a note and the designer can find it, understand it, and mark it handled. Test that whole path.

Watch someone try it. Record where they hesitate. Use those observations to choose the next improvement.

That gives your next build prompt a clear purpose.

MakerAI offers idea-validation tools and step-by-step Lovable build prompts. Bring a focused brief so the starting point is the job you've chosen to solve.

Pick one task. Write the finish line. Build and test that version.

Let's build. 🦁

Jonathan

Sponsored

28 Wishes sells ice cream in Los Angeles. Below 70°F, sales fall about 20%. So the owners put about $20 a day into Kalshi weather markets, taking the cold side. The days that keep customers away now pay something back. See how other owners are doing it

See how hedging works