Peak season in 2 months. Backlog has 500 tickets. Nobody knows what to build first.
2 weeks. I'll sort the backlog, write user stories, plan the sprints. Zero PowerPoints.
- Backlog cut from 500 tickets to 50 priorities. Your team delivers for the season.
- Marketing and dev on the same page — no more priority wars.
- A PM who delivers, not one who logs tickets in Jira.
Guarantee: No value after week 1 → you pay 7 500 PLN instead of 25 000
Too many ideas. Nothing ships.
CEO wants an app, CTO is rewriting the stack, CMO wants a loyalty program
Everyone pulls in a different direction. Result: 3 priority lists, zero alignment, dev team doesn't know what matters. Meetings last 2 hours and end without decisions.
Your PM just logs tickets — nothing moves
You have a PM but they're a "Jira admin." They transcribe what people say. No validation. No discovery. They never say "no." The backlog grows faster than the team can deliver.
Campaigns launch before tech is ready
Marketing planned a Black Friday campaign. The landing page doesn't exist. Tracking is broken. The promo went live — the site crashed under traffic.
Every month without prioritization costs 36 000 PLN — on rework, campaigns without tracking, and developers building things nobody needs.
An e-commerce without a PM loses the season.
E-commerce is growing but margins are shrinking. Your competitors have an app, personalization, a loyalty program. Your team has 500 tickets and zero priorities.
Customers expect more — free shipping, 30-day returns, same-day delivery
Seasonality demands planning — Black Friday, Christmas without a roadmap = firefighting
Marketing and tech must work together — a campaign without a landing page = money wasted
You don't need more people. You need someone who tells you what to do FIRST.
100K budget → 1M revenue. This is what a well-run e-commerce looks like.
Kazar — 1M+ PLN revenue
Marketing was inventing campaigns, dev team had its own priorities, CEO wanted innovation. I walked in and asked: what's your LTV:CAC? Silence. Social media campaign 100K → 1M+ PLN revenue.
Bauwerk — platform for 2500 partners
B2B e-commerce with a partner network. Discovery with partners instead of boardroom assumptions. Result: 80%+ adoption.
24/7Digital — scaling a digital agency
A digital agency serving e-commerce clients. I implemented product processes and sprint planning. Scaled without sacrificing quality.
"We don't have time, peak season is around the corner." That's exactly why the sprint takes 2 weeks, not 6 months.
"Our e-commerce is unique — we have a custom OMS, WMS, integrations."
I've built products with SAP integrations, custom ERPs, multi-warehouse setups. Days 1-2 are diagnostics.
"Peak season is 2 months away, we can't change processes now."
The sprint doesn't change processes — it sorts priorities. After 2 weeks your team knows what to build FOR the season.
"25K for 2 weeks? We have budget for a developer."
A developer without priorities builds things nobody needs.
In 2 weeks:
Backlog sorted, team working on what drives revenue for the season. Marketing has landing pages planned with dev. CEO stops asking "what are we doing?" because there's a roadmap.
What you get in PM Hands-On Sprint
| Deliverable | What it means | Impact |
|---|---|---|
| Backlog Cleanup | From 500 tickets to 50 for the season | -90% noise |
| User Stories | Ready for development | 0h clarification |
| Sprint Planning | Marketing and dev aligned | Zero "landing page is broken" |
| Season prioritization | Roadmap with dates | Season without fires |
| Documentation | Processes that work after I leave | Zero dependencies |
How it works — 3 weeks, step by step
Understand the context
- CEO/CTO interview
- Backlog review
- Conversations with dev + marketing
- Sprint goals
Results, not slides
- Backlog cleanup (500 → 50)
- Season prioritization
- User stories
- Sprint planning
- Checkpoint
Team operates independently
- Documentation
- Knowledge transfer
Investment vs. alternatives
| Option | Cost | Timeline | Guarantee |
|---|---|---|---|
| PM Sprint | 25 000 PLN | 2 weeks | Yes |
| Hiring a PM | 50-70K + salary | 5-9 months | No |
| No PM before peak season | Failed season = ??? | — | — |
Sprint + AI Context Architecture
Sprint + AI-powered knowledge base
Book a callI take max 2 sprints per month. Check availability.
What people I've worked with say
Fresh positive energy, an invaluable team member.
Expert, innovator, guarantees business goal delivery.
Frequently asked questions
Before and after the sprint
The season won't wait. Your backlog grows every day.
30 minutes is enough to assess whether a sprint makes sense for your e-commerce.
Book a 30-min callPS. 30 minutes is all I need to tell you whether a sprint makes sense before your season. If it doesn't — I'll say so upfront. calendly.com/rafalknap/lets-talk-about-your-product