We had plenty of ideas on the platform. What we didn't have was anyone technical to build them. Here's what we did about it

Building DVOIDER — a place for early-stage founders to post raw ideas and find people to build them with. Three weeks in, we ran into a version of the chicken-and-egg problem that I don't think gets talked about enough: it's not always "no supply, no demand." Sometimes you have supply, it's just the wrong shape of it.
We had ideas. Plenty of them. Founders were posting, the D Lab feed had real content, people were engaging. But when we actually looked at who was on the platform, it was overwhelmingly non-technical folks — marketers, students, people with a vision and no way to execute it themselves. Every idea had a "Looking for: Developer" tag and basically nobody there to fill it.
Classic two-sided marketplace mistake, in hindsight — we'd been thinking about growth as "get more users" instead of "get the specific users this side of the market is missing." More non-technical signups wasn't going to fix anything, and it would've just made the imbalance worse. This became obvious fast — we're talking days, not months, into having real usage.
So instead of waiting for organic growth to eventually even things out (it wasn't going to — why would a developer show up to a platform that's 90% non-technical people posting ideas?), we flipped the acquisition strategy specifically for that side. We started directly and manually reaching out to developers and designers — in dev communities, student CS groups, places where people are actively looking for something real to build, not places where they're looking for a co-founder pitch. The framing was different too: less "come find a startup," more "come find an interesting problem someone's already thought through, that you could actually ship."
A few things I didn't expect, all inside that same three-week window:
• The pitch to technical people needed to be almost the opposite of the pitch to founders. Founders want validation and momentum. Developers wanted to know the idea was concrete enough that they wouldn't be wasting a weekend.
• We had to get comfortable being unbalanced on purpose for a while — deliberately not pushing non-technical signups even though that side was working, because it wasn't the bottleneck.
• "Direct invite" beat "build a growth loop and wait." It felt almost too manual/unscalable at first, but manual was the only thing that worked at this stage — the imbalance was too specific for a generic acquisition channel to fix, and we didn't have months to let a loop compound.
Still early and still mostly manual on the technical side, but the ratio is noticeably healthier than it was three weeks ago. Mostly sharing this because I think "chicken and egg" gets treated like a single problem with one playbook, when in our case it turned out to be "wrong-shaped supply" that showed up almost immediately — which needed a completely different fix than "not enough supply."
Curious if others have run into a version of this, especially early — where the problem wasn't a lack of users, but the wrong mix of them, and how fast you noticed it.