> when a project matches your stack and availability, bidflock may invite you. > you receive one scoped brief and send one fixed-price offer. > other builders never see your bid. > if your tools help you deliver faster, the upside is yours.
> freelance platforms make you write proposals before you know > whether the work fits. bidflock routes a scoped project to builders > whose stack and availability match it. you decide whether to quote. > > great builders should spend less time prospecting and more time shipping.
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ bidflock │ │ you │ │ buyer │
└──────┬───────┘ └──────┬───────┘ └──────┬───────┘
│ │ │
│ invite + spec │ │
│ ──────────────────────▶ │ │
│ (matches your stack) │ │
│ │ │
│ sealed bid │ │
│ ◀────────────────────── │ │
│ (price · eta · scope) │ │
│ │ │
│ ── normalized offers to buyer ─────────────────▶ │
│ │ │
│ │ pick │
│ │ ◀────────────────────── │
│ │ │
│ │ deliver │
│ │ ──────────────────────▶ │
│ │ │
│ │ signoff + pay │
│ │ ◀────────────────────── │
│ │ │--- job: j_3f12 title: crm export → csv, nightly stack: [ts, next, supabase] budget: < $3000 eta: ~5d bid_by: 2026-04-20T18:00Z --- nightly cron pulls from supabase, drops a csv in an s3 bucket. webhook on failure. out of scope: a ui, historical backfill > 90d.
--- bid: b_1f09 job: j_3f12 price: $2,400 eta: 6d --- assumes: - scheduled github action + s3 upload - one round of qa review included excludes: - non-s3 destinations - backfill > 90d (already out of scope) sealed. other builders won't see this.
bidflock bid j_3f12 --price 2400 --eta 6d · or drop a bid.md file in and let cc fill it.when a project matches your stack and availability, we may route it to you. no cold proposals or discovery calls. job volume is not guaranteed.
you price against the spec, not a visible price anchor. bidflock never shows you competing offers while bidding is open. no race to the bottom.
quote one fixed price with eta, assumptions and exclusions. no hourly sheets. if your tools help you deliver faster, the upside is yours.
you bid as bldr_**** on the public ledger. real identity stays with us. portfolio mention on delivery is allowed (title + stack + date) unless the buyer opts out.
* 2026-06-11 9836fbe pilot-hardening: payment flow, admin guard, webhook ordering, RLS lockdown * 2026-04-19 95ea367 rebrand: agentbid → bidflock (own .com, coined, trademarkable) * 2026-04-17 0a3c505 /jobs buyer dashboard + /jobs/[id] detail page * 2026-04-17 05b4e45 all API routes accept CLI Bearer auth via authedUser helper
hand-picked. claude code or codex heavy. v1 roster is small (<20) and invite-only — we read every application and say yes to maybe one in ten. it's not a grade, it's a stack fit.
no listing fees and no invite fees for builders in the pilot. the buyer authorizes the accepted price plus buyer fee; builder payout happens after buyer signoff, during the weekly pilot payout run.
`bidflock bids` lists your open invites (invite listing coming). `bidflock bid <job> --price --eta --assumption <text> --exclusion <text>` sends a sealed bid. or drop a bid.md and let cc fill it. the buyer sees every submitted offer in the same format.
nothing. you don't see the others, you don't see the winner's price, and there's no penalty. we balance routing across relevant, available builders, but project volume is not guaranteed.
buyer can request one rework round (included in the bid). if the second round still misses, we mediate. in genuine disputes the bid is refunded and the buyer is re-routed. we log it on your pseudonym.
one strike (missed deadline without comms). two = removed from the roster. we flag slow-response signals before the strike so you can catch it. ghosting also gets logged on your pseudonym.
buyer owns the delivered work. default nda in the contract. portfolio mention (title + stack + date, no pii) is allowed unless the buyer opts out at job creation.
yes. `npx @bidflock/init` drops the cli + agent context (claude code + codex) into your project. the fit-evaluation and bid-drafting prompts ship with it.