Every week we collect stories of people who actually built something. Solo devs. Tiny teams. Founders with no engineering background.
Real builds. Real numbers. No fluff.
Here are this week's three.
A growth marketer from Brazil built a safety app in 45 days. It's at $456K ARR.
Sabrine Matos had no engineering background. She was a growth marketer who kept hearing the same story from women around her — they had no easy way to check if someone they were meeting was safe.
She scoped the problem down to one thing: give consumers access to criminal background check data that was normally locked behind corporate databases.
She built the entire thing on Lovable. Front end, backend, integrations, marketing site. No engineers hired. Shipped in 45 days.
Plinq now has over 10,000 users, is growing 300% month over month, and has reportedly helped women avoid 200+ dangerous situations. She's raising a seed round.
The part that stands out: she didn't start with a feature list. She started with one clear problem and refused to add anything until the first version worked.
The former CEO of Amazon's consumer business built a CRM in one night.
Dave Clark ran Amazon's worldwide consumer operation. Now he's CEO of a supply chain startup called Auger.
Last week he posted that he'd built a custom CRM, a full customer prototype, and reworked his pitch deck into an interactive web view — all in one weekend. The CRM took a night and a morning.
His reasoning: configuring Salesforce or HubSpot to do what he wanted was harder than just building it from scratch with AI tools.
The post went viral. Bloomberg covered the trend. The debate it kicked off is worth paying attention to — when does "build your own" actually make more sense than buying off the shelf?
For most of us the answer is: when you know exactly what you need before you start. That clarity about requirements is what separates a productive weekend build from a rabbit hole.
His first app failed. Then he shipped 30 in a year and hit $22K/month.
Max Artemov's first app didn't work. He'd spent months building something nobody searched for.
So he flipped the process. Instead of building one perfect product, he started with keyword research — finding problems people were already typing into the App Store — and scoped each app down to the smallest thing that could solve that search.
30 apps in under 12 months. $22K/month combined. The portfolio approach means no single app failing can kill the business.
The lesson he keeps coming back to: his first app failed because he over-scoped it. Everything after that worked because he figured out what to build before he built it.
That's the pattern across all three stories this week. Sabrine scoped down to one feature. Dave knew his requirements before he opened the editor. Max learned to validate demand before writing code. The builders who ship fastest are the ones who figure out what to build before they build it.
Scope before you build
Every story this week points to the same thing — clarity about what you're building matters more than how fast you can code it.
If you want help scoping your next project before you start building, try Projectmaven. It's free.