Monika Mitreva

Hi, I'm Monika. Nice to meet you!

Monika Mitreva · Product Owner · AI and B2B products

I turn manual, messy work into products people actually adopt.

I've spent more than eight years in product, business analysis and delivery, most recently as Product Owner on an AI-powered banking platform. The part I enjoy most is working out what's worth building, and why. Next, I'd like a Product Manager role in a product company. In client work you build and move on; I want to stay with one product, own an area of it and go deep.

What have I built?

Most of these started with people doing slow work by hand. Here's what we built, and what changed.

Corporate banking · a new AI module

AI document generation for banks

Bank teams wrote documents in Word and emailed them around. I owned delivery of the new module, from first scope to pilots with 3 banks. Admins mark a template section and give it a prompt; AI writes that part, facts come from the bank's data, and the user has the final say.

Documents in 2–10 seconds. Leadership saw it as the entry point to the whole platform.

US swim-school chain · online bookings

Bookings that confirm themselves

Online bookings were only requests, so staff phoned almost every family about double bookings. As our team's acting Product Owner, I worked with the client's PM on a fix: hold a place for 10 minutes at checkout, confirm it once payment goes through.

Staff went from phoning almost every family to phoning only a few.

Corporate banking · permissions

The access model a bank was waiting for

Before one bank would start using the platform, its main condition was proper access control: who can see and change what. I shaped the requirements for a role-based model with about 200 permissions and roles that can be customised.

Shipped, and the bank started using the platform.

Internal tooling · 7 European markets

A resourcing system I built, then ran

Project managers from an external vendor were matched to customer projects by hand. With my mentor I built an internal system for intake, assignment and tracking; then I took it over, extended it and kept it running.

Admin effort cut by 50%, and still in use after I left.

↑ Back to questions

How do I work?

The product habits I bring to a team, each with the moment it counted.

A feature up for removal

I check assumptions with data

Another team planned to remove the business contacts section from our client form, assuming nobody used it. I couldn't query production myself, so I asked DevOps for a report and took the numbers to the other team.

60–70% of client records relied on it. The section stayed.

A founders' wish list

I cut big plans down to what can ship

The founders wanted it all in the first version: documents, collaboration, publishing, linked spaces, with no client feedback yet. With the PM, and with presentations and user flows I prepared, I argued for shipping the core first and learning from real use.

A first version with two core flows, and a phased plan for the rest.

Live editing or taking turns

I weigh cost and effort before choosing

Our document module needed collaboration. I compared real-time editing with asynchronous collaboration, where people work on a document at different times, on cost and effort, then made the call with the PM.

Async: value in weeks rather than months, no extra vendor cost, and the flow stayed inside the platform.

AI in my own work

AI is my strongest tool, not my role

When AI-written frontend code drifted from my stories, I started a pilot nobody asked for. With the engineer I redesigned our stories: fuller acceptance criteria covering edge cases, what existing functionality changes or goes away, and examples. My Rovo agents, later rebuilt in Claude Code, cut writing an analysed story from about 30 minutes to 2–5.

On 5 stories that had failed before, 90% of the acceptance criteria were met first time.

↑ Back to questions

Want to hear a story?

Two stories in full: one that went well, and one that didn't.

Agricultural client · software services

Leading without the title

Situation
An agricultural client needed its algorithm, locked inside an Excel macro spreadsheet, turned into a reusable software package (a NuGet package for .NET). Nobody on our team had done this before, and the client's product owner wasn't technical.
What I did
I'd done the analysis and estimates for the proposal, so once we won it I joined delivery as the BA. I knew Excel best, so I became team lead: I broke the work down, designed how the data was structured and parsed so QA could test it, and wrote scripts and test materials myself.
Result
Delivered on time, and the work won the phase 2 contract. My developers joked that I was a junior developer and offered to recommend me if I ever switched.
What I learned
My title didn't decide whether I led; curiosity and taking on the hard part did. Of my client work, it's what I'm quietly proudest of, because it made me confident on the technical side.

Hackathon · my own product

A product that never reached users

Situation
My team wanted to help people build healthy habits. At the World's Largest Hackathon by Bolt we built AGAIN, a habit tracker where your commitments are made public on the blockchain.
What I did
I owned the architecture, frontend, UI/UX, backend and core flows. My own goal was to really learn to build with code, not just prompt until it works, so I reviewed every architectural decision and kept the code small enough to understand.
Result
A working app, and I understood every part of it. But it never reached users: we couldn't get Apple developer access, and the project ended there.
What I learned
I polished the design before I had a way to reach users. Next time I'll talk to users early and secure the route to them first, whether that's store access or a web version. And AI agents build fast but drift, so the architecture has to stay mine.

Better told in a call

↑ Back to questions

Where have I been?

Newest first: a product company, two software services companies, and the corporate where I started.

  1. Product Owner

    neoshare, an AI-powered banking platform · Aug 2025 – Nov 2026

    My team grew from 3 to 9+, ML engineers included. I met regularly with other teams' analysts to catch dependencies early, and one of my design ideas, naming and sharing a document on one screen, was adopted into the design.

  2. Senior Business Analyst / Product Owner

    MentorMate · Apr 2022 – Jul 2025

    Client products in healthcare, education and agriculture. For a medical-technology client, I led the integration of sleep-study data from an AI provider into a platform doctors use, working across 5 other teams.

  3. Business Analyst & Delivery Manager

    INDEAVR · Sep 2020 – Apr 2022

    Business apps on Power Platform and SharePoint for international companies. I led one client's intranet from requirements to launch and training, and stepped in as Delivery Manager on another's, piloted in 5 countries.

  4. Resource & Vendor Manager

    HP Inc. · Mar 2018 – Sep 2020

    Started as an intern and was hired full-time into my mentor's role. Managed an external vendor's pool of around 40 project managers and PMO specialists, with weekly market syncs and quarterly capacity planning.

Built in my own time

  • AGAIN, the habit tracker from my hackathon story (demo)
  • A personal AI coach: an agentic workflow over my own health notes that suggests recipes, reminders and research topics (Claude Code, Python)
  • This site: I designed and built it with Claude Code

Education

  • MA General Psychology, Sofia University (2023)
  • BA Administration and Management, UNWE (2015)

↑ Back to questions

Have more questions?

Yes! Find me at

Bulgarian (native) and English (fluent) · EU citizen, no visa needed · mostly remote since 2022, with clients in Germany and the US · open to remote, hybrid or the office in Sofia · employment or B2B contract.

No, that was plenty! Thanks for taking the time!