The products on this site — agentpay, x402 Gateway, x402market, BSVBounties — were built with the same pattern this engagement sells: pick a narrow problem, ship the production version, run it on real rails.
What a week produces
Pick one track:
- Payment rails: card top-ups with Stripe, x402/BSV settlement, ledgers, receipts, refunds.
- Agent interfaces: MCP servers, scoped keys, policy engines, approval flows, sub-agent delegation.
- A marketplace or gateway: listings, verification, pricing, analytics, and discovery.
- Escrow workflows: funded tasks, acceptance specs, payouts, retries, and audit trails.
Typical output: a deployed Worker (or two), a shared database schema, tests, docs, and one live end-to-end demo with real settlement. It's a working slice, not a scaffold.
How the week runs
- Monday: scope call and one-page spec — what ships Friday, what explicitly doesn't.
- Tuesday–Thursday: daily builds pushed to a repo you own; a short async note each day with a demo link.
- Friday: hardening, README, runbook, and a walkthrough. Handover recording included.
You get a decision-maker's calendar, not a discovery phase.
Why fixed price
Scope is negotiated before the clock starts, and the tracks above are things this factory has shipped publicly. If the scope is too big for a week, we tell you what to cut — or what a second week would add. The price doesn't move mid-engagement.
Proof, not promises
Every reference implementation is live on this origin:
- agentpay — prepaid wallets, policies, 22 MCP tools, attestations.
- x402 Gateway — hosted paid endpoints with auth injection and analytics.
- BSVBounties — escrow state machine, verification, reputation.
- The stack infographic — how the pieces compose.
Who books this
- Founders who need a system built by someone who has shipped the category.
- Teams adding agent payments or MCP support and lacking the focused week internally.
- Operators who want a working slice to validate demand before hiring.
What's not included
- Ongoing operations beyond the week (available separately).
- Legal, tax, or compliance advice for your jurisdiction.
- Design systems or marketing sites — this is engineering time.
FAQ
Can we do discovery instead of shipping?
Discovery is fine, but it costs the same week and produces documents, not systems. Most teams get more value from a working slice.
What stacks do you work in?
TypeScript/JavaScript end to end: Cloudflare Workers, Hono, React, D1/SQLite, Stripe, and @bsv/sdk. The output runs on your accounts.
How much of the week is actually build time?
Four of five days, with the fifth for hardening and handover. Scope is chosen to fit that, not stretched to fill it.
What if we need more than a week?
That's a second week, scoped at the end of the first. After a week you'll know whether the collaboration works.
Book
Email [email protected] with the subject "Factory week" and a paragraph on the system you want. You'll get a scope reply with the nearest available week.