Builder Onboarding
Turn a serious builder idea into a review-ready campaign
A preview of future builder intake — how you would prepare a profile, plan milestones and evidence, and pass review before a campaign can accept support. None of it is live yet.
Who this is for
Builder onboarding is intended for people doing real work the ecosystem depends on. None of this intake is operational today.
Open-source maintainers
Maintainers seeking sustainable support for work the ecosystem already depends on.
Infrastructure builders
Teams building the rails — nodes, indexers, APIs, and developer infrastructure.
Cardano tooling teams
Builders shipping libraries, SDKs, and tooling that make other builders faster.
Education & community builders
People growing the ecosystem through teaching, documentation, and local community.
Public-good projects
Work that benefits everyone and is hard to fund through normal channels.
Serious product teams
Teams with a clear product, real users in mind, and a credible delivery plan.
What builders prepare
The materials a builder would bring before applying. Nothing is collected, uploaded, or stored today.
Builder profile
Who you are, what you've shipped, and how to verify it — identity that earns trust.
Campaign purpose
A clear problem and the specific work this campaign funds. No vague promises.
Requested amount
A funding target in USD with the reasoning behind the number.
Milestone plan
The deliverables funds release against, each with a definition of done.
Evidence plan
How you will prove each milestone — links, repositories, reports, or demos.
Maintenance / support plan
What happens after delivery: upkeep, support, and continuity.
Public communication plan
How you'll keep contributors informed in public as work progresses.
Onboarding preview
Preview only- Builder
- Demo builder — Kojo Asante
- Campaign
- Demo campaign — Afrobeats on Chain: Debut EP
Review-readiness checklist
What review would check before support opens on a campaign. This is illustrative — no campaign is reviewed or approved today.
Clear problem
The problem is specific and real, and the campaign explains why it matters.
Credible builder identity
The builder's identity and track record can be checked, not just claimed.
Realistic milestones
Milestones are achievable, sequenced, and each has a clear definition of done.
Evidence path
Each milestone has a concrete way to prove delivery before funds release.
Budget logic
The requested amount maps to the work, with reasoning a contributor can follow.
Contributor transparency
Progress, evidence, and outcomes are intended to be visible to contributors.
Settlement / return expectations
What happens at close — including returns if a goal is not met — is stated up front.
See how these checks would roll up into a single, transparent campaign readiness score before support opens.
Preview only — nothing here is live
- No real account is created and no authentication exists.
- No real application is submitted and no form sends anywhere.
- No file is uploaded and nothing is stored.
- No database write happens; Prisma is not used in any app route.
- No campaign is approved and no funding eligibility is granted.
This page describes intended intake only. Related: builders, campaign creation preview, campaign lifecycle, review workflow, milestone evidence, and status & roadmap. Nothing here is legal, tax, or financial advice.