For Solo founders · Co-Founder Matchmaking Platform

Hackmate

Find the co-founder you'd actually build with.

DecisionOptimise for speed to first match: keep onboarding and profile setup light so a new user reaches profiles quickly.

Instead of long profile forms and an opaque ranking score.Cost: lighter profiles meant weaker match signals at first.

No screenshot: the app was not re-run for this write-up. The public repo was checked on 30 Sep 2026.

Status
Archived
Ownership
Two-person build · I owned product
Evidence
Self-reported: no file evidence
Checked
Last verified

A skill-first co-founder discovery MVP: profiles built around what you can do, a quick yes/no explore flow, and mutual matches. Shared with peers; usage was never instrumented.

Role
Co-builder · Product
Timeline
2025
Team
Two-person build
My part
Product, on a two-person build with a partner.
Stack and tools5

Next.js · TypeScript · PostgreSQL · Prisma · Redis

TL;DR

Early-stage founders struggle to find aligned collaborators beyond warm intros and noisy communities. Hackmate is a two-person build where my part was product: a skill-first matchmaking MVP with intent-rich profiles, a lightweight explore flow and mutual matches. It was shared with peers; usage was never instrumented, so there is no user count to report.

Chapters

Problem

Finding a co-founder usually happens through warm intros, college circles, or crowded startup communities. That works if you already know the right people. It breaks down for early builders who have intent but no discovery layer for skills, goals, and stage fit.

The gap: founder discovery needed to feel more like product matching than social networking, with less noise, faster qualification, and clearer signals about who should actually talk.

Users

Student builders and first-time founders looking for a collaborator with complementary skills. The working assumptions (not a formal study) were:

  • Capability, seriousness, domain interest and build stage matter more than a polished bio.
  • People would sign up only if discovery felt fast and the first useful match arrived quickly.

Decision

Trade-offs

We made three product calls for the first version:

  • Speed over completeness. A light profile now, richer signals later.
  • Legible matching over a black-box score. Users needed to understand why a profile surfaced, so discovery leans on a small number of visible inputs (skills, domain expertise and location filters) instead of an opaque ranking.
  • Treat it as a learning build. The first version was an MVP to learn from, not a finished network.

What shipped

  • Skill-first profiles. Profiles centre on skills, domain expertise and what the person wants to build, pushing users toward intent-rich profiles instead of vague networking.
  • Explore flow. A quick yes/no pass through profiles, with filters, instead of long directory browsing.
  • Mutual matches. A like on both sides creates a match.
  • Four core surfaces: onboarding, explore, profile and matches.

Validation

There is no usage evidence to report. Hackmate was shared with peers, but usage was never instrumented, so there is no user count, activation rate or match rate, and no user numbers are claimed here.

Limits and next

  • No instrumentation. The first thing to add would be post-match quality signals: conversation outcomes, follow-up prompts, and whether a match led to collaboration.
  • Not re-run. The app was not re-run for this write-up; only the public repo's file tree was checked. This page describes the product design, not a current deployment, and usage was never instrumented, so no user numbers are claimed.
  • What I'd change: marketplace quality compounds faster than raw signups, so I would measure match quality before growth.

Credits

A two-person build with a partner; my part was product. Source: hackmate-rework (public repo; returned HTTP 200 on 30 Sep 2026).

  • Product

    DeskTasks

    Your task list, pinned behind every window on the desktop.

    Decision: Pin the widget behind every window, not on top of them, and refuse attention: accountless, local-first, no dock icon.

    Solo · product, design and engineering

    LiveHosted v1.3.1 line is frozen; v2 alpha runs locallyEvidence: Tested

    0Failures · release gate run, 15 Sep 2026

  • Product

    ExperimentHub

    Self-hosted A/B testing with deterministic variant assignment.

    Decision: Let the statistics engine say no: return a sequential verdict such as keep running, not a bare p-value.

    Solo · product and architecture

    Local build · not deployedEvidence: Built

    ContinueSequential verdict at p = 0.0337 (synthetic demo)