h2. Goal Expose WordPress (pressblk.com) to AI agents via Model Context Protocol (MCP), so Claude Code and other MCP clients can manage posts, pages, media, plugins, settings, etc. directly from chat. h2. Result * MCP endpoint live at {{https://pressblk.com/wp-json/mcp/mcp-adapter-default-server}} * Protocol: MCP 2025-06-18 * Auth: Basic with WordPress Application Password (user {{mcp-bot}}, Administrator role) * *85 native MCP tools exposed* (one per WordPress operation) * Verified end-to-end: real {{mcp-wp-list-posts}} call returned actual posts from pressblk.com h2. Plugins installed (in this order) || # || Plugin || Version || Source || Role || | 1 | MCP Adapter | 0.5.0 | WordPress/mcp-adapter | Official MCP engine. Bridges Abilities API to MCP protocol. | | 2 | MCP WordPress Capabilities (WAE) | 1.0.0 | kradyy/wordpress-wae | Registers 85 abilities ({{mcp-wp/*}}) across 12 categories. | | 3 | PressBlk MCP Fix | 1.0.2 | Custom (Verixity LLC) | Disables mcp-adapter's default server so WAE's separate server can take the route. | h2. Problem found & fixed Both mcp-adapter and WAE register a server on the same REST route ({{mcp/mcp-adapter-default-server}}). mcp-adapter creates its server first (priority 10) with only 3 service tools and 0 abilities. WAE tries to register at priority 20 with all 85 abilities, but route is already taken — registration silently shadowed. {{tools/list}} returned 0 useful tools. Fix in {{pressblk-mcp-fix v1.0.2}} (4 KB plugin): * *Strategy A:* filter {{mcp_adapter_create_default_server}} → false at priority 1 (skips default server creation entirely) * *Strategy B (fallback):* on {{mcp_adapter_init}} priority 999, use reflection to scan {{$adapter->servers}}, detect route conflict, remove the default server post-hoc * Both strategies log diagnostics to {{debug.log}} After fix: * Server name in {{initialize}} response: {{MCP WordPress Capabilities}} v1.0.0 (was: {{MCP Adapter Default Server}}) * {{tools/list}}: *85 tools* (was: 0–3) h2. Tools exposed (85, by category) || Category || Count || Examples || | Posts/Pages | 10 | {{mcp-wp-list-posts}}, {{mcp-wp-create-page}}, {{mcp-wp-edit-post}} | | Comments | 5 | {{mcp-wp-list-comments}}, {{mcp-wp-create-comment}} | | Custom Post Types | 5 | {{mcp-wp-create-content}}, {{mcp-wp-list-content}} | | Menus | 10 | {{mcp-wp-create-menu}}, {{mcp-wp-assign-menu-location}} | | FSE/Block Entities | 5 | {{mcp-wp-create-block-entity}} | | Patterns | 7 | {{mcp-wp-create-pattern}}, {{mcp-wp-import-pattern}} | | Media | 6 | {{mcp-wp-list-media}}, {{mcp-wp-upload-media}}, {{mcp-wp-replace-media-file}} | | Users | 5 | {{mcp-wp-list-users}}, {{mcp-wp-edit-user}} | | Taxonomy | 6 | {{mcp-wp-create-category}}, {{mcp-wp-list-tags}} | | Settings | 4 | {{mcp-wp-get-settings}}, {{mcp-wp-update-settings}}, {{mcp-wp-get-site-stats}} | | Plugins & Themes | 14 | {{mcp-wp-install-plugin}}, {{mcp-wp-activate-plugin}}, {{mcp-wp-switch-theme}} | | Advanced | 8 | {{mcp-wp-batch-update}}, {{mcp-wp-custom-rest-call}}, {{mcp-wp-validate-blocks}} | h2. Security posture * Dedicated WP user {{mcp-bot}} with Application Password (not the owner account) * Currently Administrator role (full WP capabilities) — appropriate while we still need plugin/theme/settings management * Can be downgraded to Editor if MCP usage is limited to content operations only * Application Password used in initial setup was leaked in chat and *MUST be rotated* (see follow-ups) * {{DISALLOW_FILE_MODS}} status: TBD — site currently allows plugin uploads via wp-admin, fine for our use h2. Follow-ups * (P0) Rotate Application Password — revoke old, generate new, store securely * (P1) Wire up {{.mcp.json}} in {{/home/pressblk-back}} so Claude Code can call these tools * (P2) Consider IP allowlist on nginx for {{/wp-json/mcp/*}} route (only allow agent-server IPs) * (P3) Document common workflows: "publish blog post via MCP", "bulk update featured images", etc. * (P4) Investigate why WAE 1.0.0 conflicts with mcp-adapter 0.5.0 default — open upstream issue or PR h2. Files / artifacts * Plugin source: {{/tmp/wp-mcp-plugins/pressblk-mcp-fix/pressblk-mcp-fix.php}} on host * Distributable zip: {{/tmp/wp-mcp-plugins/pressblk-mcp-fix.zip}} (1.8 KB) h2. Test verification {code:bash} curl -X POST -u 'mcp-bot:APP_PWD' \ -H 'Content-Type: application/json' \ -H 'Accept: application/json, text/event-stream' \ -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"x","version":"1"}}}' \ https://pressblk.com/wp-json/mcp/mcp-adapter-default-server # → Server: MCP WordPress Capabilities v1.0.0 curl -X POST -u 'mcp-bot:APP_PWD' \ -H 'Content-Type: application/json' \ -H 'Mcp-Session-Id: SESSION_ID' \ -d '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' \ https://pressblk.com/wp-json/mcp/mcp-adapter-default-server # → 85 tools {code}

Session 2026-05-06 — backend and infrastructure work. *Light Theme:* - Recolored all 4 beta pages to match pressblk.com (white bg, blue #0693e3) - Fixed footer links: /about-us/ -> /about/, /contact-us/ -> /contact/ - terms-of-use.html and privacy-policy.html mounted in Docker (fixed 500) *Email Verification:* - Added /beta-verify/{token} endpoint — proper gate before media library access - Media library blocks unverified users (403) - Tickets require email_verified_at - Email button: Verify My Email -> /beta-verify/{token} *Email Campaign System (Filament Admin):* - New EmailCampaignResource with RichEditor for email body - 3 recipient fields: Users dropdown, Beta Testers dropdown, manual email input - Delivery types: manual (send now), scheduled, event triggers - SendCampaignJob with per-recipient logging - campaigns:send-scheduled command (every minute) - Fixed recipient_type default value (500 on create) *SMTP/DKIM/SSL:* - SSL cert was expired (Plesk self-signed from 2022) — admin installed Let Encrypt - DKIM configured and passing - SPF/DKIM/DMARC all PASS — spam is reputation-based, not auth *Search Backend:* - SearchController now uses ST_Distance_Sphere with lat/lng/distance - Auto-fallback: if 0 results in radius, shows 5 nearest - Hidden binary POINT location from Business JSON (was crashing mobile) - Added JSON_INVALID_UTF8_SUBSTITUTE to prevent 500 on bad data - Deleted test businesses with Cyrillic names *Chat Push Notifications:* - PushNotificationService: filter is_active tokens, parse Expo ticket errors - Auto-deactivate DeviceNotRegistered tokens - Added diagnostic endpoint GET /messages/test-push/{userId} *Security — Malware:* - pressblk.com crypto-drainer root cause: WakeX API port 3847 + phpMyAdmin port 8081 open to internet - MySQL root password hardcoded in server.js - Recommended: close ports, change all passwords *Docker:* - Mounted entrypoint.sh for Filament assets auto-publish - Filament ticket view shows attached screenshots - Ticket list shows beta tester name correctly *Commits:* d0b5d91, 3d75e2f, 0c83437, b58ba2f, 3841907, 5e87720, 4010d42, 0709944, d46a43e + more

Implemented a complete beta tester management system with 4 public pages and full workflow automation. *Pages created:* - /beta-testers — Registration form with NDA, signature canvas, iOS/Android platform selection - /my-media/{token} — Personal media library for each tester (upload screenshots, grid view, lightbox, iOS Shortcut support) - /beta-tickets — Bug report / feature request form (4-step wizard with media library integration) - /beta-faq — 39 Q&A items across 7 sections *Backend:* - BetaTester model + migration (name, email, phone, platform, NDA signature, media_token, email_verified_at) - BetaMedia model + migration (file uploads, per-tester storage) - MediaLibraryController — upload, list, delete, list-by-email endpoints - BetaTicketController — public ticket creation, library_ids attachment, email verification check - AppStoreConnectService — JWT auth, auto-add iOS testers to TestFlight, skip invite for existing ASC testers - BetaTesterWelcome email — verification link, TestFlight instructions, media library link, ticket guide - Docker: persistent volume for media uploads, mounted HTML/blade/ASC key files *TestFlight integration:* - Auto-invite new iOS testers to External Beta Testers group via ASC API - Skip invite for existing internal/external testers (isTesterExists check) - Added build 2 to Beta Testers group - Fixed Codemagic build numbering — now queries ASC API for max build + 1 - Fixed beta_groups name: Beta Testers (was AppBuilder Testers) *IAP fix:* - Fixed "Invalid request for iOS. The sku property is required" error - react-native-iap v14.7.20 requires request.apple.sku format (not request.sku) *Security — Malware analysis on pressblk.com:* - Crypto-drainer returned (same attacker wallet 0x08207B...) - Full scan: infection via wp_footer hook, /cart/ and /checkout/ clean (WooCommerce simplified template) - Root cause found: WakeX chat-api on port 3847 exposed MySQL root password to internet - phpMyAdmin on port 8081 also open externally - Same password (PressBlk2025Secure!) used across all services - SQL queries prepared for WordPress DB cleanup - Recommended: close ports 3847/8081, change all passwords, install Wordfence *SMTP issue:* - mail.pressblk.net SSL port 465 down after Plesk cleanup - Port 25 + STARTTLS works but SPF mismatch (our IP 148.72.133.193 not in SPF record) - Fix: admin needs to add ip4:148.72.133.193 to pressblk.app SPF DNS record *Commits:* 8c23313, 5c19878, 1da6226, 3bea5c9, 195138f, ab47ddd, cf3d881, ff6e96f, 7a5ec34, 0950eb4, 74459d0, 0e3bff0, 2973ea5 (mobile)

pressblk.com WordPress site was compromised with a crypto-drainer malware injected via a fake MU-plugin. The malware displayed a fake Cloudflare verification page to trick visitors into executing malicious code. Additionally, the site header/navigation menu was missing due to Hello Elementor theme not supporting standard WordPress menus. Scope: 1. Security audit and malware removal 2. Website header/navigation restoration 3. Post-incident security recommendations

h2. Sources to scrape 15 Black-owned-business directories referred by Michael Battle (Oct/Jun/Jul 2025 emails) plus Max's earlier scraping targets. ByBlack is already covered (PRESSWEB-105 + the new staging:import-from-byblack-api command). Each line below is a checkbox — update status as scrapers ship. h3. Source list (status: ☐ pending · ⚙ recon · 🛠 built · ✅ live · 🚫 blocked) *From Michael Battle — Oct 17, 2025 email:* * ☐ www.buyblack.org * ☐ www.ourgreenweb.com * ☐ www.blackbusinesslist.com * ☐ www.blackdirectory.com * ☐ www.blacksheet.net * ✅ www.byblack.us — covered in PRESSWEB-105 + new /api/v3/search/ harvester * ☐ www.blackownedworld.org * ☐ www.yourgreenbook.com *From Michael Battle — June 19, 2025 email (Green Book):* * ☐ greenbooktb.com * ☐ www.floridablackchamber.com *From Michael Battle — June 20, 2025 email (URL):* * ☐ usblackchambers.org *From Michael Battle — July 26, 2025 email (MS Black Pages):* * ☐ MS Black Pages — need to find canonical URL *Max's earlier scraping targets:* * ☐ funtimesmagazine.com/business-directory/ * ☐ championblackbusinesses.com * ☐ abc.iamblackbusiness.com * ☐ blackwomenempowereddirectory.com h2. Plan *Phase 1 — Recon (in progress):* For each site, check robots.txt, look for sitemap.xml, sample one listing page + one detail page, identify CMS/SPA (WordPress, Wix, Joomla, custom SPA, etc.). Classify each as: * *easy* — has sitemap, server-renders detail pages with clear structured data → reuse StagingImportFromDirectories framework, ~30 min per site to wire up * *medium* — needs HTML regex/JSON-LD parsing, but data is server-rendered → ~1 hr per site * *spa* — JS-rendered like ByBlack was → either find their backend API (best) or use Crawlee/Playwright (Phase 2) * *blocked* — Cloudflare WAF / login-walled / hostile → defer or use paid scraping API *Phase 2 — Build the easy wins:* For each easy/medium site, add a new entry to the $directories array in StagingImportFromDirectories.php and a new parser method. Reuse the WebShare proxy rotation, UA rotation, jitter, daily cron pattern that's already working for EatOkra and ByBlack. *Phase 3 — SPA / blocked sites:* For sites that need JS rendering, either reverse-engineer their backend API (worked for ByBlack — found api.byblack.us/api/v3/search/) or use the Playwright pipeline at /home/pressblk-crawlee/. h2. Expected yield ByBlack alone has 17,979 listings hidden behind their SPA. If even 5 of these other 15 sites have similar volume, that's potentially 50K-100K new BO-curated rows added to business_staging. h2. Tracking Description gets updated as each site moves through the workflow. Each scraper gets its own commit + completes its checkbox above. Final summary added when the full list is done. h2. Related * PRESSWEB-105 — Scraper 2.0 base + EatOkra + ByBlack * PRESSWEB-104 — fast-cycle cron + lock fixes (foundation infrastructure) * /home/pressblk-crawlee/ — Playwright infrastructure for the SPA-only sites

h2. Symptom User checking /scraper-queries observed 0 progress drainage despite the cron showing every 10 min as scheduled. Investigation showed the gmaps-scraper had been *running* but only producing duplicates (every batch returned 13 businesses, all merged into existing rows). h2. Three root causes h3. Bug 1 — *%%* in whereRaw caused MySQL syntax error In scripts/run-scraper-and-import.sh the partition picker was: {noformat} ->whereRaw('id %% \${INSTANCE_TOTAL} = \${INSTANCE_NUM}') {noformat} PHP whereRaw passes the string verbatim. MySQL saw {{id %% 2 = 0}} which is invalid (MySQL modulo is single {{%}}). Stack trace from storage/logs/scraper.log: {noformat} SQLSTATE42000: Syntax error or access violation: 1064 ... near '% 2 = 0 limit 10 for update' {noformat} The SQL exception fell through to a fallback that picked only 1 random pending query per tick instead of the requested 10. With ~12 ticks/hour × 1 query each = ~12 queries/hour throughput, where intended was 120/hour. h3. Bug 2 — 16 rows stuck in *queued* state The pickup logic sets {{status='queued'}} when reserving rows but only flips to {{completed}} after a successful run. When the script crashes / OOMs / network-fails between those steps, rows remain {{queued}} forever. Query showed 16 rows had been {{queued}} since 2026-04-14 (12 days). Permanently lost from rotation until manually reset. h3. Bug 3 — backlog vastly bigger than visible 'pending' suggested Of the 8,284 pending queries, *5,760 had never been run* (last_run_at IS NULL) — that's the genuine backlog. The remaining 2,524 had been retried at least once. h2. Fixes applied # *Script SQL fix*: scripts/run-scraper-and-import.sh — single-character change {{%%}} → {{%}}. Verified via tinker that the partition picker now returns 5 partition-1 odd-id rows correctly (#293 Orlando real-estate, #1381 Phoenix barbershop, etc.). # *Stuck-queued reset*: SQL {{UPDATE scraper_queries SET status='pending', last_run_at=NULL WHERE status='queued' AND updated_at < NOW() - INTERVAL 1 HOUR}} → 16 rows back into rotation. Pending count: 8,284 → 8,300. # *Throughput bump*: host crontab — both A and B instances bumped from {{run-scraper-and-import.sh 10 60 120}} to {{... 30 60 120}} (10 → 30 queries per tick). # *Zombie cleanup*: killed run-scraper-and-import.sh PIDs 681921+681924 (started 09:30 UTC — running 14h with no completions in the last 18h). h2. Expected throughput ||Config||Queries/hour||Time to drain 5,760|| |Before fix (broken)|~12|~480 hours / 20 days| |After Bug 1 fix only|~120|~48 hours / 2 days| |After Bug 1 + batch 30|*~360*|*~16 hours*| |+ 4 partitions later (option)|~720|~8 hours| h2. Files changed * scripts/run-scraper-and-import.sh — 1-char fix in line 52 (whereRaw) * host crontab (root) — both A and B instances run-scraper-and-import.sh max-queries 10 → 30 h2. Commit 94054de on dev — "fix(gmaps-scraper): %% in whereRaw causing partition picker to fail" h2. Verification Waiting for next cron tick to confirm 30-query batch picks up at scale. Will append result as a comment. h2. Related * PRESSWEB-105 — Scraper 2.0 (separate system, directory imports). Surfaced this bug because user asked how /scraper-queries relates to Scraper 2.0; investigation revealed the gmaps-scraper queue had been quietly broken for ~2 weeks.

h2. Why LinkedIn DW enrichment was producing low-yield matches because the populations don't overlap: the DW skews to white-collar corporate professionals while pressblk's target is small Black-owned local businesses. We pivoted away from DW-based enrichment and toward harvesting *curated Black-owned-business directories* — the right population for the platform. h2. What was built New artisan command *staging:import-from-directories*. Unlike the existing staging:verify-directories (which only flips black_owned_verified=true on existing rows), this command IMPORTS new rows from the directory: walks the sitemap, parses each detail page, inserts to business_staging with black_owned_verified=true and data_sources='directory_'. h3. Source decisions (post-recon) Research agent fetched samples from all four originally-proposed directories. Results forced two big pivots: ||Directory||Listings||Verdict|| |EatOkra|*18,914 restaurants*|PRIMARY — clean JSON-LD on every detail page| |SupportBlackOwned|~500|Wired but excluded from --directory=all; HTML structure inconsistent, parser needs rewrite| |OBWS|N/A|*Dropped* — turned out to be a Shopify product catalog, not a business directory| |WeBuyBlack|N/A|*Dropped* — same, Shopify product catalog| h3. EatOkra implementation * Sitemap: https://www.eatokra.com/sitemaps/sitemap1.xml.gz (gzipped) * URL filter: /businesses/ → 18,914 restaurant URLs * Each page has a single

Tasks Assign to Client

Key	Subject	Request	Attachments	Priority	Comments	Status	Resolution	Current Environment	Labels	Dates
PRESSWEB-21	create a header for Facebook, Linkedin accounts	create a header for Press black, include the screenshots of ... create a header for Press black, include the screenshots of the application and happy customers. give us 3 variations. Reply		High	For the Client For the Manager   headers has been created. please verify attached.	Backlog	Unresolved	--	Request_to_client	CreatedJuly 29, 2025 11:42 PM UpdatedMay 9, 2026 5:59 PM

Close

Tasks Assigned to Team

Key	Subject	Request	Attachments	Priority	Comments	Status	Resolution	Current Environment	Labels	Dates
PRESSWEB-20	Twilio - purchase of the phone number (support)	Was with Michael on the phone and also on twilio site. submi... Was with Michael on the phone and also on twilio site. submitting the ticket and reviewing the functionality.		Medium		Backlog	Unresolved	--	Request_to_team	CreatedJuly 23, 2025 8:23 AM UpdatedJuly 28, 2025 1:38 PM
PRESSWEB-18	About us page - create a new page and link to the menu	see the attached doc file and add content to the about us pa... see the attached doc file and add content to the about us page.  assign the task to Anton to create a few images so page would look better		High		Done	Done	--	Request_to_team	CreatedJuly 15, 2025 9:49 PM UpdatedAugust 28, 2025 3:58 AM
PRESSWEB-16	https://pressblk.com/lifetime/ - page fix	# We need to implement payment flow on [https://pressblk.com... # We need to implement payment flow on https://pressblk.com/lifetime page # We need to implement "thank you" page to track purchases later on as part of PRESSWEB-15 task implementation	Download	Highest	For the Client For the Manager  This is the update to this ticket.    here is one more update This is stil lnot resolved. please update us on the status.	In Progress	Unresolved	--	Request_to_team	CreatedJuly 12, 2025 5:15 AM UpdatedAugust 2, 2025 12:35 PM
PRESSWEB-15	Foundation Setup	*  Create and verify Instantly.ai account (Hyper Growth plan... *  Create and verify Instantly.ai account (Hyper Growth plan recommended) *  Set up 3-5 warm email addresses with aged domains (6+ months old) *  Configure email authentication (SPF, DKIM, DMARC records) *  Initiate email warm-up process (20 emails/day limit, increase by 1 daily) *  Install Google Analytics 4 on WordPress site *  Implement conversion tracking scripts on purchase pages *  Set up UTM parameter tracking for campaign attribution		Highest		In Progress	Unresolved	--	Request_to_team	CreatedJuly 12, 2025 4:59 AM UpdatedJuly 28, 2025 1:35 PM
PRESSWEB-13	Email campaign preparation - Action List ( copy in the email to the client)	h2. For Project Manager (Dmitry): h3. Immediate Actions (Ne... h2. For Project Manager (Dmitry): h3. Immediate Actions (Next 1-2 days) *  Follow up with Michael to obtain list of owned domains (excluding pressblk.com) *  Request domain credentials from Michael for Instantly integration *  Finalize Instantly setup based on previous suggestions once domains are provided *  Verify that Michael has proceeded with "Growth Plan" on Instantly platform *  Review attached screenshot referenced in email (if available) h3. Setup & Configuration (Next 3-5 days) *  Prioritize integration of older domains first, then newer ones *  Configure domain connections with Instantly platform *  Test email deliverability for integrated domains *  Ensure spam filter avoidance protocols are in place h3. Content & Campaign Management *  Coordinate landing page URL update from {{/lifetime-membership-v2/}} to {{/pre-sale}} *  Modify 2nd and 3rd email templates to include new landing page link (https://pressblk.com/pre-sale) *  Ensure emails are properly targeted at Black business owners as specified *  Complete final campaign setup and testing ---- h2. For Client (Michael): h3. Immediate Actions Required (Next 1-2 days) *  URGENT: Provide complete list of owned domains (excluding pressblk.com) ** Suggested examples: pressblakapp.net, mypressblack.com, or similar *  Supply domain credentials/access information for Instantly integration *  Purchase "Growth Plan" on Instantly platform (as shown in screenshot) h3. Domain Management *  Identify oldest domains in portfolio for priority setup *  Ensure all provided domains are active and properly configured *  Avoid using pressblk.com for email campaigns to protect main business domain h3. Coordination *  Respond promptly to Dmitry's requests to avoid further delays *  Review and approve final email campaign setup before launch *  Confirm landing page URL change from {{/lifetime-membership-v2/}} to {{/pre-sale}} ---- h2. Timeline Considerations: * Critical: Domain information needed within 48 hours to prevent further project delays * Note: Original 21-day wait for pre-warmed emails from Instantly makes immediate action essential * Risk: Any delays could impact campaign launch timeline and business operations		High		Backlog	Unresolved	--	Request_to_team	CreatedJuly 11, 2025 9:32 AM UpdatedJuly 28, 2025 1:38 PM
PRESSWEB-10	setup instantly account and hook up ChatGTP / AI for unique messages	h2. Campaign Overview *Launch Date:* July 8th, 2025 *Ta... h2. Campaign Overview *Launch Date:* July 8th, 2025 *Target:* 5,000 small business owners from 528web.com *Platform:* Instantly.ai *Goal:* Drive traffic to https://pressblk.com/lifetime/ for subscription purchases access to website: https://jira.verixity.com/browse/PRESSWEB-11  (credentials ) h2. Critical To-Do Checklist h3. Phase 1: Pre-Launch Setup (July 4-7, 2025) h4. Day 1 (July 4) - Foundation Setup - https://jira.verixity.com/browse/PRESSWEB-15  *  Create and verify Instantly.ai account (Hyper Growth plan recommended) *  Set up 3-5 warm email addresses with aged domains (6+ months old) *  Configure email authentication (SPF, DKIM, DMARC records) *  Initiate email warm-up process (20 emails/day limit, increase by 1 daily) *  Install Google Analytics 4 on WordPress site *  Implement conversion tracking scripts on purchase pages *  Set up UTM parameter tracking for campaign attribution h4. Day 2 (July 5) - Content & Data Management - https://jira.verixity.com/browse/PRESSWEB-14  *  Export contact list from 528web.com (5,000 contacts) *  Clean and validate email data (remove duplicates, check formats) *  Import contacts to Instantly.ai with proper field mapping *  Create 3-email main sequence content *  Write retargeting email templates (24-hour and cart abandonment) *  Design mobile-responsive email templates h4. Day 3 (July 6) - Campaign Configuration *  Set up email sequences in Instantly.ai (3-5 days between emails) *  Configure A/B testing for subject lines and content *  Set up retargeting automation triggers *  Distribute contacts across warm email accounts *  Set sending limits (50-100 emails per account per day) *  Send test emails and verify all links/tracking h4. Day 4 (July 7) - Final Preparations *  Complete final content review and compliance check *  Verify WordPress tracking end-to-end *  Confirm email authentication status *  Schedule launch sequence for July 8th, 9:00 AM EST *  Set up monitoring dashboard and alert notifications *  Brief team on launch procedures h3. Phase 2: Launch & Monitoring (July 8+) h4. Launch Day Execution *  *8:00 AM:* Final system checks and verification *  *9:00 AM:* Launch first batch (1,000 contacts) *  *11:00 AM:* Monitor initial performance metrics *  *12:00 PM:* Continue rollout (remaining 4,000 contacts in 500-contact batches) *  *6:00 PM:* Complete end-of-day performance analysis h4. Daily Monitoring Tasks *  *Morning (9:00 AM):* Check deliverability metrics (bounce <2%, spam <0.1%) *  *Afternoon (2:00 PM):* Analyze engagement and optimization opportunities *  *Evening (6:00 PM):* Generate daily performance report h3. Phase 3: Success Metrics & Optimization h4. Target KPIs to Achieve *  Delivery Rate: >98% *  Open Rate: 25-35% *  Click-Through Rate: 3-7% *  Conversion Rate: 1-3% *  Bounce Rate: <2% *  Spam Complaint Rate: <0.1% h4. Weekly Optimization Tasks *  *Week 1:* Test subject lines, send times, and content variations *  *Week 2+:* Implement advanced segmentation and dynamic content *  *Ongoing:* Refine retargeting sequences based on performance data h2. Critical Dependencies & Risks h3. Must Complete Before Launch *  Minimum 14-day email warm-up period *  Email authentication verification (SPF, DKIM, DMARC) *  WordPress tracking implementation and testing *  Compliance review (CAN-SPAM, GDPR, CCPA) h3. Contingency Plans Ready *  Backup warm email addresses prepared *  Alternative tracking methods documented *  Technical support contacts identified *  Campaign pause procedures established h2. Deliverables # *Daily Performance Reports* (starting July 8th) # *Weekly Optimization Recommendations* # *Campaign Performance Analysis* (end of campaign) # *Lessons Learned Documentation* ---- *📎 Attached:* Complete detailed project plan (email_campaign_project_plan.pdf) with technical specifications, email templates, code implementations, and step-by-step procedures. *⚠️ Priority:* This is a time-sensitive campaign with a fixed launch date. All pre-launch tasks must be completed by July 7th to ensure successful deployment.		High		Backlog	Unresolved	--	Request_to_team	CreatedJuly 3, 2025 2:18 PM UpdatedJuly 28, 2025 1:38 PM
PRESSWEB-2	improve presentation for investors	goal is to improve the presentation. figma -> [https:/... goal is to improve the presentation. figma -> https://www.figma.com/design/7o6sF0KBZ48W7HrqsfyC8b/Press-Black?node-id=2008-29042&node-type=canvas&t=LBxT1jy5RBYGuSix-0 https://www.figma.com/design/xKUkM3X1H2zJAmbaNXGB1Z/Press-Black-Web?node-id=817-2939&node-type=canvas&t=J7R7TU4UXcyp4pdn-0 -------------- PressBlk - Connecting Black Businesses to a Global Audience The Problem: Market Gap: Consumers seeking Black-owned businesses and products face significant challenges in locating desired goods and services. Despite the demand, there is no comprehensive platform designed to bridge this gap effectively. Customer Challenge: Black consumers spend approximately $300 billion annually on unsatisfactory products and services, indicating a lack of visibility and accessibility to quality, Black-owned offerings. Cost Barrier: Black entrepreneurs and business owners struggle with the high costs of promotional advertising, resulting in low visibility and missed revenue opportunities. Usability Issues: Consumers and business owners seek a seamless, easy-to-use platform that connects them without the hassle of navigating multiple disconnected channels. The Solution: Closing the Gap: PressBlk offers a dedicated mobile app that connects consumers directly to Black-owned businesses, making it easier for them to find, purchase, and support Black-owned products and services globally. No other app provides the same level of accessibility and convenience for this specific market. Cost Savings: By reducing the need for expensive advertising, PressBlk allows Black business owners to market their products more effectively and affordably, ensuring greater visibility and reach. Target Audience: A platform designed for all consumers in search of Black-owned goods and services, PressBlk creates a marketplace that elevates Black entrepreneurship by making their products easily discoverable and accessible. Ease of Use: PressBlk provides an intuitive, user-friendly app that simplifies the connection between businesses and consumers, fostering growth and empowering Black entrepreneurs through culturally conscious commerce. -------------------------- Max, Attached are the CV/ Resume of my advisory board. MR. Keenan Coningland, Mr. Curtis R. Bowers, Dr. Allen W. Toles. Executive team myself, Sky, Cameron and yourself. You can edit for spacing. Also, you will find a redlined critique from my investor. Please add specific information on pricing to the consumer (4.999 per month with a 10% discount if paid yearly) and business with the same option with Platinum receiving 15% discount, Gold receiving 10% discount, and Silver receiving 5% discount. After the initial free trial period and/or conjunction with our Beta testers. Our goal in the first year (Phase 1) is to reach 500k consumers and 20K business and entrepreneurs. Year two and three (Phase 2) our goal is to reach 3M consumers and 150K business. Ultimately, we would like to sustain 5M consumers on the platform annually. Funding Needed 500K-1M for Completion of APP (MVP2) and Beta Testing Marketing, Social Media, TV, Radio in targeted urban markets. Hiring Staff, COO and CFO, Sales team, as well IT/AI Support team. Facility Lease for headquarters. Regards, Michael		Highest		Backlog	Unresolved	--	Request_to_team	CreatedSeptember 18, 2024 2:51 AM UpdatedJuly 28, 2025 1:36 PM

Create New Close

Tasks by Label

Key	Subject	Request	Attachments	Priority	Comments	Status	Resolution	Current Environment	Labels	Dates

Close

Access Credentials

Nothing found.

For addition information, please contact customer support.

Feedback