CollectMax after the Embrace acquisition: what to ask JST now

Embrace Software has acquired JST, the maker of CollectMax and Accis; Embrace's announcement is dated 30 January 2026 and JST's 2 February 2026. Both say JST will operate as an independent business with Kurt Baese continuing as President. This guide turns that news into the diligence questions worth asking in writing.

What was announced

Embrace Software Inc. acquired JS Technologies, Inc. — JST, the company behind CollectMax and its cloud platform Accis. Embrace's own announcement is dated 30 January 2026; the version on JST's site carries 2 February 2026. The operative commitments, quoted from the announcements themselves: "JST will continue to operate as an independent business within Embrace's portfolio, maintaining its brand, team, and customer relationships, while benefiting from Embrace's long-term ownership model and operational support", and "Kurt Baese continues to lead JST as President, guiding the company's operations and product direction." Baese himself is quoted saying "This was a competitive process with multiple interested parties, and Embrace stood out as the right long-term partner for JST", and citing "Embrace's track record of continued product investment and long-term ownership approach" as the basis for "confidence in the future of Accis, CollectMax, and ongoing success of our customers." Embrace's CEO, Mohan Plakkot, described the business it bought: "JST has built a durable business around a well-established product that supports critical financial recovery workflows."

Who Embrace Software is, from its own materials

Embrace is a software holding company. Its site opens "We Buy & Build World-Class Software Businesses", describes its founders as "entrepreneurs and enterprise technologists with 35+ acquisitions under our belt", and states its criteria: "We acquire companies that offer mission-critical software, focusing on those with revenues ranging from $2 – $30 million across all industries." The JST announcement adds that Embrace acquires "world-class software businesses that provide industry-specific solutions" and believes "best practices followed by enterprise software are equally relevant for small software businesses." Two honest observations, neither of them an alarm. First, the stated model is long-term ownership of niche vertical products — which, if the practice matches the statement, is the acquirer profile an installed base should prefer. Second, the announcement's own headline says JST is Embrace's entry into the legal vertical, so its record in this specific market starts now. Neither point answers anything by itself; both are reasons to get the answers below in writing rather than by inference.

What the announcements commit to, and what they do not

Committed, in the vendors' own words: independent operation, the brand, the team, the customer relationships, and Baese's continued leadership. Not addressed in either announcement: product roadmap dates, support terms, pricing, or how investment will be split between CollectMax — the installed on-premises product — and Accis, the cloud platform JST has been publicly steering toward since it announced its first customer conversion in July 2025 with the words "There is a future where collection firms are no longer tethered to a network server environment." None of that silence is unusual; acquisition announcements are not contracts and are not written to be. It simply means the commitments that matter to your firm live in your agreements and your renewal, which is where the following questions point.

Support commitments: ask what survives the change of control

Read your own license and support agreement before asking JST anything, because the first questions are about paper you already hold: does the agreement bind successors and assigns, and did the transaction trigger any assignment or change-of-control clause in it? Then ask the vendor: are support response times a contractual term or a service description; who are the named support contacts after the acquisition and did they change; and does the support and maintenance pricing you budget against hold through your current term and your next renewal? JST's own published advice — "The total cost of collections software is more than just the initial price to get started. Consider long term expenses for ongoing support, maintenance and version upgrades." — is the right frame, and it is fair to ask the vendor to apply its own frame to the years ahead.

Roadmap: CollectMax, Accis, or both

JST sells two platforms, and the published record already shows the direction of investment: Accis is "our next-generation cloud-based platform", and the July 2025 conversion announcement describes the untethered future in JST's own words. After the acquisition, Baese's quote names both products. So ask the specific version of the roadmap question: which platform do new features land on first; is there a published end-of-development or end-of-support date for CollectMax (none is published that we have found — ask anyway, in writing); what does a CollectMax-to-Accis conversion involve, what does it cost, and is it required by any date? A vendor with good answers will give them quickly. Write down the answers you get, because a roadmap answer given orally in the quarter after an acquisition is precisely the kind of statement that is unrecoverable two years later.

Pricing at renewal

JST publishes a starting price — "JST offers monthly subscription programs starting at $300 a month" — and prices modules separately; of MaxPlans, the workflow automation, the help file says "This feature is an add-on. For pricing information, please contact Sales." The questions: does published pricing continue to apply to your program; what is the renewal uplift policy; and which third-party line items in your stack — the Advantage Database Server license the system requirements mandate, an MS-SQL license if you use SmartData, the word processor on every desk — are affected by anything in the transition? Nothing in either announcement suggests a pricing change, and this guide does not predict one. Renewal terms are simply the place an ownership change becomes visible if it ever does, which is why the question belongs on the list.

Data export rights: the question to settle while everything is calm

This is the most valuable question on the page, and the best time to ask it is when you have no intention of leaving. JST itself publishes the cleanest inventory of what a CollectMax file contains, in its documentation of the record types uploaded to the You've Got Claims network — financial transactions, debtor information, employment, bank and assets, legal captions, reconciliation, notes, suit and judgment information, balance and interest, payment plans, bankruptcy, probate and physical assets. Add the imaging store, and note that the system requirements describe "JST SmartData, a secondary MS-SQL data set" that "can be read and queried by the Customer" — a documented, queryable copy of your own data is a genuine export asset, so ask what it takes to have it. Then ask the general questions that apply to any vendor: what does a complete export contain, in what documented format, at what cost, on what turnaround, and does anything in your agreement condition it on being current on fees? A firm that can leave calmly negotiates calmly. That is what export rights are for, whether or not you ever use them.

What this guide is not saying

There is no evidence in the published record of any negative change at JST, and this guide asserts none. The stated model of the acquirer is long-term ownership and continued product investment; the president stayed; the brand and team continue. Every question above is standard third-party diligence after any change of control — the same questions a bank's vendor-risk team would put to your firm in the reverse direction — and a vendor's calm, specific, written answers to them are one of the better signals a vendor can give.

If you are evaluating alternatives

Otto is one, and this page will not argue it beyond a sentence: it is a hosted platform whose rules run before the action and whose audit record is append-only. The comparison of CollectMax against it, sourced to JST's own documents, is at /compare/collectmax/, the head-to-head of the two incumbents is at /compare/collection-master-vs-collectmax/, and the migration guide — what a move off CollectMax actually carries, whoever the destination is — is at /migrating/from-collectmax/.

This is an informational reference, not legal advice, and using it creates no attorney-client relationship. Limitations periods turn on facts this page cannot know — which state's law governs, the contract type, when the claim accrued, and whether anything tolled or revived it. Confirm against the primary source and your own counsel before acting.