WD

Collaborate

Build software instead of slides.

WeekndDevs works with small teams on real products for clubs, small businesses, and event organisers. If you'd rather build than sit in status meetings, this might be a fit.

Collaboration

How things run here.

Real products

No pitch-deck theatre, no innovation lab without users. What gets built here runs at real clubs, teams, and businesses — and has to work on Monday morning.

Clear tickets

Tasks come with a goal, scope, and acceptance criteria. No vague „do something with X“ tickets, no spec hidden inside a Slack thread.

Small teams

Direct communication instead of an account-manager chain. Whoever builds it talks to whoever uses it.

Long-term mindset

WeekndDevs isn't looking for a throwaway relationship. If you build with us, expect recurring tickets, plannable workload, and ongoing collaboration if both sides want it.

Fair compensation

Models are discussed concretely in the first call — fair and transparent, without burning internal numbers in public. No hidden clauses.

Ownership instead of handoff

If you contribute code, you also think about operations. What you build runs in production afterwards — not in a demo branch.

Boundaries

What you don't need to bring.

Compensation

Fair terms, no public number theatre.

Concrete models — hourly rate, project-tied participation, maintenance contracts — are clarified in the first call, depending on role, scope, and duration. What can be said publicly: WeekndDevs tries to compensate contributions fairly and to keep collaborators around long-term, instead of burning them out between projects.

Application

Short, concrete, honest.

Three sentences are enough: who you are, what you're good at, what you'd want to work on. Optionally a link to something you've built. No templates, no cover-letter theatre. If it fits, you'll get an honest reply — if not, also.