Sequenced moves, 90 days
3 tracks Zucity could run in parallel for the next 90 days
Not a project plan. A sequencing suggestion. Pick the 1 or 2 tracks that feel real to you and ignore the rest. The point is the sequencing, not the volume.
Each track stands alone. Run one and the other two stay parked. Run all three only if you have a builder or operator helping. Everything below assumes Kiba is the bottleneck, because that's usually where these things actually stall.
Track 1 · Wedge launch
Track 01
Revenue track
Pick one wedge, ship the funnel, soft-launch to the warmest 50
Why this is here: most leverage per hour of Kiba's time. Of the 15 wedges on the wedge-offers page, Founders Circle is the one with the highest revenue-per-hour and the lowest delivery overhead. It's the recommended pick, but any of the 15 work if one of them feels more alive.
Day 0 to 30 · Build
Pick one wedge. Founders Circle recommended. Build the landing page (single page, one CTA, no nav), the member-application form (5 questions max, focused on fit not credentials), and a 5-email nurture sequence for applicants who fit but aren't ready yet. Keep the entire build inside one week. Resist the urge to scope a v2.
Day 30 to 60 · Soft launch
Send the landing page to existing top-tier members and the 10 to 20 Lu.ma hosts you already have a relationship with. This is NOT a public X post or a newsletter blast. It's a quiet, curated, "I built this thing, you specifically came to mind" set of 50 DMs. The first 5 to 10 yes votes set the tone for the tier.
Day 60 to 90 · Refine or shelve
Review the first 10 to 15 applicants. If the quality is there and 5 to 10 said yes at price, you have a tier worth scaling. If applicants ghosted or the conversations felt forced, shelve it cleanly and try a different wedge in Q4. Either way is a useful answer.
Success looks like: 5 to 10 paying Founders Circle members by day 90, or a clear "this wedge isn't it" signal that frees you to try the next one. Both outcomes are wins. The failure mode is dragging it out for 6 months without resolving either way.
Track 2 · CRO compound
Track 02
Leak-fix track
Fix the 4 funnels in priority order, one per month
Why this is here: lowest-friction wins, no new product to build, no new audience to find. You already have traffic landing on zucity.org and dropping out at known points. The CRO teardown is the spec. This track just sequences which funnel to fix first.
Day 0 to 30 · Membership signup funnel
Highest-leverage of the 4 funnels because every wedge eventually routes through tier-select. Clarify the VIP vs Daily vs Global differentiator above the fold, add social proof to the tier-select page, fix the mobile tap targets. This is the one funnel where a half-day of work compounds across every other initiative.
Day 30 to 60 · Lu.ma handoff + event-card click-through
Right now the handoff from zucity.org to Lu.ma loses your branding and the user loses context. Add a branded interstitial, capture email on the Zucity side before the Lu.ma click so you own the data, and make event cards filterable by theme. None of these are big lifts.
Day 60 to 90 · Accommodation booking flow + mobile sweep
Clarify which properties are Zucity-direct vs partner (ADDress, MIDORI.so), add response-time guarantees on the inquiry forms, and run a single mobile sweep across the whole site to catch any leftover friction. The mobile sweep is half a day and tends to surface 5 to 10 fixes nobody saw on desktop.
Success looks like: qualitative lift on tier-select page conversion that's visible in Stripe or membership analytics. You'll know it worked when applicants stop dropping at the tier-select step. No baseline numbers here because you have to set the baseline in week 1 to know.
Track 3 · Outreach systematization
Track 03
Pipeline track
Build the inbound flywheel that compounds for years
Why this is here: of the three, this is the one that pays off latest but compounds longest. The outreach playbook has the tactics; this track turns them into a 90-day cadence Kiba can actually sustain at 4 hours a week.
Day 0 to 30 · Lu.ma host scrape
Build a list of 100 hosts of theme-adjacent events (ETH meetups, DeSci, builder communities, AI agent gatherings). Send 30 cold DMs a week with the one-line comp-pass pitch from the outreach page. Keep a spreadsheet of who replied, who ghosted, who showed up. The list itself is the asset, not the first conversion.
Day 30 to 60 · Themed-week recruiter sequence
For the next 2 themed weeks (60 days out), pick 30 ICPs per week and run the 3-touch sequence with a theme-specific hook. Not a generic Zucity pitch. The hook has to name the theme, the dates, the city, and one specific reason this person specifically would care.
Day 60 to 90 · Podcast pipeline
Get 5 podcast guest appearances booked for Kiba in the network-state, nomad, and AI-builder space. Each appearance puts Zucity in front of 30 to 100 ICP-aligned listeners and earns inbound for 6 to 12 months after. Use ListenNotes and Spotify tags to find the right shows. Pitch script is on the outreach page.
Success looks like: 10 high-quality applicants per themed week routing in via the host scrape or recruiter sequence, plus 3 podcast appearances live by day 90. The compounding starts in Q4 when the podcast episodes start surfacing on search and the Lu.ma hosts start referring their members.
Cross-track compound
The tracks aren't independent revenue lines, they're a flywheel. Track 1 (Founders Circle members) feeds Track 3 because curated members refer other founders into the pipeline. Track 2 (CRO fixes) feeds Track 1 because better tier-select conversion means more of the people Track 1 sends to the page actually convert. Track 3 (Lu.ma host outreach) feeds Track 1 because hosts become themed-week attendees become Founders Circle applicants.
Run any one alone and you get linear returns. Run two together and they reinforce. Run all three and the compounding shows up around month 4 to 6, after the 90-day window closes. That's why this is sequenced as a 90-day plan rather than a 30-day plan. The payoff lives in the next quarter, not this one.
12 quick wins (parallel to the tracks)
These don't fit cleanly into the 3 tracks but each takes under 2 hours and pays back quickly. Pull from this list whenever a track has slack.
Add testimonial cards to the tier-select page (named members, real quotes, no stock).
Add a "next themed week starts in X days" urgency widget to the homepage hero.
Move the Apparel and Stickers section above the fold on the membership page.
Capture member application emails into ConvertKit or Beehiiv for ongoing nurture.
Set up a themed-week recap newsletter template so post-week content ships in one hour, not one day.
Lu.ma calendar integration so events show on the Zucity homepage hero automatically.
Member directory page (opt-in) to surface intra-community connections without DMs.
Visa and relocation FAQ page (the 50x-per-month question, currently scattered across DMs).
Member referral incentive (one free week if you bring in a member who upgrades).
Add an "operated by Kiba" trust mark with a photo and one line of context (founder presence on a landing page raises perceived trust noticeably).
Themed-week sponsor 1-pager as a sales asset for Track 3 outreach to protocol foundations.
Member onboarding email on day 1 of any tier (the Lu.ma handoff is too cold as the first touch).
KPI scoreboard (qualitative, weekly)
4 numbers in a Notion table or spreadsheet, reviewed every Friday for 15 minutes. Set the baseline in week 1, track the trend thereafter. No targets in this doc because targets that aren't grounded in your actual baseline are just decoration.
- Track 1 signal: New Founders Circle applicants per week. Quality matters more than count; note which ones felt like a yes.
- Track 2 signal: Membership signup conversion rate from tier-select page to checkout. Pull from Stripe or whatever payment platform is in use.
- Track 3 signal: Cold DM reply rate plus the count of applicants who came in via a Lu.ma host introduction.
- Cross-cutting signal: Themed-week applicant quality on a felt-sense scale. A 1-to-5 gut score per applicant, scanned weekly. Numbers can lie; gut-scores from someone who's curated 50+ themed weeks usually don't.
Risk register
Track 1 risk: Founders Circle requires curation discipline. If you can't say no to applicants who are "fine but not a yes," the tier dies in 6 months. Build a one-paragraph "who this is for / who this isn't for" before applications open and re-read it before every accept decision.
Track 2 risk: CRO fixes need access to Lu.ma and Stripe data to measure. If you don't have analytics wired before week 1, you're guessing instead of optimizing. Half a day on instrumentation upfront saves a month of debate later.
Track 3 risk: Outreach takes Kiba's bandwidth. Realistically 4 hours a week for 90 days, which is a real commitment. If that bandwidth doesn't exist, this track stalls in week 3. Either commit the time or park the track honestly.
Meta-risk across all 3: running all three simultaneously is the failure mode most founders fall into. Two is fine. Three usually means the founder gets pulled across context-switches and none of them ship cleanly. Default to one track if Q3 is tight.
How to pick
Pick 1 track if Q3 is tight. Pick 2 if you have a builder or operator helping. All 3 only if you're ready to slow down everything else for 90 days. Honestly, the highest-leverage single move is Track 1 wedge launch. That's where money compounds fastest, and the other two get cleaner answers once there's revenue pulling them forward.
None of this is a deliverable. Screenshot what's useful, ignore the rest, and if a track sparks something you want to scope into a 1-pager, ping me and I'll draft it in 30 minutes. No clock, no expectations.
Donal · Online Optimisers · 2026-05-28