Perrigo had a problem that sounds enviable until you imagine maintaining it: a plan for more than 400 websites. A pharmaceutical manufacturer with many brands and markets needed a way to keep expanding without treating every new site as an entirely fresh construction project. Its existing architecture made changes laborious. Reuse was missing. The trouble began behind the pages.
- Ameex built and connected enterprise content, commerce and data systems.
- Its client work made reuse and editorial workflows central to delivery.
- Perficient acquired the consultancy in October 2022.
This is a useful entrance to Ameex Technologies, a company whose description could otherwise dissolve into the familiar language of digital transformation. Look at the work and something more tangible appears: an attempt to make complicated software easier to operate, repeat and change. The second website is where the argument gets interesting.
01 / The second site is the test
Ameex began Perrigo’s project by interviewing stakeholders and content authors. The resulting platform combined Acquia Site Factory, automated deployment tools, multisite profiles and Drupal’s Layout Builder. Together, these supported common components and shared governance. A country site could be cloned rather than laboriously reconstructed.
Acquia’s account reports that subsequent sites cost 80% less to implement after the first. It also reports 76% lower total ownership cost and 75% shorter time to market. These are project-specific results, with different measures describing different parts of the operation. They make a practical point: repeated work deserves architecture of its own.
The inference for other organizations is straightforward. Ask what stays the same between launches, and put that in the foundation. The economics depend on repetition. A business with one small, infrequently updated website has much less repeated work to remove. Standardization also requires people to agree on what they will share.
02 / The company between the tools
Founded in 2007, Ameex worked in the space between enterprise software and the organization expected to use it. Its services covered content systems, commerce, customer experience design, application engineering, analytics and support. Drupal, Sitecore, Magento, Adobe Experience Manager and Salesforce appeared in its public platform repertoire. Clients bought consulting and implementation work, with maintenance extending the relationship beyond launch.
This matters when placing Ameex in the market. A retailer might need a storefront connected to content and customer data. A manufacturer might need many brand sites. A nonprofit might need a publishing operation its staff can manage. Each can own capable software and still need help making the pieces cooperate.
The alternatives include a specialist agency, a larger consultancy or an internal team. Ameex’s documented combination was platform breadth and offshore delivery capacity, including Chennai. That combination could serve customers whose problems crossed software boundaries. Whether it beats an alternative depends on the actual integration work, the customer’s own skills and the continuing support required.
03 / Ten days, familiar tools
At Global Atlantic Financial Group, the assignment was more immediate: an employee vaccine-attestation application to support office reopening. Speed, integration and changing requirements were the constraints. Global Atlantic selected Drupal and Acquia partly because Ameex had already delivered successful Drupal projects for it. Familiarity influenced the platform decision.
Ameex divided the workflow into four epics, or substantial groups of work. The application had to accommodate changes in workplace requirements and vaccination guidance. Acquia reports that development, testing and delivery took ten days, with more than 1,100 employees using the system.
To develop, test and deliver Global Atlantic’s attestation application.
The lesson is about preparation as much as urgency. A trusted platform and an existing working relationship can shorten the distance to delivery. Copying the deadline without those conditions would be a poor planning method. Ten days describes one engagement; it does not turn unfamiliar integrations into familiar ones.
04 / Remember the person publishing
The Epilepsy Foundation faced another version of the problem. Its Drupal 7 website needed an upgrade, but the friction extended to content authoring, navigation, asset management and performance. Ameex used a discovery questionnaire and customer sessions, then delivered work incrementally for feedback.
The Drupal 9 migration used Acquia Site Studio for low-code page building and Acquia Personalization for audience journeys. The project finished on time, and Acquia reports a 50% improvement in site performance. The case connects technical modernization with the everyday work of publishing and maintaining information.
That attention fits Ameex’s broader data ambitions. Its partnership with Meiro covered customer-data consulting and implementation. The commercial idea was to help organizations connect information across channels and use it for more relevant experiences. Data integration was another part of the same coordination problem.
“helping customers make sense out of their data”
Ranga Srinivasan / describing an Ameex strength to Meiro
05 / A buyer for the whole operation
On October 11, 2022, Perficient acquired Ameex. More than 400 professionals joined the buyer, which described the business as generating approximately $19 million in revenue. Cofounders Dan Venkatesan and Ranga Srinivasan joined in leadership roles. Perficient highlighted engineering capacity, client relationships and technology partnerships.
The closing consideration was approximately $32.3 million, comprising cash and shares, with up to $5.7 million in contingent cash consideration. That transaction amount answers what the buyer paid at closing; it says nothing about a customer’s implementation budget. Today, the old Ameex web address leads to Perficient.
For a team contemplating its own rebuild, the useful question survives the acquisition: what will become easier after the first launch? Ameex’s public work suggests a concrete place to look. Interview the authors. Find the repeated steps. Decide what can be shared. Then judge the platform by the work it saves next time.