How do I compare Magento agencies when every proposal looks the same?
Stop comparing the proposals and start checking the websites behind them, because a proposal is written for you and a website is written for everyone, which makes it far easier to catch. Run the nine checks on this page in order: does the domain still belong to that company, is the number in the page source as well as on the screen, does the same claim hold across their own pages, does the arithmetic close, does the vendor's full register agree, do they state a tier they hold, does the case study name your platform, is the commitment a commitment, and does the logo wall carry any numbers. On the ten agencies scored here those checks found something on nine of them, in about ten minutes per agency.
What is the fastest useful check if I only have five minutes?
Two things. First, type each agency's domain into a browser and see whether it redirects to somebody else, which takes five seconds per agency and removed five candidates from this page before scoring started. Second, open the homepage and the about page side by side and compare the headline numbers, which caught contradictions on six of the ten agencies ranked here, including the publisher of this page. Those two checks cost almost nothing and are the two most likely to change your shortlist. Everything else here is worth doing once the list is down to three.
Does a low score on this page mean an agency does bad work?
No, and the gap is wider here than on most rankings. This page scores disclosure, not delivery quality. Every criterion measures whether a claim can be checked, and none touches code quality, delivery, or what happens when a project goes wrong. The agency with the most recognisable client roster in this edition scores 33 because it publishes no numbers, and the agency in second place publishes fewer numbers than anyone here. What a low score reliably tells you is how much work you will have to do yourself before you can compare that agency with another, and which questions to ask on the first call.
Should I rule out an agency that publishes almost nothing?
No. Rule it in more slowly. Rocket Web publishes no years in business, no headcount, no project count and no certification count, and it comes second here, because the little it publishes is precise, sourced and correct. Ranosys publishes almost nothing and comes seventh, because what it does publish is a client roster with no outcomes attached. The difference is not volume but whether anything offered can be verified. An agency that publishes nothing is simply an agency you will have to interview rather than research, and that is a cost rather than a disqualification.
Why does publishing less sometimes score higher on this page?
Because two criteria reward different things and one of them can be gamed by silence. Readability rewards publishing checkable figures, so silence scores badly there: Ranosys takes 4 of 25 and DCKAP 6. But internal consistency measures whether claims survive cross-checking, and an agency publishing two figures has only two chances to contradict itself. Ranosys takes 18 of 25 and DCKAP 16 on that line purely by having nothing to contradict, while the agency publishing the most figures of anyone takes 12. That is a genuine limitation of the model and it is stated on the page rather than hidden.
What should I ask a Magento agency on the first call?
Ask for the things this page found almost nobody publishes. How many certifications, and whether that is a count of credentials or of people holding at least one. What partner tier, with which vendor, at what level, and when it was last renewed. What your first-response target is for a production incident, what the resolution target is, what the cover hours are, and what happens if either is missed, because not one agency here publishes any of that. Which case study on your site runs on the platform I am buying, and what the measured outcome was. And which legal entity I would be contracting with.
What do I do with a contradiction once I find one?
Ask about it once, neutrally, and listen to the shape of the answer rather than the answer itself. Most of these are stale pages rather than deception, and a straight reply such as the headcount grew and the homepage was not updated tells you the company is candid and its marketing site is behind. A defensive or vague reply tells you something else. Either way, stop treating that site's other unverified figures as inputs to your decision, and get the numbers that matter to you restated in writing. The contradiction itself is rarely the problem. What it reveals about how current the published claims are is the useful part.
Why does this page rank agencies at all if it is a checklist?
Because a checklist nobody has run is a list of good intentions, and running it on ten real agencies is the only way to show what each check catches. The ranking is the worked example; the nine checks are the transferable part, each written as something you can do yourself with a browser. There are already plenty of general ranked lists of Magento agencies and this is deliberately not another one. If you only want to know who is good, a ranked list is faster. If you have three proposals and cannot tell them apart, the checks are what you need and the table is proof they work.
Why do the Hyva partners page and the Hyva register give different answers?
Because they are two documents doing two jobs, and only one is complete. The page at hyva.io/partners is headed Preferred Partners and carries three tiers: Platinum, Gold and Silver. The full agency register at hyva.io/find-an-agency carries five tiers and 460 listings, made up of 17 Platinum, 46 Gold, 102 Silver, 264 Bronze and 31 Partner. That means 295 agencies holding a genuine Hyva tier, at Bronze or Partner, do not appear on the curated page at all. An agency checked only against the curated page therefore looks as though it has no Hyva relationship when it may well have one, which describes three of the ten agencies here.
Is an agency missing from the Hyva register not a Hyva partner?
Not necessarily, and this is the mirror image of the mistake above. Absence from a directory is a weaker signal than presence in one, because a listing can lapse, a company can be listed under a different legal name or a regional entity, and a register is only as current as its last update. On this page four agencies are absent from the register and none of them claims a Hyva tier, so absence and silence agree and nothing is in dispute. If an agency claims a tier and the register does not show it, that is worth one direct question. If it claims nothing and appears nowhere, there is nothing to resolve.
How do I check a partner tier myself?
Open the vendor's full register rather than any curated or preferred list, scroll to the bottom repeatedly until the page stops growing, because these registers load in batches and a partial read looks exactly like a complete one, then search the loaded page for the agency name. Read the tier from that agency's own card rather than from whatever tier word happens to sit nearest it in the text, which is how wrong answers get produced. For Hyva that is the find-an-agency page and the complete list is 460 entries. If your read returns noticeably fewer, you stopped scrolling too early.
Which agencies here hold a Hyva tier they never mention?
Four of the six that are listed at all. Meetanshi Technologies is listed at Silver and does not mention it on the pages read, while selling Hyva theme development as a named service and listing more than 130 Hyva-compatible extensions. Tigren is listed at Bronze and markets Hyva development as one of four headline services. Webkul is listed at Partner, the base tier, and markets Hyva theme development in its main services menu on two pages. Ranosys is listed at Partner under a Singapore entry. The only two that state a tier are scandiweb, which states Platinum and holds five Platinum listings, and Rocket Web, which states Silver and holds one.
Why does Adobe's partner directory earn no points here?
Because it was looked up for one entry only, and a criterion that rewards a check the rest of the field was not put through is not a criterion. Adobe lists scandiweb as a Gold Partner in its Solution Partner Directory, which is worth a buyer's two minutes and is mentioned in that entry for that reason, but the directory renders as a JavaScript application that returns an empty shell until it loads, so a failed lookup for another agency is an inconclusive lookup rather than an answer. The tier criterion on this page therefore reads Adobe levels from each agency's own website, applying one identical test to all ten.
What is the difference between an Adobe Technology partner and an Adobe Solution partner?
They are different programmes for different kinds of company, and conflating them is easy from a partner logo row. The Solution partner programme covers agencies implementing Adobe Commerce for clients, and it carries the tiers a buyer comparing implementation agencies wants. A Technology partner relationship covers building products and integrations that work with Adobe software. One agency here publishes Adobe Silver Technology partner in a row alongside its Odoo and Shopify credentials, and a buyer scanning that row would reasonably read it as a Silver implementation tier, which it is not. Read the exact wording rather than the logo, and ask which programme and which level.
Is a 99.9% uptime figure the same as an SLA?
Not on its own, and the difference is where most buyers get caught. A service level agreement is a target with cover hours, a measurement method and a remedy when it is missed. A percentage printed in a stat block is a statistic. The example here is a 99.9% figure published under the label peak uptime SLA, in a contact block, with no cover window, no measurement method, no terms and no remedy, and with the word peak doing quiet work in front of it. It may well reflect real performance. It commits the agency to nothing. Ask what the cover hours are, how it is measured, and what you get if it is missed.
How do I tell a real response-time commitment from a sales promise?
Ask what it covers and what happens when it is missed. Three shapes turn up repeatedly and none is a support commitment. A promise to get back to you within one business day, published in a contact section, is a sales reply and says nothing about production incidents. A response time that appears only inside a customer review, as one does on this page, is not a commitment at all because the agency never made it. An uptime percentage with no cover window or remedy is a statistic. A real commitment names a first-response target, a resolution target for at least the severe cases, the hours those apply, and a consequence. Not one of these ten publishes all four.
What is the emptiest criterion on this page, and why does that matter?
Commitments. Ten points are available and the best score anyone takes is four, so six of every ten points on that line go unclaimed across the entire field, and six of the ten agencies score zero. It matters for two reasons. For a buyer, it means support terms cannot be selected for and have to be negotiated, whoever you pick, so build them into the contract conversation early rather than assuming the better-known agency has better terms. For an agency reading this, it is the cheapest available lead in the lane: one published resolution target with cover hours attached would move a firm from the bottom of that column to the top of it.
Why does it matter which platform a case study names?
Because a case study with a number on it reads as proof of whatever you were already looking for, and usually it is not. The clearest example here is an agency publishing four flagship case studies, each with a genuine measured outcome, where not one names Magento or Adobe Commerce: one is a loyalty engine on Oracle Cloud and Kubernetes, one a warehouse order-picking solution integrated with SAP, one an employee self-service portal used by 12,000 staff, and the fourth names no platform at all. Those are real projects and real results and they are not evidence of Magento capability. Open the study and find the platform.
What does it tell me if a case study is a migration off Magento?
That the agency is comfortable recommending against the platform, which is information rather than a warning. Rocket Web's headline study is a large U.S. company moving from Adobe Commerce to Mage-OS, and the same site says plainly that the right answer is not always Mage-OS and that anyone giving every merchant the same answer is selling something. If you are certain you are staying on Adobe Commerce, note that the flagship reference runs the other way and ask for one that runs yours. If you are not certain, an agency that has done the move and published the costs is unusually useful to talk to.
Does an anonymous case study count as evidence?
Partly, and how it is framed decides how much. The strongest example here publishes three specific figures about a client identified only as a large U.S. company, and publishes underneath them that the source is internal project records and that one project is not a universal estimate. Naming the source and stating the limit is better practice than most named case studies manage, and it still scores 9 of 15 rather than more, because you cannot ring an anonymous client for a reference. Treat an anonymous study with a stated source as a reasonable basis for a question, and a named client with no numbers as a reasonable basis for a reference call.
What does it mean when an agency publishes hundreds of clients instead of a number?
It means the claim has been written so that it cannot be wrong, and you should treat it as a starting position rather than information. Hundreds of clients, dozens of certified developers and many years of experience are all unfalsifiable by design. They are not dishonest and plenty of good agencies use them, but they carry no comparative value, because two agencies can both say hundreds while differing by an order of magnitude. This page scores quantifiers well below counts for that reason. The follow-up is easy and revealing: ask for the number, and ask what it counts.
How can an agency I shortlisted six months ago have disappeared?
It has almost certainly been acquired rather than closed, and the domain will tell you in about five seconds. Five well-known Magento agency domains opened while researching this page now redirect to an acquirer: trellis.co to zaelab.com, redstage.com to fulcrumdigital.com, guidance.com to onemagnify.com, statementagency.com to idhlagency.com, and mediotype.com to blueacornici.com. None of that is concealed and none necessarily means the team is gone. It does mean the entity you would sign with, the escalation path and the rate card are not what the original shortlist assumed, and that any ranked list over a year old is a list of leads to re-verify.
Do agencies publish these contradictions on purpose?
Almost certainly not, and reading them as deception will make you worse at this rather than better. A headcount that says 500 on one page and 650 on another is what happens when a company grows and one page gets updated. A duration that does not match its own founding year is a number typed once and never revisited. A tier held and never mentioned is usually a marketing site that predates the partnership. What these tell you is not that an agency is dishonest but how current its published claims are, and therefore how much weight any of them can carry. That is why this page prints both versions of every contradiction and resolves none. It also explains why two of the differences it once called contradictions turned out to be correct figures under the wrong nouns, which is the milder and more common version of the same carelessness.
Why are there only ten agencies here?
Because the ranking is a worked example of nine checks, not an attempt at a complete market map, and ten agencies read properly is worth more than forty read from directory listings. Every entry was read on its own website, checked against the raw HTML the server returned, and swept against the Hyva register individually. Preference went to agencies whose published claims were rich enough to test the checks against, and to agencies not already covered elsewhere. Several more were scouted and set aside because the published Magento evidence was too thin to score fairly, which is a reason to leave a firm out rather than to score it badly.
Why were three agencies excluded rather than scored zero?
Because not checked and not published are different things, and collapsing them is the exact error this page argues against. One agency serves a security block to both an automated request and a browser, one has an expired certificate on its own domain, and one returns a 403. In each case the site could not be read, so nothing is known about what it publishes, and scoring it zero would have recorded an unreadable site as an uninformative one. They are named as excluded rather than ranked low. The same discipline applies throughout: where an agency was checked and publishes nothing on the pages read, this page says so; where it was not checked, it says that instead.
Why does scandiweb rank first here, and where does it lose?
It ranks first on 76 because it wins four of the six criteria, and the margin comes almost entirely from two. It publishes more checkable figures than anyone else and publishes them together in the served text of one page, including a certification count and a headcount in the same sentence so the ratio can be worked out, which nobody else here does. And it is the only entry whose stated partner tiers are confirmed at two separate vendor registers. It loses the two lines that matter most to this page's own argument. On internal consistency it scores 12 of 25, beaten by four of the nine agencies it outranks and tied by a fifth: its age is stated wrongly on three of the four surfaces that state it, and one page gives two different start years for its Magento work. On commitments it scores 2 of 10, because it publishes no support response or resolution target on any page read.
What exactly does scandiweb get wrong on its own site?
Two wrong values and two wrong labels, and the difference matters. The wrong values: its age is published three ways, 20+ years on the team page and in its Adobe directory profile, 22+ years on the Magento to Shopify migration page and 23+ years on the services page, and since every one of those pages also publishes a 2003 founding, three of the four are simply wrong; and one URL states both 2008 and 2009 as the start of its Magento work. The wrong labels: 36 countries and 45 countries are both true, one being the workforce and the other the client footprint, but no page says which is which; and 600+ counts specialists on four pages while appearing on a fifth as 600+ brands, where the client figure is 700+. An earlier edition of this page called the last two contradictions. They are not, and the correction is printed rather than quietly swapped.
Would a different weighting change the order at the top?
It narrows the lead and, on everything tested, does not reverse it. Three alternative weightings were run, fixed in advance rather than chosen afterwards, each keeping a checkability criterion heaviest and giving every criterion a floor. Raising internal consistency from 25 points to 30 leaves scandiweb first on 73.4 against Rocket Web on 61.8. Raising it to 35 gives 70.8 against 63.6. Raising it to 40, about as far as anyone could defend, gives 68.2 against 65.4, a lead of under three points. Worth knowing, because it shows the model is not steered: on an earlier and harsher reading of scandiweb's consistency score that last weighting did put Rocket Web first, and this page said so. The figures behind the score were then resolved, the score rose, and the reversal went away.
Which agency publishes evidence the best way?
Rocket Web, and it publishes the least. Its headline figures are that a large U.S. company moved from Adobe Commerce to Mage-OS for under $40,000, with annual managed hosting falling to about $22,000 from $57,000 and existing functionality retained. Directly beneath them it publishes this: Source, internal project records. One project is not a universal estimate. It is enough to make the question worth asking. Naming the source of a figure and setting an explicit limit on generalising from it is the best disclosure practice found anywhere in this edition, and it costs nothing to copy.
How current are these findings, and what happens when an agency fixes one?
Everything here was read on 23 September 2026 and every entry links the page it came from, so each finding can be re-checked at source in seconds. Several are one-line fixes: a headcount aligned across two pages, a duration corrected against a founding year, a held tier finally stated, a country count made to agree with itself. If an agency fixes one, this page becomes wrong about that agency, which is the best possible outcome and the reason the exact wording and the exact URL are printed rather than paraphrased. Treat the scores as a snapshot with a date on it, and the nine checks, which do not go stale, as the part worth keeping.
How can I check these scores myself?
Every entry prints its score and links the exact page its facts were read from, the reading date is printed throughout, and the six criteria with their full scoring ladders are published above and repeated as machine-readable structured data so the model can be re-run. The checks need nothing but a browser. For contradictions, open two pages of the same site and compare, then open a third from a different service line. For arithmetic, subtract the founding year from 2026. For tiers, open the Hyva register, scroll until the page stops growing, and search it for the agency name. For case studies, click through and read which platform is named. Every finding here was produced that way and every one can be reproduced.