Repository navigation
Venture and Beyond — First Brand System Implementation #234
Description
Project Idea
Project Submitted By
Louchi, Brand Steward, with Deekan / Duckanbro providing development support.
Working ID: rip-draft-venture-and-beyond-2026-08-28
Summary
Venture and Beyond is the first implementation campaign in RaidGuild’s ongoing brand and website evolution. It combines visual design, narrative, UX/UI, imagery, frontend implementation, and reusable brand-system tooling.
This RIP proposes:
- Adopt Venture and Beyond as the first canonical implementation of RaidGuild’s evolving brand direction.
- Request $1,000 if the related DAO proposal passes, split $500 to Louchi and $500 to Deekan / Duckanbro.
The work is substantially underway but is not yet complete or adopted.
Why this work?
RaidGuild is preparing for a new cycle and wants to renew attention around the guild as a builder collective with distinct “tip of the spear” offerings. The proposal argues that a systematized brand foundation can represent those offerings consistently while remaining adaptable:
- The Brand Guide documents shared direction and constraints.
- Storybook exposes reusable design primitives and components.
- The Venture and Beyond webpage demonstrates the system in practice.
- The direction can later propagate through the Portal and Handbook.
The Brand Steward supports the rebrand and, under the stewardship model proposed here, has final responsibility for the brand direction. This stewardship judgment is the proposal’s basis for proceeding; it is not presented as proof that the current brand caused weak acquisition, nor as evidence of unanimous community agreement. The conversion baseline below is therefore context and a measurement starting point—not evidence that branding caused the current results. Related narrative and design-process discussions remain exploratory context, not settled community consensus.
Current website baseline
The current analytics report covers June 3–September 3, 2026:
Traffic
- 2,160 visitors
- 3,298 page views (1.53 per visitor)
- 84% bounce rate
- 424 visitors clicked a CTA (19.6% of visitors)
Hire funnel
| Stage | Visitors | Conversion |
|---|---|---|
| Website visitors | 2,160 | 100% |
| Hire form viewed | 572 | 26.5% of visitors |
| Form step completed | 6 | 1.05% of form viewers |
| Submit attempt | 3 | 0.52% of form viewers |
| Submit success | 3 | 0.52% of form viewers |
The measured visitor-to-successful-submission rate is 0.14%: approximately one submission per 720 visitors.
The largest measured drop-off occurs after viewing the Hire Form. However, tracking needs validation before this is treated as a reliable benchmark: seven visitors generated Submit Error events while only three generated Submit Attempt events, and the unusually low Step Completed count may indicate incomplete instrumentation.
A separate review of the prior year found 39 apparent intake notifications, with 13 plausible inquiries. These are not yet confirmed as organic website conversions, qualified leads, paid work, or attributable revenue; some were referrals, internal entries, duplicates, or opportunities originating elsewhere.
Sources: three-month conversion report · historical intake review
Measurement deliverables
In addition to the implementation deliverables, this RIP will:
- Validate or correct analytics events for Hire Form view, form start/step completion, submit attempt, submit error, and submit success.
- Preserve the June 3–September 3 baseline and clearly document its limitations.
- Produce comparison reports six and twelve months after production adoption.
- Report visitors, CTA engagement, funnel-stage conversion rates, submissions, qualified leads, paid engagements, and attributable RaidGuild revenue where attribution can be supported.
- Separate organic website acquisition from referrals, internal tests, duplicates, and opportunities originating through existing relationships.
The Keeper of Knowledge Steward is responsible for analytics validation and the six- and twelve-month reports. The implementation is scheduled to go live on October 1, 2026. The initial performance evaluation window is October 1–December 31, 2026.
Minimum implementation deliverables
- A usable RaidGuild Storybook
- A documented brand system and Brand Guide
- The Venture and Beyond webpage
Portal and Handbook propagation are adoption targets, not minimum completion requirements.
Ownership and maintenance
Louchi will maintain the brand direction and assets, with development maintenance support from Deekan / Duckanbro.
Tae contributed lore, concept ideation, and imagery. That work is credited as part of the project lineage but is outside this RIP’s compensation request. Other contributions may use CookieJar separately.
Adoption and funding
Passing a later DAO proposal would authorize the $1,000 payment and adoption of this work as the first canonical implementation. It would not automatically approve future changes to shared brand elements.
The $1,000 covers the initial website, Storybook, and Brand Guide implementation; it is not presented as full compensation for redesigning every RaidGuild surface. Forum feedback argues that broader rollout would be materially underpriced at this amount. Compensation for later propagation remains outside the confirmed terms of this RIP. A $5,000 performance bonus may be requested through a separate future DAO proposal if the measured visitor-to-successful-submission conversion rate exceeds the 0.14% baseline during October 1–December 31, 2026. The Keeper of Knowledge Steward will validate the result. The future proposal will determine the bonus split and payment execution; it is not authorized by this RIP.
Open questions
- Is the Brand Steward’s mandate and stated support sufficient authority for canonical adoption, or is an additional community approval standard required?
- Which measurable outcomes, besides conversion, should define success?
- Are the minimum deliverables clear and verifiable?
- Which elements should be stable foundations, and which should remain experimental?
- What accessibility review should precede production adoption?
- Are font, imagery, and other asset licenses documented appropriately?
- Who owns hosting and deployment responsibilities?
- How should the system integrate with the Portal and Handbook?
- What review process should govern future shared-brand changes?
Raid Party Skills Needed
- Brand and visual design
- UX/UI and art direction
- Frontend implementation
- Documentation and design-system maintenance
- Analytics instrumentation and reporting
- Accessibility and licensing review
Cost (in USD)
$1,000 total
- $500 to Louchi —
0x35b248d06Bf280E17d8Cbff63C56A58e52a936f1 - $500 to Deekan / Duckanbro —
0xCED608Aa29bB92185D9b6340Adcbfa263DAe075b
Payment is contingent on passage of the related DAO proposal. Use USDC if available; otherwise use ETH or WETH valued at the USD spot price when the proposal is created.
Future performance bonus: A separate DAO proposal may request $5,000 if visitor-to-successful-submission conversion exceeds 0.14% during October 1–December 31, 2026, as validated by the Keeper of Knowledge Steward. This RIP does not authorize that bonus.
Review environments
These are review environments, not final production destinations.
Activity
ECWireless commentedon Sep 2, 2026
I'd be interested in some baseline stats to show that this is improving on something in particular. Fundamentally, I think the why of this RIP has not been explained. "This work establishes an evolving, reusable foundation rather than a one-off redesign," is understandable. But it's not really shown that the current brand does not already do exactly this. That brand has evolved over the last year, and has be used in various ways in various RaidGuild applications.
I've seen the audit and think it's thorough and well put together, but it doesn't seem to justify overhauling of the entire landing page (including it's entire narrative), and every RaidGuild surface that exists (including social media).
On only the website side of things: what is missing from the current brand and website that this is improving with this RIP, and how can we prove that? Main worry is that this will be the culmination of a lot of work with no verification that it did the thing it was supposed to do.
Considering all this, the cost seems enormously under-priced. If the hours were accurately counted for this and all that is involved to change every other RaidGuild surface, this RIP would likely cost around $10k. Recommend boosting the cost way higher than currently proposed, or else we run the risk of not correctly pricing the work that we do internally.
luisblancoach commentedon Sep 4, 2026
@ECWireless , I strongly agree with the under-pricing point. What I'm requesting here is intentionally a symbolic payment for Dekan and myself to give this initiative momentum, rather than pricing the full scope of a RaidGuild-wide rebrand.
I also think your point about the why and verification is fair. The audit identifies inconsistencies and opportunities, but it doesn't yet establish a baseline that lets us say: this is what is currently not working, and this is how we'll know the redesign improved it. I think we should add that.
For this RIP, I'd narrow the scope and focus primarily on the website: information hierarchy, narrative clarity, consistency of the design system, maintainability, and the connection between the brand system and implementation. We can establish a few baseline indicators around those areas before considering the work successful.
The narrative update is part of the exploration, but I'm not proposing that we immediately replace every RaidGuild surface. The existing brand has evolved and has been used successfully in many contexts. My intention is to build on that work, identify what should remain, what should evolve, and gradually establish the next iteration of the guidelines.
Design is an exploratory process, so some of the graphic and communication resources will emerge through the work itself. But I agree that exploration still needs a clear hypothesis and a way to evaluate the outcome.
dekanbro commentedon Sep 4, 2026
https://admin.daohaus.club/molochv3/0x64/0xf02fd4286917270cb94fbc13a0f4e1ed76f7e986/proposal/224