Mevrik AX Growth
Launch & GTM Programme
Complete category launch plan covering engineering, product, website, content, sales, community, legal, analytics, and post-launch GTM momentum. Three-wave launch sequence: AX Growth → Shopify → Pulse. Status, priority, and checklist state below is shared and live — anyone with this link can update it.
Executive Summary
Engineering Phase 1 (SaaS backbone, Shopify integration, sign-up wizard, billing) completed ~June 25, 2026. Phase 2 (Workflows, Routing, Trace, Sandbox, Auto QA, BYOLLM) completes ~August 25, 2026. The engineering foundation is ahead of GTM readiness. This programme closes that gap in seven weeks. The target September 22 launch is achievable — but requires immediate action on website, legal, pricing page, demo environment, and sales enablement in parallel with Phase 2 engineering completion.
Top 10 Immediate Priorities (Week of Aug 2)
- Submit Shopify App Store listing now — 2–4 week review SLA means submitting by Aug 9 is the only path to an Oct 6–20 approval
- Lock canonical pricing numbers — Pricing Engineering v1.0 is locked structurally; founder must confirm actual GBP amounts before Stripe and website build proceed
- Commission Privacy Policy, ToS, and DPA — Legal docs are P0 launch blockers; engage solicitor this week
- Begin website core pages build — Home, Product, Enterprise, Pricing are the conversion core; target staging by Sep 1
- Assign GTM Head as programme lead — One person must own the weekly launch checklist and chase every open item
- Expand beta to 5–10 customers — Need proof + testimonials + case studies before launch
- Audit old website blog for SEO — Map all existing blog URLs, inbound links, and rankings before migration
- Set up Stripe Checkout in test mode — Pricing page build cannot complete without a working Stripe integration
- Commission 60-second explainer video — Video production has 3–5 week lead time; must brief studio immediately
- Update social media bios with locked category — Category Migration Spec is locked; update all profiles to "Agentic AI Customer Operations Platform"
Development Activity
mevriklabs/ax-platform · via GitHubReal-time engineering pulse from GitHub. This section is read-only and is never written back to the shared tracker below.
ConnectingPull Requests
| PR | Title | Author | Branch | Updated |
|---|---|---|---|---|
| Loading… | ||||
Issues
| Issue | Title | Labels | Author | Updated |
|---|---|---|---|---|
| Loading… | ||||
Recent Commits
Launch Sequence Assessment & Recommendation
Proposed Sequence (as submitted)
Wave 1 (AX Growth) is achievable in ~7 weeks. The 2-week gap to Wave 2 (Shopify) is too short because Shopify App Store review takes 2–4 weeks minimum. The 2-week gap to Wave 3 (Pulse) is too short for marketing bandwidth and customer base development. Recommended: extend gaps to 4 weeks each, and begin Shopify App Store submission immediately (before AX Growth launches).
Recommended Sequence
Wave 1: AX Growth — Sep 22, 2026. Wave 2: Mevrik for Shopify — Oct 20, 2026 (+4 weeks). Wave 3: Mevrik Pulse — Nov 17, 2026 (+4 weeks). Submit Shopify App Store listing by Aug 9 to achieve App Store approval by ~Sep 8, giving two weeks of buffer before the Oct 20 launch.
| Wave | Product | Proposed Date | Recommended Date | Gap Change | Verdict | Key Risk | Mitigation |
|---|---|---|---|---|---|---|---|
| Wave 1 | AX Growth — SaaS self-serve launch | TBD (original) | 22 Sep 2026 | — | Viable | Phase 2 engineering overrun; GTM readiness gap | 7-week pre-launch plan; parallel workstreams now |
| Wave 2 | Mevrik for Shopify — App Store listing | +2 weeks | 20 Oct 2026 (+4 weeks) | +2 weeks | Change Required | Shopify App Store review is 2–4 weeks; 2-week gap assumes instant approval | Submit App Store listing by Aug 9; review completes ~Sep 8 giving 6 weeks buffer |
| Wave 3 | Mevrik Pulse — Module/add-on launch | +4 weeks from W1 | 17 Nov 2026 (+8 weeks from W1) | +4 weeks | Change Recommended | 3 launches in 4 weeks exhausts small GTM team; Pulse needs AX Growth customers to upsell to | Allow AX Growth to stabilize; build Pulse audience from day-1 AX Growth signups |
Key Dependencies Between Waves
| Dependency | Required By | Deadline | Status | Owner |
|---|---|---|---|---|
| Shopify OAuth + App Store Partner Portal registration | Wave 2 | Aug 5 | Lead Engineer | |
| Shopify App Store listing submission (assets, copy, privacy URL) | Wave 2 | Aug 9 | Product Head + GTM Head | |
| Phase 2 complete (Workflows, Routing, Trace, Auto QA) | Wave 1 + 2 | Aug 25 | Lead Engineer | |
| Pricing numbers locked (GBP amounts confirmed by founder) | Wave 1 | Aug 4 | Prince Mojumder | |
| Legal docs (ToS, Privacy Policy, DPA) | Wave 1 | Sep 7 | HR & Admin Lead | |
| AX Growth customer base (min. 10 paying) for Pulse upsell | Wave 3 | Oct 20 | GTM Head | |
| Pulse Phase 2 readiness validation (is Pulse built in Phase 2?) | Wave 3 | Aug 25 | Lead Engineer + Product Head | |
| SOC 2 Type II observation logging active (for enterprise sales) | Wave 1 | Done | Lead Engineer |
Critical Path Analysis
Any delay to a starred (★) task directly delays the Sep 22 launch. Items without stars have up to 7 days float before they become critical. The bottleneck is legal & website: both have external dependencies (solicitor, design/dev) that must start immediately.
| Seq | Task | Duration | Start | End | Predecessor | Float | Owner |
|---|---|---|---|---|---|---|---|
| CP-01 ★ | Founder confirms GBP pricing numbers | 1d | Aug 2 | Aug 4 | — | 0d | Prince |
| CP-02 ★ | Engage solicitor for legal docs (ToS, PP, DPA) | 2d | Aug 4 | Aug 5 | CP-01 (budget sign-off) | 0d | HR Admin |
| CP-03 ★ | Legal docs drafted & reviewed | 21d | Aug 5 | Aug 26 | CP-02 | 0d | Solicitor |
| CP-04 | Phase 2 engineering completion (Workflows, Trace, Auto QA) | 23d | Aug 2 | Aug 25 | — | 7d | Lead Engineer |
| CP-05 ★ | Website core pages (Home, Product, Pricing) build starts | 1d | Aug 4 | Aug 4 | CP-01 (pricing confirmed) | 0d | Product Head |
| CP-06 ★ | Website core pages live on staging | 28d | Aug 4 | Sep 1 | CP-05 | 0d | Product Head |
| CP-07 ★ | Stripe Checkout (Pricing page) integration complete | 14d | Aug 11 | Aug 25 | CP-01 (pricing), CP-04 (billing hooks) | 7d | Lead Engineer |
| CP-08 ★ | 14-day free trial flow end-to-end working | 7d | Aug 25 | Sep 1 | CP-07 | 0d | Lead Engineer + Product |
| CP-09 ★ | Legal docs published to website | 1d | Aug 26 | Aug 26 | CP-03, CP-06 | 0d | HR Admin |
| CP-10 | Old blog SEO audit + redirect map | 7d | Aug 2 | Aug 9 | — | 14d | GTM Head |
| CP-11 | Blog migration (all posts + 301 redirects) | 14d | Aug 9 | Aug 23 | CP-10 | 14d | Product Head |
| CP-12 ★ | Website full QA, performance, accessibility | 7d | Sep 8 | Sep 14 | CP-06, CP-08, CP-09 | 0d | QA + Product Head |
| CP-13 ★ | Load test pass (800ms first token, 1000 concurrent) | 3d | Sep 8 | Sep 11 | CP-04 | 3d | Lead Engineer |
| CP-14 ★ | Demo environment seeded + demo script trained | 7d | Sep 8 | Sep 14 | CP-04 | 0d | GTM Head |
| CP-15 ★ | Analytics instrumentation complete (GA4 + PostHog) | 5d | Sep 8 | Sep 14 | CP-12 | 0d | Lead Engineer + GTM |
| CP-16 ★ | Cookie consent + GDPR banner live | 2d | Sep 14 | Sep 15 | CP-12, CP-09 | 0d | Lead Engineer |
| CP-17 ★ | DNS switch rehearsal (staging → prod) | 1d | Sep 16 | Sep 16 | CP-12 | 0d | Lead Engineer |
| CP-18 ★ | Go-live sign-off meeting (all department heads) | 1d | Sep 19 | Sep 19 | All CP-0X | 0d | Prince Mojumder |
| CP-19 ★ | AX Growth public launch | 1d | Sep 22 | Sep 22 | CP-18 | 0d | Full team |
| ID | Task Name | Pri | Status | Start | End | Owner | Support | Key Dependencies | Next Action |
|---|---|---|---|---|---|---|---|---|---|
| ENG-01 | Phase 2 Module Completion | Jun 25 | Aug 25 | Lead Engineer | Full eng team (7) | Phase 1 done ✓ | Weekly status check; flag any Phase 2 slippage by Aug 11 | ||
DeliverablesWorkflows (Goal Engine v1), Routing engine, Trace (token-level audit), Sandbox, Auto QA, BYOLLM, Zendesk migration tool, first AX Enterprise customer ready path
Success CriteriaPhase 2 acceptance bar met: first AX Enterprise customer path live; 5 SaaS customers in production; all Phase 2 modules passing CI
Risk / MitigationPhase 2 overrun pushes launch. Mitigation: scope-cut Zendesk tool to Phase 3 if needed; keep Routing + Workflows as hard P0 for launch
| |||||||||
| ENG-02 | Mobile Apps — Flutter QA & App Store Submission | Aug 25 | Sep 14 | ax-mobile team | ax-qa team | ENG-01 (Phase 2 complete); App Store Dev accounts active | Confirm Apple Dev + Google Play accounts active; assign QA owner for mobile | ||
DeliverablesMevrik Business (iOS + Android) submitted to App Store / Play Store. Mevrik Business Desktop tested. WhatsApp-grade chat performance validated on device.
Success CriteriaApp Store + Play Store submission complete by Sep 14. Review SLA: Apple 1–3 days, Google 1–7 days. Target approval by Sep 19 (launch week).
Risk / MitigationApple App Store rejection delay. Mitigation: launch announcement can proceed without app store listing; include in launch day if approved, otherwise announce "coming to App Store"
| |||||||||
| ENG-03 | End-to-End Signup Flow Performance | Aug 11 | Sep 1 | Lead Engineer | ax-frontend, ax-qa | ENG-01; BIL-02 (Stripe integration) | Run full E2E timing daily from Aug 25; target under 5 min from landing page to first AI conversation | ||
DeliverablesVerified end-to-end time from signup start to first AI conversation ≤5 minutes. 5-step wizard + Aura chat mode both paths tested.
Success CriteriaPhase 1 acceptance bar: SaaS signup → first conversation <5 min. Verified on prod infra, not just staging.
Risk / MitigationKnowledge crawl + first conversation takes longer on cold start. Mitigation: seed demo templates so first conversation works immediately even without crawl completion
| |||||||||
| ENG-04 | Load Testing & Performance Validation | Sep 1 | Sep 11 | Lead Engineer | DevOps Engineer | ENG-01; Production EKS cluster stable | Finalise load test scripts (k6 or Locust); schedule test window Sep 1–5 on prod-mirror | ||
DeliverablesLoad test report: first token <800ms at 1000 concurrent; full response <3s p95; no errors at 500 concurrent sustained 30min; auto-scaling validated
Success CriteriaAll four performance bars met per Blueprint v2.3.0 §4.2 Week 4 acceptance criteria. Report signed off by Lead Engineer.
Risk / Mitigationpgvector HNSW queries slow under concurrent load. Mitigation: pre-warm index; add read replica; set query timeout + graceful degradation
| |||||||||
| ENG-05 | Production Infrastructure Hardening | Aug 2 | Aug 25 | DevOps Engineer | Lead Engineer | ENG-01 | Review K8s resource limits, HPA configs, PDB policies; confirm multi-AZ Postgres | ||
DeliverablesEKS prod cluster with HPA, PDB, multi-AZ RDS Postgres, Redis Sentinel, NATS JetStream cluster, S3 versioned buckets, Loki + Grafana + Sentry operational
Success Criteria99.9% uptime SLA achievable; single node failure causes no customer-visible outage; RTO <15min, RPO <1hr
Risk / MitigationAzure-to-AWS migration complexity (primary = Azure, secondary = AWS per memory). Clarify primary prod cloud with Lead Engineer before Sep 1.
| |||||||||
| ENG-06 | Disaster Recovery & Backup Validation | Aug 25 | Sep 7 | DevOps Engineer | Lead Engineer | ENG-05 | Document DR runbook; run one full backup+restore drill; confirm RTO/RPO met | ||
DeliverablesDR runbook (written); backup restore drill completed and timed; RTO validated <15min; Postgres PITR confirmed; S3 cross-region replication active
Success CriteriaFull restore from backup completed in <15 minutes. Drill witnessed and signed off by Lead Engineer.
RiskUndocumented DR procedures create launch-day risk if any incident occurs in first 48 hours
| |||||||||
| ENG-07 | Kill Switch — All Four Scopes | Jun 25 | Jun 25 | Lead Engineer | — | Phase 1 done ✓ | Verify kill switch works at workspace and tenant level on production; document procedure | ||
| ENG-08 | Widget CDN & Embed Script Distribution | Aug 25 | Sep 7 | Lead Engineer | ax-frontend | ENG-05; Phase 2 widget build complete | Configure CloudFront CDN for widget JS; set embed documentation ready for onboarding | ||
| ENG-09 | Status Page & Incident Response Setup | Sep 7 | Sep 14 | DevOps Engineer | Lead Engineer | ENG-05 | Set up status.mevrik.com (BetterUptime or Instatus); configure PagerDuty on-call rotation for launch week | ||
| ENG-10 | agent.mevrik.ai URL + QR Code System | Jun 25 | Jun 25 | Lead Engineer | — | Phase 1 done ✓ | Verify QR codes generate correctly for new workspaces; test 5 fresh signups | ||
| ID | Task Name | Pri | Status | Start | End | Owner | Support | Key Dependencies | Next Action |
|---|---|---|---|---|---|---|---|---|---|
| QA-01 | Automated Eval Suite (100 conversations, CI gate) | Jun 25 | Aug 25 | ax-qa team | Lead Engineer | Phase 1 done (eval suite started) ✓ | Expand to 200 replay conversations covering edge cases; target 0 P0 regressions on CI | ||
Deliverables200-conversation eval suite; CI gate blocking deploy on regression; coverage: Support, Sales, Lead-gen role bundles; edge: multilingual, long context, tool calls
Success CriteriaZero P0 regressions on CI green. Eval run time <10 min in pipeline.
RiskEval suite only covers known scenarios; real customer conversations will expose novel failures. Mitigation: shadow mode on first 100 real conversations post-launch
| |||||||||
| QA-02 | Full End-to-End User Journey Testing | Sep 1 | Sep 14 | Product Head | ax-qa, GTM Head | ENG-03; WEB-01 (website on staging) | Write test scripts covering: discovery → pricing → trial signup → onboarding wizard → first AI conversation → upgrade → support ticket | ||
DeliverablesQA report covering 12 full user journeys (5 SME personas × 2 paths: Aura chat mode + wizard). All P0/P1 bugs resolved before Sep 19 sign-off.
Success CriteriaZero P0 bugs. P1 bugs either resolved or have documented workaround. CSAT score from 5 test users ≥4.0/5.0.
RemarksInclude GTM Head in test runs — they will catch positioning/copy issues that pure technical QA misses
| |||||||||
| QA-03 | Cross-Browser & Device Testing | Sep 1 | Sep 14 | ax-frontend | ax-qa | WEB-01 | Test: Chrome/Safari/Firefox/Edge; iOS Safari; Android Chrome; widget embed on third-party site | ||
| QA-04 | Accessibility Testing (WCAG 2.1 AA) | Sep 7 | Sep 14 | ax-frontend | ax-qa | WEB-01 | Run axe-core on all website pages; confirm widget is keyboard-navigable and screen-reader compatible | ||
| QA-05 | Beta Customer Programme — Expand to 10 | Aug 2 | Sep 7 | GTM Head | Product Head, Prince | Phase 1: 1 beta customer confirmed ✓ | Identify 9 additional beta candidates from network; brief each; target 10 active workspaces by Sep 7 | ||
Deliverables10 active beta workspaces. At least 3 Shopify merchants. At least 1 enterprise-size business. Beta feedback log. 2+ testimonial quotes secured for launch.
Success Criteria10 workspaces with ≥50 conversations each. NPS ≥7. At least 2 customers willing to be named as launch references.
RiskBeta customers find critical bugs that require engineering time to fix, delaying launch. Mitigation: weekly beta bug triage; P0 fix SLA = 48 hours
| |||||||||
| QA-06 | Onboarding Flow QA (Wizard + Aura Mode) | Aug 25 | Sep 7 | Product Head | ax-qa | ENG-03 | Test both onboarding paths for 5 different business types; measure time to first AI response per path | ||
| QA-07 | P1 Bug Backlog Clearance | Sep 8 | Sep 19 | Lead Engineer | Full eng team | QA-01, QA-02, QA-05 | Freeze feature work Sep 8; triage all open bugs; P0 resolved, P1 resolved or deferred with approval | ||
| QA-08 | Security Penetration Test (external) | Aug 25 | Sep 14 | Lead Engineer | HR Admin (vendor) | ENG-05 | Engage pen-test vendor this week; scope: OWASP Top 10 + auth + tenant isolation + billing; report needed by Sep 14 | ||
DeliverablesExternal pen test report (OWASP Top 10, authentication, multi-tenancy isolation, billing, API). All critical/high findings resolved. Report available on request for enterprise buyers.
Success CriteriaZero critical/high severity findings unresolved at launch. Medium findings documented with remediation timeline.
RiskFinding critical vulnerability close to launch could delay or embarrass. Mitigation: internal security review first (Lead Engineer); external pen test on pre-hardened surface
| |||||||||
Mevrik processes customer conversation data and PII. Operating without a Privacy Policy and Terms of Service is a regulatory violation under UK GDPR. Engage a solicitor this week. Estimated cost: £1,500–£3,000 for the full pack. Budget must be approved immediately.
| ID | Task Name | Pri | Status | Start | End | Owner | Support | Dependencies | Next Action |
|---|---|---|---|---|---|---|---|---|---|
| SEC-01 | SOC 2 Type II — Observation Period Active | Jun 25 | Ongoing | Lead Engineer | — | Phase 1 done ✓ | Confirm observation period logging is producing evidence artefacts; review controls monthly | ||
DeliverablesContinuous controls logging. SOC 2 preparation in progress. External statement: "SOC 2 Type II ready — observation period underway." Do NOT claim certified.
Success Criteria6+ months of clean controls evidence by end of Phase 3. Audit ready by Dec 2026.
RemarksThis is a live competitive differentiator — enterprise buyers in financial services and government require this. Statement must appear on Security page and in sales materials.
| |||||||||
| SEC-02 | Privacy Policy (UK GDPR compliant) | Aug 4 | Aug 26 | HR Admin Lead | Solicitor | Solicitor engaged | Brief solicitor Aug 4; must cover: data categories, legal basis, retention, third-party processors (Stripe, Claude API, SendGrid), cross-border transfers, data subject rights | ||
DeliverablesUK GDPR-compliant Privacy Policy covering: data controller identity (Mevrik UK), data categories (conversation data, PII, usage data), lawful bases, retention schedules, third-party processors, data subject rights process
Success CriteriaReviewed by solicitor; ICO-compliant; includes cookie consent section; published at /privacy by Aug 26
RiskClaude API (Anthropic) is a data processor — ensure DPA with Anthropic is referenced; confirm Anthropic's DPA covers UK GDPR
| |||||||||
| SEC-03 | Terms of Service | Aug 4 | Aug 26 | HR Admin Lead | Solicitor | Same solicitor as SEC-02 | Cover: acceptable use, AI output disclaimers, liability limitations, IP ownership, subscription terms, termination, governing law (England & Wales) | ||
| SEC-04 | Data Processing Agreement (DPA) Template | Aug 4 | Aug 26 | HR Admin Lead | Solicitor | SEC-02 | Required for enterprise customers and for Mevrik's own sub-processors. Include standard contractual clauses for cross-border transfers. | ||
| SEC-05 | Cookie Policy + Consent Banner | Sep 1 | Sep 15 | Lead Engineer | HR Admin, Product Head | SEC-02; WEB-01 (website on staging) | Implement privacy-first consent banner (decline non-essential by default); integrate with GA4 consent mode; publish cookie policy at /cookies | ||
DeliverablesGDPR/PECR compliant consent banner. Three categories: Essential (always on), Analytics (opt-in), Marketing (opt-in). Preference stored in local storage. GA4 respects consent mode.
Success CriteriaPasses Cookiebot or similar scanner. ICO guidance compliant. Analytics data only collected on consent.
RiskIf analytics fires before consent, ICO can issue enforcement notice. No analytics data before consent is accepted.
| |||||||||
| SEC-06 | UK ICO Registration | Aug 4 | Aug 11 | HR Admin Lead | Prince Mojumder | — | Register as data controller with ICO (ico.org.uk/register) — mandatory for UK companies processing personal data. Fee: £40–£60/yr. Provide ICO registration number on Privacy Policy. | ||
| SEC-07 | Sub-Processor Register | Aug 11 | Aug 25 | HR Admin Lead | Lead Engineer | SEC-02 | Document all third-party data processors: Anthropic (Claude API), Stripe, SendGrid/Resend, OpenTelemetry sink, Sentry, AWS/Azure, Loki. Confirm each has a DPA with Mevrik. | ||
| SEC-08 | Vulnerability Disclosure Policy | Aug 25 | Sep 7 | Lead Engineer | — | QA-08 | Publish /security page with responsible disclosure process, PGP key, response SLA, and out-of-scope items | ||
| SEC-09 | Acceptable Use Policy (AI-specific) | Aug 11 | Aug 26 | HR Admin Lead | Solicitor, Lead Engineer | SEC-03 | Cover: prohibited uses of AI agents (misinformation, illegal activities, high-risk AI applications), human oversight requirements, agent guardrails compliance | ||
| SEC-10 | EU AI Act Awareness Review | Sep 1 | Sep 14 | HR Admin Lead | Solicitor | SEC-02 | Brief legal review of EU AI Act applicability to Mevrik AX (general purpose AI system / provider obligations); document position for enterprise sales in regulated markets | ||
Pricing Engineering v1.0 is structurally locked (conversation slider, £49–£499 range, GBP billing currency, annual default, 20% annual discount). The exact amounts per stop are still marked "illustrative." Founder must confirm actuals before Stripe, website, and pricing page build can proceed. This is a Day 0 blocker for at least 8 downstream tasks.
| ID | Task Name | Pri | Status | Start | End | Owner | Support | Dependencies | Next Action |
|---|---|---|---|---|---|---|---|---|---|
| BIL-01 | Canonical Pricing Locked (founder sign-off) | Aug 2 | Aug 4 | Prince Mojumder | GTM Head | — | Prince to confirm GBP amounts for each slider stop; GTM Head to sense-check vs. competitive benchmark | ||
DeliverablesLocked pricing table: 6 stops × (annual GBP/mo + monthly GBP/mo). Add-on prices (Surveys, Voice AI, Vitals) if ready.
Success CriteriaConfirmed by founder in writing (Slack/email). Handed to Lead Engineer for Stripe setup and Product Head for website.
ContextPricing Engineering v1.0 structure: stop 1 = 500 conv/mo ~£49 annual; stop 6 = 5,000 conv/mo ~£399 annual. Confirm or adjust these figures.
| |||||||||
| BIL-02 | Stripe Checkout Integration (GBP, slider) | Aug 5 | Aug 25 | Lead Engineer | ax-backend | BIL-01 (pricing locked); ENG-01 | Configure Stripe products + prices (6 stops × 2 terms = 12 price IDs). Set up Stripe Checkout session. Test all 12 paths in test mode by Aug 18. | ||
DeliverablesStripe Checkout working for all 6 stops × monthly/annual. Webhook handlers: checkout.session.completed, invoice.paid, customer.subscription.updated/deleted, invoice.payment_failed. GBP currency only.
Success CriteriaFull checkout → subscription → workspace provisioning flow in <60 seconds. Tested with Stripe test cards including 3DS and failed payment. Annual billing default confirmed.
RemarksPer Pricing Engineering v1.0: annual billing is the DEFAULT UI state. Both annual and monthly prices visible simultaneously — never hide monthly behind a toggle.
| |||||||||
| BIL-03 | 14-Day Free Trial Flow | Aug 25 | Sep 7 | Lead Engineer | Product Head, GTM Head | BIL-02; ENG-03 | Build trial state in workspace: trial_active, trial_expired, trial_converted. Configure trial-start/trial-end email triggers. Trial ends → prompt to add card. | ||
DeliverablesTrial state machine: 14-day free trial, 500-conversation cap, card not required at signup. In-app trial countdown banner. Trial expiry → soft paywall with upgrade prompt. Trial-to-paid conversion tracked.
Success CriteriaTrial signup → first conversation without card. Expiry grace period of 24h with reminder. Conversion prompt converts ≥15% of trials in first 30 days post-launch.
RiskTrial abuse (repeated free trials). Mitigation: rate-limit by email domain + IP on trial creation.
| |||||||||
| BIL-04 | Pricing Page Build (website) | Aug 5 | Sep 1 | Product Head | ax-frontend, GTM Head | BIL-01; WEB-01 | Build interactive conversation slider; AX Growth plan card; AX Enterprise "Talk to sales" card; FAQSchema markup; billable-conversation definition explained | ||
DeliverablesPer Website PRD §20.3: Primary CTA = Start free (AX Growth); Talk to sales (AX Enterprise). FAQ with JSON-LD. Billable-conversation definition with examples. No per-resolution language.
Success CriteriaPricing page loads in <1.5s. Slider interactive. Annual prices shown by default. Add-ons section. Enterprise band visible but no self-serve prices.
RemarksNever use "per resolution" language — Mevrik's competitive differentiation is per-conversation pricing. This must be explicit and explained clearly.
| |||||||||
| BIL-05 | Usage Alerts & Overage Handling | Aug 25 | Sep 7 | Lead Engineer | ax-backend | BIL-02; ENG-01 | 85% usage alert email, 100% limit email (soft-limit: conversations paused with explanation), upgrade CTA in-app | ||
| BIL-06 | Invoice & Receipt Generation | Aug 25 | Sep 7 | Lead Engineer | — | BIL-02 | Stripe handles invoicing; configure: company name (Mevrik Ltd), VAT number (if applicable), UK address, GBP currency. Confirm VAT registration status with HR Admin. | ||
| BIL-07 | Demo Booking Integration (Pricing Page) | Sep 1 | Sep 14 | GTM Head | Product Head | WEB-01; BIL-04 | Embed Cal.com or Calendly on /pricing and /demo; connect to HubSpot; tag demo requests in CRM pipeline; send confirmation email with demo prep doc | ||
| ID | Task Name | Pri | Status | Start | End | Owner | Support | Dependencies | Next Action |
|---|---|---|---|---|---|---|---|---|---|
| WEB-01 | Core Pages Build (Home, Product, Enterprise, Pricing) | Aug 4 | Sep 1 | Product Head | ax-frontend, GTM Head | BIL-01; CATEGORY_MIGRATION_SPEC locked ✓ | Apply locked category ("Agentic AI Customer Operations Platform") and tagline ("AI runs your customer operations. Humans supervise what matters.") throughout. Build order: Home → Product → Enterprise → Pricing. | ||
Deliverables4 core pages live on staging by Sep 1. Homepage: 16 chapters per Website Experience Bible. Category descriptor, tagline, all locked naming conventions applied per Category Migration Spec.
Success CriteriaAll locked naming applied (zero "Agentic eXperience OS", zero "chatbot/bot", zero "AI-powered"). Core Web Vitals: LCP <2.5s, FID <100ms, CLS <0.1. SEO schema implemented.
RemarksPer Website PRD §20.6 build order: conversion core first. Do not delay core pages waiting for secondary pages. Secondary pages (Platform, Solutions, Industries) can ship post-launch.
| |||||||||
| WEB-02 | Secondary Pages (Platform, Solutions, Security, About, Contact) | Sep 1 | Sep 19 | Product Head | ax-frontend | WEB-01 | Platform page: AX Engine architecture. Security page: SOC 2 Type II observation statement, security controls. About: team, mission, Grameenphone proof. Contact: demo booking + sales email. | ||
| WEB-03 | Industry & Solutions Pages | Sep 19 | Oct 6 | GTM Head | Product Head | WEB-01 | Priority: Shopify (SME), Telecom (Grameenphone anchor), Financial Services. Build 3 before launch; remaining post-launch. | ||
| WEB-04 | Blog Migration (SEO-safe, 301 redirects) | Aug 2 | Sep 7 | GTM Head | Product Head, Lead Engineer | Old website access; new website staging | Step 1 (Aug 2–9): audit all existing blog URLs, inbound backlinks, search rankings, metadata. Step 2 (Aug 9–23): migrate content to new CMS with identical slugs or 301 redirects. Step 3 (Aug 23–Sep 7): verify redirects, test with Screaming Frog. | ||
DeliverablesFull URL map: old URL → new URL + redirect type. All existing posts live on new website. 301 redirects for all changed URLs. OG metadata preserved. Canonical tags correct. Sitemap updated. GSC property updated.
Success CriteriaZero 404s for existing indexed URLs post-migration. GSC reports no coverage errors 7 days post-launch. No ranking drop >20% within 30 days (monitor Semrush/Ahrefs).
Risk — HIGHIncorrect or missing redirects will destroy SEO equity built on existing blog. This is one of the highest-risk GTM tasks. Assign a dedicated person and use Screaming Frog to crawl both sites before and after.
| |||||||||
| WEB-05 | SEO Technical Setup (Schema, sitemap, meta) | Aug 25 | Sep 7 | Product Head | GTM Head | WEB-01 | Implement per Website PRD §20.4: Organization schema (Home), Product schema (Product/Enterprise), FAQPage schema (Pricing), BreadcrumbList (all pages). Submit sitemap to Google Search Console. Verify robots.txt allows all key pages. | ||
| WEB-06 | OG Cards, Twitter Cards & Favicon Suite | Aug 25 | Sep 7 | Product Head | Design | Logo rebrand decision; WEB-01 | Create OG image (1200×627) per Website PRD for each key page. Favicon suite: 16×16, 32×32, 180×180 (Apple), SVG. Twitter card "summary_large_image" for all pages. | ||
| WEB-07 | Core Web Vitals Optimization | Sep 1 | Sep 14 | ax-frontend | Lead Engineer | WEB-01 | Run Lighthouse on all core pages. Target: LCP <2.5s, FID <100ms, CLS <0.1. Optimize: images (WebP, lazy load), fonts (FOUT prevention), JS bundle splitting. | ||
| WEB-08 | Google Search Console Setup & Verification | Aug 25 | Sep 1 | GTM Head | Lead Engineer | WEB-01 (domain confirmed) | Verify mevrik.com in GSC. Add sitemap. Set up GSC for mevrik.ai separately. Configure crawl budget settings. | ||
| WEB-09 | Demo Booking Page (/demo) | Sep 1 | Sep 14 | GTM Head | Product Head | WEB-01; BIL-07 (Cal.com/Calendly set up) | Build /demo page: "Book a 30-minute demo" + embedded calendar + demo confirmation email + HubSpot CRM tracking. Include ROI teaser and Grameenphone proof point. | ||
| WEB-10 | Analytics Instrumentation (GA4 + PostHog) | Sep 1 | Sep 14 | Lead Engineer | GTM Head | WEB-01; SEC-05 (consent banner) | GA4: pageviews, scroll depth, form submissions, CTA clicks, checkout starts, trial signups. PostHog: product analytics — signup funnel, onboarding steps, feature adoption. | ||
| WEB-11 | DNS Switch & SSL Go-Live | Sep 16 | Sep 22 | Lead Engineer | DevOps Engineer | All WEB tasks complete; QA-02 signed off | Rehearse DNS switch Sep 16. TTL reduced to 300s 24h before launch. Go-live Sep 22 at planned time. Monitor DNS propagation globally with dnschecker.org. | ||
| WEB-12 | Comparison Pages (/vs/Fin, /vs/Intercom, /vs/Zendesk) | Sep 22 | Oct 6 | GTM Head | Product Head | WEB-01 (post-launch) | Per Website PRD §13: scrupulously fair comparison tables; include "when to choose them" section for credibility. Priority: vs. Fin/Intercom (highest search volume). | ||
| WEB-13 | mevrik.ai — AI Agent Product Landing Experience | Oct 6 | Oct 20 | Product Head | GTM Head | WEB-01 (post-launch) | Currently redirecting to mevrik.com. Build dedicated AI agent product landing for mevrik.ai — targeted at Shopify/ecommerce audience. Coincides with Wave 2 (Shopify) launch. | ||
Mevrik's own website and platform must use its own AI agent. This is both a proof point ("production-proven") and a lead-gen engine — every visitor to mevrik.com gets to experience the product before buying. The agent should be configured with Support, Sales, and Lead-gen role bundles, and Aura as the concierge overlay. This is a live demo available 24/7.
| ID | Task Name | Pri | Status | Start | End | Owner | Support | Dependencies | Next Action |
|---|---|---|---|---|---|---|---|---|---|
| AGA-01 | Mevrik Own-Brand Workspace Setup | Aug 25 | Sep 7 | Product Head | GTM Head, Lead Engineer | ENG-01; WEB-01 | Create Mevrik's own AX Growth workspace. Crawl mevrik.com. Upload: product docs, pricing FAQ, Grameenphone case study, onboarding guide. Role: Support + Sales + Lead-gen. | ||
DeliverablesLive Mevrik AX workspace with full knowledge base crawled. Greeting configured. All three role bundles active. Aura overlay enabled.
Success CriteriaAgent answers 95%+ of pre-defined test questions correctly. Handoff to demo booking working. Captures lead details (name, email, business type) before handoff.
Remarks"Mevrik on Mevrik" is a category proof point. Prince should be able to demo the website agent live in any sales conversation.
| |||||||||
| AGA-02 | Agent Knowledge Base & QA (100 test conversations) | Sep 1 | Sep 14 | Product Head | GTM Head | AGA-01 | Build 100 test QA scenarios: product questions, pricing queries, Shopify integration, demo requests, "how does it work", competitor comparisons, "can it do X". Target: 90%+ pass rate. | ||
| AGA-03 | Agent Brand Voice & Guardrails | Sep 1 | Sep 7 | GTM Head | Product Head | AGA-01 | Configure: tone (confident, precise, Stripe-documentation register — no hype), forbidden phrases (bot, chatbot, AI-powered, leading, best-in-class), competitor mention handling ("happy to compare"). | ||
| AGA-04 | Demo Booking Handoff Flow | Sep 7 | Sep 14 | GTM Head | Lead Engineer | AGA-01; BIL-07 (Cal.com configured) | Agent qualification flow: collect name, company, business type, conversation volume estimate → qualify → offer demo booking link OR self-serve trial link | ||
| AGA-05 | Agent Analytics Dashboard | Sep 14 | Sep 22 | GTM Head | Lead Engineer | AGA-01; ANL-01 | Track: total conversations, resolution rate, demo requests generated, lead captures, escalations. Daily report in HubSpot or Slack via n8n automation. | ||
| AGA-06 | In-App Aura Co-Pilot (onboarding assist) | Jun 25 | Sep 1 | Lead Engineer | Product Head | ENG-01 (Aura scaffold in Phase 1) | Confirm Aura overlay is active in the platform console. Validate onboarding wizard Aura chat mode end-to-end. Aura should suggest next steps, offer help, and celebrate first conversation milestone. | ||
The 60-second explainer and product demo video are the highest-ROI launch assets. They cannot be produced in a week. Commission the explainer video studio immediately. The product demo can be self-produced using Higgsfield + screen recording, but still needs scripting and editing time.
| ID | Task Name | Pri | Status | Start | End | Owner | Support | Dependencies | Next Action |
|---|---|---|---|---|---|---|---|---|---|
| VID-01 | 60-Second Brand Explainer Video | Aug 2 | Sep 7 | GTM Head | Prince Mojumder, Design/Studio | Logo rebrand direction; Category Migration Spec ✓ | URGENT: brief animation studio this week. Script: "AI runs your customer operations. Humans supervise what matters." Brand: Ink/White/Indigo. Tone: Stripe-documentary register. No talking heads. | ||
Deliverables60-second animated explainer: the before (traditional CX) → the shift (agentic) → Mevrik AX. Brand-system locked (Indigo, Ink, Inter typography). Voice-over: measured, confident.
Success CriteriaLive on website hero and YouTube by Sep 14 (one week before launch). Shared across all social channels launch week.
RemarksUse Higgsfield nano_banana_pro for any motion graphics elements. If budget constrains, produce in-house with Higgsfield video tools + CapCut/Premiere.
| |||||||||
| VID-02 | Product Demo Video (2–3 min walkthrough) | Aug 25 | Sep 14 | Product Head | GTM Head, Lead Engineer | ENG-03 (product stable on staging) | Script: problem → Mevrik AX solution → live demo (signup in 5 min → first AI conversation). Record on staging. Edit with screen recording tool. Post to YouTube + website /demo page. | ||
| VID-03 | Onboarding Video Series (3 × 60s) | Sep 7 | Sep 22 | Product Head | GTM Head | ENG-03; QA-06 | Video 1: Connecting your knowledge base. Video 2: Configuring your first AI agent. Video 3: Going live on your website. Screencasts with voice-over. Embed in product onboarding checklist. | ||
| VID-04 | Founder Vision Video (2 min) | Sep 7 | Sep 19 | Prince Mojumder | GTM Head (scripting) | — | Prince on-camera: "Why we built this, what Era 3 means, why now." 2 minutes. Professional but not over-produced. Use for LinkedIn personal launch post and /about page. | ||
| VID-05 | Social Short-Form Cuts (15s, 30s) | Sep 14 | Sep 22 | GTM Head | — | VID-01; VID-02 | Cut 15s and 30s versions from the explainer and demo videos. Format for: LinkedIn (landscape), Instagram Reels (9:16), X (landscape). Use for launch week social campaign. | ||
| VID-06 | Grameenphone Case Study Video (optional, Phase 3) | Oct 20 | Nov 17 | GTM Head | Prince, Grameenphone contact | Post-launch; Grameenphone approval | A produced customer story video featuring Grameenphone. This is the enterprise anchor proof point. 2–3 minutes. Professional production budget required. | ||
| ID | Task Name | Pri | Status | Start | End | Owner | Support | Dependencies | Next Action |
|---|---|---|---|---|---|---|---|---|---|
| SOC-01 | All Social Bios Updated (locked category) | Aug 2 | Aug 9 | GTM Head | — | Category Migration Spec locked ✓ | Update all profiles immediately: LinkedIn Company, X/Twitter, Instagram, Facebook, YouTube. Bio: "The Agentic AI Customer Operations Platform. AI runs your customer operations. Humans supervise what matters. mevrik.com" | ||
PlatformsLinkedIn Company Page · X/Twitter @mevrikAX · Instagram Business · Facebook Page · YouTube Channel · Prince's personal LinkedIn · Team LinkedIn profiles
Success CriteriaAll bios use locked category descriptor. Cover images updated with Mevrik AX brand. Website URL: mevrik.com. All accounts verified where possible.
RemarksPrince's personal LinkedIn is disproportionately important for enterprise sales credibility. Update first. Use it to announce from a founder perspective, not just a brand account.
| |||||||||
| SOC-02 | 30-Day Social Content Calendar (Pre + Post Launch) | Aug 9 | Aug 23 | GTM Head | Prince Mojumder | SOC-01; VID-01 brief started | Adapt the existing 10-Day Launch Content Plan into a full 30-day calendar. Days 1–9: Founder POV thought leadership (agentic CX education, no product). Day 10: Launch reveal. Days 11–30: proof, feature demos, customer stories, comparative content. | ||
Deliverables30-day calendar: post per day (platforms: LinkedIn + X primary; Instagram + Facebook amplify). Each post: copy, image/video brief, hashtags, CTA, posting time. Batched and scheduled via Postiz or Hypefury.
Success CriteriaCalendar approved by Prince by Aug 23. First 10 posts produced and ready to schedule by Sep 8. All launch-day posts ready Sep 19.
RemarksPer 10-Day Plan: Days 1–9 must read as genuine Agentic CX education — no product mentions. Mevrik AX is only named on Day 10. This is the discipline that builds pre-launch anticipation.
| |||||||||
| SOC-03 | YouTube Channel Setup & First Videos | Sep 7 | Sep 22 | GTM Head | Product Head | VID-01; VID-02 | Brand YouTube channel: channel art, about section, links to mevrik.com. Upload: explainer video, product demo. Create playlists: "What is Mevrik AX", "Getting Started", "Customer Stories". | ||
| SOC-04 | LinkedIn Company Page — Full Optimisation | Aug 9 | Aug 16 | GTM Head | Prince Mojumder | SOC-01 | Company description (500 chars), specialities, logo, cover image (1128×191), custom button ("Visit website"), products section with AX Growth + AX Enterprise. Enable showcase pages if needed. | ||
| SOC-05 | Prince's Personal LinkedIn — Founder Positioning | Aug 9 | Aug 16 | Prince Mojumder | GTM Head | — | Update headline: "Founder & CEO, Mevrik — Building The Agentic AI Customer Operations Platform." Featured section: company page + launch announcement. About section: mission statement. Headshot current. | ||
| SOC-06 | Team LinkedIn Profiles Brief | Aug 16 | Aug 30 | HR Admin Lead | GTM Head | SOC-01 | Brief Lead Engineer, Product Head, GTM Head on profile updates. Ensure all show "at Mevrik" with correct title. Optional: ask team to share launch announcement on Day 10. | ||
| SOC-07 | Launch Week Social Assets (OG cards, carousel, animations) | Sep 7 | Sep 19 | GTM Head | Design | WEB-06; SOC-02 | Design 10 launch-week social images: announcement card, feature highlights (3), proof (Grameenphone), pricing teaser, quote cards (2), team. All Mevrik brand-system locked. | ||
| SOC-08 | X/Twitter Profile & Community Engagement Plan | Aug 9 | Aug 23 | GTM Head | — | SOC-01 | X is secondary channel for Mevrik. Update bio, pin launch tweet. Identify 20 accounts to engage with (AI founders, CX practitioners, SaaS commentators). 3 replies per week minimum pre-launch. | ||
| SOC-09 | Social Listening Setup (brand mentions) | Sep 14 | Sep 22 | GTM Head | — | — | Set up brand monitoring: Mevrik AX, @mevrikAX, "agentic customer operations" in: Google Alerts, Mention, or Brand24. Daily digest to GTM Head Slack channel. | ||
| ID | Task Name | Pri | Status | Start | End | Owner | Support | Dependencies | Next Action |
|---|---|---|---|---|---|---|---|---|---|
| CNT-01 | Launch Blog Post: "Introducing Mevrik AX Growth" | Sep 1 | Sep 19 | GTM Head | Prince Mojumder | WEB-01 (blog section live) | 2,000-word launch announcement. Structure: the problem (traditional CX), the shift (agentic), what Mevrik AX Growth is, how it works, Grameenphone proof, pricing, how to start. Prince byline. | ||
| CNT-02 | Grameenphone Case Study (canonical published format) | Aug 9 | Sep 7 | GTM Head | Prince Mojumder | Grameenphone metrics locked ✓ (73.7M messages, 3,400+ digital sales, 30% OPEX reduction, >50% Tier-1 reduction) | Write 1,500-word case study + 1-page PDF. Publish at /customers/grameenphone. Quote from Grameenphone contact if available. This is the enterprise anchor proof used on every sales call. | ||
| CNT-03 | Pre-Launch Blog Series (4 posts, SEO-targeted) | Aug 9 | Sep 14 | GTM Head | Prince Mojumder | WEB-04 (blog live) | Post 1: "What is Agentic AI for Customer Operations?" Post 2: "Why per-conversation pricing beats per-resolution." Post 3: "5 signs you've outgrown your helpdesk." Post 4: "How to measure AI agent ROI." Publish weekly from Aug 23. | ||
| CNT-04 | Press Release | Sep 7 | Sep 19 | GTM Head | Prince Mojumder | — | Draft 600-word press release. Newswire distribution (PR Newswire / PRWeb) on launch day. Send to 10 targeted journalists at: TechCrunch, VentureBeat, CX Today, The Drum, Tech.eu (UK focus). | ||
| CNT-05 | SEO Keyword Strategy & 12-Week Content Plan | Aug 16 | Sep 1 | GTM Head | — | WEB-05 | Primary targets: "agentic AI customer service", "AI customer operations platform", "AI agent for Shopify", "customer service AI UK", "Intercom alternative", "Fin AI alternative". Map to 12 blog posts. | ||
| CNT-06 | Newsletter: "The Agentic CX Brief" — Launch Issue | Sep 7 | Sep 22 | GTM Head | Prince Mojumder | CRM-02 (email platform); WEB-01 (subscription form) | Newsletter name: "The Agentic CX Brief." Monthly. Set up on Resend/Beehiiv/Substack. Launch issue: category intro + product launch + 3 practical tips. Subscription form on website. | ||
| CNT-07 | G2, Capterra, Software Advice Profiles | Sep 22 | Oct 6 | GTM Head | — | Post-launch; need customer reviews to populate | Claim and complete G2 profile (priority — used by enterprise buyers). Add to Capterra/Software Advice. Seed with first customer reviews post-launch. |
| ID | Task Name | Pri | Status | Start | End | Owner | Support | Dependencies | Next Action |
|---|---|---|---|---|---|---|---|---|---|
| CRM-01 | HubSpot CRM Configuration | Aug 2 | Aug 16 | GTM Head | HR Admin Lead | — | Configure pipelines: SME Self-Serve (Trial → Paid → Expansion), Enterprise (Lead → Demo → Proposal → Closed). Properties: business type, conversation volume, channel interest, Shopify (Y/N). Connect to website forms. | ||
DeliverablesTwo deal pipelines. Contact properties set up. Form-to-HubSpot connection live. Demo booking auto-creates HubSpot contact+deal. Trial signup syncs to HubSpot via webhook.
Success CriteriaEvery trial signup, demo request, and sales inquiry lands in HubSpot within 5 minutes of occurring. GTM Head gets Slack notification for new demo requests.
RemarksNote: Mevrik has its own CRM module (Mevrik AX). The internal team's primary CRM is HubSpot basic for the launch period. Migrate to Mevrik's own CRM post-stabilisation.
| |||||||||
| CRM-02 | Email Platform Setup (transactional + marketing) | Aug 2 | Aug 16 | Lead Engineer | GTM Head | DNS (SPF/DKIM/DMARC configured) | Transactional: Resend (already connected) for product emails (trial start, welcome, upgrade). Marketing: set up Resend campaigns or Beehiiv for newsletter. Ensure SPF/DKIM/DMARC configured for mevrik.com. | ||
| CRM-03 | Welcome Email Sequence (Trial Signup) | Aug 16 | Sep 7 | GTM Head | Product Head | CRM-02; BIL-03 | Email 1 (immediate): Welcome + product tour link + "your agent is ready" CTA. Email 2 (Day 2): Tips to improve agent performance. Email 3 (Day 5): "Have you gone live yet?" with quick-start checklist. Email 4 (Day 12): Trial expiry reminder + upgrade CTA. | ||
Deliverables4-email sequence automated via Resend/HubSpot. Personalised with first name and business name. Each email has clear single CTA. Unsubscribe compliant.
Success CriteriaOpen rate ≥40% (product email expected high). Click-through ≥15%. Day 12 expiry email drives ≥20% upgrade prompt opens.
RemarksTone: Stripe-documentation register. Short. Outcome-driven. No "excited to have you" fluff. Lead with what the user can DO right now.
| |||||||||
| CRM-04 | Demo Follow-Up Email Sequence | Sep 1 | Sep 14 | GTM Head | — | CRM-01; BIL-07 | Pre-demo: confirm + prep doc 24h before. Post-demo: personalised summary + next steps + Grameenphone proof within 2h. Day 3: additional question cadence. Day 7: decision-prompt if no reply. | ||
| CRM-05 | Remarketing Pixels (LinkedIn + Meta) | Sep 1 | Sep 14 | Lead Engineer | GTM Head | WEB-10; SEC-05 (consent) | LinkedIn Insight Tag: all pages + conversion events (trial signup, demo request). Meta Pixel: all pages + trial signup event. Audiences: website visitors 30-day, pricing page visitors, trial non-converters. | ||
| CRM-06 | Lead Scoring Model | Sep 1 | Sep 14 | GTM Head | — | CRM-01 | Score: business email (+10), pricing page visit (+15), demo request (+30), Shopify merchant (+20), trial signup (+25), enterprise size (+20). Alert GTM Head when score ≥70 for manual outreach. | ||
| CRM-07 | n8n Automation — CRM Sync & Lead Routing | Sep 1 | Sep 14 | Lead Engineer | GTM Head | CRM-01; CRM-02 | n8n workflows: (1) Stripe event → HubSpot deal update. (2) Trial signup → welcome email sequence trigger. (3) Inactivity trigger (7 days no login) → reactivation email. (4) Upgrade → success notification to GTM Head. | ||
| CRM-08 | LinkedIn Ads Setup (Retargeting + Awareness) | Sep 22 | Oct 6 | GTM Head | — | CRM-05; VID-05 (social videos) | Post-launch. Retargeting: website visitors who didn't sign up. Awareness: ICP targeting (CX Directors, COOs, Founders) in UK/EU. Budget: £500/month initially. Measure: CPL, CTR, demo bookings. | ||
| CRM-09 | Churn Signal Detection & Win-Back Sequence | Oct 6 | Oct 20 | GTM Head | Lead Engineer | ANL-01; CRM-07 (n8n) | Churn signals: 14-day no login, conversation volume drop >50%, billing failure. Trigger: personal outreach from GTM Head (not automated sequence) for paying customers. Automated reactivation for trials. | ||
| ID | Task Name | Pri | Status | Start | End | Owner | Support | Dependencies | Next Action |
|---|---|---|---|---|---|---|---|---|---|
| SAL-01 | Demo Environment (Dedicated Workspace) | Aug 25 | Sep 7 | Product Head | Lead Engineer, GTM Head | ENG-01 | Create a permanent "Mevrik Demo" workspace, never reset after demos. Pre-seeded: e-commerce knowledge base (Shopify-like), telco scenario, support + sales + lead-gen agents all configured. 30+ representative conversations loaded. | ||
DeliverablesThree demo scenarios: (1) E-commerce SME with Shopify integration. (2) Telecom support (echoing Grameenphone). (3) SaaS B2B support + lead-gen. All with seeded conversations, trained agent, Mission Control populated.
Success CriteriaGTM Head can run a compelling 20-minute demo without engineering support. Demo never breaks in the middle of a call. Reset procedure takes <5 min if needed.
RemarksThe demo environment is used on every sales call. It must be impeccable. Treat it as a product — assign a dedicated workspace with a locked config that no one edits without approval.
| |||||||||
| SAL-02 | Sales Deck (AX Growth + Enterprise) | Aug 16 | Sep 7 | GTM Head | Prince Mojumder, Product Head | Category Migration Spec ✓; Grameenphone metrics ✓ | 15-slide deck: Problem (Era 1+2 CX) → Shift (Era 3, agentic) → Mevrik AX (the platform) → AX Growth (self-serve entry) → AX Enterprise (depth + sovereignty) → Proof (Grameenphone metrics) → Pricing → CTA. Both SME + enterprise paths in one deck. | ||
| SAL-03 | FAQ Document (Sales + Support) | Aug 16 | Sep 7 | GTM Head | Product Head, Lead Engineer | BIL-01 | 50-question FAQ: product ("what is agentic"), pricing ("what counts as a conversation"), security ("is my data safe"), technical ("what LLMs does it use"), competition ("how is this different from Intercom/Fin"), legal ("SOC 2 status"). | ||
| SAL-04 | Competitive Battlecards (Fin, Intercom, Zendesk, Sierra) | Aug 25 | Sep 14 | GTM Head | Prince Mojumder | fin-ai-research.md ✓; decagon-ai-research.md ✓ | Per-competitor one-pager: their positioning, their weaknesses, Mevrik's differentiation, when to choose us, how to handle their objections. Fin: per-resolution vs per-conversation wedge. Zendesk: cloud-only vs sovereign. Sierra: no self-serve, no SME path. | ||
| SAL-05 | Demo Script + Team Training | Sep 7 | Sep 14 | GTM Head | Prince Mojumder, Product Head | SAL-01; SAL-02 | 20-minute demo script: opening (their context), live product demo (3 scenarios), handle objections. Two practice sessions with Prince + Product Head. Record a reference demo for training. | ||
| SAL-06 | ROI Calculator / Value Framework | Aug 25 | Sep 14 | GTM Head | — | — | Build spreadsheet calculator: input (current support team size, avg salary, ticket volume, current resolution rate) → output (projected OPEX reduction, conversations handled by AI, cost per conversation). Used in enterprise sales proposals. | ||
| SAL-07 | Proposal Template | Sep 1 | Sep 14 | GTM Head | Prince Mojumder | SAL-02; BIL-01 | Enterprise proposal template: executive summary, solution design (channels + agent roles + integrations), commercial terms (AX Scale/Private/Sovereign), deployment timeline, success metrics, legal (DPA, MSA terms). | ||
| SAL-08 | Proof Asset: Grameenphone One-Pager | Aug 16 | Sep 1 | GTM Head | Prince Mojumder | CNT-02 (case study) | 1-page PDF: company overview, challenge, solution (Mevrik AX, on-prem sovereign), results (canonical 5 metrics), deployment detail. Sent to every enterprise prospect. Used in sales emails and demo follow-ups. | ||
| ID | Task Name | Pri | Status | Start | End | Owner | Support | Dependencies | Next Action |
|---|---|---|---|---|---|---|---|---|---|
| CSX-01 | In-App Onboarding Checklist | Jun 25 | Sep 1 | Product Head | ax-frontend, Lead Engineer | ENG-03 (wizard live) | Validate checklist steps: (1) Connect knowledge source, (2) Configure agent role, (3) Set widget, (4) Go live, (5) Invite team member. Each step has completion tracking. Completion triggers celebration + first success email. | ||
| CSX-02 | Help Documentation (Getting Started + Core Guides) | Aug 25 | Sep 14 | Product Head | Lead Engineer | ENG-01; QA-06 | Minimum docs for launch: Getting Started Guide (5 min quickstart), Widget Embed Guide, Knowledge Base Setup Guide, Shopify Integration Guide, Billing FAQ, Troubleshooting. Publish at /docs or /help. | ||
Deliverables8 core documentation articles live at launch. Searchable. Embedded in product via in-app help links. Video links embedded (VID-03 series).
Success CriteriaSupport ticket deflection rate ≥40% from docs in first 30 days. Docs cover 100% of onboarding checklist steps.
RemarksUse ax-docs repository (already scaffolded per Blueprint). Documentation quality is a direct revenue lever — poor docs increase support volume and churn.
| |||||||||
| CSX-03 | Customer Support Channel Setup | Sep 7 | Sep 19 | Product Head | Lead Engineer, HR Admin | WEB-01; AGA-01 (own agent) | Mevrik runs its own AX agent for first-line support. Configure: [email protected] → Mevrik AX inbox. Human escalation to Product Head (P0 bugs) or GTM Head (commercial). Define SLAs: P0 = 1h, P1 = 4h, P2 = 24h, P3 = 48h. | ||
| CSX-04 | Launch-Week Customer Support War Room Plan | Sep 14 | Sep 22 | Product Head | Lead Engineer, GTM Head | CSX-03 | Launch week (Sep 22–29): all hands on support. Product Head triage. Lead Engineer on-call (PagerDuty). GTM Head monitors HubSpot pipeline + demo requests. Daily standup 08:00 UK time. Escalation chain defined. | ||
| CSX-05 | Customer Success Check-In Flow (Day 1, 7, 30) | Sep 14 | Sep 22 | GTM Head | — | CRM-01; CRM-03 | Day 1: automated "How was your first day?" (1-question NPS). Day 7: Product Head personal check-in for all paying customers. Day 30: Quarterly review offer for customers processing >100 conversations/day. | ||
| CSX-06 | Support Team Training | Sep 14 | Sep 21 | Product Head | Lead Engineer | CSX-02; SAL-03 (FAQ) | 2-hour training session: product walkthrough, FAQ review, escalation procedures, common issues and fixes, how to use the internal Mevrik dashboard to debug customer issues. | ||
| CSX-07 | Trustpilot Profile Claim & Review Process | Sep 22 | Oct 6 | GTM Head | — | Need paying customers first | Claim Trustpilot profile. At Day 14 after each customer's first payment, automated email: "How are you getting on with Mevrik AX? Please leave us a review." Target: 10 reviews in first 30 days. | ||
| CSX-08 | Customer Community Setup | Oct 6 | Oct 20 | GTM Head | — | Post-launch; need customers | Slack community "Mevrik AX Users" — invite first 50 customers. Channels: #general, #tips-tricks, #feature-requests, #announcements. Product Head presents monthly update. Customers help each other = churn prevention. | ||
| ID | Task Name | Pri | Status | Start | End | Owner | Support | Dependencies | Next Action |
|---|---|---|---|---|---|---|---|---|---|
| ANL-01 | Event Tracking Plan (full funnel) | Aug 2 | Aug 16 | GTM Head | Lead Engineer | — | Define all events: website (CTA click, pricing view, demo book, trial start), product (signup, onboarding_step_1-5, first_conversation, first_live_widget, team_invite, upgrade, churn). Document as event spec before instrumentation. | ||
Key Eventstrial_signup, activation (first_conversation), first_live_widget (agent deployed), team_invite_sent, plan_upgraded, plan_cancelled, demo_requested, conversation_milestone_100
Success CriteriaEvent spec signed off by GTM Head + Lead Engineer. Events firing correctly in PostHog staging by Sep 7.
RemarksActivation metric = first AI conversation. This is the single most important metric to track — customers who reach first conversation within 24h of signup have significantly higher retention.
| |||||||||
| ANL-02 | PostHog Product Analytics Instrumentation | Aug 16 | Sep 7 | Lead Engineer | ax-frontend | ANL-01 | Instrument all product events from ANL-01 in Next.js console. Funnels: signup → activation, trial → paid. Session recording for first 500 users. Feature flags for gradual rollout. | ||
| ANL-03 | Revenue Dashboard (MRR, churn, expansion) | Sep 1 | Sep 14 | Lead Engineer | GTM Head | BIL-02 (Stripe); CRM-01 | Stripe → n8n → dashboard (Metabase or Google Sheets): MRR, ARR, new MRR, churned MRR, expansion MRR, ARPU, active trials, trial-to-paid rate. Daily update. Shared with Prince + GTM Head. | ||
| ANL-04 | Funnel Dashboard (website → trial → paid) | Sep 7 | Sep 19 | GTM Head | Lead Engineer | ANL-02; WEB-10 | GA4 + PostHog combined: website visitors → pricing page → trial signup → activation → paid. Show drop-off at each step. Weekly review cadence. | ||
| ANL-05 | Launch KPI Baseline (Day 0 snapshot) | Sep 19 | Sep 22 | GTM Head | — | ANL-02; ANL-03 | Record day-0 baseline for all KPIs: website traffic, trials, paid customers, MRR, social followers, email list size. Used as comparison point for all future reporting. | ||
| ANL-06 | Cohort Retention Analysis Setup | Oct 6 | Oct 20 | GTM Head | Lead Engineer | ANL-02; 2 weeks of data | PostHog cohort analysis: weekly cohorts by signup date. Retention metric: % still active (≥1 conversation) after 7, 14, 30, 60 days. Target: 30-day retention ≥60%. | ||
| ANL-07 | Agent Performance Monitoring (AI quality) | Sep 22 | Oct 6 | Lead Engineer | Product Head | ENG-01 (Trace module) | Monitor: resolution rate, human handoff rate, CSAT, response latency, hallucination rate (via Trace). Weekly agent quality report to Product Head. Trigger manual review if resolution rate drops >10%. | ||
| ANL-08 | Weekly Reporting Pack Automation | Oct 6 | Oct 20 | GTM Head | Lead Engineer | ANL-03; ANL-04; ANL-07 | n8n automation: every Monday 08:00 → compile week's KPIs → post to #mevrik-metrics Slack channel. Include: MRR delta, trials started, paid converted, churn, top support topics, agent quality score. | ||
| ID | Task Name | Pri | Status | Start | End | Owner | Support | Dependencies | Next Action |
|---|---|---|---|---|---|---|---|---|---|
| INT-01 | Internal Launch Brief (all team) | Sep 14 | Sep 19 | Prince Mojumder | GTM Head | All plans locked | Full-team briefing: launch date, what's launching, each person's launch-day role, escalation paths, success metrics, company priorities for the first 30 days post-launch. Written brief + verbal meeting. | ||
| INT-02 | Beta Customer Pre-Launch Notification | Sep 14 | Sep 19 | GTM Head | Prince Mojumder | QA-05 (beta customers active) | Personal email from Prince to all beta customers: "Thank you for being a founding user. We're launching publicly on Sep 22. Here's what's new. Your feedback shaped this product." Include exclusive launch discount for beta → paid upgrade. | ||
| INT-03 | Investor / Stakeholder Update | Sep 19 | Sep 22 | Prince Mojumder | — | — | 1-page investor update: launch milestone, early metrics, market reception, next 90-day targets. Send to advisors, strategic partners, and any investor contacts on launch day. | ||
| INT-04 | Partner Ecosystem Communication | Sep 14 | Sep 22 | Prince Mojumder | GTM Head | — | Personal email to design agency (rebrand partner), strategic advisors, any technology partners (Anthropic relationship, Twilio, Stripe). Brief on launch. Ask for reshares/amplification where appropriate. | ||
| INT-05 | Product Hunt Launch Preparation | Aug 25 | Sep 22 | GTM Head | Prince Mojumder | VID-01; WEB-06 | TIMING NOTE: Do NOT launch on Product Hunt on Sep 22 (same as website launch = split focus). Target Product Hunt launch: Week of Oct 6 (after product has stabilised). Prep: hunter briefed, tagline, gallery (5 screenshots + video), 300-word description, supporters identified (300+ upvotes target). | ||
Product Hunt Best PracticeLaunch on Tuesday or Wednesday. Submit midnight PST. Hunter must be active community member (not first-time). Notify supporters in Slack/LinkedIn at 00:01 PST — never ask directly for upvotes. Offer exclusive PH deal (e.g. 20% first 3 months).
Target#1 Product of the Day. This generates 1,000–5,000 visitors in a single day. Real volume boost only comes if website and onboarding are already smooth (hence Oct 6, not Sep 22).
Assets neededTagline (60 chars), Gallery (5 images + 1 video), Description (300 words), Maker commentary. All must be ready by Oct 4.
| |||||||||
| INT-06 | Reddit Presence & Community Engagement | Sep 22 | Oct 6 | GTM Head | Prince Mojumder | Post-launch | Target subreddits: r/SaaS, r/CustomerService, r/Entrepreneur, r/shopify, r/artificial. Strategy: be genuinely helpful (answer questions about agentic AI/CX) before mentioning Mevrik. Karma needed before posting. Assign Prince for r/SaaS founder perspective posts. | ||
| INT-07 | VAT Registration (if UK threshold reached) | Aug 2 | Aug 16 | HR Admin Lead | Prince Mojumder | — | UK VAT threshold: £90,000 turnover in rolling 12 months. If projected revenue exceeds this within 12 months of launch, register proactively. Confirm with accountant. UK B2B SaaS typically VAT-able. Stripe handles EU VAT via tax calculation APIs. | ||
| INT-08 | Advisory Board — Recruitment & Website Listing | Sep 22 | Nov 17 | Prince Mojumder | HR Admin | Post-launch | 3–5 advisors (equity + success fee structure confirmed). Ideal profiles: enterprise CX buyer, SaaS GTM veteran, telecoms/regulated industries, UK/EU VC. List on /about page — significant trust signal for enterprise buyers. | ||
| INT-09 | Weekly GTM Programme Standup (cadence) | Aug 4 | Ongoing | GTM Head | Prince, Product Head, Lead Engineer | — | Monday 09:00 UK: 30-minute standup. Agenda: week's completions, this week's priorities, blockers, KPI update. GTM Head sends written summary to all before meeting. Prince attends weekly; Lead Engineer monthly. | ||
| INT-10 | Launch Programme Ownership Assignment | Aug 2 | Aug 4 | Prince Mojumder | — | — | Prince assigns one programme lead (GTM Head recommended) who owns the master launch checklist, escalates blockers to Prince, and runs the weekly programme standup. Without this, the plan won't execute. | ||
Shopify App Store review takes 2–4 weeks. To hit Oct 20, you need approval by Oct 6 at latest. Working backwards: submit by Sep 5 at the latest (conservative). But to be safe, submit by Aug 9. Shopify requires: app installed successfully on a development store, privacy policy URL live, app listing complete, app passed Shopify's requirements checklist. Start this immediately.
| ID | Task Name | Pri | Status | Start | End | Owner | Support | Dependencies | Next Action |
|---|---|---|---|---|---|---|---|---|---|
| SHP-01 | Shopify Partner Portal Registration & App Setup | Aug 2 | Aug 9 | Lead Engineer | HR Admin (billing) | Shopify integration done ✓ (Phase 1) | Register at partners.shopify.com. Create app in Partner Portal. Configure OAuth scopes (read_products, read_orders, read_customers). Test on development store. Prepare app for review. | ||
| SHP-02 | Shopify App Store Listing (copy + assets) | Aug 2 | Aug 9 | GTM Head | Product Head, Design | VID-01 (brief started); WEB-06 (OG assets) | App name: "Mevrik AX — AI Customer Agent". Tagline (100 chars). Description (detail + features). Screenshots (5×1920×1080 showing Shopify integration). App icon (512×512). Support email. Privacy Policy URL live (from SEC-02). | ||
| SHP-03 | Shopify App Store Review Submission | Aug 9 | Sep 7 | Lead Engineer | GTM Head | SHP-01; SHP-02; SEC-02 (privacy policy live) | Submit for review by Aug 9. Monitor for Shopify feedback (they may request changes). Respond within 48h to any reviewer queries. Target approval: Sep 8 (giving 6 weeks of buffer before Oct 20). | ||
| SHP-04 | Shopify-Specific Landing Page (mevrik.ai or /shopify) | Sep 22 | Oct 13 | Product Head | GTM Head | WEB-01; WEB-13 | Dedicated Shopify page: "The AI agent your Shopify store needs." Show: product catalog knowledge, order lookup, cart recovery, Shopify setup in 5 min. Include Shopify App Store badge/link. | ||
| SHP-05 | Shopify Wave Launch Campaign | Oct 13 | Oct 20 | GTM Head | Prince Mojumder | SHP-03 (approved); SHP-04 | Launch campaign: email to all AX Growth trial/paying customers who are Shopify merchants. LinkedIn + Reddit /r/shopify post. Target: 50 Shopify store installs in first week. |
The Blueprint references a "Pulse pixel" in the messenger widget and lists Pulse as an add-on in pricing. Confirm with Lead Engineer whether Pulse (analytics module) is complete in Phase 2 (by Aug 25) or deferred to Phase 3. The Nov 17 target assumes Phase 2 completion. If Phase 3, move to Dec 2026.
| ID | Task Name | Pri | Status | Start | End | Owner | Support | Dependencies | Next Action |
|---|---|---|---|---|---|---|---|---|---|
| PLS-01 | Pulse Phase Scope Validation | Aug 2 | Aug 9 | Lead Engineer | Product Head | — | Lead Engineer to confirm: (1) What does Pulse include? (2) Is it Phase 2 complete? (3) If not, what's the actual delivery date? Decision gates Nov 17 target or pushes to Dec. | ||
| PLS-02 | Pulse Pricing & Packaging Decision | Aug 25 | Sep 7 | Prince Mojumder | GTM Head | PLS-01 (scope confirmed); BIL-01 | Decide: Is Pulse a free-included feature, a paid add-on (per Pricing Engineering §7), or a separate SKU? Pricing Engineering v1.0 lists it as a named add-on. Founder decision needed. | ||
| PLS-03 | Pulse Landing Page / Add-On Section | Oct 20 | Nov 10 | Product Head | GTM Head | PLS-01; PLS-02; WEB-01 | Add Pulse add-on to pricing page. Build /pulse landing page. Include: what it measures, sample dashboard screenshot, pricing (add-on), "upgrade" CTA for existing customers. | ||
| PLS-04 | Pulse Launch Campaign (upsell to AX Growth base) | Nov 10 | Nov 17 | GTM Head | — | PLS-03; Existing customer base (≥30 paying) | Email to all AX Growth customers: "Introducing Pulse — your AI customer intelligence dashboard." In-app notification. LinkedIn announcement. Target: 20% of existing customers adopt Pulse in first month. |
Week-by-Week Launch Timeline
Aug 2 – Nov 17, 2026Launch Day Command Plan
Monday, September 22, 2026One person owns each domain. No one is doing two things at once. GTM Head coordinates everything and has Prince's direct line for escalations. Engineering is on-call but not actively working unless there's an incident. Launch is a marketing day, not an engineering day — engineering did its job last week.
Launch Day Escalation Matrix
| Incident Type | Severity | First Responder | Escalate To | Response Target |
|---|---|---|---|---|
| Website down / 5xx errors | P0 | DevOps Engineer (PagerDuty) | Lead Engineer → Prince | 15 minutes |
| Stripe payments failing | P0 | Lead Engineer | Prince | 30 minutes |
| AI agent not responding | P0 | Lead Engineer | Prince | 30 minutes |
| High support ticket volume | P1 | Product Head | GTM Head | 1 hour |
| Negative press / social mention | P1 | GTM Head | Prince | 1 hour |
| Legal / compliance concern raised | P1 | Prince Mojumder | Solicitor | 2 hours |
| Trial signup spike (infra scaling) | P2 | DevOps Engineer | Lead Engineer | 2 hours |
| Demo booking system failure | P2 | GTM Head | Product Head | 2 hours |
First 30-Day Post-Launch GTM Plan
Sep 22 – Oct 21, 2026Week 1 Post-Launch (Sep 22–28): Stabilise & Capture
| Priority | Action | Owner | Target Metric |
|---|---|---|---|
| P0 | Daily KPI monitoring and P0 bug fixes (war room active all week) | Lead Engineer + Product | Zero P0 incidents by Day 3 |
| P0 | Personal outreach to every trial signup on Day 1: "Can I help you get set up?" (GTM Head) | GTM Head | 50% Day-1 signups reached personally |
| P1 | Social content: daily posts (per 30-day calendar, Days 11–17) | GTM Head | 2,000+ LinkedIn impressions/post |
| P1 | First 5 demo calls: lead with Grameenphone proof, collect enterprise prospect feedback | Prince + GTM Head | 5 demos booked and conducted |
| P1 | Compile first week support patterns: top 5 questions → update FAQ and docs | Product Head | FAQ updated Day 7 |
| P2 | Day-7 personal check-in with all paying customers | GTM Head | 100% paying customers contacted |
Week 2 Post-Launch (Sep 29–Oct 5): Optimise Onboarding
| Priority | Action | Owner | Target Metric |
|---|---|---|---|
| P0 | Analyse signup → activation funnel. If activation rate <60%, identify step 1 drop-off and fix | Product Head | Activation rate ≥60% |
| P1 | Launch comparison pages: /vs/fin, /vs/intercom (SEO traction begins) | GTM Head | Pages indexed and ranking within 30 days |
| P1 | Claim G2 profile. Email all paying customers requesting a review | GTM Head | 5+ G2 reviews |
| P1 | Industry pages: Shopify + Telecom published (pre-Wave 2) | Product Head | Pages live and indexed |
| P2 | Trial expiry emails going out — monitor conversion rate daily | GTM Head | ≥15% trial → paid in first cohort |
Week 3 Post-Launch (Oct 6–12): Product Hunt + Community
| Priority | Action | Owner | Target Metric |
|---|---|---|---|
| P0 | 🚀 Product Hunt launch (target Tuesday Oct 7). Activate supporter network at midnight PST. | GTM Head + Prince | #1 Product of the Day; 1,000+ website visitors |
| P1 | Trustpilot review campaign: email all Day-14 customers | GTM Head | 5+ Trustpilot reviews |
| P1 | First monthly newsletter "Agentic CX Brief" Issue 2 sent | GTM Head | 35%+ open rate |
| P1 | Reddit presence: 3 valuable answers in r/SaaS and r/CustomerService (no promotion yet) | GTM Head | Karma building; 1 top-voted answer |
| P2 | 30-day retrospective: all metrics vs. targets, top 3 learnings, 30-day-2 priorities | Prince Mojumder | Retrospective doc shared with team |
Week 4 Post-Launch (Oct 13–19): Shopify Wave Preparation
| Priority | Action | Owner | Target Metric |
|---|---|---|---|
| P0 | Final Shopify App Store readiness check (listing, pricing, privacy URL, support email) | Lead Engineer + GTM | App Store approved and ready |
| P1 | Shopify landing page (/shopify or mevrik.ai) live and indexed | Product Head | Page live; CTA to App Store |
| P1 | Email all AX Growth Shopify merchant signups: "Shopify launch next week — be first" | GTM Head | 50% open rate on Shopify-targeted list |
| P1 | Identify first 5 Shopify lighthouse customers for Wave 2 launch testimonials | GTM Head | 5 Shopify customers briefed and ready |
30-Day KPI Targets (Sep 22 – Oct 21)
Ownership & Accountability
Every task has exactly one Responsible owner (the person doing the work) and one Accountable owner (the person who signs it off). Where these are the same person, they both own and approve. Prince is the Accountable for all P0 items. Blockers are escalated to the Accountable within 24 hours — not left unresolved. The GTM Head programme lead is the first escalation point before Prince.
Weekly Status Report Format
Sent every Monday 08:30 UK by GTM HeadThe weekly status report is the programme's heartbeat. It creates accountability without requiring meetings. GTM Head compiles it every Monday morning for 8:30 UK. All workstream owners respond to their items by Sunday 20:00. Prince reads and acknowledges by Monday 10:00.
| Section | Content | Max Length |
|---|---|---|
| 📅 Week Dates | Week of [date] — L minus [N] weeks to Sep 22 launch | 1 line |
| 🚦 Overall Status | GREEN (on track) / AMBER (at risk, recovery plan in place) / RED (delayed, escalation needed). One sentence explaining the colour. | 2 lines |
| ✅ Completed This Week | Bullet list: task ID + task name + owner. Only completed tasks — not "in progress." | 5–10 bullets |
| 🎯 This Week's Priorities | Bullet list: top 10 tasks due this week, each with task ID, owner, and due date. Flag P0 items in red. | 10 bullets max |
| 🚫 Blockers | Any task that is blocked. Format: [TASK-ID] [task name] — Blocked on: [what/who]. Required action: [who needs to do what by when]. | 3–5 bullets |
| ⚠ Risks | New risks identified this week or existing risks that have changed severity. Each with: risk description, impact, mitigation. | 2–3 bullets |
| 📊 KPI Update | Pre-launch: [tasks completed] / [total tasks]. [P0 blockers remaining]. [Days to launch]. Post-launch: MRR, trials, activation rate, churn. | 3–4 lines |
| ❓ Decisions Required | Any items requiring Prince's decision before next week. Format: [decision needed] — needed by [date] — to unblock [TASK-ID]. | 2–3 bullets |
KPI Dashboard Recommendations
Three dashboard views recommended: (1) Daily CEO dashboard (Prince): revenue + conversion funnel. (2) Weekly GTM dashboard (GTM Head): full funnel + content + channel performance. (3) Weekly product dashboard (Product Head): activation, retention, agent quality.
Revenue & Commercial
Acquisition & Pipeline
Product & Activation
Agent Quality & Customer Satisfaction
Marketing & Community
Risk Register
| ID | Risk | Severity | Probability | Impact if Realised | Mitigation | Owner | Trigger Date |
|---|---|---|---|---|---|---|---|
| R-01 | Phase 2 engineering overrun past Aug 25 | Medium | Launch pushed to Oct; Wave 2 and Wave 3 cascade delayed | Weekly Phase 2 burndown tracking. Scope-cut Zendesk migration tool first. Lead Engineer flags any slip by Aug 11. Prince authorizes overtime or scope reduction. | Lead Engineer | Aug 11 (review) | |
| R-02 | Pricing not locked — founder delay | Low–Medium | Blocks website, Stripe, pricing page, and all downstream materials. Each day's delay costs ~2 days downstream. | Prince confirms pricing by Aug 4. GTM Head prepares final competitive brief and Pricing Engineering v1.0 summary for Prince's decision meeting. | Prince Mojumder | Aug 4 (hard deadline) | |
| R-03 | Legal docs not ready by Sep 7 | Medium | Cannot launch without Privacy Policy and ToS. ICO enforcement risk. Enterprise deals blocked without DPA. | Solicit engaged Aug 4. Budget approved immediately. 21-day drafting window. Contingency: use vetted AI-generated template as placeholder for 48h if solicitor is delayed — but only with Prince's explicit approval. | HR Admin Lead | Aug 4 (solicitor engaged) | |
| R-04 | Shopify App Store rejection | Medium | Wave 2 (Oct 20) delayed by 2–4 weeks. Loss of Shopify-specific GTM momentum. | Submit Aug 9 (3x buffer). Monitor Shopify reviewer email daily. Respond within 24h to any change request. Have a "direct integration" landing page ready as fallback (merchants install via embedded script, not App Store). | Lead Engineer | Aug 9 (submission) | |
| R-05 | Blog SEO equity loss on migration | Medium | Loss of organic search traffic. Rankings take 3–6 months to recover. GTM traffic plan relies on organic. | Full URL audit before migration. Screaming Frog pre and post crawl. All redirects tested individually. GSC monitored daily for 30 days post-launch. Reverse migration plan ready if significant rankings drop. | GTM Head | Aug 9 (audit complete) | |
| R-06 | Low trial-to-paid conversion (<10%) | Medium | MRR targets missed. Investor narrative weakened. Marketing spend not recoverable. | Personal GTM Head outreach to every Day-1 trial signup. Identify top activation drop-off in PostHog funnel by Day 7. Rapid product fix or onboarding improvement within 72h. A/B test onboarding flow starting Week 2. | Product Head + GTM Head | Day 7 post-launch (first review) | |
| R-07 | AI agent hallucination / incorrect output causing customer complaint | Low–Medium | Reputational damage, customer churn, negative press. Potential legal liability if incorrect advice given in regulated industry. | Trace module logs all outputs. Auto QA catches systematic failures. ToS disclaims AI accuracy. Agent configured with human escalation trigger for regulated topics. Beta testing on 10 real customers pre-launch. Kill switch available. | Lead Engineer + Product Head | Launch day onwards | |
| R-08 | Stripe payment failures on launch day | Low | Trial signups cannot upgrade. Revenue missed. Reputational damage if widely reported. | Full test of all 12 Stripe price paths by Sep 14. 3DS and failed payment paths tested. GTM Head has Stripe support contact. Contingency: manual PayPal/bank transfer for first 24h if needed with refund promise. | Lead Engineer | Sep 14 (Stripe tests complete) | |
| R-09 | Pulse module not ready in Phase 2 | Medium | Wave 3 delayed from Nov 17 to Dec 2026. Pricing page add-on section misleading. | Lead Engineer validates Pulse scope by Aug 9 (PLS-01). If Phase 3, Wave 3 moves to Dec. Remove Pulse pricing from website at launch. Announce "coming soon" instead. | Lead Engineer | Aug 9 (scope confirmed) | |
| R-10 | Key team member unavailable during launch week | Low | Launch day operations disrupted. Decision-making delayed. | All team members confirm availability Sep 19–26. Written handover procedures for each launch-day role. GTM Head knows all launch-day processes well enough to cover for Product Head. | Prince Mojumder | Sep 14 (confirm availability) | |
| R-11 | Competitor announces directly competing product | Low–Medium | Press coverage diluted. Pricing pressure. Some prospects may delay decisions. | Differentiate on: deployment sovereignty (unique), per-conversation pricing (unique), self-serve entry (most competitors are sales-led). Competitor announcement is signal that market is real — can be framed as validation. | Prince Mojumder + GTM Head | Ongoing monitoring | |
| R-12 | Website performance fails Core Web Vitals | Low | Google ranking penalty. Conversion rate drops. User experience degraded. | WEB-07 (CWV optimisation) due Sep 14. Lighthouse checks run daily from Sep 1. Target: LCP <2.5s, FID <100ms, CLS <0.1. Issues escalated to Lead Engineer for same-day fix. | ax-frontend | Sep 14 (CWV check) |
Go-Live Readiness Checklist
Sep 19, 2026 — Sign-off meetingThis checklist is reviewed in the Sep 19 sign-off meeting. Each item is verified by the owner and confirmed PASS. Prince gives final go-live authorisation only when all items are PASS. No exceptions unless explicitly approved by Prince with documented risk acceptance.
Engineering & Infrastructure
- Website loads in under 2.5 seconds (LCP) on 4G mobileLead Engineer
- Load test passed: <800ms first token at 1,000 concurrent usersLead Engineer
- Stripe checkout works for all 12 price paths (test cards passed)Lead Engineer
- Free trial signup → first AI conversation in <5 minutes (verified on prod)Product Head
- Status page live at status.mevrik.com showing "All Systems Operational"DevOps Engineer
- Disaster recovery drill completed; RTO <15 minutes verifiedDevOps Engineer
- SSL certificate valid; HTTPS enforced on all pagesDevOps Engineer
- PagerDuty on-call rotation configured for launch weekLead Engineer
- Kill switch tested at workspace and tenant scopeLead Engineer
- DNS TTL reduced to 300s (confirmed 24h before launch window)DevOps Engineer
Legal & Compliance
- Privacy Policy published at /privacy (UK GDPR compliant, reviewed by solicitor)HR Admin
- Terms of Service published at /terms (reviewed by solicitor)HR Admin
- Cookie consent banner live, GA4 respects consent modeLead Engineer
- ICO registration confirmed (registration number on Privacy Policy)HR Admin
- DPA template available on request (linked from Privacy Policy)HR Admin
- Vulnerability disclosure policy published at /securityLead Engineer
- SOC 2 Type II statement: "observation period underway" — on Security pageLead Engineer
Website & Content
- Home, Product, Enterprise, and Pricing pages live on productionProduct Head
- All locked naming applied: zero "chatbot", "bot", "AI-powered" on any pageGTM Head
- Pricing page: interactive slider, annual default, Enterprise CTA, FAQ with schemaProduct Head
- Sitemap submitted to Google Search ConsoleGTM Head
- Blog migration complete: all 301 redirects tested with Screaming FrogGTM Head
- OG images render correctly on LinkedIn, X, and iMessageProduct Head
- Launch blog post ready to publish (not yet published)GTM Head
- Help docs: 8 core articles live at /docsProduct Head
- Grameenphone case study published at /customers/grameenphoneGTM Head
- About, Contact, Security, and Platform pages live (secondary pages)Product Head
Product & AI Agent
- Zero P0 bugs open in QA backlogLead Engineer
- Mevrik own website agent live and passing 90%+ of 100 QA test conversationsProduct Head
- Demo environment: 3 scenarios seeded and tested (e-commerce, telco, SaaS)Product Head
- Welcome email sequence live and tested (4 emails, personalization verified)GTM Head
- In-app onboarding checklist (5 steps) complete and showing correct completion statesProduct Head
- Trial state machine tested: trial starts, countdown shows, expiry soft-paywall worksLead Engineer
- Cross-browser testing passed: Chrome, Safari, Firefox, iOS Safari, Android Chromeax-frontend
Analytics & CRM
- GA4 tracking firing correctly: trial_signup, demo_requested, plan_upgraded events verifiedLead Engineer
- PostHog product analytics instrumented: signup funnel, activation, onboarding stepsLead Engineer
- HubSpot: trial signup webhook creating contact + deal in CRM within 5 minutesGTM Head
- Revenue dashboard (Stripe → dashboard) showing real-time MRRLead Engineer
- LinkedIn Insight Tag and Meta Pixel firing (with consent)Lead Engineer
- Launch KPI baseline snapshot taken (Day 0 values recorded)GTM Head
Sales & Marketing Readiness
- Demo booking system (Cal.com/Calendly) live and creating HubSpot dealsGTM Head
- Sales deck finalised and approved by PrinceGTM Head
- Competitive battlecards: Fin, Intercom, Zendesk completeGTM Head
- ROI calculator spreadsheet tested with 3 customer scenariosGTM Head
- GTM Head and Prince have completed 2 demo practice sessionsGTM Head
- All social media bios updated with locked category and taglineGTM Head
- 30-day social content calendar scheduled in Postiz (first 7 days queued)GTM Head
- Press release written, approved, and queued for distributionGTM Head
- Beta customers notified of public launchGTM Head
- All social launch assets (10 images) designed and readyGTM Head
Team Readiness
- All team members have confirmed availability Sep 22–26Prince Mojumder
- Internal launch brief completed (all team know their launch-day role)Prince Mojumder
- Support channel ([email protected] → Mevrik AX inbox) live and testedProduct Head
- Support team training completed (2-hour session; escalation procedures documented)Product Head
- Escalation matrix confirmed: all phone numbers + Slack handles currentGTM Head
- Investor update email drafted and Prince-approvedPrince Mojumder
Master Launch Checklist
Grouped by week — use as the programme lead's daily tracking listWeek 1 (Aug 2–8) — Must complete before Aug 9
- Prince confirms GBP pricing numbers (BIL-01)Prince
- Programme lead assigned — GTM Head takes ownership (INT-10)Prince
- Solicitor engaged for Privacy Policy, ToS, DPA (SEC-02/03/04)HR Admin
- ICO registration submitted (SEC-06)HR Admin
- Shopify Partner Portal registration started (SHP-01)Lead Eng
- All social media bios updated (SOC-01)GTM Head
- Event tracking plan drafted (ANL-01)GTM Head
- Old blog SEO audit started (WEB-04)GTM Head
- Weekly programme standup cadence started (INT-09)GTM Head
- Explainer video studio briefed (VID-01)GTM Head
- HubSpot CRM config started (CRM-01)GTM Head
- Email platform (Resend) setup started (CRM-02)Lead Eng
- Pulse scope validation requested from Lead Engineer (PLS-01)Product Head
- VAT registration status confirmed with accountant (INT-07)HR Admin
Week 2 (Aug 9–15) — Critical delivery week
- Shopify App Store listing submitted for review (SHP-02/03)Lead Eng + GTM
- Website core pages build started (WEB-01)Product Head
- Stripe Checkout integration started (BIL-02)Lead Eng
- LinkedIn Company Page fully optimised (SOC-04)GTM Head
- Prince's personal LinkedIn updated (SOC-05)Prince
- Grameenphone case study writing started (CNT-02)GTM Head
- Sales deck drafting started (SAL-02)GTM Head
- 30-day social content calendar drafted (SOC-02)GTM Head
- Blog migration URL mapping complete (WEB-04)GTM Head
- Sub-processor register compiled (SEC-07)HR Admin
Weeks 3–4 (Aug 16–29)
- HubSpot CRM fully configured + tested (CRM-01)GTM Head
- Email platform live + SPF/DKIM/DMARC configured (CRM-02)Lead Eng
- Sales deck + FAQ document drafted (SAL-02/03)GTM Head
- Pre-launch blog post 1 published (CNT-03)GTM Head
- Blog migration content complete (WEB-04)GTM Head
- Phase 2 engineering completed (ENG-01)Lead Eng
- Legal docs drafted by solicitor and in review (SEC-02/03/04)HR Admin
- Stripe checkout tested for all 12 price paths in test mode (BIL-02)Lead Eng
- Pen test vendor engaged (QA-08)Lead Eng
- Explainer video first draft reviewed (VID-01)GTM Head
- Pre-launch blog post 2 published (CNT-03)GTM Head
Weeks 5–6 (Aug 30–Sep 13)
- Core 4 website pages live on staging (WEB-01)Product Head
- Free trial flow end-to-end working on staging (BIL-03)Lead Eng
- Legal docs published to website (SEC-02/03/04/CP-09)HR Admin
- PostHog + GA4 analytics live on staging (ANL-02/WEB-10)Lead Eng
- Demo environment seeded with 3 scenarios (SAL-01)Product Head
- Help docs: 8 core articles complete (CSX-02)Product Head
- Mevrik own website agent workspace set up (AGA-01)Product Head
- DR drill completed (ENG-06)DevOps Eng
- Welcome email sequence live in Resend (CRM-03)GTM Head
- Pen test report received (QA-08)Lead Eng
- Competitive battlecards complete (SAL-04)GTM Head
- Core Web Vitals passing on all 4 core pages (WEB-07)ax-frontend
- SEO schema + sitemap live (WEB-05)Product Head
- Full E2E QA testing started (QA-02)Product Head
- Agent QA (100 conversations) complete (AGA-02)Product Head
- Product demo video recorded and uploaded (VID-02)Product Head
- Pre-launch blog posts 3 + 4 published (CNT-03)GTM Head
- Demo booking system live (BIL-07)GTM Head
Week 7 (Sep 14–21) — Final countdown
- All P0 bugs resolved (QA-07)Lead Eng
- Cookie consent banner live + GA4 consent mode verified (SEC-05)Lead Eng
- Status page live at status.mevrik.com (ENG-09)DevOps Eng
- Load test passed (ENG-04)Lead Eng
- DNS switch rehearsal completed (WEB-11/CP-17)Lead Eng
- Internal launch brief: all-hands meeting (INT-01)Prince
- Go-live sign-off meeting Sep 19: all PASS (CP-18)Prince
- Second demo practice session: GTM Head + Prince (SAL-05)GTM Head
- Support team training completed (CSX-06)Product Head
- Beta customers notified of public launch (INT-02)GTM Head
- All 10 launch social assets designed and approved (SOC-07)GTM Head
- Launch blog post approved by Prince (CNT-01)GTM Head
- Newsletter launch issue ready to send (CNT-06)GTM Head
- Press release finalised and queued (CNT-04)GTM Head
- Investor update drafted and Prince-approved (INT-03)Prince
- Launch KPI baseline snapshot taken (ANL-05)GTM Head
- DNS TTL reduced to 300s (Sep 20 action)DevOps Eng
- Social media: first 7 posts scheduled in Postiz for launch weekGTM Head
- All team members confirmed available Sep 22–26Prince
Sep 22 — Launch Day
- 05:00 — DNS switched; all health checks greenLead Eng
- 06:00 — Website agent live; lead capture testedGTM Head
- 07:00 — GA4 + PostHog firing; revenue dashboard at £0 baselineGTM Head
- 08:00 — All-team go/no-go confirmedPrince
- 08:30 — Launch blog post publishedGTM Head
- 09:00 — All social posts live + newsletter sentGTM Head
- 09:00 — Press release distributedGTM Head
- 09:00–17:00 — Hourly Slack status updatesGTM Head
- 13:00 — Midday metrics checkGTM Head
- 17:00 — Investor update sentPrince
- 18:00 — Day 1 debrief callPrince