Writing a project post, what should I include so the right person/people apply?

when i write, i state the tech clearly include numbers (react 3 years), state the budget, but even then i get 100 applications. half of them are a bad fit. now i put applicants straight into a test that helps a bit

A good project post includes these elements: 1- Title (short and clear), 2- Project summary (what it does in 3 sentences), 3- Tech stack (Must-have and nice-to-have) 4- Budget and timeline 5- Skills (years of experience) 6- Application instructions (CV, portfolio requests)

Question for me: did you prepare a screening test for applicants? Because after the post, you can see actual competence by testing. So make the post as clear as possible then filter with a screening test.

when writing a project post: be clear (but not too long), don't hide the budget (candidates research), prepare a test (some love the post but fail the test) and i mean this cmbo solves it.

Bro where are you posting? Because forums and Fiverr attract different people. If you post on tech forums, you get more qualified candidates. Pay attention to this too!

my perspective changed after experiencing that but just because everyone does it doesn't mean it's right.

corect me if I'm wrong.

How did you solve this? Most time waste accumulates in tasks waiting for approval.

Hasty decisions become decisions you have to fix six months later. This is my opinion, I'm not claiming it's absolute truth.

Three different views emerged, they all complement each other. The harder it is to reverse a decision, the slower you should make it.

When you try to change everything at once, nothing settles. If I were you, I'd go this route.

Let me speak from the other side; I'm on the supplier side. When making a decision first look at what data you have on hand.

Hasty decisions become decisions you have to fix six months later.

Same here. Don't hesitate to ask; those who don't ask always pay more.

If it's your first time, start small; scaling comes later. That's all, sorry if I went on too long.

timeely topic.

This thread is archived.

I don't think this advice fits everyone. tbh start with a small trial; don't commit to everything at once.

Of course, it varies if your situation is different.

Exactly like that. When listing, put proof that the product actually works at the very top.

The real issue isn't the number, but what it's based on. Good luck with that.

Let me summarize what's been said so far. Valuation methods for exits must be defined by formula; "market value" isn't enough.

Just leaving this note, it might be useful.

the opposite happened to me, that's why I'm writing. partnership isn't a decision to make without working together first.

partnership isn't a decision to make without worknig together first. i mean just leaving this note, it might be useful.

The answer above hits the nail on the head. When we decide without measuring, we always end up in the same place.

If you post the result here, it will help others too.

Thanks a lot, I'll try it today. When you try to change everything at once nothing settles.

When we decide without measuring, we always end up in the same place.