Svitlana Lysiak — Co-Founder
Your team isn't slow. The system they work in is. "The bugs were introduced by AI. I had to fix them manually. It took more time than writing myself." That's what you hear after buying seats for the whole team and wondering why you aren't shipping faster. You use AI. You get results. You assumed the team would too. Instead: ↳ Engineers burning cycles fixing AI-generated bugs ↳ 13–18% of engineering capacity gone to rework every quarter ↳ Debug commits eating 16% of all engineering output ↳ Smart people drowning in AI noise, not shipping I work with startup founders (20–150 people) where AI tools are running but launches keep slipping, decisions still stall, and nobody can explain why the team isn't faster. I don't install generic frameworks. I install yours. I extract how the founder thinks: what matters, what "good" looks like, what the non-negotiables are. I encode that into AI guardrails, decision ownership, and workflows the team actually runs. One of the clients: Series B, Logistics platform, ~20 engineers -> Before: - Copilot writing code that looked right and broke under load - Requirements written against hallucinated assumptions, not how the system actually works - 5–16 fix cycles per ticket. 4 weeks on a single feature - Every production incident and client escalation routed through the founder After the system was installed: - 12x less code thrown away - Issue rate dropped 56% - Workflows encoded into the system, incident resolution time cut x3 - The founder: "I'm not around for three days and things run smoothly" How do I know what makes or breaks the startup? I lived both: Group PM at Glovo. 30+ people, 3M MAU, ~90 solutions across 7 countries. One year I ran 20 initiatives at once and got sick from the overload. That year taught me what a decade of best practices couldn't: overload is a system failure, never a people failure. We ended up the top-impact product unit in the company. Turns out building systems beats running on adrenaline. Who knew. I continue building systems that work, except now they have AI inside them for the best clients. How I work: → Map where work actually breaks: decisions, handoffs, AI noise → Encode what already works: founder judgment, existing processes, team knowledge → Close the biggest gaps: ownership, quality gates, "done" → Stay until the team runs it Everything stays in your tools after I leave. Not in a slide deck. Founders who want systems working and someone who'll give them the hard truths? DM me or email svitlana.lysiak.work@gmail.com
Stackforce AI infers this person is a Product Management expert with a focus on AI-driven systems in the SaaS and Fintech sectors.
Location: Warsaw, Mazowieckie, Poland
Experience: 8 yrs 7 mos
Skills
- Product Management
- Process Engineering
- Strategic Thinking
- Mentoring
- User Experience
Career Highlights
- Installed AI operating systems for scale-ups.
- Led product initiatives across multiple countries.
- Transformed decision-making processes for startups.
Work Experience
Self-employed
Startup Operator (8 mos)
Glovo
Group Product Manager (3 yrs 1 mo)
Technical Product Manager (9 mos)
Projector Institute
Course Mentor (6 mos)
Maxitech
Product Owner (11 mos)
Qualtie
Project Manager (2 yrs 1 mo)
SilverTree Systems, Inc.
Project Manager (1 yr 9 mos)
Frontend Developer & UX Designer (1 yr 5 mos)
Junior UX Designer (2 mos)
Education
User Experience and Interaction Design at IxDF - The Interaction Design Foundation
Bachelor's degree at V.I. Vernadsky Taurida National University