A pesticide application has a surprisingly long life. It arrives with documents. Someone reviews it. Someone checks a payment. Someone needs to know which version is current. California’s Department of Pesticide Regulation managed that journey through paper and more than a dozen legacy systems, according to MERP Systems’ account of the project. Each separate system offered another place for information to stop moving.
MERP helped replace that arrangement with a digital platform connecting registration, payments, tracking and product information. The interesting part is the connection. Put a paper form on a screen and you have changed its address. Connect it to the next decision and you have changed the work.
- MERP builds and connects business applications on Microsoft technology.
- Its customers include regulators, laboratories and other public agencies.
- Reusable accelerators give projects a starting point; implementation still takes work.
The business between the boxes
Founded in 2010, MERP occupies a particular patch of the technology market: the space between a large software platform and the peculiar requirements of the organization buying it. Microsoft supplies Power Platform, Dynamics 365, Azure and SharePoint. MERP designs applications, moves data, connects systems and configures workflows around the customer’s rules.
This is a consultancy and implementation business with a catalog of reusable software. Its customers include federal agencies, state and local governments, businesses, nonprofits and associations. An agency can bring MERP a licensing problem, an investigation backlog or an approval process. The resulting work may involve a public portal, staff applications, reporting and connections to existing records.
The company’s own delivery sequence runs from discovery and design through building, integration and operation. That last word matters. A functioning system needs governance, security and continuing attention after launch. MERP’s place in the market depends on knowing both the Microsoft tools and the administrative job those tools must perform.
A laboratory and a gambling license
Consider two customers that would rarely appear in the same conversation. At the U.S. Geological Survey, MERP describes laboratories managing procedures, equipment, training and audits through fragmented systems and manual processes. Its bureau-wide quality management work brought those activities together using Power Apps, Power Pages, Power BI, Power Automate and SharePoint.
At the Washington State Gambling Commission, the problem involved aging licensing, case management, timekeeping and billing systems. Different subject matter; familiar seams. MERP’s published case study describes an integrated Microsoft cloud platform replacing multiple systems that had reached the end of their useful lives.
A July 2026 Microsoft event listing puts numbers on that second project: MERP reports delivery in 18 months against an original four-year plan, with more than 140 forms digitized. These are the company’s reported project results. They make the practical ambition legible: a regulator should be able to move an application through connected operations without rebuilding its history at every desk.
A head start with room to change
MERP calls its reusable solutions accelerators. The proposition sits between buying a ready-made application and commissioning everything from scratch. A buyer starts with an existing structure, then adapts it to the organization. The distinction is useful because public administration contains plenty of recurring patterns and plenty of stubborn exceptions.
Take mGrants. It covers announcements, applications, evaluation, awards, disbursement, monitoring and closeout. A grant’s announcement is its most visible moment; much of the administrative work happens afterward. Reviewer controls, audit trails and financial tracking address the less photogenic parts of distributing money responsibly.
Then there is mDocket, described by MERP as a One-stop tool for content authoring, review, & publishing
. Its features include approval tracking, version history and compliance alerts. Other accelerators address records requests, environmental documentation, investigations and inmate needs assessments. These are specific workflow tools built around familiar enterprise platforms.
Put a paper form on a screen and you have changed its address. Connect it to the next decision and you have changed the work.
The $200,000 reality check
The economics become clearer in a less celebratory document. San Mateo County’s March 2025 procurement materials describe selecting MERP for a Dynamics 365 Finance implementation at $200,000. The county entered a contract in March 2024, then determined the project would cost more. It terminated the agreement in February 2025 and issued a new request for proposals.
That account documents a budget mismatch and a procurement restart. It does not establish what was actually spent or a technical failure. The county’s revised requirements still specified Dynamics 365 Finance and said it had already purchased the required license. The platform choice survived; the implementation arrangement changed.
For another buyer, the lesson is concrete: separate the software license from the full implementation budget. Define the records to migrate, connections to build and acceptance criteria before treating an accelerator as a cost estimate. A reusable foundation can reduce work while leaving difficult work intact.
Follow one record all the way through
MERP’s other projects reinforce the pattern. Its SBA case study addresses audit recommendations scattered across offices, inconsistent approvals and limited visibility. Its CDC work replaces an outdated fellowship management system. CAL FIRE needed investigation workflows and reporting suited to California’s Dig Safe requirements. Each begins with an administrative task whose complexity has outgrown its supporting tools.
For prospective customers, a useful first move is to trace one real record from submission to completion. Count the retyping, approvals and separate places holding its history. This is an editorial reading of MERP’s portfolio: the opportunity appears where the same information repeatedly crosses organizational boundaries.
The approach fits buyers prepared to use Microsoft’s ecosystem and make decisions about shared processes. It becomes harder when departments cannot agree on ownership, permissions or what completion means. Software can carry an approval to the right person. Somebody still has to decide who that person is.