How Confinity actually works.
Pick a side of the loop. Ask for something to get built, or offer your skills to build it — here's exactly what to do and what to write.
Asking for help, step by step
From idea to an inbox full of real replies.
Open "Post a project"
Head to the post page from the button in the nav. No account wall first — write your project, then attach your email so replies reach you.
Describe it like you'd explain it to a friend
Skip the jargon you think you're supposed to use. Say what's broken, what you want built, or what outcome you're after.
Give a real budget and timeline
A range is fine. "Open to offers" works too — but a number gets you faster, more serious replies than leaving it blank.
Reply to who fits, ignore who doesn't
Developers message you directly. Pick based on their portfolio and how well they understood the brief — not just the lowest price.
What to put in your post
The fields that make a post easy to say yes to.
Post checklist
for the "ask for help" formTitle
One line, specific. "Fix mobile checkout bug" beats "Need a developer."Category
Frontend, backend, mobile, design, data, DevOps — helps the right people find it.Budget
A flat fee, an hourly rate, or a range. "Open" is okay, "$0" isn't.Timeline
This week, this month, no rush — sets expectations before anyone replies.Description
What exists today, what you want instead, and any links, files, or examples.Contact email
Where replies land. Nothing gets posted publicly on your behalf.Rebuild a landing page in React + Tailwind
Have a Figma file, need it turned into a responsive, fast-loading page. Bonus if you know basic SEO.
what a well-written post looks like
Posting your gig, step by step
From "I'm free right now" to your first message.
Open "Post a project" and pick "I build things"
Same page, different form. It takes your skills and availability instead of a project brief.
List what you're actually good at
Name the languages, frameworks, and kinds of work you take on — not a generic "full-stack developer" line.
Link proof, not promises
Your GitHub, a live site, a case study — one good link does more than three paragraphs of self-description.
Say when you're free and go
Clients browsing the open work board see your gig and message you directly. No bidding, no fees taken.
What to put in your gig
The fields that make a client trust you enough to reach out.
Gig checklist
for the "post your gigs" formRole / title
What you do in one line — "iOS developer," not "tech enthusiast."Skills & tools
The specific languages and frameworks — this is what people filter by.Portfolio or GitHub link
One working link beats a long bio. Make sure it's public.Availability
Hours per week, or "free until [date]" — sets the pace early.Rate
Hourly, flat, or "depends on scope" — clients skip gigs that hide this entirely.Contact email
Where a client's message lands first.iOS developer, free for new projects this month
Built 6 shipped SwiftUI apps solo. Comfortable taking a rough idea to App Store-ready.
what a well-written gig looks like
What actually gets replies
Small, unglamorous habits that make a real difference on a young board.
Be specific, not impressive
"Fix the Safari cart bug" gets three good replies. "Seeking rockstar ninja developer" gets none.
Answer before you're asked
Budget, timeline, and scope up front save both sides a round of back-and-forth messages.
Reply, even to say no
It's a small board right now — a short "not a fit, thanks" goes a long way toward people posting again.
Ready to close the loop?
Post your project or your gig — it takes about a minute either way.