Cinci variante comparate clar, ca sa stii pe care s-o alegi.
Five variants compared clearly, so you know which one to choose.
Comparam Legacy, Graph, SharePoint, Dataverse si SQL in limbaj de business, nu tehnic: ce promite fiecare varianta, cui i se potriveste cel mai bine si ce compromis trebuie asumat constient. Matrix-ul este un instrument de decizie pentru client, nu o lista de argumente de vanzare.
We compare Legacy, Graph, SharePoint, Dataverse and SQL in business language, not technical: what each variant promises, who it fits best and what trade-off must be consciously accepted. The matrix is a decision tool for the client, not a list of sales arguments.
Comparison matrixComparison matrix
Cinci optiuni, comparate in limbaj de business si adaptare pe client.
Five options compared in business language and client adaptation terms.
Matrix-ul nu incearca sa impinga o singura varianta. Rolul lui este sa ajute clientul sa vada repede care este alegerea potrivita pentru contextul sau si ce trade-off trebuie asumat constient.
The matrix does not try to push a single variant. Its role is to help the client see quickly which option fits their context best and which trade-off must be consciously accepted.
| CriteriuCriteria | Legacy | Graph | SharePoint | Dataverse | SQL |
|---|---|---|---|---|---|
| Cum o pozitionamHow we position it | solutie validata, inca disponibilavalidated solution, still available | varianta-punte: UI Excel pastrat, backend modernizatbridge path: preserved Excel UI, modernized backend | modernizare rapida si accesibilafast and accessible modernization | varianta premium pentru enterprisepremium enterprise path | varianta pentru performanta si analyticsthe performance and analytics path |
| Cui i se potrivesteBest fit | clientului care vrea continuitate si schimbare minimathe client who wants continuity and minimal change | clientului care vrea sa pastreze Excel-ul, dar sa elimine Accessthe client who wants to keep Excel, but eliminate Access | clientului care vrea viteza si cost controlatthe client who wants speed and controlled cost | clientului care vrea control, audit si standard enterprisethe client who wants control, audit and enterprise standards | clientului care vrea performanta, reporting si flexibilitate tehnicathe client who wants performance, reporting and technical flexibility |
| Promisiunea principalaMain promise | pastrezi ce functioneaza dejayou keep what already works | pastrezi UX-ul Excel si modernizezi accesul la dateyou keep the Excel UX and modernize data access | ajungi repede la o platforma modernayou reach a modern platform quickly | castigi control si livrare maturayou gain control and mature delivery | castigi viteza si putere de analizayou gain speed and analytical power |
| Nivel de adaptareAdaptation level | adaptam fluxuri si configurari pe modelul actualwe adapt workflows and configuration around the current model | adaptam formulare, mapari, OAuth2, cache si configuratia listelorwe adapt forms, mappings, OAuth2, caching and list configuration | adaptam campuri, roluri, aprobari si rapoartewe adapt fields, roles, approvals and reporting | adaptam guvernanta, securitatea si modelul operationalwe adapt governance, security and the operating model | adaptam structura de date, integrarea si modelul de reportingwe adapt the data structure, integration and reporting model |
| Viteza de rolloutRollout speed | cea mai mica schimbare pentru echipa actualathe smallest change for the current team | rapida pentru clientii deja pe Excel/VBAfast for clients already on Excel/VBA | cea mai rapida dintre variantele web modernethe fastest among the modern web variants | mai lenta, dar cu mai mult controlslower, but with more control | moderata, in functie de complexitatea tehnicamoderate, depending on technical complexity |
| Nivel de guvernantaGovernance level | limitat, dar familiarlimited, but familiar | mediu, peste legacy datorita OAuth2 si accesului direct in cloudmedium, above legacy thanks to OAuth2 and direct cloud access | bun pentru SMBgood for SMB | foarte ridicatvery high | ridicat daca este implementat disciplinathigh when implemented with discipline |
| Scalare si volumScale and volume | potrivita pentru continuitate, nu pentru crestere agresivafit for continuity, not aggressive growth | mica spre medie, cu atentie la pragurile SharePointsmall to medium, with attention to SharePoint thresholds | mica spre mediesmall to medium | medie spre enterprisemedium to enterprise | medie spre foarte maremedium to very large |
| Forta pe reportingReporting strength | raportare familiara din modelul actualfamiliar reporting from the current model | buna pentru operare in timp real si raportare familiara in Excelstrong for real-time operations and familiar Excel reporting | buna pentru nevoi standardgood for standard needs | puternica pentru control operationalstrong for operational control | cea mai buna pentru analytics si Power BIthe strongest for analytics and Power BI |
| Profil de costCost profile | cost mai mic al schimbarii, dar limite pe termen lunglower change cost, but long-term limits | cost controlat, fara Access si fara licente Power Platform Premiumcontrolled cost, without Access and without Power Platform Premium licenses | cea mai accesibila varianta web modernathe most accessible modern web option | cost mai mare, justificat de controlhigher cost, justified by control | cost variabil, adesea bun la volum marevariable cost, often strong at larger scale |
| Principal trade-offMain trade-off | mai putin spatiu pentru crestere si guvernanta avansataless room for growth and advanced governance | fara mod offline, cu dependenta de Excel desktop, internet si competenta VBAno offline mode, with dependency on Excel desktop, internet and VBA capability | compromis la volum si guvernantatrade-off on volume and governance | cost si setup mai marihigher cost and setup effort | complexitate tehnica mai marehigher technical complexity |
Citire rapida: `Legacy` pentru continuitate, `Graph` pentru UI Excel cu backend modernizat, `SharePoint` pentru viteza, `Dataverse` pentru enterprise, `SQL` pentru performanta si analytics. In toate cazurile, implementarea se adapteaza la cerintele clientului.
Quick read: `Legacy` for continuity, `Graph` for preserved Excel UI with a modernized backend, `SharePoint` for speed, `Dataverse` for enterprise, `SQL` for performance and analytics. In all cases, implementation is adapted to the client requirements.
Cum folosesti matrix-ulHow to use the matrix
Porneste de la nevoia clientului, nu de la preferinta tehnologica.
Start from the client need, not from a technology preference.
Cand vrea continuitate
When continuity matters
Legacy poate fi recomandarea corecta daca schimbarea minima si familiaritatea sunt critice.
Legacy can be the right recommendation when minimal change and familiarity are critical.
Cand vrea un pas intermediar credibil
When a credible bridge step matters
Graph intra in discutie atunci cand clientul vrea sa pastreze Excel-ul, dar sa elimine Access si sync-ul fragil.
Graph enters the conversation when the client wants to keep Excel, but remove Access and the fragile sync layer.
Cand vrea control sau performanta
When control or performance matters
Alegerea merge spre Dataverse sau SQL, in functie de accentul pe guvernanta versus analytics si optimizare tehnica.
The choice moves toward Dataverse or SQL, depending on whether governance or analytics and technical optimization matter more.
Ce evita matrix-ulWhat the matrix helps avoid
Cele mai frecvente alegeri gresite pe care le prevenim.
The most common wrong choices we help prevent.
Modernizare fortata
Forced modernization
Nu impingem clientul spre o varianta moderna daca Legacy rezolva mai bine nevoia de continuitate.
We do not push the client toward a modern variant if Legacy better solves the continuity need.
Subdimensionare
Undersizing
Nu vindem SharePoint acolo unde volumul, controlul sau reporting-ul cer deja un nivel superior.
We do not sell SharePoint where volume, control or reporting already require a higher level.
Supradimensionare
Oversizing
Nu impunem Dataverse sau SQL doar pentru ca suna premium daca proiectul nu cere acel nivel.
We do not impose Dataverse or SQL just because they sound premium if the project does not require that level.
Proces comercialCommercial process
Cum folosim matrix-ul intr-o discutie reala cu clientul.
How we use the matrix in a real client discussion.
1. Clarificam obiectivul dominant1. We clarify the dominant objective
Vedem daca discutia este despre continuitate, viteza, control sau performanta.
We determine whether the conversation is about continuity, speed, control or performance.
2. Eliminam variantele nepotrivite2. We eliminate the wrong variants
Taiem rapid optiunile care nu servesc contextul real al clientului.
We quickly remove the options that do not serve the client real context.
3. Pozitionam trade-off-ul3. We position the trade-off
Explicam limpede ce castiga clientul si ce compromis isi asuma.
We explain clearly what the client gains and what compromise is being accepted.
4. Intram in adaptari4. We move into adaptations
Abia dupa alegerea directiei definim fluxuri, roluri, date si raportare.
Only after choosing the direction do we define workflows, roles, data and reporting.
Mesaje de incredereTrust messages
Ce ar trebui sa inteleaga clientul dupa ce vede matrix-ul.
What the client should understand after reading the matrix.
Legacy nu este ascunsa
Legacy is not being hidden
Daca aceasta este varianta potrivita, o recomandam si o livram in continuare.
If it is the right option, we still recommend and deliver it.
Modernizarea poate fi etapizata
Modernization can be phased
Graph, SharePoint, Dataverse sau SQL apar atunci cand aduc valoare reala si cand ritmul clientului o permite.
Graph, SharePoint, Dataverse or SQL enter the conversation when they bring real value and when the client pace allows it.
Orice varianta se adapteaza
Every variant is adaptable
Alegerea platformei este doar inceputul. Implementarea se construieste pe cerintele clientului.
Choosing the platform is only the start. The implementation is built around the client requirements.
FAQFAQ
Intrebari pe care le clarifica matrix-ul foarte repede.
Questions the matrix clarifies very quickly.
Care varianta este „cea mai buna”?
Which variant is the best?
Nu exista o singura varianta cea mai buna. Exista varianta cea mai potrivita pentru obiectivul si constrangerile clientului.
There is no single best variant. There is only the best fit for the client objective and constraints.
Daca un client vrea Legacy, il impingem spre modern?
If a client wants Legacy, do we push them toward modern?
Nu. Daca Legacy este potrivirea corecta, ea ramane o recomandare valida si vandabila.
No. If Legacy is the right fit, it remains a valid and sellable recommendation.
Unde se pozitioneaza Graph?
Where does Graph fit?
Intre Legacy si modernizare completa: pastreaza Excel si VBA, dar muta accesul la date intr-o arhitectura moderna bazata pe Graph API si SharePoint Lists.
Between Legacy and full modernization: it keeps Excel and VBA, but moves data access into a modern architecture based on Graph API and SharePoint Lists.
Dupa matrix urmeaza o propunere fixa?
After the matrix, do you issue a fixed proposal?
Nu. Dupa matrix urmeaza discutia despre adaptari, iar propunerea se construieste pe contextul clientului.
No. After the matrix comes the adaptation discussion, and the proposal is built around the client context.