We build it, we run it, and we answer for it

The company started by writing software for martial arts schools, which turned out to be the hardest version of a general problem: recurring billing that is rarely monthly, families on one account, attendance that matters, and an owner who is teaching a class when the payment fails. Software built for that handles a gym or a swim school comfortably. The reverse is not true, which is why the product went the direction it did.

Payments work the same way. The gateway and the processing are a payment company's, and the merchant account is opened through us, because tying it to the member record takes encrypted gateway credentials rather than a checkout someone can paste in. A membership business does not experience “the software” and “the processor” as two things; it experiences a member whose card did not go through. Setting both up as one piece is what makes the decline, the member and the follow-up one problem instead of three systems.

Anexan is deliberately small, and support is not routed through anyone who has to go and ask. The people who wrote the billing engine are the people who answer when it misbehaves.