###### tags: `Raid Guild x402`

# x402-product-sprint

- Post research to GitHub (~~x402-dashboard~~ [x402-product](https://github.com/raid-guild/x402-product) repository)
- Write RIP after we have completed initial research

## Action Items

1. Collect and analyze feedback from the upcoming hackathon to inform product improvements and identify cross-promotion opportunities.
- blockers: ~~x402 hackathon results~~
- priority: 1
- deadline: ~~TBD (dependant on x402 hackathon)~~ NA
- lead: ~~Patrick~~ Ryan
- github: https://github.com/raid-guild/x402-product/pull/1

2. Conduct market research on existing facilitator solutions, including pricing models, usage metrics, and feature sets.
- priority: 0
- deadline: January 14th
- lead: Rome
- draft: https://hackmd.io/@O2wj3TmiS0i6lidAWHJYIg/rJoaEtSrWe
- github: https://github.com/raid-guild/x402-product/pull/2

3. Evaluate cost structures and determine rate limiting strategies to prevent spam bot abuse and gas drainage.
- priority: 1
- deadline: January 14th
- lead: Rome
- draft: https://hackmd.io/ZGCRi7QSTSyKjiRqc-Nl2Q
- tldr: https://hackmd.io/@O2wj3TmiS0i6lidAWHJYIg/rJ3ZDUPBbx
- github: https://github.com/raid-guild/x402-product/pull/3

4. (previously 5) Research the feasibility of a white-label facilitator product for L2/L3 chains, including branding, maintenance, and pricing models.
- priority: 1
- deadline: January 14th
- lead: Patrick
- draft: https://hackmd.io/@sinachpat/r178NX4H-x
- github: https://github.com/raid-guild/x402-product/pull/4

5. (previously 6) Evaluate the use of Raid Guild's Vercel account for hosting the facilitator dashboard and related documentation.
- priority: 1
- deadline: January 14th
- lead: Ryan
- draft: https://hackmd.io/LkvePjwtTqibmS8lk2cHRA
- github: https://github.com/raid-guild/x402-product/pull/5

6. (previously 4) Investigate whether deploying separate facilitator instances per network (e.g., Arbitrum, Optimism) is necessary and sustainable.
- priority: 1
- deadline: ~~January 19th~~ NA
- lead: ~~Patrick~~ Ryan
- github: https://github.com/raid-guild/x402-product/pull/6

7. Assess the technical viability of integrating with Aztec’s Noir language and shielded transactions within the current EVM-compatible stack.
- priority: 2
- deadline: January 19th
- lead: Ryan
- draft: https://hackmd.io/4u8ESQgcTWyzXCd-uas1FQ
- github: https://github.com/raid-guild/x402-product/pull/7

8. Create a Raid Improvement Proposal (RIP) ~~outlining the facilitator product vision~~ to launch a customer discovery campaign (white-label and privacy-preserving), hosted on GitHub and linked to the Discord forum for community feedback.
- blockers: ~~all above action items are completed~~
- priority: 0
- lead: ~~TBD (whole team effort)~~ Patrick (and Rome)
- draft: https://hackmd.io/@sinachpat/H1xBc9c8Zx
- github: TODO

## Next Steps (2026-01-19)

- [ ] Rome to review materials and better understand her bandwidth for contributing
- [ ] Run idea by Duck and get his feedback on initial/smaller first proposal
- [ ] Patrick to draft customer discovery campaigns (white-label and privacy-preserving)
- [ ] Start drafting and continue with feedback from Rome/Duck
- [ ] Ryan to finish privacy-preserving facilitator artifact
- [ ] Ryan to consolidate team research artifacts into github repo

### Proposal(s) Strategy

- open questions / steps to submitting proposal
- How much more research is necessary (if any)?
- Are we requesting anything or more so putting this on the guild's radar?
- What is the goal of the project? Revenue generating? Break-even? Publicity?
- Comparable to wrapETH? Something that opens new client opportunities?
- What is the value proposition for the proposal? (white-label, privacy-preserving)
- What is the scope of the proposal? (involvement depends on scope)
- Consider a more iterative approach to proposals (thinking multiple smaller proposals rather than one big proposal)
- Maybe first proposal focused on customer discovery campaigns, asking for small amount to continue work?
- Maybe second proposal on improving existing tools or building a prototype for new tool/feature (based on campaign outcomes)?

### First Proposal (rough ideas)

- Patrick and Rome to take lead and do the bulk of the work (Ryan as support)
- 2 hours every day for next 2-3 weeks, $50/hour - 2 hours a day may be too much...?
- work includes drafting campaign briefs, writing messages for reaching out, then doing the outreach
- goals and metrics will be important to demonstrate work was successful (should be included in work)

## Next Steps (2026-01-21)

- [ ] Consider repositioning this as a "service" rather than a "product" (Rome)
- A service that brings more work in for the guild
- Deliverables can be repurposed as the knowledge we have on the topic
- What do we mean by service?
- White-label packaged service (consensus interpretation)
- Product research as a service (Ryan's misinterpretation but still worth considering)
- Pivoting to identifying who would want and need this service
- Maybe proposal could be customers of service rather than facilitator?
- Framing "customer development" over "customer discovery" (Patrick)
- [ ] Consider what our end goal is for the month (cohort season 11)
- Present multiple angles we could go (without necessarily going there)
- Presenting research on "privacy-preserving facilitator" (Ryan)

## Next Steps (2026-01-26)

- [ ] how should we engage with Raid Guild members?
- we are in the last week of cohort 11
- what do we want to share and when do we want to share it?
- we could use the demo day as a starting point (2/4)
- we may need to schedule a follow up call (if low attendance)
- we can present our work as a "case study" (might be out of scope)
- post announcement in x402-product-sprint announcing our intentions
- maybe ping all raid guild members in discord
- provide context on "we are looking for feedback"
- we need feedback to determine if we should continue
- asking questions like - will this bring in more clients?
- what are we presenting to raid guild members?
- the process we went through ("service")
- how we solve client needs (x402 as example)
- the service/product we want to build ("service"/"product")
- white-label service/product offering (x402)
- privacy-preserving service/product offering (x402)
- how to package up what we did into summary / delivarable?
- (last month) learning about topic and building prototype
- (early month) identifying areas for product improvements
- (mid month) conducting research / producing artifacts
- (end of month) reviewing, polishing, and process summary
- [ ] review project shared with Rome (reached out via LinkedIn)
- [Edge & Node](https://www.edgeandnode.com/) built similar dashboard payment flow
- they complimented our project and wanted to discuss further

---

- "product" to "service" framing
- "customer discovery" to "customer development"
- last month exploration of topic / build prototype
- this month exploration of process / product next steps