Mewa.io began as the platform plan managers ran on. We did not manage the plan, but we handled much of the day to day: termination verification, document production and distribution, member communications, census collection. That has been running since 2019, at 99.992% uptime. What is new is the scope. Mewa.io now does the whole job, with more of it visible to you than before.
Certified to file, and built for the rest
You sign as plan administrator with your own EFAST2 credentials; we transmit as a registered transmitter.
Michael has worked in employee benefits since 2001. In 2006 he founded FormFire, which lets an employee complete one health application and get underwritten rates from multiple carriers, the kind of underwriting many MEWAs still use today. In 2018 he founded Reform Labs to build software for the corners of healthcare where trust and sensitive data matter most. Mewa.io was its first product. The products he has built along the way have served more than a million employees.
At Reform Labs, years in that support role showed us a market where the work is heavy and much of it is still done by hand. That is exactly where our expertise lies: automation applied to a narrow, high-stakes filing problem. The result is a plan that is better run, and an engagement priced against the work itself.
The platform, the filing and the accounting are built and run by one in-house team. The people who wrote the system are the ones on your plan. The delicate ERISA calls go to outside counsel.
One team built the system and runs it. The people who wrote it are the ones on your plan.
Most support volume in this market is somebody asking where something stands, or why an employer is still being billed for a terminated employee.
Those are not support questions. They are symptoms of a system that cannot answer for itself. Where the status is already on the screen, and where the termination posted the week it happened, the call does not get made.
What is left over reaches a person: employers, brokers, carriers and you. Including the unglamorous part, which is carrier files arriving malformed or contradicting last month, and somebody having to notice and chase it.
The plan’s accounting and its filing record belong to the plan, not to us. And much of the filing record is public to begin with, retrievable from EFAST2 by anyone.
Nothing about working with Mewa.io puts your own data out of your reach.
Running a self-funded MEWA is a narrow specialty, and it is not one job: the arrangement’s own filings, the trust’s books, premium reconciled against enrollment for thousands of employers, and the day-to-day that each of those generates. The people who can hold all of it are few, and every firm in this market runs on a handful of them. A bigger firm does not solve that. It just has more people whose method nobody else can see.
The repeatable part is encoded: the premium register computed from the enrollment, the month closed on its own rules, every return generated from that reconciled book and checked before it is filed. What is left is the part that was always judgment, the exception the rules cannot settle and the call that turns on how a plan is written. That is what the team spends its time on, and it is why there are fewer of them than the work would otherwise take.
The platform does not make the judgment calls. It makes them the only calls left.
Leave your email and you’ll hear from the person who would manage your account. There’s nothing to prepare: much of what we’d need to understand your arrangement is already public, so we can get familiar with yours before we ever take your time.
Or email us directly.