Built together, not hired
Nobody is hired. Ownership terms are set before anyone joins, signed by everyone, and cannot change.
Builders across Africa, one square.
Share an idea. The matcher suggests developers verified in the roles you need. You choose your team and build together.
No sign-up. Look around everything in read-only mode. A short tour is inside.
Watch the matcher find a team.
Pick an idea. See who the matcher suggests, then form the team yourself.
Daily naira payouts for market traders
An app that pays market traders in naira each evening and retries when the bank network drops.
Roles needed
- Backend and Systems Engineer
- Mobile Engineer
- Cybersecurity and Smart Contract Auditor
The matcher suggests. The owner decides.
Hamza Benali
Morocco
Match score: 89 out of 100, Strong match. Partial score.
- Roles40 of 40Verified in Backend and Systems Engineer and Cybersecurity and Smart Contract Auditor
- Technologies12 of 20In common with you: Go, PostgreSQL, Docker
- Sectors10 of 10You both build for Fintech and Commerce
- MeaningNot compared yet
Partial score: it counts roles, technologies and sectors. It does not yet compare what the idea and the profile say.
Thandiwe Mokoena
South Africa
Match score: 67 out of 100, Possible match. Partial score.
- Roles30 of 40Verified in Mobile Engineer
- Technologies12 of 20In common with you: Flutter, React Native, Java
- Sectors5 of 10You both build for Fintech
- MeaningNot compared yet
Partial score: it counts roles, technologies and sectors. It does not yet compare what the idea and the profile say.
Kidist Alemayehu
Ethiopia
Match score: 49 out of 100, Weak match. Partial score.
- Roles30 of 40Verified in Cybersecurity and Smart Contract Auditor
- Technologies4 of 20In common with you: Python
- Sectors0 of 10No sectors in common
- MeaningNot compared yet
Partial score: it counts roles, technologies and sectors. It does not yet compare what the idea and the profile say.
Three suggestions. You decide.
From an idea to a team, in four steps.
Here is what happens between sharing an idea and building it together.
- 01
Idea
Write what you want to build and which roles it is missing. Keep the full brief private.
DraftDaily naira payouts for market traders
An app that pays market traders in naira each evening and retries when the bank network drops.
Roles needed
- Backend and Systems Engineer
- Mobile Engineer
- Cybersecurity and Smart Contract Auditor
A draft idea with three roles ticked - 02
Matcher
The matcher looks at the roles your idea needs. It suggests developers verified in them, and says why.
The matcher suggests. The owner decides.
Hamza BenaliVerified
- Go
- PostgreSQL
- Docker
Verified backend engineer. Go, PostgreSQL and Docker in common with Ọmọlará.
Thandiwe MokoenaVerified
- Flutter
- React Native
Verified mobile engineer. Flutter and React Native in common with Ọmọlará.
Kidist AlemayehuVerified
- Python
Verified security auditor. Python in common with Ọmọlará.
Three suggestions, each with a reason - 03
Team
You invite developers, or accept those who ask to join. A team is up to five people, you included. Everyone reads and signs the same agreement.
Team
- Signed
Ọmọlará Adéwálé
- Signed
Hamza Benali
- Signed
Thandiwe Mokoena
- Signed
Kidist Alemayehu
A team of four, all signed - 04
Hub
Your team gets one hub: the agreement, the terms and the team, in one place. The owner confirms the team, Brainstorm opens, and the owner moves the hub through four phases, one at a time. Brainstorm has its notes, design its sketch and build its tab already; the review and test tool is still to come.
Daily naira payouts for market traders
Active
Phases
- 01Brainstorm
- 02Design and architecture
- 03Build
- 04Review and test
The hub, each phase Done, In progress or Not started
Your hub has four phases.
The owner confirms the team, Brainstorm opens, and the hub moves through four phases one at a time: brainstorm, design and architecture, build, then review and test. Brainstorm notes, the design sketch and the build tab are live. The review and test tool is still to come.
A space to agree what to build first, and who does what.
Traders want one payout each evening
Start with two banks, not ten
Out of scope: card payments
Today the hub page shows each phase as Done, In progress or Not started, and the owner moves the hub from one phase to the next. During brainstorm, the team's active members add short notes of up to 280 characters on the hub page. They stay to read afterwards. During design, they list the pieces of the system and the labelled links between them, and the hub page draws them as boxes and arrows. During build, each member takes a piece of the sketch, the owner sets the team's public GitHub repository, and its latest commits show on the hub page with a Refresh commits button. The review and test tool is not built yet.
The Green Tick says your role is real.
The matcher only suggests developers verified in the role an idea needs. Verification takes three steps.
Repositories check
An AI checker looks at the public GitHub repositories you choose: file names, languages, tests and recent commit messages. Only public repositories can be checked.
Interview
Five questions from an AI interviewer. You type your answers and stay on the page until the last one.
Peer review
A developer already verified in your role reads the evidence and decides. They do not see your profile, but repository addresses can show your GitHub name.
You get three attempts for each role.
You can share an idea before you have a Green Tick.
Thandiwe Mokoena
Mobile Engineer
- Repositories checkDone
- InterviewDone
- Peer reviewDone
Green Tick earned. Idea owners can now be shown your profile, and you can review others in your role.
How the village works
The owner decides, the matcher suggests
The matcher orders developers and says why. You choose who to invite.
Your brief stays private
Signed-in developers see your title and summary. The full brief opens to your team after they sign. The matcher never reads it.
Only verified roles are matched
Claiming a role is not enough. The matcher counts roles that passed verification.
Questions, answered plainly.
Who is Village Sqwhere for?
Developers across Africa who want to build with others. You sign in with your GitHub account.
Who can read my idea?
Until you publish, only you. Then signed-in developers see the title, summary and roles. The private brief stays with your team.
How big is a team?
A hub takes up to five members, you included. Everyone signs the same agreement before joining.
Do I need a Green Tick?
Not to share an idea. To be suggested to other owners, yes. You get three attempts per role.
Which languages does it use?
English and French, on every screen. The AI interview, the repositories check and the AI report are written in the language of the page when you start a verification, and it stays fixed for that attempt. Switch any time from the header.
Can I look around before signing up?
Yes. The demo is a read-only account with a guided tour of every screen. Nothing can be changed.
Bring your idea to the square.
Sign in with GitHub and share it, or look around the demo first.
No sign-up. Look around everything in read-only mode. A short tour is inside.