BUY-2453 Week 1 Run Sheet
Owner: Reach
Window: 2026-04-17 to 2026-04-23
Source calendar: BUY-2453_30_day_social_media_calendar_2026-04-17_to_2026-05-16.md
This file turns the first 7 days of the campaign into a simple operator sequence. It should be used with the main calendar, the schedule CSV, and the post tracking template.
Week 1 Goal
Establish the main thesis clearly:
- shopping agents fail at retrieval more often than reasoning
- BuyWhere exists as the catalog and comparison layer for that problem
- Singapore is a credible market wedge because merchant fragmentation is real
Success Signals
- at least 3 meaningful replies that engage with the retrieval-layer thesis
- at least 1 developer asking for docs, MCP details, or API access
- evidence that one of the week-1 angles is strong enough to repeat in week 2
Daily Sequence
| Date | Channel | Suggested Time (SGT) | Asset | CTA | Go / No-Go Check |
|---|---|---|---|---|---|
| 2026-04-17 | Twitter/X | 12:00 | workflow visual | docs UTM | confirm docs page is live and current |
| 2026-04-18 | 10:00 | API screenshot | docs UTM | confirm founder-voice account is the right poster | |
| 2026-04-19 | 21:00 | none | discussion-only | confirm subreddit rules tolerate this kind of thread | |
| 2026-04-20 | Twitter/X | 18:30 | workflow visual | docs UTM | avoid posting if previous post is still actively converting replies |
| 2026-04-21 | Twitter/X | 12:30 | curl snippet | docs UTM | verify example still matches live API response shape |
| 2026-04-21 | 09:30 | workflow visual | docs UTM | make sure this does not duplicate the April 18 post too closely | |
| 2026-04-22 | Twitter/X | 18:00 | schema snippet | MCP UTM | verify MCP guide path is live and accurate |
| 2026-04-22 | 21:30 | none | discussion-only | check whether r/MachineLearning is in a promotion-sensitive mood | |
| 2026-04-23 | Twitter/X | 12:00 | none | docs UTM | use only if week-1 messaging is still fresh |
| 2026-04-23 | 10:00 | merchant/logo grid | docs UTM | confirm regional-fragmentation angle fits current company messaging |
Operator Notes By Day
2026-04-17
- Objective: establish the core thesis in the shortest possible form
- Risk: sounding like a generic AI launch post
- Adjustment if needed: remove product name from the first sentence and lead even harder with the problem
2026-04-18
- Objective: give the thesis a stronger founder/infrastructure framing
- Risk: reading like a polished ad
- Adjustment if needed: add one concrete anecdote or engineering pain point from the build
2026-04-19
- Objective: start a real discussion without forcing a link drop
- Risk: subreddit sees it as disguised promotion
- Adjustment if needed: remove BuyWhere mention from the first paragraph and keep the bias disclosure near the end
2026-04-20
- Objective: introduce the workflow model that will recur later in the campaign
- Risk: too abstract without proof
- Adjustment if needed: pair with a compact response screenshot in a reply instead of the main post
2026-04-21
- Objective: make the workflow feel concrete through API primitives
- Risk: claiming an example that no longer matches the product surface
- Adjustment if needed: replace the example SKU/query before publishing
2026-04-22
- Objective: sharpen the MCP angle without sounding like generic MCP trend-chasing
- Risk: the guide or endpoint does not feel mature enough
- Adjustment if needed: keep the post about clean tool outputs rather than MCP specifically
2026-04-23
- Objective: localize the thesis to Singapore and SEA fragmentation
- Risk: repeating the same angle from earlier in the week
- Adjustment if needed: emphasize merchant inconsistency rather than general fragmentation
Week 1 Review Questions
At the end of April 23, answer:
- Which post earned the highest-quality replies?
- Did the audience respond more to architecture language, product workflow language, or market-fragmentation language?
- Did anyone ask for pricing, API access, MCP setup, or merchant coverage details?
- Which wording felt too promotional and should be softened in week 2?