A shop owner across town has an app idea and needs somebody who can build it.

What a business sounds like the month before it commissions an app

Nobody sets out to hire an app developer. They set out to stop doing one job twice: taking bookings on the phone that is also the register, texting twelve people a schedule every Sunday night, running a loyalty card half the customers lose. So what goes up isn’t a specification. It’s four lines in a group they already read, saying they want a simple app for the business, nothing fancy, does anyone know somebody good and roughly what does that come to. There’s no feature list in it, because nothing has been written down yet. What is in it is a business that works, a job being done by hand, and somebody who has stopped expecting to do it themselves.

On the latest sweep, twenty of the twenty-five posts that came back lit were people asking the group outright for a builder: who makes apps around here, what a first version runs, and whether anybody takes a job this size or only works with companies. Five hadn’t committed to paying anybody and were still weighing a no-code tool, a relative who writes software for a living, and a template bought off a marketplace. Those are not the same reply. Whoever is asking for a builder wants a range and a timeline and takes the first answer carrying both. Whoever is pricing out the do-it-yourself route needs to hear where that route runs out, which is a real place rather than a sales objection.

The rest of a local feed is a local feed: somebody recommending a plumber, a photo of the line outside a new bakery, a long thread about the construction on the main road, and the weekly post asking who else lost power. At two-to-one, one post from somebody who has finally set money aside for a build sits underneath all of that, and an evening of scrolling down to it earns nobody anything.

Where to find app development clients in Facebook groups

Sort the groups by who is inside them rather than by what they are called, and three kinds are worth a morning. Groups for business owners in one town or one county come first, because whoever posted wants somebody they could meet for coffee and will take a local name over a cheaper stranger every time. Groups built around a single trade come next, and the asks inside them are the most specific anywhere on the platform, since everybody there already knows the job the app is meant to replace. Founder groups are third, noisier and further from money, though the people in them describe what they want precisely enough that a scope can be quoted straight off the post. Groups full of developers hold no clients at all, only framework arguments and rate threads. Three neighboring jobs turn up in the same feeds. An idea that is really three tools which never learned to talk to each other belongs with whoever wires them together in an afternoon. An app whose entire job is answering the same eleven questions is something that only ever needed to hold a conversation. And a build that turns out to hang off a store somebody already runs is an add-on rather than an app.

The reply that wins the build prices the first version, not the idea

Everybody else under that post either asks what the app does or says it depends. Neither helps. Take the two sentences they wrote and turn them into a first version out loud: the one thing it does, the things it deliberately doesn’t do yet, and how many weeks that is. Give a range and name what moves the range, because the figures they’ve heard so far came from an agency pricing a year and a relative offering to do it for nothing. Then say the uncomfortable part, which is that a business taking twelve bookings a week doesn’t need an app and needs a form and a calendar. Talking somebody out of a build in front of the whole group looks like handing back the work. It is also why the next three people there who genuinely need one arrive with your name already in hand.

What finding clients on Facebook actually costs you

Three replies before standup, ten minutes, less of a day than one scoping call that ends in circling back. It still never happens, because everything else in this job leaves an artifact and this leaves none. A sprint ends in something running. A release ends in a build number somebody can point at. A month of answering strangers in a group ends in an empty commit history, so it loses to the ticket that came in overnight. Meadowrank gives it something countable. A post with a real business behind it waits under a short match-3 board. The cover clears, the card opens on the post itself, the job the owner is doing by hand, and a reply already written the way you scope a first version for somebody who has never commissioned software. When a release week takes every hour, the feed lists the same signals for a little less XP, and a full sprint costs you nothing on the streak. Points only ever come from replies you actually sent, so a month counts owners who heard back rather than threads that stayed open in a tab until the group moved on.

Nothing is charged for the game itself. Free covers every part of it, board and feed and streak together, with five cards dealt each morning from the pool Hazel keeps stocked, and that is the whole thing rather than a look around one. $35 a month, or $350 taken for the year, digs you a Quarry nobody else works, so the scan follows the towns you can reach for a kickoff, the trades whose problems you already understand, and the groups where those owners ask.