Illustrative example – fictional idea

Example 03 · Family · Consumer marketplace

Kids' clothes swap

A size-by-size clothes swap for the parents at one Melbourne primary school, run through a Friday pickup table and an app that tracks each family's credit.

Launchifier is a guided path: five stages, 45 tasks, and a go/no-go gate at the end of each stage. Below is every task this founder was given, what they did, and what the guide decided.

Outcome

Go – build it

Interviews done

12

Features cut

9 → 3

Build budget

A$150 of A$800

The idea, as the founder entered it

“I'm a stay-at-home dad in Melbourne with two kids who grow out of everything in about four months. We have bags of barely worn clothes in the garage, and we keep buying new ones. I want an app where parents swap kids' clothes by size: you drop in a bag, you get credit, and you pick out the next size up. Everyone I've mentioned it to at school pickup loves the idea. I can put in around A$800.”

The path the founder followed

Stage 1 of 5

Validate

Is this a real problem for a customer you can reach, who wants it solved?

Gate: Go. Move on to Define.

Tasks in this stage

13 of 16 done

  • ✓Describe who has the problem and what it is
  • ✓List at least three alternatives, including the low-tech ones
  • ✓Record your visitors, signups and result
  • + 13 more

What the founder did: talked to 12 parents at two schools, then ran a test: a swap table at one school's Friday pickup. 23 families brought 41 bags, and 19 of them took clothes home. Asked about an app, 9 of 12 said they'd use one if their own school's parents were on it, but only 2 would swap with strangers across the city.

What the guide flagged: a city-wide swap app has to fill both sides at once, and Vinted, Facebook Marketplace and op shops already serve strangers swapping clothes. The founder couldn't name the first 50 users of a city-wide app, but could name 50 at one school. That became the starting point: a closed group that already trusts each other and meets twice a day.

Why Go: the swap table proved supply and demand in a single afternoon, at a school where the founder already knows the parents. The narrowed version doesn't need strangers, shipping or ratings. Weak spot noted: it grows one school at a time, and every school needs a parent willing to run the table.

Stage 2 of 5

Define

What's the smallest thing you can build that proves value?

Gate: Go. Start building.

Tasks in this stage

11 of 14 done

  • ✓List at least three feature ideas
  • ✓Write your metric and target
  • ✓Make the plan fit your budget
  • + 11 more

What got cut: the first list had 9 features: city-wide browsing, shipping, ratings, photos of every item, chat, a points shop, school rankings, donations and family credit. Kept: each family's credit balance, a list of the sizes each family needs, and a text when a matching bag comes in. The clothes stay on the physical table, not in the app.

Why Go: three features turn a one-off swap table into something that runs every month without the founder keeping a notebook. The target is 30 families swapping at least twice by the end of term. Everything that was cut assumes strangers, which this version doesn't need.

Core user flow

Parent drops a bag at Friday pickup → founder logs it and adds credit → parents who need that size get a text → they collect from the table.

Explicitly not in v1

Shipping, photos, browsing, chat, other schools. Clothes never leave the school grounds.

Stage 3 of 5

Build

Can you build it with AI tools without losing control?

In progress · 2 of 5 tasks

Tasks in this stage

2 of 5 done

  • ✓Create your builder account and turn on two-step sign-in
  • ✓Set up a backup or export of your code
  • ▶Finish every milestone and pass its tests
  • + 2 more

Build path chosen: an AI app builder with text messages, no custom code. A spreadsheet form was the first idea, and it would have handled credit, but it couldn't send the "your size just came in" text, which is the part parents said they wanted. The builder plan and texts come to about A$35 a month.

What the guide flagged: the app holds children's ages and sizes and parents' phone numbers. The guide flagged keeping it to what the swap needs: no children's names, no photos of children, and parents can delete their family's record themselves. Those went in as the first milestone, not the last.

Budget

A$800

Planned A$150 · spent A$40

Running cost

A$35/mo

Builder plan + texts

Stages 4–5

Launch & Learn

Not started · 0 of 10 tasks

What the guide flagged: launch is one school: the founder runs the table and the app together for the rest of term before approaching a second school's parents' association. The readiness check will look hardest at who can see a family's sizes and phone number.

Timeline

  1. Idea entered Sep 8
  2. Swap table: 23 families, 41 bags Sep 19
  3. Validate gate: Go Sep 23
  4. Define gate: Go. Start building. Oct 2
  5. Build in progress Oct 2 →

What this run got right

The idea didn't change; its size did. One Friday swap table answered the question most marketplace ideas can't, whether both sides will turn up, and it cost nothing. Starting with one school traded a big market for one the founder can actually fill.

What we’d watch

Each new school needs a parent who will run the table, and that's volunteer work. If the second school can't find one, the app is a nice tool for a single school, not a business. Learn will show whether parents keep swapping once the novelty of the first term wears off.

Have an idea like this?

Run it through the same five stages. The first one is free, and you’ll know by the end whether to keep going.

Run your idea

Illustrative examples are written to show the shape of a Launchifier run. Examples marked ‘sample run’ are unedited product output.