Scored across 5 criteria · 🟢 Low 🟡 Medium 🔴 High
| Objective | |||||
|---|---|---|---|---|---|
| Budget: Cap non-media fees | Market: Expand to new audiences | Campaign: CRO audit & fix funnel | Attribution: Server-side tracking | Product: Competitive benchmarking | |
| Implementation period | 🟢 Low | 🟡 Medium | 🟡 Medium | 🔴 High | 🟢 Low |
| Development costs | 🟢 Low | 🟢 Low | 🟡 Medium | 🔴 High | 🟢 Low |
| Maintenance costs | 🟢 Low | 🟢 Low | 🟢 Low | 🟡 Medium | 🟢 Low |
| Expected revenue impact | 🟡 Medium | 🔴 High | 🔴 High | 🟡 Medium | 🔴 High |
| Expected benefits | 🟡 Medium | 🔴 High | 🔴 High | 🟡 Medium | 🔴 High |
| Implementation risks | 🟢 Low | 🟡 Medium | 🟢 Low | 🔴 High | 🟡 Medium |
| Quick win. Immediate cost efficiency with minimal effort. | Requires audience research and testing cycles across 3 markets. | Fast impact. Traffic is already paid for — fix the funnel. | Heaviest lift — needs dev, legal and analytics alignment. | Fast to start, but outcome depends on product team velocity. | |
Where each solution sits — and what to do first
#1 Cap non-media fees — days to implement, immediate cost recovery. High impact, low effort.
#2 CRO funnel fix — traffic already paid for; fixing conversion multiplies results fast. High impact, low–medium effort.
#3 New audience expansion — high revenue upside but needs research, testing, and 3-market rollout. High impact, high effort.
#4 Competitive benchmarking — critical for offer relevance but depends on product team; medium effort, high strategic impact.
#5 Server-side tracking — important long-term but requires dev, legal & analytics alignment. Medium impact on new customers directly; very high effort.
| Product | Activity | Start Date | End Date | Time (hours) | Costs (EUR) | Responsible Person |
|---|---|---|---|---|---|---|
| 🚫 NOTE: School year starts 1 Sep — reduced team availability first week. Stage 1 begins Wed 2 Sep with lighter tasks only. | ||||||
| STAGE 1 — Audit & Requirements · 2–19 Sep 2026 | ||||||
| P5_1 Tracking audit | Map all existing tags, pixels, GA4 events across site. Deliverable: full audit document. | 02 Sep | 09 Sep | 16 | 640 | Roberts |
| P5_2 Legal & consent review ⚡ | Review GDPR & consent mode v2 requirements for Latvia. Runs parallel to audit. | 02 Sep | 12 Sep | 12 | 300 | Inguna |
| P5_3 Analytics baseline snapshot ⚡ | Export current CVR, traffic, conversion volumes as baseline reference. Parallel task. | 02 Sep | 05 Sep | 8 | 200 | Ieva |
| P5_4 Technical requirements spec | Define SST architecture, data layer spec, tag manager config, cloud hosting choice. | 10 Sep | 19 Sep | 20 | 800 | Roberts |
| STAGE 2 — Development & Setup · 22 Sep – 17 Oct 2026 | ||||||
| P5_5 Server-side container setup | Configure GTM server container and cloud hosting (GCP/Azure). Core infrastructure. | 22 Sep | 03 Oct | 24 | 960 | Roberts |
| P5_6 Data layer implementation ⚡ | Web dev implements data layer events on site. Runs parallel to container setup. | 22 Sep | 10 Oct | 32 | 800 | Raivo |
| P5_7 Consent mode v2 integration ⚡ | Implement Google Consent Mode v2. Can begin parallel once container is provisioned. | 29 Sep | 10 Oct | 16 | 640 | Roberts |
| P5_8 Meta CAPI & GA4 SST config | Route Meta Conversions API and GA4 events through server container. | 06 Oct | 17 Oct | 24 | 960 | Roberts |
| STAGE 3 — Testing & QA · 20 Oct – 7 Nov 2026 | ||||||
| P5_9 QA: event validation | Validate all events fire correctly; prevent duplicate conversions between browser & server. | 20 Oct | 31 Oct | 20 | 800 | Roberts |
| P5_10 Internal UAT & reporting check ⚡ | Business-side check: dashboards and campaign reports still accurate. Parallel to QA. | 27 Oct | 07 Nov | 12 | 300 | Ieva |
| 🚫 LV PUBLIC HOLIDAY: 18 Nov — Latvijas Neatkarības proklamēšanas diena. No work. Buffer built into Stage 4 start. | ||||||
| STAGE 4 — Go-Live & Monitoring · 10 Nov – 5 Dec 2026 | ||||||
| P5_11 Production go-live | Switch server-side tracking live in production. Monitor closely for first 48 hours. | 10 Nov | 14 Nov | 8 | 320 | Roberts |
| P5_12 Post-launch monitoring | Monitor data quality, conversion volumes, anomaly alerts daily. 2-week window. | 17 Nov | 28 Nov | 16 | 500 | Raivo + Ieva |
| P5_13 Stakeholder report & handover ⚡ | Prepare sign-off report: before/after data, cost impact, recommendations. Parallel. | 24 Nov | 05 Dec | 10 | 250 | Inguna |
| 🚫 CHRISTMAS RISK: All deliverables must be signed off by 12 Dec to avoid year-end delays. Christmas period begins ~20 Dec. | ||||||
| TOTAL | 218 h | €6,470 | Roberts: ~148h · In-house: ~70h | |||
| # | Author | Date | Category | Description | Probability 1 low – 4 high | Impact 1 low – 4 high | Risk Exposure P × I / EUR | Planned Activity | Description of the planned activity | Status | Responsible Person |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Inguna | 02.09.26 | Suppliers | Roberts (outsource specialist) is busy — unavailable or delayed at critical stages | 4 – High | 4 – High | 16 / €5,920 | Prevent | Lock Roberts' availability and sign contract before project kick-off. Identify backup SST freelancer as contingency. | Open | Inguna |
| 2 | Raivo | 02.09.26 | Product | Data layer implementation delayed — website changes blocked by IT release schedule | 3 – Med-High | 3 – Med-High | 9 / €2,000 | Reduce | Align data layer tasks with IT release windows in advance. Add 1-week buffer in Stage 2 schedule. | Active | Raivo |
| 3 | Inguna | 02.09.26 | Employees | Legal sign-off delayed — GDPR / consent mode review takes longer than planned | 2 – Low-Med | 3 – Med-High | 6 / €450 | Reduce | Start legal review in parallel on Day 1 (Sep 2). Involve legal team in kick-off meeting to pre-align on consent mode requirements. | Active | Inguna |
| 4 | Ieva | 02.09.26 | Product | Server-side data diverges significantly from client-side — QA reveals major discrepancies | 2 – Low-Med | 4 – High | 8 / €1,600 | Reduce | Establish analytics baseline snapshot before go-live. Run parallel tracking for 2 weeks post-launch before switching off client-side tags. | Open | Ieva |
| 5 | Raivo | 02.09.26 | Suppliers | Cloud hosting costs (GCP/Azure) exceed budget estimate after go-live | 2 – Low-Med | 2 – Low-Med | 4 / €800 | Accept | Monthly cloud cost is low (<€150/mo est.). Monitor post-launch and adjust plan if costs exceed €300/mo. Acceptable risk given project ROI. | Accepted | Raivo |
| 6 | Inguna | 02.09.26 | Employees | Key in-house team member unavailable due to holiday or illness during critical phase | 2 – Low-Med | 2 – Low-Med | 4 / €500 | Reduce | Map all LV public holidays and school breaks into project plan. Cross-train Raivo and Ieva on each other's tasks where possible. | Active | Inguna |
| 7 | Ieva | 02.09.26 | Product | Modelled conversions in Google Ads / Meta not accepted by platform — tracking gap remains | 1 – Low | 3 – Med-High | 3 / €600 | Accept | Risk is platform-dependent and partially outside project control. Monitor post-launch platform reporting; escalate to Roberts if model gaps exceed 15%. | Accepted | Ieva |
| Total estimated risk exposure (worst case) | ~€11,870 | Highest risks: Roberts availability (R1) · Data divergence post go-live (R4) | |||||||||