🚀 Launch Promotion Strategy & Meeting Availability Poll #185
Replies: 15 comments 3 replies
📅 Meeting Availability PollTeam — let's coordinate our scoping meeting! Please reply to this comment with the times you're available from the options below: Proposed Dates & Times (April 24–27, 4pm–8pm IST):
Format: Just reply with the slots you can make! E.g.:
We'll count votes and pick the time with the most availability. Looking forward to planning the next phase together! 🎯 cc: @Dipanita45 @avanithumballi @Annunitha @sadhami0519 @aryansondharva @ritvik-37 @Asutosh-1234 @tirth1356 |
|
I'm free: Apr 25 6-8pm, Apr 26 6-8pm |
|
I'm free: Apr 25 4-6pm, Apr 26 4-6pm
…On Thu, 23 Apr 2026, 9:53 am Abi, ***@***.***> wrote:
📅 Meeting Availability Poll
Team — let's coordinate our scoping meeting! Please *reply to this
comment with the times you're available* from the options below:
*Proposed Dates & Times* (April 24–27, 4pm–8pm IST):
- Apr 24: 4:00pm – 6:00pm IST
- Apr 24: 6:00pm – 8:00pm IST
- Apr 25: 4:00pm – 6:00pm IST
- Apr 25: 6:00pm – 8:00pm IST
- Apr 26: 4:00pm – 6:00pm IST
- Apr 26: 6:00pm – 8:00pm IST
- Apr 27: 4:00pm – 6:00pm IST
- Apr 27: 6:00pm – 8:00pm IST
*Format*: Just reply with the slots you can make! E.g.:
I'm free: Apr 25 4-6pm, Apr 26 4-6pm
We'll count votes and pick the time with the most availability. Looking
forward to planning the next phase together! 🎯
cc: @Dipanita45 <https://github.com/Dipanita45> @avanithumballi
<https://github.com/avanithumballi> @Annunitha
<https://github.com/Annunitha> @sadhami0519
<https://github.com/sadhami0519> @aryansondharva
<https://github.com/aryansondharva> @ritvik-37
<https://github.com/ritvik-37> @Asutosh-1234
<https://github.com/Asutosh-1234> @tirth1356
<https://github.com/tirth1356>
—
Reply to this email directly, view it on GitHub
<#185?email_source=notifications&email_token=BS3CS4CV6HRN5WDBAAWCRDD4XGLCPA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWG44TAMZYUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-16679038>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BS3CS4BPBTY7CARAUECJ5HT4XGLCPAVCNFSM6AAAAACYDFV5B6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNRXHEYDGOA>
.
You are receiving this because you were mentioned.Message ID:
<LarytheLord/Adventurers-Guild/repo-discussions/185/comments/16679038@
github.com>
|
|
I'm free Apr 25, 26, 27 anytime! |
|
25 any time |
|
25 is fine with me |
|
I am free on 26 any time
…On Thu, 23 Apr 2026, 7:18 pm Avani Thumballi, ***@***.***> wrote:
25 is fine with me
—
Reply to this email directly, view it on GitHub
<#185?email_source=notifications&email_token=A7SRZ6ETWOT3GO7SIWDHCHD4XINLHA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWHA2TGMRTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-16685323>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7SRZ6APYEYCHTSQ4SCQM4L4XINLHAVCNFSM6AAAAACYDFV5B6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNRYGUZTEMY>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/A7SRZ6GMLJAXYN33M7LIBRT4XINLHA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWHA2TGMRTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ>
and Android
<https://github.com/notifications/mobile/android/A7SRZ6FG3MNZK6FDCLA5L3D4XINLHA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWHA2TGMRTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>.
Download it today!
You are receiving this because you were mentioned.Message ID:
<LarytheLord/Adventurers-Guild/repo-discussions/185/comments/16685323@
github.com>
|
|
April 25 and 26, anytime is good with me! |
Meeting Availability SummaryBased on responses so far (still missing @ritvik-37 and @tirth1356), here is the tally:
Apr 25 is the winner — 5 confirmed. Still waiting on @ritvik-37 and @tirth1356 to respond. If no further conflicts, the meeting will be on April 25, 5:00pm – 7:00pm IST. A calendar invite / link will be shared closer to the date. Agenda will cover: Guild Card UI, Squad/Party system next steps, Submission Service Layer, and early launch checklist. |
|
Im okay with 25th April 6-8 pm |
Meeting ConfirmedApril 25 at 6:00pm – 6:30pm IST Final tally with all responses in:
Still missing @tirth1356 — you're welcome to join if free! The call will be 30 minutes and we will cover:
A meeting link will be shared before the call. See you all on the 25th! |
Meeting LinkSaturday, 25 April · 6:00 – 6:30pm IST Join via Google Meet: https://meet.google.com/uye-vbqe-xyt Or dial in (US): +1 518-519-0065 — PIN: 512 235 493# See you all there! @aryansondharva @Annunitha @Asutosh-1234 @avanithumballi @sadhami0519 @ritvik-37 @tirth1356 @Dipanita45 |
|
No issues, will share the after meet notes and steps for everyone for future updates and new contributors |
|
@aryansondharva @Annunitha @Asutosh-1234 @avanithumballi @sadhami0519 @ritvik-37 @tirth1356 @Dipanita45 The meeting started , you can join now |
|
Every one @aryansondharva @Annunitha @Asutosh-1234 @avanithumballi @sadhami0519 @ritvik-37 @tirth1356 @Dipanita45 |
📌 Engineering Standard: Always Rebase Before Requesting ReviewThis is a heads-up for all active contributors. Going forward, a PR cannot be reviewed or merged unless it is rebased onto the current This is standard industry practice and it matters for three reasons:
The rule: # Before requesting review or asking for a merge:
git fetch origin
git rebase origin/main
# resolve any conflicts
git push --force-with-leaseIf your PR has merge conflicts, it will not be reviewed until they are resolved. If you don't know how to rebase, ask in this thread and someone will walk you through it. Why This applies to all open PRs: @Adil2009700 @Dipanita45 @MaryamMohamedYahya @ritvik-37 @i-am-sachin-verma @sadhami0519 PR #189 was just rebased and merged today as an example of what a clean, rebase-ready PR looks like. |
🚀 May 2026 Launch Plan — Concierge MVPWe are going into our first live cohort this month. This post is the single source of truth for what needs to land before we go live. Read it fully if you're contributing. What "Launch" means (Concierge MVP)
This is not a public launch. This is a controlled, managed cohort. We can handle rough edges — but the core flows must work. ✅ Already Built and Working
🔧 Critical — Must land before first cohortThese are the gaps between "platform exists" and "platform actually runs a cohort."
These four issues are the launch blockers. Everything else is polish. 🟡 High Value — Land in the first two weeksThese improve the experience for both cohort members and the companies we bring in.
⏳ Defer to Q3These are real and valuable but don't affect the May cohort:
Rebase before you submitMain has moved significantly this week. All PRs must be rebased onto current git fetch origin && git rebase origin/main && git push --force-with-leaseHow to contribute to the launch
The fastest contributors on #218 and #220 unlock the entire cohort pipeline. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Adventurers Guild Launch Promotion Strategy
Hey team @Dipanita45 @avanithumballi @Annunitha @sadhami0519 @aryansondharva @ritvik-37 @Asutosh-1234 @tirth1356 — this is our comprehensive go-to-market plan for the Adventurers Guild launch!
Overview
We're executing a 4-phase promotion strategy starting April 24 to drive awareness, signups, and early payment adoption. This is a coordinated effort where everyone plays a role.
Phase 1: Pre-Launch Hype (Apr 24–26)
Goal: Build anticipation and warm up audience
Channels & Tactics:
X/Twitter:
LinkedIn:
Dev Communities:
Email: Pre-launch list warmup (50-100 existing leads)
Content: Teaser video, GIFs of UI, hero image, stats graphic ready for reposts
Phase 2: Launch Day (Apr 27)
Goal: Maximum visibility on launch day; land top rankings
Channels & Tactics:
Product Hunt (THE centerpiece):
HackerNews "Show HN":
Other Launch Sites:
Press Outreach:
Content Marketing:
Phase 3: Sustained Momentum (Apr 28–May 10)
Goal: Convert curiosity into engaged users; drive first payments
Channels & Tactics:
Content Syndication:
Community Building:
YouTube + Video:
Partnerships:
Paid Ads (if budget allows):
Milestone Posts:
Phase 4: Organic Growth (Ongoing)
Goal: Sustainable, network-driven growth
Tactics:
Messaging Angles
For Developers (Adventurers):
For Companies:
For Educators (Boot Camps):
Content Assets Checklist
Week 1 Success Metrics
Contingency Plan
If PH/HN underperform:
If signups convert poorly:
Timeline
Next Steps
🗓️ Team Meeting: Future Scoping & Planning
We'll be hosting a project scoping meeting for next-phase planning (Party system, Guild Cards, advanced payment features, etc.).
Proposed Dates: April 24–27
Proposed Times: 4:00pm – 8:00pm IST
Duration: 1–2 hours
Please reply below with your available times, and we'll find a slot that works for everyone. Format: "I'm free Apr 24 from 5–7pm IST" or similar.
Let's ship this and make AG a household name in dev marketplaces! 🚀
All reactions