Stella Župić
🇭🇷 Croatia · Balkans · 29 cancellations
"…most of all because we don't deliver on time."
Before any individual is named, the structural defect must be named first.
Almost every conflict happening right now — the decree, the suspension PDF, the statements, the unilateral moves on both sides — traces back to a single structural omission: Primework Group is a 50/50 partnership operating without any defined governance framework. No shareholder agreement was ever signed. This is not Marwan's fault. It is not Konrad's fault. It is what trust and momentum produced in place of structure.
There is no written agreement on:
- → Decision authority by domain (operations, technology, finance, HR)
- → Veto rights and escalation paths
- → Separation between owner decisions and operational decisions
- → Who hires and fires on which side, and with whose approval
- → Ownership of infrastructure, intellectual property, and operational systems
- → What happens if either side wants to exit
Important to understand
Without these structures, every disagreement collapses into the same dynamic: both sides reaching for unilateral action because there is no agreed mechanism for shared decisions. That is what created the current escalation cycle, and that is what will keep producing it unless we fix the root. The 11 May triple-detonation (decree + suspension PDF + commission PDF) is not the cause of the crisis — it is what a governance void looks like under pressure.
The findings that follow — 122 customer cancellations with ~909 worker-positions of demand exposed, the 737-worker live pipeline gap, 14 VAs rating the QuickPlus team 0.6:1, the Ukraine market collapse — are operational symptoms of a governance condition. Fix the operational symptoms only, and they will return. Fix the governance root, and the operational fixes become enforceable.
122 employer relationships terminated. ~909 worker-positions of demand exposed. The convergent evidence points at the same direction.
The numbers below describe two layers of evidence. The cancellation event count (122 customers walked away) is robust at the event level. The system snapshot of currently-linked candidates per cancelled order is what the data exports show today — almost all at "0 / X" because cancelled customers tend to lose candidate linkage in the CRM. The exact historical recruitment number per customer is unknown without IT extraction (see "Call to IT" section), but every other independent evidence source in this audit — VA confidential testimony, the 24-case Status Orders forensic, the Ukraine lifecycle — converges on the conclusion that actual historical delivery was very low. Treat the snapshots below as floor estimates, not point estimates.
Cancelled customers
122
signed contracts ending in cancellation · defensible event count
Source · cancelled.csv · 13 May 2026 snapshot · each line is one terminated employer relationship
Worker-positions of demand
~909
total demand across the cancelled portfolio · the size of the lost opportunity
Order quantities at time of contract · contracts that signed and ended without fulfilment
System snapshot · candidates now linked
0
candidates currently linked to cancelled-customer records · 122 of 122 show "0 / X" in the CRM export
Expected system behaviour — cancelling a customer unlinks all candidates from the record. Historical delivery is not zero by default; the per-customer conversation history is the only place that truth lives. Per-customer extraction needed.
Cancelled portfolio by country — how many employer relationships were signed in each market and how large the contracted demand was
🇵🇱 Poland
15 CUSTOMERS
297worker-positions ordered
🇲🇪 Montenegro27 CUSTOMERS
146worker-positions ordered
🇧🇬 Bulgaria17 CUSTOMERS
119worker-positions ordered
🇺🇦 Ukraine7 CUSTOMERS
67worker-positions ordered
🇱🇹 Lithuania4 CUSTOMERS
52worker-positions ordered
🇷🇴 Romania11 CUSTOMERS
51worker-positions ordered
🇭🇺 Hungary5 CUSTOMERS
37worker-positions ordered
🇬🇷 Greece9 CUSTOMERS
25worker-positions ordered
🇭🇷 Croatia3 CUSTOMERS
24worker-positions ordered
🇧🇦 Bosnia4 CUSTOMERS
23worker-positions ordered
🇸🇰 Slovakia8 CUSTOMERS
18worker-positions ordered
🇦🇱 Albania5 CUSTOMERS
16worker-positions ordered
🇸🇮 Slovenia4 CUSTOMERS
14worker-positions ordered
🇸🇪 Sweden1 CUSTOMER
13worker-positions ordered
🇨🇿 Czech Republic2 CUSTOMERS
7worker-positions ordered
Total customers
122
Total worker-positions ordered
909
Markets covered
15
Each card shows the number of distinct employer relationships signed in the country and the total worker-positions those contracts asked for. Per-customer historical fulfilment is not derivable from the CRM export — the cancellation event unlinks candidates by design — so this section reports only what the data defensibly shows: signed-and-cancelled employer count and contracted demand size by market. The structural concentration sits in Poland (15 customers · 297 positions), Montenegro (27 · 146), and Bulgaria (17 · 119) — together 59 of 122 customers and 562 of 909 positions (62% of the cancelled-portfolio demand).
Cancelled portfolio by position — what kind of workers the contracts asked for
Trailer Driver 🚚
201
positions
Physical Worker 💪
120
positions
Hospitality 🏨
83
positions
Construction 🚧
61
positions
Painter / Physical (mixed)
50
positions
Various Worker ★
47
positions
Wood Worker 🪚
33
positions
Welder MIG/MAG 💥
30
positions
Cleaner 🧽
21
positions
Production Worker 🏭
20
positions
Top of the demand is the highest-volume, most standard category in international labour recruitment: Trailer Driver (201 positions). Combined with Physical Worker, Hospitality, Construction and Cleaner, the top five position families account for 485 of 909 cancelled-portfolio positions (53%) — none of them niche.
Cancelled portfolio by VA owner — which country specialist signed each contract
Jan Prokop 🇵🇱
11 customers
252
positions
Stella Župić 🇭🇷
29 customers
184
positions
Georgi Penchev 🇧🇬
17 customers
119
positions
Gerda Steponaite 🇱🇹
4 customers
52
positions
Theodora Şerban 🇷🇴
11 customers
51
positions
Diana Nikitina 🇺🇦
6 customers
48
positions
Dariusz Włodarczyk 🇵🇱
4 customers
45
positions
Kovacs Almos 🇭🇺
5 customers
37
positions
Milica Disic 🇸🇮
9 customers
29
positions
Anastasia Poursanidou 🇬🇷
9 customers
25
positions
Dima Nikitin 🇺🇦
1 customer
19
positions
Egzon Bulliqi 🇦🇱
5 customers
16
positions
Emma Kolaříková 🇨🇿
5 customers
15
positions
Matus Holan 🇸🇰
5 customers
10
positions
The VAs found the employers. They signed them. Each row shows the contracts each country specialist brought into the portfolio — the front-end of the funnel they own. Per-customer historical fulfilment lives in the conversation log of each customer record and is not derivable from the CRM export alone.
14 of your VAs filled in a confidential review. They told you what is wrong.
On 13–22 March 2026, 14 country VAs filled in an anonymous process-review form. They were asked, among other things, why clients walk away after signing, what they would change in one move, and how they describe cooperation with the Dubai team. The answers below are theirs, verbatim. Source: VA_Communication__Process_Review__Answers.xlsx.
Fourteen people. One verdict. — aggregated sentiment scores
PRIMEWORK TEAM
+39
/
−8
Konrad · Ola · Marcin · Aleks · Jan
Roughly 5 positive signals for every 1 negative · ratio 4.9:1
QUICKPLUS TEAM
+18
/
−30
Jelena · Ashik · Shahab · Bipin · Ariana
Roughly 1.7 negative signals for every 1 positive · ratio 0.6:1 — slow to respond, missing critical information, unclear ownership of responsibilities
Primework team — sentiment distribution
39 positive / 8 negative · ratio 4.9:1
QuickPlus team — sentiment distribution
18 positive / 30 negative · ratio 0.6:1
Read carefully, brother. This is not a survey commissioned to make a point. It is a routine internal process review completed by our own operational layer. The same 14 VAs were asked the same question about both teams. They have nothing to gain by criticising the Dubai side and nothing to gain by praising the Polish side. They answered. This is what they said.
Q2
Why do clients refuse to continue cooperation? — your VAs' own answers
Diana Nikitina
🇺🇦 Ukraine · 6 cancellations
"the main reason for discontinuing cooperation is the excessively long candidate search process."
Georgi Penchev
🇧🇬 Bulgaria · 17 cancellations
"we don't provide the right candidates with the necessary qualifications and they don't answer to us."
Kovacs Almos
🇭🇺 Hungary · 5 cancellations
"Delayed recruitment."
Anastasia Poursanidou
🇬🇷 Greece · 9 cancellations
"The main reasons are delays in the process, lack of full understanding of the procedure, concerns about costs…"
Jan Prokop
🇵🇱 Poland · 11 cancellations
"This is caused by an excessively long recruitment process and a lack of clear next steps."
Q3
What happens AFTER the client signs? — your VAs' difficulties
Georgi Penchev
🇧🇬 Bulgaria
"i have to lie to them because we need months to find 3-4 persons for whatever kind of job."
Matus Holan
🇸🇰 Slovakia · Sonat VA
"No update regarding status of candidates. After several weeks sometimes months, client requests more info but I have no info to share."
Stella Župić
🇭🇷 Croatia
"The delivery of the CVs from our side in the agreed time frame."
Milica Disic
🇸🇮 Slovenia
"Only one is too long of a wait for candidates… they start calling and texting every day, asking did we find workers…"
Q10
Confidential: what would you share that the form did not ask?
Georgi Penchev
🇧🇬 Bulgaria · CONFIDENTIAL
"The guys from Dubai are slow and not efficient · info is often incomplete. Always some docs are missing."
Continues: "Often pushing me to arrange an interview for 3 out 5 candidates. This is not serious client asked for 5 not for 3. They telling we have 3 candidates waiting WTF we need 5."
Diana Nikitina
🇺🇦 Ukraine · CONFIDENTIAL
"…not fully sure whether there is sufficient internal interest and engagement in the development… of international recruitment to Ukraine."
Gerda Steponaite
🇱🇹 Lithuania · CONFIDENTIAL
"it had become quite discouraging to work when nothing was moving forward at all and there was no motivation."
Q9
Direct rating: cooperation with QuickPlus team (Jelena · Shahab · Bipin · Ariana)
Milica Disic
🇸🇮 Slovenia · Q9 multi-select
"Responses are too slow. We do not always know who is responsible for what. Embassy-related documents are often delayed."
Rita
🇱🇻 Latvia · Q9 multi-select
"Communication is unclear or confusing. We do not always know who is responsible for what."
Lenka Emma Kolaříková
🇨🇿 Czech · Q9 multi-select
"Answers are sometimes incomplete… The team is accessible when support is needed."
Out of 14 VAs filling in a confidential form across 14 countries, 12 named delivery delay, candidate quality, or Dubai-side communication failure as the operational problem. Not one VA blamed cost structure, Polish team, or partnership equity. The field is unanimous about where the failure is.
Case-by-case forensic — my response to the report your team gave me, where the failure was framed as the client's fault.
Important context, brother. The table below is not an audit I built in isolation. It is my direct rebuttal to the status report your Dubai team produced — a report whose left column ("REMARKS QuickPlus") consistently framed every problem as the employer's fault: "No response from employer", "Resigned by employer", "No response from client", "Too long process". I read every entry. Then I went into the CRM and reconstructed what actually happened chronologically. The right column is the result. Read them side by side. The pattern that emerges is the filtered narrative — true sentences ("the employer is silent") that point at the wrong party. The employer was silent because 3 to 7 months had passed since the contract was signed and no candidates had arrived. Source: Status_orders_200_people.xlsx · Konrad's personal 4+ hour audit of every entry in the Dubai-side status report.
Sonat, s.r.o · 🇸🇰 Slovakia
Trailer Drivers
2 / 10
7-month wait
Dubai team · Remarks
"No response from employer · too long process."
Konrad · chronological reconstruction
Contract signed 14 July 2025. Candidates finally submitted only in February 2026 — 7 months later. "This is effectively a record waiting time." Of 10 ordered, 2 arrived. The employer did not "stop responding" — the employer waited seven months for the workers your network was meant to deliver, then walked away.
Warrior · Krzysztof Gering · 🇵🇱 Poland
Trailer Drivers
10 / 10
6-month wait
Dubai team · Remarks
"Resigned by employer · 10 candidates · no response still."
Konrad · chronological reconstruction
Contract signed 28 July 2025. First candidates submitted 23 January 2026 — almost six months later. "Considering such a long waiting period, it is undefendable." Yes, the candidates eventually "resigned" — after the employer had already lost six months of operational planning. The resignation is a consequence of the delay, not its cause.
СБАЛХЗ ЕАД · 🇧🇬 Bulgaria
Cleaner
6 / 6
6-month wait
Dubai team · Remarks
"15 days no response."
Konrad · chronological reconstruction
Contract signed 18 July 2025. Candidates delivered only at the beginning of January 2026 — approximately six months later. On 12 February, Georgi re-contacted the client to re-engage. The "15 days no response" framing collapses six months of Dubai-side delay into a recent two-week silence — and assigns the cause to the silent party.
ET ЗП АЛИ ДЖАМАЛ ТАИР · 🇧🇬 Bulgaria
Physical worker
4 / 4
6-month wait
Dubai team · Remarks
"Its been a month, still no response."
Konrad · chronological reconstruction
Contract signed August 2025. First candidates submitted only 9 January 2026 — six months later. "In the system Ashik assigned the task to a person not responsible for this project, so the case never got proper follow-up." This is a Dubai-side CRM routing error. The employer waited six months because the case was sitting in the wrong coordinator's queue.
Montage rack · 🇵🇱 Poland
Physical worker
43 / 50
4-month wait
Dubai team · Remarks
"Resigned by employer · 43 candidates · no response still."
Konrad · chronological reconstruction
Contract signed 19 August 2025. First batch of 19 candidates arrived only 3 December 2025. Followed by 13 more on 28 December, more on 7 January. Trickle, not delivery. The order was for 50 in one go; instead it became a 4-month patchwork that exhausted the employer's tolerance.
Royal Staff · 🇵🇱 Poland
Production / Fish processing
14 / 20
5-month wait
Dubai team · Remarks
"Resigned by employer · 14 candidates · no response still."
Konrad · chronological reconstruction
Contract signed 1 August 2025. First candidates arrived mid-January 2026 — five months of waiting. And then in tiny batches: 13 Jan = 4 candidates, 15 Jan = 1 candidate. An order for 20 fish-processing workers met with five-month silence followed by drip-feed delivery.
Ingiliz group LLC · 🇧🇬 Bulgaria
Various positions
17 / 20
3-month wait
Dubai team · Remarks
"Too Long process · No response."
Konrad · chronological reconstruction
Contract signed 24 July 2025. First 15 candidates submitted only on 27 October. Three months of silence. The Dubai remark "too long process" describes the process correctly — but the process is the Dubai side's, and the silence is the Dubai side's.
Natália Bačíková · 🇸🇰 Slovakia
Cook + Cook Assistant
33 / 50
drip delivery
Dubai team · Remarks
"15 Days no response."
Konrad · chronological reconstruction
Contract signed 3 November 2025. First 4 candidates arrived 6 January 2026. Then trickle: 10 Feb, 12 Feb, 17 Feb. Order was for 50 cooks; delivery was synchronised "as candidates arrived" — meaning we could never present a real batch. Konrad's recurring principle: candidates must be submitted in batches of at least 10, never one-by-one.
Καμπουράκης Ανδρέας · 🇬🇷 Greece
Housekeeper
2 / 2
VA called 3×
Dubai team · Remarks
"VA tried 3 times a call to employer · No response from client."
Konrad · operational assessment
"What is your solution then?!!!!! Replace for another · you have 13 employers with signed agreement for Greece · what are you waiting for? Talk to VA immediately." A 2-housekeeper order falling through because the client did not pick up a phone three times is not a delivery problem — but the response should be replacement, not waiting. The Dubai team logged a "no response" without escalating to substitution.
UAB AUTODAMAS · 🇱🇹 Lithuania
Trailer Drivers
0 / 50
no delivery
Dubai team · Remarks
"VA follow up with client · no response."
Konrad · directive
"Please leave this market entirely Shabab · ALL CANDIDATES WILL BE HANDLED BY PRAXIS (Philippines)." A 50-trailer-driver order, the largest in Lithuania, currently showing zero candidates linked. Konrad's directive structurally removed the market from Shahab's portfolio and reassigned it to PRAXIS partner agency. This is the only durable response: take the failed channel out of the rotation.
Ralen Dna · 🇵🇱 Poland
Physical worker
0 / 50
no delivery
Dubai team · Remarks
"No response from employer · too long process."
Konrad · chronological reconstruction
Contract signed 2 September 2025 for 50 physical workers. "Until today the required group has still not been completed. Only a small number of candidates have reached the interview stage." Eight months since signing, no real delivery. The employer is correctly recorded as no-response — they gave up.
All-Rounders Group Oy · 🇫🇮 Finland
Bus Drivers
27 / 50
handled externally
Dubai team · Remarks
"No response with us, they are handling directly with candidates."
Konrad · self-indictment (preserved for integrity)
"In this case I take full responsibility. I apologize for introducing Markus as the contact person… Markus has proven to be completely unreliable… this situation is the result of poor judgment on my side." One case in the forensic audit where Konrad's own decision is named as the cause. The audit is not one-sided.
Robert Mládek · 🇨🇿 Czech Republic
Bricklayer · Drywall installer · Locksmith · Welder MIG/MAG
4 / 5
3-month process · ongoing
Dubai team · Remarks
"Applied on 21.01.2026 · no response."
Konrad · chronological reconstruction
Contract signed 22 Oct 2025. 3 candidates received 07 Jan 2026, sent by VA 12 Jan 2026. Fourth candidate appeared 21 Jan 2026, sent 22 Jan 2026. Process is ongoing — vacancy numbers received, work permits in progress. Communication fully visible in WhatsApp group "Czech Republic" and CRM. Not a "no response" case — an active file mislabelled.
Pavel Bauer · 🇨🇿 Czech Republic
Massage SPA
2 / 2
2-month silence after delivery
Dubai team · Remarks
"Applied on 16.12.2026 · no response."
Konrad · chronological reconstruction
Contract signed 14 Oct 2025. Candidates received 16 & 18 Dec 2025 and forwarded to client for approval. The client has not responded — but here the silence is genuine and post-delivery, not the chronic pre-delivery silence that defines the rest of the file. Outcome pending client decision, not VA performance.
Royal Team Work · 🇵🇱 Poland
Physical worker
20 / 20
5-month wait
Dubai team · Remarks
"No response from employer · too long process."
Konrad · chronological reconstruction
Contract signed 26 Aug 2025. Candidate files only delivered 20 Jan 2026 — 5 months later. All 20 work permit applications were submitted in the system and shared with Ashik. "Under normal circumstances delays of this magnitude often lead to projects being cancelled." The fact that this client did NOT walk away and proceeded with the work permits is the positive outlier — frankly, we should be grateful they stayed.
TOB СУНП '2K' · 🇺🇦 Ukraine
Car mechanic · Cook assistant · Packing · Physical worker · Sushi master
4 / 12
process not yet startable
Dubai team · Remarks
"Applied on 05.02.2026 · still no response."
Konrad · chronological reconstruction
Contract signed 10 Dec 2025. First 3 profiles submitted 23 Dec, one more 05 Jan. Quick first reaction — credit where due. But recruitment does not work candidate-by-candidate. For an order of 12, the process cannot realistically begin until at least 10 candidates are submitted as a batch. Sending profiles individually creates confusion and looks unprofessional to the client. Status: paused pending full batch — not a client-failure case.
Лекс Консулт Родопи ООД · 🇧🇬 Bulgaria
Waitress · Kitchen worker · Massage therapist
2 / 10
partial submission
Dubai team · Remarks
"—"
Konrad · chronological reconstruction
Contract signed 13 Jan 2026. Candidates submitted 11 Feb 2026 — but only 2 of 10 ordered. Same pattern as Ukraine: under-batched delivery. The process will not start with 2 candidates. We need to treat both each other and our clients seriously and complete the full group of at least 10 as soon as possible.
MM ТАСК ЕООД · 🇧🇬 Bulgaria
Cook assistant
4 / 4
client escalated to Konrad on LinkedIn
Dubai team · Remarks
"15 days · no response."
Konrad · chronological reconstruction
Contract signed 09 Dec 2025. First candidates submitted ~1 month later, then replaced with different profiles 2 months after that. The client wrote to me directly on LinkedIn. His message: after 2.5 months only one interview had been arranged, the candidate appeared "sitting in bed in pajamas", and despite three Primework representatives on the call no follow-up interviews were scheduled. This file did not collapse from client silence — it collapsed from process embarrassment.
АГРО ЮНИЙН БЪЛГАРИЯ ООД · 🇧🇬 Bulgaria
Physical worker
3 / 3
2-month delivery · CRM-silent VA
Dubai team · Remarks
"It's been two months · still no response."
Konrad · chronological reconstruction
Contract signed 29 Sep 2025. Candidates completed ~2 months later. The deeper issue is communication: Georgi has not been responding consistently in the CRM, which makes status tracking impossible from the Dubai side. Until CRM email notifications are reliable, follow-ups here need to go via WhatsApp directly to Georgi — not waiting on a CRM that the VA does not check.
Dear Well · 🇸🇰 Slovakia
Massage SPA
3 / 5
6-month wait to first profile
Dubai team · Remarks
"It's been a month · still no response."
Konrad · chronological reconstruction
Contract signed 08 Jul 2025. First profile only appeared on 28 Dec 2025 — six months later. VA submitted 2 more profiles on 13 Jan 2026. Same chronology as Sonat: half-year of pre-delivery silence, then the client is recorded as "no response" when they finally disengage. The cause is the wait, not the employer.
Across 20 forensic cases above, your team's standing explanation is some variant of "no response from employer". The chronology consistently shows: contract signed → 3–7 months of Dubai-side silence → employer disengages → the employer is then recorded as "no response." This is what Konrad calls the filtered narrative — a true sentence (the employer is silent) that points at the wrong party.
Open invitation to your team
If you still have doubts about any single case above — I am ready to investigate it personally, customer by customer.
The 20 cases above cover every entry in the Dubai-side status report. There are dozens more. If you, Jelena, Ashik, Shahab, or anyone on your side reads any of these and believes the chronology is wrong — name the customer. I will sit down with the CRM, pull every timestamp, every message, every status transition, every owner-reassignment, and reconstruct exactly what happened. Not in narrative form. In dated evidence. Customer by customer if needed.
But the path I want you to take is bigger than my individual investigation, brother. The right move — and I have written this formally in the "Call to IT" section later — is for your IT people in Dubai to extract the full conversation history of every customer profile in the CRM. Every chat. Every internal note. Every document upload. Every status change. Every owner reassignment. Every candidate link and unlink event. Per customer. With timestamps. With actor names.
Once that data is shipped, the truth about every cancelled customer surfaces automatically — without me, without you, without anyone's interpretation in between. Who picked up the file. When. Who replied. With what. When the silence started. Who was on the file when the employer last received an update. The system holds the receipts. We just need IT to release them.
Two-track offer · my commitment
→ Track A · Per-customer deep dive
You name a customer where you doubt the chronology. I commit to producing a dated, timestamped, evidence-anchored reconstruction within 48 hours per customer. No narratives. Receipts only.
→ Track B · IT-led bulk extraction
Your IT team in Dubai exports the full conversation history of every customer profile (134 active + 122 cancelled = ~256 records). I run AI analysis across all of it. The "kwiatki" surface at scale.
My position: Both tracks should run in parallel. Track A handles the cases you specifically dispute. Track B produces the full forensic picture for the company going forward — at the per-customer level rather than the per-market level we have today. Either way: we will learn a lot more than we know now.
A complete operational lifecycle — from launch to abandonment, in one WhatsApp channel.
Ukraine is the only market where we have a complete, dated, documented record from launch (20 June 2025) to silent abandonment (March 2026) in a single channel. It is also the only market you personally championed, brother. For both reasons it is the most precise diagnostic we have of how the current operational structure performs end-to-end. The 24-case forensic above shows a pattern; Ukraine shows a lifecycle.
"We will find the candidate I promise you that. Currently I have 5 applications from Egypt … Ukraine is in my list."
From "let's go" to silent abandonment
Eight months. One market. One partner personally engaged. The record reads in one channel, in one direction.
2025-06-20
Launch
Onboarding
Diana Nikitina and Dima onboarded · Ukraine market opens with strong belief
Marwan welcomes the team. Initial energy is high. The market is positioned for fast acquisition.
2025-10-14
First client
Konrad → Ashik, Jelena, Abdelrahman
Sotka LLC signed · "let's go"
First Ukrainian client. Market officially live. Optimism intact.
2025-10-28
Personal commitment
Marwan → Diana directly
Marwan personally takes over candidate sourcing
Marwan tells Diana the words above — 5 Egyptian applications already in hand, Ukraine on his personal list. Market no longer an experiment — championed at partner level.
Nov 2025 – Jan 2026
Slow drift
Diana ↔ Ashik
Diana writes formal, dated escalations · Ashik responds with the same pattern
Recurring Ashik template: "Thank you for your message. We are currently working on this. Will update you shortly." Acknowledgement does not match delivery pace. Diana keeps tagging Marwan, Jelena, Ashik for status updates that arrive late or not at all.
2026-02-11 (11:40)
Crisis surfaces
Diana → Konrad → all
Formal written escalation: three clients about to terminate
Diana, in writing: "at least three clients have stated that they are willing to wait approximately one more week … they are considering terminating their contracts." Konrad tags Marwan, Ashik, Jelena. Marwan replies at 11:44: "I will give u an update today inshallah." That update never comes.
2026-02-12 (12:19)
Root cause
Marwan acknowledges
The foundational document check was never done
Four out of five Egyptian candidates cannot produce the bank statement required by the Ukrainian embassy — a standard document for virtually every visa process. Marwan: "No one can apply for Ukraine without a bank statement and we not going to do photo shop … Customers know if they get busted it jail time for forgery." The candidates have already spent ~€420 each (~€2,000 combined) preparing documentation.
2026-03-18
Trust collapse
Diana reports Sotka ending
Sotka LLC ends cooperation · raises possibility of lawsuit
After failed visa applications, Sotka LLC formally ends cooperation, demands expense refund, and mentions possible lawsuit. Diana, in writing: "she does not see any further prospects for working together. She had also previously mentioned the possibility of filing a lawsuit." No structural response from Dubai recorded after this point.
Late Mar 2026 →
Silent abandonment
Channel goes quiet
Ukraine WhatsApp group goes effectively silent for 5+ weeks
Market has not been formally closed — it has simply been abandoned. The next meaningful activity comes only on 7 May 2026, when Arianne is added as part of a general cleanup across all market channels. The market Marwan personally championed went silent under his name.
"I hope that in the future the responsible recruitment manager … will carefully verify candidates' ability to obtain the necessary certificates and documents."
What this case alone tells us
This is not a story about a difficult market. Ukraine has real challenges, but it is not unworkable. This is a story about the operational system we currently have failing at the most fundamental level — verifying that candidates can actually meet visa requirements before processing them.
If we cannot do this in a market the partner himself championed, with a partner-level commitment dated 28 October ("Ukraine is in my list"), with personal sourcing involvement, with the operational layer escalating in writing for two months — then we cannot scale to fifty markets. The Ukraine record is not the exception. It is the lifecycle.
Eleven WhatsApp groups + 134 active customers. The data shows which markets are dead, which are dying, and which can still be saved — read against the actual live pipeline.
I read every WhatsApp group we run between Primework and the Dubai team — message by message. For each I counted how many times the country VA had to chase Dubai for status, and how long the silences were. I then cross-referenced those numbers with the current live pipeline (actual_customers.csv · 134 active customers, 1,274 worker-positions ordered, 537 currently in-process, 737-worker gap to fill) and the cancelled-customer pattern. This is the per-market scorecard. Verdict scale: Critical · High Risk · Recovering · Stable · Dead.
Snapshot interpretation note. All "X / Y" values below are system snapshots of currently-linked candidates per order — not full historical recruitment counts. A "0 / 50" line means zero candidates currently associated, not necessarily zero ever sourced; the customer profile conversation history would tell the full story. The system-level pattern, however, is unambiguous: across 122 cancelled customers, only 4 still show any candidate linkage today.
Active pipeline · today
1,274
worker-positions ordered across 134 active customers · 537 in-process · 737 gap to fill
Source · actual_customers.csv · 13 May 2026 snapshot
Customers with 0 candidates now
38
28.4% of active customers · signed contracts with zero currently-linked candidates
Same pattern that produced the 122-customer cancellation file — replaying in real-time
WhatsApp forensic · worst silence
19.8d
days a VA waited for any Dubai response · Finland · Markus
Bulgaria 15.7d · Finland median 12.8d · Ukraine max 11.0d · across 9,591 messages parsed
Per-market scorecards — viability verdict with the evidence
🇺🇦 Ukraine
VA: Diana Nikitina · group active 20 Jun 2025 → 7 May 2026
Live pipeline today: 12 active customers · 73 ordered · 18 currently in-process · 24.7% fill rate · 81-day average delay · 158-day worst case in the tracker. Diana's portfolio reaching for delivery against a structurally absent sourcing layer.
Cancelled file: 7 customers in the cancellation pattern. Chat forensic: 23 documented VA follow-ups by Diana in 320 days. Median Dubai chat response 0.2h but max silence 11 days after the 11 Feb "three clients about to terminate" escalation. Marwan's "I will give u an update today inshallah" update never came.
Compounding factor: bank-statement check should have been upstream. 4 of 5 Egyptian candidates failed it. ~€2,000 in candidate personal costs lost. Sotka LLC threatened lawsuit.
Market silent since late March 2026 · partner-championed · diagnostic for entire structure
🇵🇱 Poland
VA: Jan Prokop + Dariusz Włodarczyk · group active Feb 2025 → 8 May 2026
Live pipeline today: 19 active customers · 597 worker-positions ordered · 148 currently in-process · 449-worker gap to fill — the largest active gap of any market in the company. Jan Prokop owns 18 of these customers (467 ordered, 349 gap).
Cancelled file: 15 customers in the cancellation pattern · 297 worker-positions of demand exposed to risk. Single worst market in absolute terms. Chat forensic: only 9 follow-up requests in 445 days of group activity — not because the situation was fine, but because the Polish team gave up on chat-escalation and moved to forensic-audit (Status Orders 200 People).
The active orders sitting at zero candidates RIGHT NOW: Laa Trans 0/50 trailer drivers · Transet 0/50 trailer drivers · Thai Bali Spa 0/50 massage · METAL-FAN 0/100 welders · Essa Grupa 0/15 trailer drivers · Jartrans 0/30 trailer drivers · EPL Poland 0/30 production · CENTRUM MASAŻU 0/20 massage. These are positions LinkedIn is flooded with from Philippines, India, Vietnam, Nepal — your network's strongest source markets.
"On hold" per decree · 449-worker live gap · Polish team blamed for failures of Dubai-side sourcing
🇧🇬 Bulgaria
VA: Georgi Penchev · group active 17 Feb 2025 → 13 May 2026
Live pipeline today: 5 active customers · 24 ordered · 24 in-process · 100% fill rate. Georgi has caught his current book up. Improvement from earlier snapshot — Bulgaria has been recovered in the active pipeline.
Cancelled file: 17 customers in cancellation pattern · 119 worker-positions of demand exposed. Chat forensic: Single documented follow-up max-silence of 15.7 days. Georgi's confidential VA survey quote crystallizes the historical pattern: "i have to lie to them because we need months to find 3-4 persons."
Quality + delivery historical pattern: Bulgaria suffered from both delivery delay AND candidate-quality issues (pyjama interview MM ТАСК, Case 21 SBALHZ 6-month wait, Case 18 Ashik wrong-owner assignment). The recovery in the current snapshot does not erase the 17-customer cancellation file.
Active book recovered to 100% · 17 cancelled-customer history must still be addressed · "on hold" per decree contradicts current performance
🇷🇴 Romania
VA: Theodora Şerban · group active 21 May 2025 → 13 May 2026
Live pipeline today: 10 active customers · 59 ordered · 58 in-process · 98.3% fill rate. Theodora's portfolio has been substantially caught up since the previous snapshot.
Cancelled file: 11 customers in cancellation pattern · 51 worker-positions of demand exposed. Chat forensic: 67 documented follow-up requests in 356 days — highest of any single-country group. Theodora chased relentlessly. Median chat response 0.2h, but the volume of follow-ups proves replies are fast and candidates are not.
The chat-responsiveness paradox: Romania has both the fastest chat replies AND the highest historical cancellation rate. This proves the bottleneck is not communication — it is sourcing throughput. Theodora's 67 follow-ups did not produce candidates; they produced acknowledgements.
Listed as Active per decree · current 98% fill validates that decision · sustain not reset
🇭🇺 Hungary
VA: Kovacs Almos · group active Balkans (shared)
Live pipeline today: 17 active customers · 127 ordered · 87 in-process · 68.5% fill rate · 37-day average delay · 200-day worst case (longest of any active customer).
Cancelled file: 5 customers in the cancellation pattern · 37 worker-positions of demand exposed.
Cancelled file: 5 customers in the cancellation pattern · 37 worker-positions of demand exposed.
Process Review verdict: Kovacs's two-word answer to "why do clients refuse to continue" — "Delayed recruitment." Single phrase. No elaboration needed.
Mixed signals: Healthy 68.5% headline fill rate but a 200-day worst-case delay points to abandoned cases within the active book. Kovacs is operating effectively; the system around him produces sporadic deep failures.
Listed as Active per decree · biggest single active book but worst single delay · recoverable
🇬🇷 Greece
VA: Anastasia Poursanidou · group active Balkans (shared)
Live pipeline today: 17 active customers · 48 ordered · 49 currently in-process · 102% fill rate (over-delivery).
Cancelled file: 9 customers in cancellation pattern · 25 worker-positions exposed — but historical net delivery shows over-fulfilment here too.
Cancelled file: 9 customers in cancellation pattern · 25 worker-positions exposed — but historical net delivery shows over-fulfilment here too.
Why Greece works: Anastasia over-delivered her cancelled book and is running the highest active fill-rate. Small-batch model (most orders 2–6 candidates). Status Orders Case 12 shows when Greece does fail, response is to replace, not wait.
The lesson: Greece proves that the operational structure can deliver when (a) order batches are small, (b) the VA can substitute candidates, (c) follow-up is tight. Replicating these conditions is the path forward for other markets.
Best fill-rate of any active market · Anastasia is operational counter-example
🇨🇿 Czech + 🇸🇰 Slovakia
VAs: Emma Kolaříková · Matus Holan · groups active Aug 2025 + Feb 2025 →
Live pipeline today (combined): 19 active customers · 101 ordered · 52 in-process · 51.5% fill rate (CZ alone: 14 cust · 70 ordered · 35 in-process; SK alone: 5 cust · 31 ordered · 17 in-process).
Cancelled file: CZ 2 customers · SK 7 customers.
Cancelled file: CZ 2 customers · SK 7 customers.
Chat forensic: Czech group: 12 follow-ups in 262 days. Slovakia group: 6 follow-ups in 449 days but max silence 7.2 days. Matus's confidential Q3 review: "After several weeks sometimes months, client requests more info, I have no info to share."
Record case sits here: Sonat trailer drivers (SK) — Case 24, 7-month wait, the single worst delay documented in the entire forensic file.
Both markets "on hold" per decree · Sonat 7-month record · recoverable with new sourcing
🇱🇹 Lithuania
VA: Gerda Steponaite · group active inside Balkans/Baltics coordination
Live pipeline today: 4 active customers · 95 worker-positions ordered · 6 currently in-process · 6.3% fill rate · 89-worker gap. After Poland and Hungary, Lithuania is the third-largest order book in the company — and the worst-served by an order of magnitude.
The UAB AUTODAMAS trailer-driver order alone: 1 / 50 currently in-process. This is the same order from Status Orders Case 13 where Konrad's directive was: "Please leave this market entirely Shabab — all candidates will be handled by PRAXIS." The market was formally re-routed from Shahab's portfolio months ago and still sits at 1/50.
Gerda's confidential Q10 verdict: "it had become quite discouraging to work when nothing was moving forward at all and there was no motivation." The VA owns the largest under-served book in the company. Demotivation in the field reflects what the system delivers — or fails to.
"On hold" per decree · 89-worker live gap · already failed even with PRAXIS reassignment
🇬🇧 United Kingdom
Single active customer · no dedicated VA channel · 1 / 134 of book
Live pipeline today: 1 active customer · 30 worker-positions ordered · 0 currently in-process · 0.0% fill rate. Recently-signed and already at zero candidates.
Pattern repetition: A market signed without a sourcing channel ready, parked in the same queue that produced the 122-customer cancellation file. New market, same pattern.
No dedicated coordination · early-warning case · prevent it joining the cancellation file
🇦🇱 Albania
VA: Egzon Bulliqi · group active Balkans (shared)
Live pipeline today: 7 active customers · 20 ordered · 14 in-process · 70% fill rate.
Cancelled file: 5 customers · 16 worker-positions of demand · 0 candidates currently linked in CRM snapshot (cancellation-unlink artefact).
Cancelled file: 5 customers · 16 worker-positions of demand · 0 candidates currently linked in CRM snapshot (cancellation-unlink artefact).
Egzon's Q10 confidential note: "it would be very beneficial for us to successfully complete a few recruitments in Albania as soon as possible … Albania is a relatively small market where many business owners know each other." Reputation in tight market — proof-of-concept matters more than scale here.
Process Review Q8 verdict on Primework team: Egzon describes responsiveness during weekends and late hours — one of the most positive single accounts. This market has support.
"On hold" per decree but VA reports positive Primework support · recoverable
🇫🇮 Finland
VA: Markus Varpa (+ Liana, Estonia) · group active 21 May 2025 → 7 May 2026
Not in active tracker · zero active pipeline. Status Orders Case 14 (All-Rounders Group Oy bus drivers) is Konrad's self-indictment — Markus was unreliable, contact mishandled.
Chat forensic: 6 follow-ups in 350 days. Median Dubai response time 12.8 days. Max silence 19.8 days. 3 of 6 follow-ups got responses ≥7 days late. Highest median-silence of any market analyzed.
Operational diagnosis: No active customers. No partner channel. VA absent. This market is effectively closed regardless of whether the decree formally lists it.
"On hold" per decree · operationally already abandoned · re-open with different VA only
🇲🇪 Montenegro · 🇭🇷 Croatia · 🇸🇮 Slovenia · 🇧🇦 Bosnia · 🇲🇰 Macedonia
VAs: Stella Župić + Milica Disic · single Balkans WhatsApp · 4,090 messages
Cancelled file (combined): Montenegro 27 customers · 141-worker gap · Croatia 3 cust · 24-worker gap · Bosnia 4 cust · 11-worker gap · Slovenia 4 cust · 14-worker gap = 190 worker-positions of demand across 38 cancelled customers. Stella alone holds 29 cancellations.
Chat forensic: 14 follow-up requests across 449 days in the umbrella Balkans group — relatively low frequency suggests VAs gave up chasing through chat. Max silence under 24h, but the volume of cancellations shows the real issue is not chat-response but candidate delivery.
Stella's Q2 verdict (her own words): "we don't deliver on time." Milica's Q9 verdict on QuickPlus team: "Responses are too slow. Embassy-related documents are often delayed."
Macedonia/Montenegro listed Active per decree · Croatia/Slovenia/Bosnia on hold · Stella's portfolio largest single damage
Cross-cutting groups — the coordination layer itself
VA Communication (cross-VA)
Operational artery · all VAs + Dubai team · 2,407 lines · 677 messages
Created October 2025 as the cross-border coordination spine. Runs through every subsequent crisis. The single point where Olga's 26 Feb candidate-quality red flag was raised.
Coordination role: When Olga and the country VAs needed to escalate Dubai-side delays, this is the channel where they did it — and where the responses defaulted to "noted, will check, will update" patterns. The chat has the receipts.
Operational artery · target of the decree's centralization push · to be migrated to primework360 Chat module
Primework-QP (Abdelrahman era)
Legacy QuickPlus coordination · 3,408 lines · 1,205 messages
The original Primework × QuickPlus operational channel. Used during the early build phase. Abdelrahman was on it. The channel reflects the period where the 3–4 month wait pattern was already beginning — before the Polish team existed.
Forensic value: This channel is the chronological evidence base for Contradiction #5 — that the delivery failures predate the structure being restructured.
Historical record · chronologically establishes pre-Polish-team failures
Konrad ↔ Jelena (direct)
2,089 messages · trust-arc fully documented
Four-stage trust arc: warm onboarding → cooperative period → "love you ❤️" exchanges → 14 April Discord/WhatsApp rupture → 11 May suspension PDF.
Diagnostic value: The single most detailed evidence base for the Konrad-Jelena rupture — where the "He told me to take all even if is 1" admission appears, where the minimum-order policy reversal of 1 February is documented, where Jelena's relationship with Bipin and Shahab is described.
Channel formally closed by suspension PDF · evidence preserved in audit
Of 11 country/cross-VA groups analyzed: 4 Critical (Ukraine, Poland, Bulgaria, Romania), 3 High Risk (Hungary, CZK/SK, Balkans umbrella), 1 Recovering (Albania), 1 Stable (Greece), 1 Dead (Finland). The decree's "6 active markets" list includes 2 of the 4 Critical-rated markets (Romania, Hungary) and treats Greece — the only stable market — as one of six rather than the model the others should aspire to.
Who, specifically, failed — by named individual, with documented incident
The 20-point decree treated the Dubai operations team as a single unit to be empowered. The forensic record treats them as individuals with documented incidents. This section names them — not to attack people, but because no fix is possible without identifying who did what. One name in this list is positive: Mohammed Ashik is the bilateral asset both principals agree on.
Jelena Sladaković
VA Supervisor · QuickPlus · suspended 11 May 2026
Started cooperative and curious. Drifted into a positional role producing narrative rather than operational output. A year of cooperation with no proactive escalations on cost structure, VA performance, or recruitment bottlenecks — followed by an "analytical" voice that surfaced only after the crisis broke into the open.
1. The 1 February 2026 minimum-order reversal — verbatim receipts. Privately told Konrad in chat: "hi Konrad · I spoke with Marwan · about the problem with the minimum order · he told me to take all even if is 1 · so kindly post on discord in announcements." Reversed Konrad's September 2025 Balkan minimum-order policy (4–5 candidates) without consulting Konrad — only after-the-fact request to post the new rule to the VAs. The exact policy reversal that produced the cancellation pattern of tiny, unprofitable orders.
2. Authority creep — from documents to supervision to restructuring opinions. Started as document preparation for Balkan agreements. Marwan to Konrad in chat: "My advise leave jelena caz she not busy at all and I made her in charge of making sure we get daily reports." Over time expanded into VA supervision (without operational competence verified) and then into restructuring opinions — without a single measurable operational deliverable matching that authority growth.
3. "Noted" / "will check" pattern across hundreds of exchanges. Documented signature response: "Noted" / "I will check it out" / "let me know when..." across the Konrad-Jelena thread (5,051 lines, 1,215 Jelena mentions). The acknowledgements arrive fast; the operational follow-through does not. Konrad to VA-Communication 11 May: "Almost everything I heard from her about what she would 'handle,' 'fix,' or 'take care of' simply never materialized in reality."
4. Created VA WhatsApp groups excluding Olga — the direct supervisor. Olga's formal escalation 11 May (verbatim): "You decided to move all communication to WhatsApp and created multiple groups, including groups for the VAs that I directly supervise, without even adding me to those groups. What's even more concerning is that you started assigning tasks and communicating with my VAs directly, despite them being under my management. They even asked you why I'm not in these groups, and you skipped the answer." Direct breach of the chain of supervision.
5. Style of communication when challenged — positional, not operational. When Olga publicly raised the exclusion issue (11 May, VA-Communication channel), Jelena's documented responses, verbatim: "Careful — disrespect looks ugly on you" · "why u are spying on my private stuff bro" · "no time for this" · "u did weeks back" · "u are annoying bro" · ":D at least I have personality" · "just mems bro, whats wrong with u, why u didnt share my pool pic too". The operational complaint received an Instagram-screenshot deflection.
6. 29 April 2026 · the disengagement signal. Konrad: "Could someone tell me what is happening why don't you join to the discussion? We count on you @Jelena @Ashik @SHAHAB SHAIKH @Quickplus Recruitment - Vipin". Jelena's response: "busy now - full house." The VA Supervisor declining operational presence in the central coordination channel.
7. The 14 April rupture · Discord migration refused. Konrad asked the Dubai team to migrate from WhatsApp to Discord (auditable, structured). Jelena refused because the move would have made Bipin and Shahab's slow response patterns visible across the team. Konrad's same-day diagnostic: "Bipin and Shahab they are so useless. I cannot believe they are still working under QuickPlus." The Dubai coordination layer could not be migrated to an auditable platform because the supervisor's authority depended on the platform being unauditable.
8. The Konrad summary diagnostic (verbatim, 11 May 2026, VA-Communication). "Jelena's promises and her attitude almost like a Sicilian mafia boss · never reflected any real or direct impact on operational performance. In the end, there was far more talk than actual execution." Counterpart to Konrad's own self-criticism in the Strategic Letter — Konrad has acknowledged his own conduct in conflict moments was not professional. But the underlying behavioural pattern existed long before any of his reactions.
Suspended by Official Statement SPrimework_26051115400.pdf · 11 May 2026 · operational scope to be reassigned to Ashik
Neha
QuickPlus Management · Dubai · joined 4 Nov 2025
Arrived late into a structure she did not build. Engagement is administrative, not strategic. A manager who only repeats "let's discuss this with management" when their team is in conflict is not managing — they are forwarding. This pattern has repeated since November 2025.
1. Imposed commission structure without understanding the markets — 5 November 2025. Verbatim, day 2 of her engagement: "Dear Team, we are introducing a new target and commission structure effective immediately. Each VA is required to achieve a minimum target of 15 successful demands. No commission will be applicable unless the target is achieved. €10 per 100% completed delivery." The structure was so unclear that Marcin had to ask follow-up questions about what "15 demands" meant and when the commission triggered. Target imposition before market understanding — the inverse of operational management.
2. Default communication pattern: "I will check on this as priority." Konrad's specific escalation 14 Feb 2026 (verbatim): "@Neha I am calling on you to take immediate action and plan the necessary restructuring within the company if things are going to continue like this." Neha's response, 21 minutes later: "I will check on this as priority." No documented follow-up action in the next 30 days. Repeated across the VA group with limited visible follow-through.
3. Sided with WhatsApp-over-Discord shift quickly — alignment with internal politics, not independent judgment. When Ola raised the operational case for Discord (10 May 2026 — auditable, structured, channel-separated, integrating with the incoming CRM), Neha's response was a long defence of WhatsApp ending with: "Peace out pls for now and lets discuss this again after we have all pros and cons of same @Ola Myśliwiec." Operational pushback received "peace out" — a manager closing the conversation rather than engaging the substance.
4. No evidence of having challenged Marwan's decisions on behalf of operational reality. A strong manager in this position should be the one telling Marwan when the operations team is wrong. Across 5,000+ lines of cross-cutting channel records covering 6 months of operations, there is no documented instance of Neha pushing back internally on operational decisions that produced field harm. Olga's 26 Feb candidate-quality red flag, the 67-resignations narrative, the trailer-driver delivery failures — none of these received an internal challenge through this channel.
5. Recordings / meeting follow-through. Ola requested (5 Nov 2025): "I'd like to listen too :) Can you also record future meetings and send them to us? It will also be very helpful for me to familiarize myself with the structures and processes :) If yes I suggest uploading all recordings to discord channel - VA meetings." Neha: "Sure, we do plan such meetings." Six months later, no recordings uploaded; no meetings-to-recordings infrastructure built.
6. Across the 14-VA confidential Process Review, Neha is bracketed inside the QuickPlus team scored 18+ / 30− (ratio 0.6:1). The operational layer she manages rates her function the same way they rate Jelena's — slow, incomplete, unclear in ownership.
Management function not delivering · "forwarding" pattern documented across 6 months · scope reassignment recommended
Shahab Shaikh
Recruitment coordinator · Dubai office
Konrad's verdict, 14 April: "Bipin and Shahab they are so useless. I cannot believe they are still working under QuickPlus."
Trailer-driver mislabel incident. Sent an update to Polish channel labelled "trailer driver." Konrad: "Are you sure?" Shahab: "sorry this is not trailer driver, unskilled worker, my bad." Position confusion on a single message.
Lithuania trailer-driver order · Case 13. 50-trailer-driver order with zero candidates currently linked in the snapshot. Konrad directive: "Please leave this market entirely Shabab · all candidates will be handled by PRAXIS." Market removed from his portfolio in operational response to the documented delivery failure.
Behavioural pattern across conferences and live calls. Visibly lost in the agenda — unable to track which order, customer, or country is being discussed. Close-minded — pushes back on new processes (Discord migration, primework360 routing, AI parser) before understanding what is being proposed. Unfocused and distracted — context-switches mid-sentence, returns to the call having missed the directive, asks questions already answered three minutes earlier. Does not listen. Konrad's instructions are repeated 2-3 times across separate calls and still come back as "sorry, my bad" mislabels (trailer-driver vs unskilled-worker is the visible surface symptom; the underlying pattern is a coordinator who is not present in the conversation he is being paid to coordinate).
Replacement candidate to be displaced by primework360 AI Document Parser + automated routing
Bipin (Vipin)
Coordinator · Dubai office
Konrad's verdict, 14 April: "Bipin and Shahab they are so useless." Paired in the indictment with Shahab.
VA Process Review Q9 testimony (Milica, Slovenia): "Responses are too slow. We do not always know who is responsible for what." The "who is responsible" ambiguity describes precisely the coordinator layer.
The 20-point decree retained him. Point 8 of the decree assigns "CV handling, processing, coordination, administration" to a Dubai team that includes Bipin — the same person Konrad named as a bottleneck three weeks earlier.
Behavioural pattern across conferences and live calls. Mirror image of Shahab — the two operate as a single coordination void. Lost in the operational picture (which customer, which order, which country, which status — pick one, he cannot place it). Close-minded — defends the existing WhatsApp-and-forwarding workflow against every proposed structural improvement (Discord, primework360, AI routing) without engaging with the substance. Unfocused and distracted — drifts off the topic on calls, replies to messages from yesterday's thread mid-discussion of today's escalation, then asks for the directive to be re-sent. Does not listen. The "responses are too slow · we do not always know who is responsible" testimony from the VA review (Milica, Q9) is the field-level diagnosis of exactly this: instructions go in, nothing comes out, and the next call starts from zero as if the previous one never happened.
Functions automated by primework360 modules on 18 May 2026
Syed Rahman
Coordinator · Dubai office
Bracketed with Shahab and Bipin in Konrad's 11 May summary: "I don't need Jelena, Shahab, Bipin, Quality dept and Developers. I need only Ashik."
Coordinator layer pattern. The three-name layer (Shahab, Bipin, Syed) is the structural bottleneck inside QuickPlus's own direct-sourcing pipeline. This is the layer that handled 731 worker-positions of demand across 89 customers in the QuickPlus-direct queue — the CRM snapshot of which now shows zero remaining candidate linkage (cancellation-unlink artefact; per-customer chat extraction needed to recover the historical fulfilment numbers).
The decree empowered this layer further. Decree point 8: "the Dubai team will act as central operations" — assigning more authority to the team that produced the failure pattern.
Functions replaceable by automated routing — primework360 escalation rules
Dubai Quality Team
Internal QA / candidate review · Dubai
The "67 candidates resigned" narrative. Repeatedly relayed to Marwan as a Poland-side problem. Konrad's forensic reconstruction proved the narrative false in every traceable case — yet it continued being relayed during restructuring discussions.
The candidate-quality failure (Olga's 26 Feb red flag). "Fake or heavily embellished CVs… do not speak English… cannot do anything." This is what the Quality team was supposed to catch before candidates reached employers. The pyjama-interview incident (Case 19) is what happens when it does not.
The filter is the problem. Marwan's operational reality reached him through this team's summaries. The summaries did not match the CRM. The decree was based on the summaries.
I genuinely do not understand why this department was created in the first place. They had every tool: access to our bank accounts, full Upwork access, the entire VA payment and settlement layer, and the operational reports (collected by Jelena). With that access, the bare minimum expectation is initiative — flagging risks, raising concerns, recommending interventions. For the entire period they have existed I have not seen one such initiative. No alerts. No warnings. No consultation. Nothing escalated to us before it became a problem. Neha did not even shake my hand when I came to Dubai — that level of basic professional engagement was absent. It is absurd. What kind of people are working there. They reacted to nothing, warned about nothing, consulted on nothing, communicated nothing — so what is the department for? If they communicated nothing then I have to assume they had no objections and no concerns about anything that was happening. Either the department is purely decorative, or it is actively filtering reality before it reaches Marwan. Both readings end at the same conclusion: the function as it exists today does not justify the cost.
To be displaced by audit-trail-by-default in primework360
"Dubai CRM Developers" — The "Development Team"
EXTERNAL / QUICKPLUS RETAINED · Laravel/Concord CRM
The headline: A monthly cost line item against an output that is essentially non-existent. I raised the underperformance of this team with you many times and asked for them to be replaced or restructured. Nothing happened — so I took my own action with Aleks and built what they were supposed to build, at a fraction of the cost. The system going live on 18 May is the proof.
Cost: approximately 3,000 AED per developer per month, multiple developers retained over multiple months. Output: a CRM with persistent speed issues, unresolved server errors and basic operational gaps.
Marwan's own assessment, 2 April: "We have spent over 2 million AED on prime work · we cover only less than half." The CRM this team has been patching for 16 months covers less than 50% of operations.
Parallel build that actually shipped: While they did not ship, Aleks and I built primework360.com — the actual new CRM — in parallel at a fraction of the cost. Konrad to Jelena, 9 April: "Very soon we will not need these developers. The new CRM is coming. Few weeks maximum I believe."
The cost structure is upside down: Their continued retention while the Poland infrastructure side is being asked to take pay cuts is the clearest single example of how the current cost structure is inverted — paying premium for non-delivery in Dubai while squeezing the side that actually produces.
Decommissioned with the Laravel/Concord CRM · 18 May 2026 · replaced by primework360.com
Marwan Khalifa Qasqoos
Owner · QuickPlus Group · Dubai
Konrad's diagnostic, 11 May: "You are not inside the groups daily. You are not directly inside the operational pressure daily." The principal who must make the decisions has not been close enough to the daily operation to see what this audit consolidates.
Decisions arriving as decrees. The 20-point decree was issued as a 102-line WhatsApp message after "this drama" dismissal of the Jelena Instagram concern. The decree was authored from outside the operational reality this audit documents.
Counter-evidence for fairness. Marwan funded the European build-out (his stated AED 2.1M). Marwan brought Konrad to Dubai in January 2025. Marwan kept re-engaging despite conflict. Marwan asked to keep Ashik in any forward structure. He is not absent — he is filtered. Removing the filter restores his decision-making.
Re-attachment to operational reality via this audit + primework360 audit-trail
Mohammed Ashik
Project Manager · QuickPlus · Dubai
Konrad's verdict, 11 May: "I don't need Jelena, Shahab, Bipin, Quality dept and Developers. I need only Ashik."
Marwan immediately, same evening: "I will keep Ashik." One of very few names both principals agree on without negotiation.
Operational honesty. Across the 16-month record, Ashik is documented correcting Shahab's errors (Case 18 mis-assignment), responding to escalations promptly, and giving Konrad straight answers when relayed information would have been easier. The "bilateral asset" — if the partnership survives in any form, Ashik is the executive thread.
PROMOTE · VA coordination scope reassigned from suspended Jelena role
Olga's escalation pattern · context for Jelena & Neha accountability
It was not one complaint from one person. It was six months of documented Polish-side escalations meeting the Dubai-side "noted / will check" wall.
26 Feb 2026 · Olga → VA-Communication channel · formal escalation
"there are fake or heavily embellished CVs · candidates do not present themselves professionally in meetings · candidates often do not speak English even though it is mandatory · candidates without experience in physical work, this only comes out during the interview when they admit they 'cannot do anything'."
Proposed remediation: joint call VA + Polish team + Dubai team. No call scheduled in next 30 days.
Proposed remediation: joint call VA + Polish team + Dubai team. No call scheduled in next 30 days.
~April 2026 · Olga → VA-Communication · escalation #2
"Our VAs are increasingly saying they don't want to continue working here because their efforts go to waste. The main problems are poor communication with the people handling candidates and sending candidates who are completely misaligned with client expectations. It's like someone orders a salad, but gets a burger instead — and is then asked if that's okay."
29 April 2026 · Olga → VA-Communication · the breakage moment
"Hey, is anyone in Dubai still working? People have been waiting a really long time for your replies — sometimes for weeks. It's not just about discord, but also CRM. This isn't normal."
Then: "Ashik, you're not the only one working here. You're the only one handling everything — it's too much for you to handle alone :("
Konrad tagged Jelena, Ashik, Shahab, Vipin. Jelena's response 3 minutes later: "busy now - full house."
Then: "Ashik, you're not the only one working here. You're the only one handling everything — it's too much for you to handle alone :("
Konrad tagged Jelena, Ashik, Shahab, Vipin. Jelena's response 3 minutes later: "busy now - full house."
10 May 2026 · Olga → VA-Communication · the Discord pushback
"In Europe, WhatsApp is generally not used as a primary business communication platform in structured operations like this. From an operational perspective, Discord is simply much more convenient and transparent. I clearly said during Thursday's discussion that I did not want to make changes like this without consulting Konrad first, and the response I received was that 'there is nothing to consult.' I do not think this is the right way for us to make operational decisions that affect the whole team. The main issue seems to be personal reluctance toward Discord rather than actual operational problems."
Neha's response: a long defence of WhatsApp ending with "Peace out pls for now."
Neha's response: a long defence of WhatsApp ending with "Peace out pls for now."
11 May 2026 · Olga → Jelena directly · the exclusion confrontation
"I need to address something that honestly feels very unprofessional to me. You decided to move all communication to WhatsApp and created multiple groups, including groups for the VAs that I directly supervise, without even adding me to those groups. What's even more concerning is that you started assigning tasks and communicating with my VAs directly, despite them being under my management. They even asked you why I'm not in these groups, and you skipped the answer. My VAs are very honest with me; they sent me screenshots and complained that this change is really bad and poorly communicated."
Jelena's responses: "Careful — disrespect looks ugly on you" · "no time for this" · ":D at least I have personality" · "just mems bro."
Jelena's responses: "Careful — disrespect looks ugly on you" · "no time for this" · ":D at least I have personality" · "just mems bro."
Read this together, brother. Five formal Polish-side escalations across six months, raising candidate quality, comms structure, supervisory access, and operational responsiveness — each one met with deflection, dismissal, or silence. The 11 May suspension PDF for Jelena and this audit's call for Neha's scope reassignment are not reactions to a single bad day. They are responses to a documented six-month pattern of operational concerns reaching the Dubai-side management layer and being filed under "noted."
The 20-point decree centralizes operations onto a team that, by named individual, includes: a suspended supervisor with a documented "narrative over execution" pattern, a manager who responds "I will check on this as priority" to operational crisis escalations, two coordinators Konrad calls "useless," a Quality team that produced false narratives, and a developer group whose CRM Marwan himself says covers "less than half." The decree empowers exactly the people the forensic record shows did not deliver — and assigns secondary status to Ashik, the one named operational asset both principals agree on.
The markets are not the hard part. The team is.
Every operational claim that "we cannot find candidates" or "the regulations are difficult" or "the embassy is slow" needs to be tested against a simple fact: LinkedIn, Facebook, and every recruitment platform in the GCC region are flooded daily with visa-eligible workers from Ukraine, Albania, Bulgaria, Romania, Philippines, India, Vietnam, Nepal, Indonesia, Sri Lanka and Bangladesh. The candidates exist. They are reachable. They have documents. What is missing is not supply — what is missing is the Dubai operational team's ability to operationalize a market they do not already know.
Knowledge gap
What the team does not know about the markets it is supposed to serve
Bank-statement check (Ukraine). Four out of five Egyptian candidates failed a standard embassy document requirement that should have been verified before any candidate entered the pipeline. This is not exotic knowledge — it is basic embassy intake. The team did not have it.
Trailer-driver salary calibration (Ukraine). Marwan acknowledged: "Gas welders will be very hard to get … in dubai they make over 1000 euro." But the demand letters were issued anyway, with Ukrainian-market salaries that could not compete. No upstream market-rate check.
Order-batch sizing (cross-market). The Status Orders Case 22 Natália Bačíková 4-1-1-1 drip-feed pattern reflects a Dubai-side default of "send what we have" rather than understanding that recruitment for 50 cooks requires presenting batches of 10. Konrad has had to write this rule into chats multiple times.
Team operates on knowledge it already has · cannot acquire new market expertise without coaching it does not get
Execution gap
What the team is asked to do and what they actually deliver
67 follow-up requests in Romania alone. Theodora chased relentlessly for status. The chat responses came fast (0.2h median). The candidates did not. Execution capacity is decoupled from chat responsiveness — the team replies but does not deliver.
38 active customers right now have 0 candidates linked. Signed contracts. Real employers. Workers ordered. Zero currently in process. 28.4% of the live pipeline. The same pattern that produced the 122-customer cancellation file is replaying — in real time, while this report is being read.
"3 of 5" delivery pattern (Bulgaria · Georgi's confidential testimony). Client orders 5, Dubai delivers 3, Dubai pushes Georgi to schedule the interview with 3. Georgi: "This is not serious." Operational corner-cutting that the VA layer has to absorb and explain to clients.
Pattern of accepting orders the team cannot fulfil · execution discipline missing at the coordinator level
Adaptability gap
How the team handles new markets, positions, or sourcing channels
Ukraine collapse · partner-championed market. Marwan personally took over candidate sourcing on 28 October ("Ukraine is in my list"). Even at partner-level engagement, the team could not adapt the standard intake to Ukrainian embassy requirements. If they cannot scale a market you championed, they cannot scale a market they are unfamiliar with.
Lithuania trailer drivers · 1 / 50 currently. Konrad reassigned this market to PRAXIS partner agency months ago because Shahab could not deliver. Even after the structural reassignment, the order sits at 1 of 50. The adaptation (use partner) did not produce results because the coordination back to the partner is broken.
The 67-resignations narrative. When a delivery problem surfaces, the Dubai-side response is to construct a narrative ("the Polish team rejects candidates"; "67 resigned because of delays") rather than to investigate root cause. Narrative construction is a sign of adaptability absence — adaptive teams trace, adapt, retry; non-adaptive teams explain.
Cannot extend the playbook to new conditions · defaults to narrative when results do not match
The market is not the obstacle. LinkedIn is flooded daily with visa-eligible candidates from Ukraine, Albania, Bulgaria, Romania — exactly the markets your team treats as "difficult to source." Of 134 active orders, 67 specify Filipino candidates · 36 Indian · 23 Vietnamese · 21 Nepalese · 13 Bangladeshi · 12 Indonesian · 12 Sri Lankan · 43 accept "All 🌎" (any nationality). The sourcing universe is open. The execution that should match it is what is missing.
From "Don't take any loans, brother" to the triple-detonation of 11 May
Five operational phases. The dates that matter most are the dates that show execution failed before the structure being restructured was built. Each phase ends with an inflection point — the moment the trajectory turned.
The Founding Bet
Verbal 50/50 crystallises in Dubai. Marwan's promise of "375 paid customers." No shareholder agreement signed. First 3–4 month wait periods quietly begin in March 2025.
2025-01-17
Founding
Marwan → Konrad
"Don't take any loans brother. Be honest and tell me what you need."
The line that establishes the founding moral contract.
2025-03
Critical
QuickPlus clients
First 3–4 month wait periods begin — before the Polish team exists
This is the chronological foundation of every other finding in this report. Clients are waiting for candidates before there is a Polish team to blame.
The Build-Out
Marcin joins. Jelena onboarded. The contracts that become the 7-month Sonat failure and the 6-month SBALHZ failure are signed in July. Marwan flags VFS as a 6-month-to-1-year blocker. Nothing structural is done.
2025-07-14
High
Sonat s.r.o. signs
Slovak trailer-driver order signed · will wait 7 months for 2 candidates
The single most-cited delivery failure in Status Orders 200 People. Same week, Polish Warrior signs for 10 trailer drivers · 6-month wait.
2025-07-28
Flagged
Marwan acknowledges
"appointment date take over 6 months to 1 year" — VFS backlog flagged, never addressed
Tata2 raises the first formal escalation. Marwan acknowledges the embassy-appointment problem. No structural action follows in the next 10 months.
The Scaling Mismatch
Polish team formalized: Marcin, Olga, Aleksander, Jan. Romanian entity opens. Polish burn rate roughly triples. Konrad sets Balkan minimum-order policy (4–5 candidates). Marwan signs off "ok 👍."
2025-09-03
Policy
Konrad → Balkans
Konrad sets Balkan minimum order: 4–5 people
The exact policy Jelena will reverse on 1 February 2026 without consulting Konrad. The decision detonates the Konrad-Jelena trust arc five months later.
2025-10
Comms
VA Communication group
VA Communication WhatsApp group created · the cross-border coordination artery
Runs continuously through every subsequent crisis until 11 May 2026.
The Reversal
The minimum-order reversal. The pyjama interview. Olga's candidate-quality red flag. The Status Orders forensic audit. Marwan's mass-layoff disclosure framed externally as "US-Iran war." Tone collapses from brotherly to transactional.
2026-02-01
Trust break
Jelena → Konrad
"He told me to take all even if is 1" — the minimum-order reversal
Jelena reverses the 4–5 minimum without consulting Konrad. The 121-cancellation pattern of tiny, unprofitable orders accelerates from this date.
2026-02-26
Red flag
Olga → VA Communication
"fake or heavily embellished CVs · do not speak English · cannot do anything"
Olga's structured candidate-quality alarm. No structural response at the Dubai-side recruitment-partner level follows in the next 30 days.
2026-02-27
Pyjamas
Georgi → LinkedIn
"This is ridiculous" — Bulgarian client emails Konrad after pyjama interview
MM ТАСК ЕООД. A candidate joined an interview from bed in pyjamas. The Bulgarian employer wrote to Konrad via LinkedIn directly.
2026-03-31
Shock
Marwan → Konrad
"Removed like 100 staff this week. So it's like Covid."
Mass-layoff disclosure framed externally (US-Iran war, fuel prices). Twelve months after the documented recruitment failures began.
The Rupture
CRM rebuild fight. Discord/WhatsApp whiplash. "Sicilian mafia don" verbal rupture. Triple detonation. Polish-team letterhead responses. This audit.
2026-04-02
CRM fight
Konrad ↔ Marwan
"Over 2 million AED · cover only less than half"
Konrad proposes scrapping the dev team, AI-rebuilding the CRM. Marwan refuses. Two operating philosophies, opposite directions.
2026-04-14
Rupture
Konrad ↔ Jelena
Discord vs WhatsApp · the Sicilian-mafia episode
Jelena refuses to migrate to Discord because "Bipin and Shahab need her there." Konrad: "Bipin and Shahab they are so useless." The Konrad-Jelena working relationship cannot be repaired from here — only suspended.
2026-05-11
Triple detonation
Both principals
16:32 decree · evening suspension · 23:47 commission PDF
16:32 Marwan publishes 20-point centralization decree. Evening Konrad publishes Jelena suspension PDF. 23:47 Konrad publishes Commission Model PDF tied to 18 May CRM launch. Three documents, same day, two opposite philosophies.
2026-05-12
Document Day
Polish team
Three Polish-side letterhead responses
Olga (cut −56% to 4,000 PLN), Aleksander (cut −47% to 4,500 PLN), Jan Prokop (Strategic Letter). Conflict moves from chat to letterhead.
2026-05-13
Audit
This document
Master Knowledge Base + this accountability audit compiled
Five days before the scheduled primework360.com launch and commission-model activation date.
What the decree says · what the operational record shows
Each pair below presents the official position alongside the documented operational reality. Both sides are quoted with equal fidelity — selective editing would disqualify the audit. The contradictions are not arguments; they are the structural reasons the restructuring cannot work as written.
OfficialDecree pt 14
"Communication centralized through the Dubai operations team via WhatsApp and email."
11 May 2026 · §6.6 master
vs
Reality14 April rupture
"Centralization" routed through the most fragmented coordination layer — per-employer, per-country WhatsApp groups.
Konrad-Jelena · Discord whiplash
Impact · Critical. The decree claims to solve fragmentation by mandating the most fragmented layer. The same evening's primework360 PDF replaces WhatsApp with a CRM-embedded Chat module. Two opposite mechanisms for the same problem — issued the same day by partners not acknowledging each other's documents.
OfficialRestructuring
Polish-team salary cuts 30–60% to "address cost pressure." Aleksander 8,500 → 4,500 PLN.
11 May proposal · §6.8
vs
RealityCuts the builder
Aleksander is the IT/CRM Specialist building primework360.com — the cost-replacement system the restructuring claims to want.
Aleksander_Ptak_official_statement.pdf
Impact · Critical. Warsaw market floor for these roles is 6,000–8,000 PLN net. The proposed levels are below floor — triggering resignation, not retention. Cutting the salary of the person delivering the cost reduction is structurally incoherent.
OfficialDecree pts 1–4
13 markets "on hold" — claimed to generate no real opportunities.
11 May 2026
vs
RealityActive clients
Bulgaria 119 ordered, Poland 297, Ukraine 67, Slovakia 22 — these are the markets in the cancellation file.
customers_202605122.csv
Impact · High. 5 of the top 6 cancellation markets are in the "on hold" set. The markets are not on hold because they generate no demand — they are on hold because Dubai-side delivery to them failed. The decree treats the symptom as the cause.
OfficialDecree pt 8
"Dubai team will act as central operations · CV handling, processing, coordination, administration."
11 May 2026
vs
RealityJust downsized
Same week: Jelena suspended · "removed like 100 staff this week" · CRM covers "less than half."
§6.5 + 31 Mar + 2 Apr chats
Impact · Critical. The decree centralizes responsibility onto an entity simultaneously losing capacity. The structure is non-executable on the day it is issued.
OfficialRationale
"Current structure is not working properly. Payroll high, communication fragmented, results not matching cost."
Restructuring narrative
vs
RealityPredates structure
3–4 month wait periods documented from March 2025 — before the Polish team existed.
Konrad-Marwan §6.7
Impact · Critical. The foundational causal claim of the restructuring is reversed by chronology. The structure being restructured was built in response to a delivery failure that preceded it.
OfficialCentralize
Authority routed through Dubai operations team — Shahab, Bipin, Syed coordinators.
Decree pt 9, pt 14
vs
RealityBottleneck team
Konrad: "Bipin and Shahab they are so useless." Case 18: Shahab wrong-owner assignment.
Konrad-Jelena · Status Orders
Impact · High. Centralization proposes to fix execution problems by giving more authority to the team that produced the execution problems.
OfficialVA role
"VA role limited to: lead-gen, qualification, demand letter, handover." "After handover, VA involvement ends."
Decree pts 10–11
vs
Reality14 VA testimony
VAs are the only ones the employers talk to. The Process Review shows 12 of 14 VAs describing post-handover client distress.
VA Process Review · Q3 · 14 respondents
Impact · High. The decree removes VAs from the relationship at exactly the moment the relationship is hardest. The employer keeps calling the VA when there is no candidate news from Dubai. Georgi: "i have to lie to them."
OfficialVerbal 50/50
Primework = front-end (infra, expansion). QuickPlus = back-end (sourcing, embassy). Clean split.
Master §1.2 · 26–28 Jan 2025
vs
RealityCross-domain decrees
Marwan's 20-point legislates Primework's domain. Konrad's commission PDF legislates QuickPlus's domain.
§6.4 + §6.6 · same evening
Impact · Critical. Each partner is now legislating the other partner's stated domain. No shareholder agreement exists to mediate. The 50/50 verbal partnership has run out of governance capacity.
primework360 vs. the Dubai operations layer — same job, different architectures
The two principals are not arguing about strategy — they are running two different operating systems for the same business. The decree pushes one direction (centralize through humans). The 18 May CRM pushes the opposite (centralize through audit-trail software).
Primework — software-native
Forward- Comms backboneCRM-embedded Chat module · per-record, audit-trailed, searchable
- CV intakeAI Document Parser · ~$20/month replaces AED 3,000/month coordinator
- Lead → customer8-stage pipeline · one-click Convert
- Status visibilityAuto-dashboard · 30d/60d idle alerts
- Doc generationWizard + AI translation PL/CZ/SK/ME/HU
- VA compensationCommission per placement, uniform across markets
- Source of truthprimework360.com database
- Decision rightsCEO-led, evidence-based, document-trail visible to all
QuickPlus Dubai — human-coordinator
Current- Comms backboneWhatsApp groups · per-employer · per-country · fragmented
- CV intakeManual via Shahab / Bipin / Syed
- Lead → customerMemory-based · no formal pipeline stages
- Status visibilityManual weekly tracker (xlsx) · Quality-team summaries
- Doc generationAleksander on demand · multilingual
- VA compensationUpwork hourly · per-market variance
- Source of truthLaravel/Concord CRM "covers less than half"
- Decision rightsOwner-led, decree-based, filtered through Quality team
Both systems can scale — but only one of them can scale to 20 countries × 1,000 placements/year without proportional headcount growth. The Dubai system requires more coordinators. The Primework system requires more rows in a database. The architectural divergence is the partnership's root structural disagreement.
Ten risk categories, current severity, named instances
Three risks at Critical, six at High, one at Elevated. Every cell anchored to documented evidence in earlier sections. No category sits at Stable — the system has no slack.
R-01
Operational delivery
CRITICAL
122 cancelled customers · ~909 demand exposed · 7-month delivery wait records · trailer-driver 0/201 current linkage
R-02
Recruitment collapse
CRITICAL
122 customer cancellations · 38 active customers with 0 candidates linked now · 28.4% of live book exposed
R-04
Leadership trust
CRITICAL
Konrad-Marwan rupture · Jelena suspension · two PDFs same day
R-03
Financial instability
HIGH
May payroll uncertain · April late · "100 staff removed" · Upwork risk
R-05
Scalability blocker
HIGH
WhatsApp proliferation · 19 → 6 market reduction · "less than half" CRM
R-06
VA exodus risk
HIGH
Process Review demotivation · commission-shock · Gerda "discouraging"
R-07
Dependency risk
HIGH
"I need only Ashik" · Aleksander single-thread CRM · Tata2 legal
R-08
Comms collapse
HIGH
Discord/WhatsApp split · per-employer groups · 12-48h gaps
R-09
Automation resistance
HIGH
Decree centralizes via humans · cuts the builder · 2M AED legacy CRM
R-10
Organizational toxicity
ELEVATED
"Sicilian mafia don" · Instagram episode · bounded by document-trail
Reading the heatmap. Operational delivery, recruitment collapse, and leadership trust are at Critical simultaneously. These three reinforce each other: delivery failure produced the trust break, which produced the unilateral decrees, which now legislate against the only fix (automation). Cooling any one of them cools the other two.
Three paths the next fourteen days can take
The report does not assign probabilities — the 18 May launch is the inflection. Below: what each path looks like operationally and what observable signals indicate the partnership is moving toward it.
Reconciliation through Konrad's framework
Best-case path
primework360.com launches 18 May on schedule. Commission model effective. Marwan accepts Jelena's operational removal. The 13 on-hold markets remain on hold by mutual agreement; the 6 active become joint focused operation. Ashik bilateral. Quarterly review cadence replaces ad-hoc decree.
✓ Konrad — agreed
I accept shutting down the 13 on-hold markets. Concentrate the joint operation on the 6 active markets where delivery can actually be measured.
Signals: CRM live on date · suspension uncontested · May payroll resumes · joint planning established · VA commission earnings positive within 60 days.
Operational separation
Middle path
CRM ships unilaterally. Commission model takes effect on Primework-aligned VAs. Partnership becomes transactional — Dubai pays per placement on referral basis. Primework operates European front-end independently. The 50/50 fiction formally retired without rupture.
✓ Konrad — flexible
On the rest of the VA layer I am open and not insisting on any single outcome — whether we suspend the remaining VAs, keep them on, or roll them onto the new commission model, I will go with whatever you decide. No fight on this point.
Signals: Marwan stops responding to decree-implementation requests · Konrad operates CRM with Primework-aligned VAs only · payments restructured per-placement · Ashik continues bilateral · no new joint contracts.
Total wind-down
Worst-case path
May payroll fails. Polish team departures cascade. VA exodus on commission-shock or Upwork-payment failure. 86-active pipeline bleeds toward the 121-cancelled pattern. Both sides exit; Primework continues as independent Polish entity with CRM as asset.
⚠ Konrad — this is happening NOW
This worst-case scenario is not hypothetical. It is the trajectory we are already on if we do not react fast enough. Right now — WE ARE SINKING. Every day without a decision moves us further down this path, not toward A or B.
Signals: May payroll partial or absent · multi-resignation event in Warsaw · CRM launch slips · statements escalate to legal · active customers begin cancelling at >5/week.
Ten operational moves — every one targets Dubai-side accountability
Each recommendation maps to a documented failure mode above. Priorities: P0 (next 7 days), P1 (next 30), P2 (next 90). Owner and deadline specified.
-
01
Ship primework360.com on 18 May — non-negotiableThe CRM is the substrate of everything below. Slippage gives the 20-point decree default operational authority and compromises the commission PDF's credibility.P0 · 5d
-
02
Formally reassign Jelena's scope to AshikThe suspension removed Jelena from VA coordination. The decree assigned the function to "Dubai operations team" — but that team's senior coordinator is now gone. Ambiguity in week 1 is the highest single execution risk. Ashik named by both principals.P0 · 7d
-
03
Reverse Polish-team salary cuts on Aleksander and OlgaAleksander delivers primework360. Olga absorbs Dubai-side coordination scope. Both below Warsaw market floor at proposed levels — guaranteed resignation, not retention. Cuts produced 3 letterhead replies in 24 hours.P0 · 7d
-
04
Triage the 86 active customers before they become the next 12168 of 86 stalled in Recruiting at 48-day average. 6 of 12 Ukrainian customers at zero candidates after 100+ days. Either close cases sitting in QuickPlus-direct queue without sourced candidates (write down formally) or route them to an external partner agency and restart the clock — no indefinite limbo.P0 · 14d
-
05
Disband the Shahab–Bipin–Syed coordinator layer functionallyFunctions covered by primework360 modules (Inbox AI, AI Document Parser, escalation rules, status dashboard). The named "useless" assessment + the case-level mis-routing (Case 18 Ashik wrong-owner) + the VA Process Review Q9 testimony all converge. Retention without function = continued bottleneck.P1 · 30d
-
06
Centralize VA compensation on commission table uniformlyCommission effective 18 May. Transition needs: per-VA earnings projection, 60-day comparison vs Upwork hourly, withdrawal mechanism for VAs who exit. Without these the commission PDF reads as unilateral cost cut.P1 · 30d
-
07
Write the shareholder agreement that was never signedThe 50/50 verbal has run out of governance capacity (Contradiction #8). Whether path A or B, putting equity, decision rights, and exit mechanism on paper is the precondition for any durable forward arrangement. A 16-month partnership cannot survive another year on memory.P1 · 30d
-
08
Sunset the 77 QuickPlus-direct cancellation backlog explicitly89 cancelled customers had no external partner — they sat in QuickPlus's own direct-sourcing queue with 731 worker-positions of demand. The CRM snapshot shows zero candidates currently linked (cancellation unlinks by design); the historical fulfilment per customer must be reconstructed from the per-customer conversation log. Each customer gets a written close (apologetic, brief, naming the structural reason). Reputation recovery as basic hygiene; the new CRM stops it happening again.P1 · 30d
-
09
Stand up the employer-facing client portalEmployers seeing their own pipeline real-time is the structural answer to "filtered narrative." When data is in the portal, neither Quality team summaries nor selective reports can shape the narrative for either principal. Strongest forward governance piece.P2 · 90d
-
10
Quarterly forensic-cadence reviews using this report's templateA one-time audit decays. Quarterly forensic snapshots using the same KPI set (cancellation file, active pipeline, fill rate, delay) and the same case-by-case structure institutionalize the truth-anchoring this document achieves. The next 16 months include their own audit cadence.P2 · 90d
This audit was built without database access. The next pass needs the IT team to open every customer profile.
Every finding in this report was derived from external evidence — WhatsApp groups, exported CSVs, PDF statements, Process Review survey, the Status Orders 200 People audit. None of it touches the conversation history inside each customer profile in the CRM. Those are the per-customer chat threads, the call notes, the document-exchange logs, the assignment changes, the timeline of who picked up the file when. That is where the real "kwiatki" — the small, traceable failures — sit. They are invisible to me from outside the system.
🔍
What I am asking IT to extract — per customer
For every customer profile in the CRM (134 active + 122 cancelled = ~256 records), export the complete internal-conversation history with timestamps and actor names. Specifically:
- The customer-level chat thread — every message, every assignment change, every status change.
- Document upload events with timestamps — who uploaded what, when.
- Internal notes added by any team member (Dubai-side or Polish-side).
- Owner-reassignment history (especially the Case 18 pattern where Ashik wrong-routed a customer).
- Status transitions with dates — when did the customer move from "Recruiting" to "Sent to Client" to whatever next state.
- Candidate-link/unlink events — when candidates were associated and dis-associated from each customer.
⚙️
Why this matters — and why this audit cannot answer it from outside
The current report can show that 38 active customers have zero candidates linked right now and that 122 customers ended in cancellation. It cannot show how many times the Dubai coordinator logged in, looked at the customer, and did nothing. It cannot show how long the customer profile sat in "Recruiting" status before anyone touched it. It cannot show which coordinator was on the file when the employer last received an update. The customer profile conversation is the receipt for execution — without it, every "we are working on it" claim from the Dubai side is unfalsifiable.
🤖
What happens after extraction
Once the per-customer conversation data is exported (JSON, CSV, or markdown — any structured form), I will run AI analysis across all profiles to extract: (a) median time-in-status per coordinator per market, (b) gap days between any team activity on a file, (c) actor heat-map showing who actually touched which customer, (d) follow-up-without-action patterns (a "noted" reply with no subsequent action visible in the file), (e) candidate-link churn (candidates added then removed without delivery). This produces the next forensic edition of this report — at the per-customer level rather than the per-market level.
📋
Concrete IT request — what to ship
An export endpoint or one-off dump that delivers, per customer ID:
{
"customer_id": "...",
"customer_name": "...",
"country": "...",
"contract_signed_date": "...",
"current_status": "...",
"current_owner": "...",
"status_history": [{ts, status, actor}, ...],
"owner_history": [{ts, owner, actor}, ...],
"candidate_links": [{ts, candidate_id, action: "linked"|"unlinked", actor}, ...],
"messages": [{ts, actor, body, channel: "chat"|"note"|"email"}, ...],
"documents": [{ts, filename, uploaded_by}, ...]
}
"customer_id": "...",
"customer_name": "...",
"country": "...",
"contract_signed_date": "...",
"current_status": "...",
"current_owner": "...",
"status_history": [{ts, status, actor}, ...],
"owner_history": [{ts, owner, actor}, ...],
"candidate_links": [{ts, candidate_id, action: "linked"|"unlinked", actor}, ...],
"messages": [{ts, actor, body, channel: "chat"|"note"|"email"}, ...],
"documents": [{ts, filename, uploaded_by}, ...]
}
Audit completeness requires database access I do not currently have. I am asking the IT team to ship the customer-profile conversation export within 7 days — so that the next edition of this report names execution failures at the per-record level, not just at the aggregate. The aggregate already produced what we have above. The per-customer detail will produce what the team has been hoping no-one would compile.
Marwan — brother.
I am writing the last part of this document outside the formal tone of the rest, because some things should not be said inside corporate language. They should be said in plain words between two people who started this with real trust.
When I came to Dubai in January 2025, I did so because I believed in you. Not in QuickPlus, not in the structure, not in the team — in you. You said the words "trust, integrity, time is money," and I believed every one of them. I left other partners, took financial risks, worked through every personal limit, and built infrastructure that I could have built for someone else.
I still believe in you. That is why this document is not a separation letter. It is a wake-up letter.
You are surrounded by people whose interests are not yours. Their job is to look indispensable to you. My job — as your partner — is to tell you that indispensability is a story they tell, not a reality they create. The three evidence sources in this document show that: 14 VAs in a confidential survey · 24 cases in a forensic audit · one complete market lifecycle in Ukraine you personally championed.
I am not asking you to choose me over them. I am asking you to look at the operational evidence and choose the company over the people you are loyal to. There is a difference. A big one. The first is the choice of a businessman. The second is the choice of a friend. You can be both — but only if you separate the two roles clearly.
Off the record · human to human
But I also need to tell you something honestly as a human being, not only as your business partner.
I put everything on one card for this project. Everything.
And the hardest part for me is not even the financial pressure itself — it is the fact that I was never truly warned about how serious the situation had become. I was kept believing that things were under control while continuing to operate at full speed, continuing to build, continuing to invest my time, my energy, my people, and my future into this operation.
You did not leave me space to protect myself, create alternatives, or stabilize my own situation before all of this exploded.
Today my family is suffering because of it.
I genuinely do not have money right now for:
- office rent
- apartment costs
- basic school expenses
- responsibilities that should never be uncertain at this level
And I am sorry, but this is not how serious partners handle situations like this.
You do not allow someone to continue carrying operational pressure for months while internally the situation is collapsing, and then suddenly introduce restructuring, payment delays, uncertainty, and operational chaos almost overnight.
Because costs do not stop.
Pressure does not stop.
Life does not stop.
And right now, honestly, I feel mentally destroyed by all of this.
Not because the business is struggling — I can survive difficult periods.
But because I increasingly feel like I am being treated not as a partner who carried this project together with you, but as an enemy standing on the other side. That hurts more than the financial situation itself.
If after reading all of this you still believe Jelena, Neha, Shahab, and the current layer are the right team to take Primework forward — say so to me directly, in writing, with the operational reasoning, and I will respect that decision. We can talk about what that means for the partnership.
But if you read this and recognize even half of what I am describing, then the question is no longer whether they leave. The question is when, and with what dignity, and replaced by whom. Hire whoever you want. Build whatever team you want. I do not care about names. I care about competence, contribution, and character. The current team fails on all three, and now we have the evidence to show it.
I am ready to keep building. I am ready to fix what is broken between us. I am ready to put governance, structure, and clean accountability between us so we never end up in another week like this one. But I cannot keep building on a foundation that protects people who do not protect the business.
Read this. Sit with it for two days. And come back to me as my partner, not through anyone else.
Issued under the letterhead of
PRIMEWORK GROUP SP. Z O.O.
Konrad Włodarczyk
Managing Director · Primework Group
Date
13 May 2026 · Revision 2 · Evidence Edition
Every claim traces to a named source. The audit is reproducible.
Where a source is contested, both sides are quoted. Where evidence is silent, the report is silent. This section catalogues the inputs, the integrity boundaries, the residual uncertainties, and the key dates.
Sources analyzed 1 master KB · 13 chats · 6 PDFs · 4 datasets
Primary · Master Knowledge Base. PRIMEWORK_MASTER_KNOWLEDGE_BASE.md — 2,035 lines · compiled 13 May 2026.
Operational datasets (4 — all integrated).
• customers_202605122.csv — 121 cancelled customers (Qty Status parsed for 906 / 75 / 831 aggregate)
• Status_orders_200_people.xlsx — 24 forensic case audits with side-by-side Dubai vs Primework remarks
• VA_Communication__Process_Review__Answers.xlsx — 14 VAs · 12 questions · 13–22 Mar 2026
• VA_Weekly_Tracker_FINAL_MAY.xlsx — 86 active customers · 48.7d avg delay
Conversation archives (13). Konrad-Marwan (7,795 messages), Konrad-Jelena (2,089), VA Communication (677), Primework-Balkans (4,090), Romania (1,736), country VA groups (BG, CZ, FI, PL, SK, UA), Primework-QP, Primework-Marketing.
PDF statements (7). Strategic Letter / Reality.pdf (Konrad MD · 12 May · Evidence Edition · the synthesizing document this report operationalizes), Commission Model (Konrad 11 May), Jelena Suspension (Konrad 11 May), Olga letterhead (12 May), Aleksander letterhead (12 May), Jan Prokop Strategic Letter (12 May), VApp deck (Primework 3 March).
What was NOT analyzed — integrity boundaries 5 explicit exclusions
Financial P&L not in scope. No access to QuickPlus or Primework general ledger, audited statements, bank records, or month-by-month cash flow. Marwan's "2.1M AED spent" is reported as his stated position, not independently verified. Konrad's "no money left" the same.
Pre-March 2025 not in scope. Marwan's prior East2West venture, original QuickPlus founding, Konrad's pre-Primework career sit outside this 16-month window.
Personal/HR records excluded. Polish team contracts, individual performance reviews, personnel files not in scope. Salaries appear only where named in formal letterhead responses.
Dubai-side internal communications not seen. This report reads Konrad-Marwan and Konrad-Jelena threads. It does not see Marwan-Jelena, Marwan-Ashik, or Marwan-Quality-team internal channels. Inferences about Dubai-side internal dynamics restricted to what is observable from the Konrad-facing record.
Marwan's case preserved verbatim, not adjudicated. Where Marwan's positions appear, they are quoted from his own messages. The chronological adjudication of competing claims (Contradiction #5) addresses the documentary record, not Marwan's full operational reality.
Confidence levels & quote discipline Evidence rules
High confidence: claims anchored in named documents, datasets, or timestamped multi-source corroboration. The 906/75/831 aggregate (record-level), the VA Process Review (per-VA-named), the letterhead PDFs (verbatim), the 20-point decree (verbatim), the Status Orders 200 People (case-level) all sit here.
Medium-high: behavioral patterns supported by multiple convergent instances across timestamped chat record. The Konrad-Jelena 4-stage arc, the Marwan tone collapse, the Polish-team formalization curve.
Single-side: interpretive claims supported by one party's reconstruction (e.g. Konrad's forensic refutation of the "67 candidates resigned" narrative). Flagged where they appear; not treated as bilaterally established.
Quote discipline: each direct quote kept under 15 words; no source quoted more than once verbatim except where the source itself contains multiple irreplaceable phrases (the 20-point decree). Polish, Croatian, Bulgarian originals preserved where operational weight is in original wording.
Glossary · 12 operational terms Essential terms
VA — Virtual Assistant, country-specific recruitment specialist working primarily via Upwork.
Demand letter — Formal employer document confirming intent to hire foreign workers; required for work permit application.
MWO accreditation — Migrant Workers Office (Philippines) accreditation of foreign employer; required for Filipino candidate deployment.
Corridor / coordinator — Dubai-side intermediary managing flow between a recruitment source country and a destination market.
Handover — Moment a VA transfers an employer relationship to operations. Under the 20-point decree, the moment the VA's involvement ends.
CRM Primework360 — primework360.com · Konrad/Aleksander-built platform launching 18 May 2026.
Commission model — €100 per placed candidate (€50 on contract signing + €50 on permit issuance).
The 6 active markets (per decree) — Macedonia, Greece, Hungary, Romania, Serbia, Montenegro.
The 13 on-hold markets — Finland, Estonia, Latvia, Sweden, Lithuania, Ukraine, Bulgaria, Czech, Slovakia, Albania, Slovenia, Bosnia, Croatia.
The triple detonation — Three documents on 11 May 2026: Marwan's 20-point decree, Konrad's Jelena suspension PDF, Konrad's commission model PDF.
Document Day — 12 May 2026; three Polish-side letterhead responses (Olga, Aleksander, Jan Prokop).
The 50/50 fiction — Unrecorded verbal partnership structure; no shareholder agreement ever signed.
Compressed master timeline · key dates 21 inflection points
2025-01-17 — Marwan: "Don't take any loans brother."
2025-01-26 → 28 — Konrad in Dubai; verbal 50/50 crystallises.
2025-03 — First QuickPlus clients; first 3–4 month wait periods begin.
2025-05 — Marcin joins; Jelena onboarded; Theodora onboarded.
2025-07-14 — Sonat signs for 10 trailer drivers (→ 7-month delay).
2025-07-28 — Tata2 first formal escalation; Marwan flags VFS scarcity.
2025-09-03 — Konrad sets Balkan minimum order: 4–5 people.
2025-09 — Polish team formalized; burn rate ~triples.
2025-10 — VA Communication WhatsApp group created.
2026-01-17 — Lumina formal introduction.
2026-02-01 — Jelena reverses minimum-order policy without Konrad.
2026-02-26 — Olga's candidate-quality red flag.
2026-02-27 — Pyjama interview incident (Bulgaria).
2026-03 — Status Orders 200 People audit; Claude AI discovered.
2026-03-13 → 22 — VA Process Review window · 14 confidential responses.
2026-03-31 — Dubai mass layoff disclosed.
2026-04-02 — CRM rebuild fight; "2M AED, covers less than half."
2026-04-14 — Konrad-Jelena verbal rupture (Sicilian mafia episode).
2026-05-11 (16:32) — Marwan's 20-point centralization decree.
2026-05-11 (evening) — Konrad publishes Jelena suspension PDF.
2026-05-11 (23:47) — Konrad publishes commission model PDF.
2026-05-12 — Three Polish-side letterhead responses.
2026-05-13 — Master KB + this audit compiled.
2026-05-18 — primework360.com launch + commission model effective.