fewpips · internal handoff
“Will send them today!” — what Nick is owed, and how to get it to him
Send-readiness handoff · Fewpips Marketing thread · 2026-08-30 · prepared for Veljko & Djordje
1 · The two messages this task is about
Nick Jones — Aug 30, 12:42 (msg 764)
“…lets have our weekly call tomorrow at 5pm Dubai Time? Does this work? Or 6pm?”
Nick Jones — Aug 30, 13:39 (msg 765)
“Also do we have banners for the CRM and website for the giveaway?”
Veljko — Aug 30, 16:00 (msg 766)
“That works Nick”
Veljko — Aug 30, 16:01 (msg 767)
“Will send them today!”
2 · What the two replies resolve to
“That works Nick”
Confirms the weekly call: 5pm Dubai time, tomorrow (Sun 31 Aug).
No deliverable — just a scheduling ack. Nothing to send.
“Will send them today!”
“them” = the giveaway banners — one for the CRM, one for the website.
Direct reply to Nick’s msg 765. This is the promised file drop.
3 · The deliverable owed — giveaway banners
The live giveaway is Vault 4, extended by decision to run through 31 Aug (Dylan, msg 740:
“Decision has been taken to extend vault 4 until the 31st Aug. A new banner to be uploaded to the CRM.”).
Nick is asking whether the two placement banners for it exist.
| Placement | What it is | Typical spec | Status on runner |
| CRM banner | Dashboard hero for the Vault 4 giveaway (users’ CRM view) |
Wide banner, e.g. 1200×400 / 3:1 | not on runner |
| Website banner | Homepage / promo strip for the same giveaway |
Hero 1600×600 + mobile 1080×1080 | not on runner |
Checked: task inbox (empty), Fewpipss GitHub org (only fewipips, no banners repo),
Supabase client_tasks (brand b244996f…), and the Fewpips thread/Drive links — no Vault 4 banner
files are present on the runner, and no rendered banner was posted in the thread.
4 · CONFIRM before the banners can be finalized
The runner will not invent giveaway figures. To render final CRM + website banners, confirm the
verified Vault 4 copy:
- Prize / offer — exact reward and amount(s)
- Live dates — confirm
Aug 30 → Aug 31, 2026 (Vault 4 extension)
- Promo / entry code — if any (e.g. a
CLAIMxxx style code)
- CTA + destination URL — what the button says and where it points
- Any required T&Cs / eligibility line
Note: the September “Gold Rush” plan (msg 555) is marked INTERNAL · NOT FOR DISTRIBUTION
and explicitly says “no site banner” for its private track — it is not a source for this public
Vault 4 creative.
Reply with the above (or drop the finished banners) and the runner renders both placements immediately —
brand copy locked to fewpips (lowercase p).
5 · How Nick gets the files (send path)
- The runner does not post to Telegram/Discord/CRM or message Nick — that step is Veljko/Djordje.
- Once the two banners are approved: Veljko sends them in the Fewpips Marketing thread today,
upload the CRM banner to the CRM, and place the website banner live (via the normal
Fewpipss/fewipips PR flow if it goes on fewpips.com).
- Then get Nick’s “received / good to go” and log filenames + links back into this CRM task’s notes.