Key points

• Zero of the five state whether an extracted value cites the page or clause it came from.
• Zero of the five mention confidence levels or the flagging of values the model was unsure about.
• Zero of the five publish a policy on whether customer documents are used to train AI models.
• Four of five describe a human review step, in language ranging from 'you approve' to 'a quick review'.
• Two publish performance claims, 3X accuracy and 4X faster, with no methodology attached to either.

In July this publication set out five questions worth asking any platform selling contract extraction to coordinators. This month we put them to the published material of the five platforms named in that story. The exercise took an afternoon, which is roughly how long it should take a buyer.

The result is not that the products are bad. It is that on the two questions which decide whether an extraction can be trusted, the category is silent.

What each one publishes

Cites the page or clause it read a value from

• ListedKit: Not stated
• Rebillion.ai: Not stated
• DocJacket: Not stated
• Trackxi: Not stated
• Nekst: Not stated

Flags values the model was unsure about

• ListedKit: Not stated
• Rebillion.ai: Not stated
• DocJacket: Not stated
• Trackxi: Not stated
• Nekst: Not stated

States whether client documents train AI models

• ListedKit: Not stated
• Rebillion.ai: Not stated
• DocJacket: Not stated
• Trackxi: Not stated
• Nekst: Not stated

Where they do say something

Human review is the one question the category does answer, and mostly in the same words. DocJacket puts it as AI preps, you approve. Rebillion.ai describes going from worker to reviewer, with the user approving and the model handling the rest. ListedKit says Ava does the work and your team reviews. Nekst describes a quick review before you are ready to go. Trackxi's material describes automatic extraction of names, prices, dates and contingencies without describing a review step at all.

Four out of five is a reasonable showing. It is also the easiest of the five questions to answer, because saying a human approves costs nothing and commits to nothing about how the approval is meant to work.

Why the two silent questions are the load-bearing ones. A review step is only meaningful if the reviewer can see what to check. Told that the closing date is 28 April, a coordinator can confirm it only by re-reading the contract, which is the work the tool was bought to remove. Told that the closing date is 28 April from page 9, clause 14, and that the model was unsure about it, the same coordinator checks one clause in seconds. Citation and confidence are what convert a review into an actual control.

The claims that arrive without arithmetic

Two of the five publish performance figures. Rebillion.ai states it is up to three times more accurate than manual entry. Trackxi states contracts are processed four times faster with AI-powered data extraction. Nekst puts a number on the clock instead, describing extraction in about ninety seconds.

No methodology accompanies the first two. Three times more accurate than which manual baseline, measured on what document set, scored by whom. Four times faster than what. These may well be defensible internally. As published, they are not checkable, which is the same problem this publication identified in the unsourced market sizing circulating around coordinator insurance.

Speed is the easiest thing to measure and the least useful thing to promise. Nobody was ever sued for reading a contract slowly.

TC Bulletin, Editorial position

What this survey is not

This is a survey of what these companies publish, not of what their products do. A platform may cite sources beautifully inside the application and simply not mention it on a marketing page. Several probably do.

That distinction matters and it does not rescue the position. A coordinator evaluating five products cannot see inside any of them before buying. The published material is the entire basis for a shortlist, and on the questions that determine whether an extraction is auditable, that material currently says nothing at all. The first vendor in this category to publish a citation and confidence model in plain terms will have a genuine advantage, and it is available to any of them this week.

Right of reply. Any platform named here that does cite sources, surface confidence, or publish a training-data policy is invited to send the documentation. TC Bulletin will update this story and date the correction.

The five questions, unchanged

1. Does every extracted value cite a page or clause in the source document?
2. Are low-confidence values visibly flagged rather than silently included?
3. Does anything reach the calendar before a human approves it?
4. Is AI usage priced into the plan, or metered separately in a way that punishes a busy month?
5. Are client documents excluded from model training, in writing?

Material surveyed

• ListedKit
• Rebillion.ai
• DocJacket
• Trackxi
• Nekst
• The July story that set the questions

Sources cited

• ListedKit
• Rebillion.ai
• DocJacket
• Trackxi
• Nekst

Freehold enforces workspace separation with Postgres row-level security and logs who performed each sensitive action. For a desk holding wire instructions and client logins, the difference between those two places is most of the argument.

Key points

• Freehold states that every workspace is separated using Postgres row-level security, enforced by the database rather than by application code alone.
• Documents are described as envelope-encrypted at the application layer before storage, so direct database access returns ciphertext.
• Stored client logins are described as envelope-encrypted and revealed only on click.
• A full audit log records deletions, portal access changes, credential reveals, sent emails and integration connections, with the person who performed each one.
• TC Bulletin has not audited any of this. The claims are the vendor's own and are testable by anyone self-hosting, because the code is public.

Almost every platform in this category says your data is secure, and almost none of them says where the separation is enforced. It is an unglamorous distinction and it is the one that decides what a bug costs you.

Two places to put the wall

In a shared system, something has to guarantee that one workspace cannot read another's files. That guarantee can live in the application, where every query carries a filter the developers remembered to write, or it can live in the database, where the engine refuses to return rows that do not belong to the caller regardless of what the query asked for.

The practical difference shows up on the bad day. Application-layer separation fails open: one missing clause in one query, one endpoint that forgot the check, and the data crosses. Database-enforced separation fails closed, because the rule is not restated in every query. It is a property of the table.

Freehold's published description is specific about which of the two it uses. Its material states that every workspace is walled off with Postgres row-level security, enforced by the database itself and not just application code.

Why a coordinator should care about a database feature. You hold wire instructions, identity documents, payoff figures and in many cases client logins, for parties who never chose your software. The question is not whether you trust your vendor. It is what happens to somebody else's file when one line of your vendor's code is wrong.

What sits on top of it

Two further claims in the same material are worth separating from the marketing register they arrive in, because both are checkable statements about where plaintext exists.

• Documents are described as envelope-encrypted at the application layer before they are stored, so that direct access to the database yields ciphertext rather than files.
• Saved client logins are described as living in a credential vault, envelope-encrypted and revealed only on click rather than held in plaintext.

The second is the one coordinators should read twice. Storing portal logins for clients is ordinary practice on a busy desk and it is the single worst thing on most systems, because it is frequently kept in a note, a spreadsheet or a password field that was never designed to hold somebody else's credentials.

The audit log is the part that pays for itself

Freehold's material describes a full audit log covering deletions, portal access changes, credential reveals, sent emails and integration connections, each recorded with who did it.

That is a security feature, and it is also the answer to a question this publication has already covered from the other direction. Specialist brokers describe the coordinator claim profile as missed deadlines, missing signatures, the wrong version of a document and misdirected files. Every one of those is an argument about what happened and when, and every one of them is easier to survive when the system can say so without relying on anyone's memory.

What the audit log is recorded as covering

• Deletions: Logged (With the person who performed them)
• Portal access changes: Logged
• Credential reveals: Logged
• Sent emails: Logged
• Integration connections: Logged

The part that makes the claim testable

Security claims are usually unfalsifiable from outside. A vendor asserts an architecture, and a customer either believes it or does not, because there is nothing to inspect.

Freehold is source-available under the Elastic License 2.0 and self-hosting is free for an organisation's own use, which changes the standing of every claim above from an assertion into something a sufficiently motivated brokerage or IT provider can go and check. TC Bulletin has not done that. The point is that it can be done, which is not true of most of this category.

What this story is and is not. This is a description of published architecture, not an audit, a penetration test or a security endorsement. TC Bulletin has read the vendor's documentation and nothing else. Anyone making a purchasing decision on security grounds should read the code or have someone read it for them.

Questions worth asking any vendor

1. Is workspace separation enforced by the database, or by filters in application queries?
2. Where does plaintext exist, and who or what can read it?
3. Are stored client credentials encrypted, and is a reveal recorded?
4. Does the audit log record who performed an action, or only that it happened?
5. Can I obtain the log, and my data, without asking permission?

Sources for this story

• Freehold features Vendor documentation. Sister property, see the disclosure above
• PostgreSQL row security policies The underlying database mechanism
• TC Bulletin on coordinator liability cover

Sources cited

• Freehold features
• PostgreSQL row security

Key points

• Radian announced both transactions on 3 August 2026. One is done, the other is not.
• Completed: the Real Estate Services business, comprising Radian Real Estate Management LLC and homegenius Real Estate, has been sold to PLACE.
• Pending: a definitive agreement to sell Radian Title Insurance Inc. and Radian Settlement Services Inc., expected to close in the fourth quarter subject to regulatory approval.
• Terms were not disclosed for either transaction.
• Per ALTA market share data cited in its reporting, Radian Title wrote $17 million in title insurance premiums in 2025, which is small enough that most coordinators will never see one of these files.

Two Radian transactions were announced in the same release on 3 August 2026, and they are being reported as one. They are not one, and the difference is the part that matters to anyone with a live file.

The sale of Radian's Real Estate Services business to PLACE has completed. That business covers Radian Real Estate Management LLC, which does property management, and homegenius Real Estate, which does brokerage and valuation work. That deal is done.

The title business is a separate transaction and it has not closed. Radian has entered a definitive agreement to sell Radian Title Insurance Inc., the underwriter, and Radian Settlement Services Inc., a national title agency. Completion is expected in the fourth quarter and is conditioned on regulatory approvals and customary closing conditions. Financial terms were not disclosed for either deal.

How it has run

• 2018: Radian acquires the EnTitle Direct underwriter, which is rebranded as Radian Title the following year.
• 25 September 2025: ALTA reports that Radian intends to sell its title services.
• 3 August 2026: Radian announces the completed sale of Real Estate Services to PLACE and a definitive agreement to sell the title business to the same buyer.
• Q4 2026, expected: Target completion for the title sale, subject to regulatory approval.

A scale check before anyone panics

Title consolidation stories tend to be written as though every file is affected. This one is not on that scale. ALTA market share data cited in reporting on the deal puts Radian Title's 2025 title insurance premiums at $17 million, which is a rounding error against the national underwriters most coordinators actually encounter.

The practical read is that the large majority of desks will never have had a Radian Title policy cross them. The agency side, Radian Settlement Services, operated nationally and is the more likely point of contact.

What to do about it today. Nothing, if your files do not involve Radian Title or Radian Settlement Services. If they do, the deal has not closed, so the parties, the policy and the closing protection letter on a file in progress are unchanged until it does.

What changes when it completes

An underwriter changing hands is not a paperwork event for the coordinator on the day it happens. It becomes one later, through the ordinary channels: which agents an underwriter approves, which forms and endorsements are issued, what a closing protection letter says and who stands behind it, and the name that appears on the documents.

On the last point, PLACE has said it is evaluating next steps on rebranding and has nothing to announce. A coordinator's practical exposure is a name change arriving mid-file, which is a template and checklist problem rather than a legal one, and is much cheaper to handle if you know it is coming.

The pattern worth tracking

PLACE describes itself as a real estate technology and services platform, and its co-founder and chief executive Ben Kinney has described it as a homeownership ecosystem. It already owned a small title business serving residential resale before this deal. Kinney has said the purchase moves PLACE deeper into title and settlement and opens it to serving large lenders and single-family rental investors.

That is the direction to watch rather than the transaction itself. Software platforms buying underwriters and agencies puts the same company in the workflow and in the settlement, which is a different arrangement from the one most coordinators grew up with. Radian, for its part, is moving the other way, out of these businesses and toward a global multi-line specialty insurer.

Primary sources for this story

• Radian, release of 3 August 2026 Announces the completed services sale and the pending title agreement
• ALTA, Radian to sell title services 25 September 2025
• National Mortgage News on the PLACE purchase 5 August 2026

Sources cited

• Radian release, 3 August 2026
• ALTA
• National Mortgage News

Key points

• ListedKit publishes $14.99 per transaction credit with no subscription and no monthly fee.
• Rebillion.ai publishes $199 and $499 monthly tiers, describing one usage-based price covering the whole team with no per-user fees.
• DocJacket states its AI is included with every subscription.
• Trackxi and Nekst do not publish an answer on whether AI is included or metered on the pages surveyed.
• On the stated ListedKit rate, a desk running 14 files a month passes $199, which is where the two published models cross.

Feature comparison is the easy part of choosing a platform. The harder question, and the one that decides whether a coordination business works, is what the software costs at the volume you actually run.

On that question the AI-native cohort has quietly split into two camps, and they are not pricing the same thing.

Per file, or per team

ListedKit publishes a consumption model: $14.99 per transaction credit, with the explicit statement that there is no subscription and no monthly fee. Cost scales with the number of files.

Rebillion.ai publishes the opposite arrangement. Its material describes one usage-based price covering the whole team with no per-user fees, at $199 or $499 a month depending on tier. Cost is flat against file count and flat against headcount.

DocJacket sits in a third position, stating that AI is included with every subscription. Trackxi and Nekst, on the pages surveyed for this story, do not say either way.

Published pricing, as stated

• ListedKit: $14.99 (Per transaction credit. No subscription, no monthly fees.)
• Rebillion.ai: $199 or $499 (Per month, whole team, no per-user fees)
• DocJacket: Included (With every subscription)
• Trackxi: Not published (On the page surveyed)
• Nekst: Not published (On the page surveyed)

Where the two models cross

The arithmetic is simple enough to do on the back of a closing statement. At $14.99 a credit, ten files a month is $149.90 and twenty files is $299.80. The published $199 tier is passed somewhere around the fourteenth file.

• 10 files a month: about $150 on the per-credit model.
• 14 files a month: about $210, roughly where the flat $199 tier becomes the cheaper of the two.
• 20 files a month: about $300.
• 40 files a month: about $600, which has passed the published $499 tier.

One assumption, stated plainly. This arithmetic assumes one transaction credit corresponds to one file. Neither the credit definition nor what exhausts one is set out on the material surveyed, and a credit that covers a document rather than a transaction would change every figure above. Confirm the unit before you model anything on it.

Which model suits which desk

A consumption price is genuinely better for a new or seasonal practice. Nothing is owed in a quiet month, the cost of trying the software is one file, and there is no annual commitment to argue about. For a coordinator building a book, that is a real advantage and not a marketing one.

It inverts at volume, and it inverts precisely when the business is going well. A per-file cost is a variable cost, and a coordinator charging a flat fee per file is taking that variable cost straight out of the margin on every transaction. A flat team price does the opposite: it is worst when you are quiet and best when you are busy.

The practical test is not which is cheaper today. It is which one behaves the way you want in the month when everything closes at once.

The number nobody publishes

What is missing across the category is the cost per file at a stated volume, which is the only figure that lets a coordinator compare two of these products in a single line. Two of the five surveyed do not publish pricing on the relevant pages at all, and where pricing is published the units differ enough that comparison requires the arithmetic above rather than a glance.

That is not a scandal. It is the ordinary condition of a young category, and it will resolve the moment a buyer with volume asks for it in writing.

Material surveyed

• ListedKit
• Rebillion.ai
• DocJacket
• Trackxi
• Nekst

Sources cited

• ListedKit
• Rebillion.ai
• DocJacket

The category grew out of back offices, which is why so much of it is organised around the brokerage rather than the file. Freehold's per-transaction email addresses and contract-anchored deadlines are built from the other side of the desk.

Key points

• The major platforms in this category originate as brokerage systems: Brokermint now sits inside BoldTrail alongside kvCORE and BoomTown, brokerWOLF sits under Lone Wolf, and TotalBrokerage describes itself as an all-in-one brokerage CRM.
• Lineage shows up as organising principle. Brokerage systems are built around agents, listings and commissions, because that is what a brokerage counts.
• Freehold states that each workspace gets dedicated email addresses, with replies threaded back to the transaction they belong to.
• It describes deadlines that compute from the contract's close date and cascade when an amendment is confirmed.
• It also describes automatic time accrual while a file is open, reporting profitability per file and per client, which is a coordinator's question and not a brokerage's.

There is a reason so much transaction software feels like it was designed for somebody else. It was.

Follow the lineage

The dominant products in this category did not begin as coordinator tools. Brokermint now trades as BoldTrail BackOffice inside Inside Real Estate's portfolio alongside kvCORE and BoomTown, both of which are brokerage and agent platforms. brokerWOLF, a brokerage back office system, sits with zipForm and TransactionDesk under Lone Wolf. TotalBrokerage describes itself, in its own words, as an all-in-one brokerage CRM with transaction and back office attached. SkySlope's centre of gravity is brokerage compliance.

None of that is a criticism of those products, which are generally good at the job they were built for. It is an observation about whose job that was.

Lineage becomes an organising principle

A brokerage system is built around what a brokerage counts: agents, listings, production, splits, commissions, compliance exceptions. Its natural unit is the agent, and the transaction is a thing that hangs off one.

A coordinator's unit is the file. They work across several brokerages, frequently for agents who are not colleagues of each other, and the questions they need answered are per-file rather than per-agent. What is due on this one, who has not responded, where did that document go, and is this file making money.

That last question is the tell. Brokerage software does not usually ask whether an individual transaction was profitable, because for a brokerage the answer is the commission. For a coordinator charging a flat fee per file it is the whole business, and it is a question most of the category simply does not have a field for.

Three features that show which side they were designed from

Email addressed to the transaction

Freehold states that a workspace gets dedicated email addresses, with replies threaded back onto the transaction they concern. The design assumption there is that correspondence belongs to a file rather than to a person's inbox, which is how a coordinator actually experiences it and is not how a CRM built around an agent tends to model it.

There is a security consequence too. Correspondence that arrives at a per-transaction address and lands against that transaction is correspondence whose context is established before anybody reads it, which is an unhelpful environment for a message pretending to be about a closing it is not part of.

Deadlines that come from the contract

Freehold describes deadlines that compute from the contract's close date, with dates cascading when an amendment is confirmed, plus role-based routing and priorities that escalate.

Cascading is the part worth noting. The failure mode this publication keeps meeting, in the brokers' claim descriptions and in the state guidance alike, is a date that moved and a dependent date that did not. A system where the amendment updates the chain is addressing the actual documented claim profile rather than a generic idea of task management.

Time recorded against the file

Freehold describes minutes accruing automatically while a file is open, reported as profitability per file and per client, without anyone starting a timer. Whether or not a given coordinator wants that, it is a feature that only makes sense if the product assumes the user is running a business rather than occupying a seat at one.

What this does not establish

Lineage is not destiny and it is not a verdict. A brokerage platform with a decade of investment may serve a coordinator working inside a single large firm better than a coordinator-first tool will, particularly where the brokerage's compliance file is the system of record and the coordinator's job is to feed it.

The useful question when comparing is not which product has more features. It is whose problem the product was originally built to solve, and whether that is your problem. The answer is usually visible in what the software counts by default.

Sources for this story

• Freehold features Vendor documentation. Sister property, see the disclosure above
• BoldTrail
• Lone Wolf Technologies
• TotalBrokerage
• TC Bulletin on transaction software ownership

Sources cited

• Freehold features
• BoldTrail
• Lone Wolf Technologies

Key points

• ListedKit markets an AI assistant branded Ava.
• Rebillion.ai, DocJacket, Trackxi AI and Nekst AI all ship AI features aimed at coordinators.
• Trackxi launched AI tooling in April 2025.
• There is no industry standard for how contract extraction should be validated or cited.
• The practical test is whether the tool shows the page it read a date from.

The most repetitive part of a coordinator's week is reading a signed contract and typing what it says into a system that will then remind them about it. It was always the obvious thing to automate, and between 2024 and 2026 a cohort of platforms did.

ListedKit markets an assistant branded Ava. Rebillion.ai has built its positioning entirely around AI coordination. DocJacket ships AI extraction alongside an unusually heavy editorial operation. Trackxi launched AI tooling in April 2025. Nekst, founded by Brett Keppler, ships Nekst AI. These are not the same product, but they are pitched at the same job.

The unresolved question

Nobody has agreed what extraction may be trusted to do. A contract date is not a fact in a database; it is the output of a clause, sometimes a conditional one. The classic example is a deadline expressed as ten days from the effective date, where the effective date is itself defined elsewhere in the document and the day count may or may not exclude weekends depending on the form.

Get that wrong and the coordinator has not saved time. They have introduced a deadline error into a file, with the added hazard that the error arrived looking authoritative.

The test that matters

There is a simple functional standard the market has arrived at without formalising: does the tool show you where it read the value from. An extraction that returns a closing date is a guess. An extraction that returns a closing date with a page and clause reference, and a confidence marker on the ones it is unsure about, is a draft a coordinator can check in seconds.

• Does every extracted value cite a page or clause in the source document?
• Are low-confidence values visibly flagged rather than silently included?
• Does anything reach the calendar before a human approves it?
• Is AI usage priced into the plan, or metered separately in a way that punishes a busy month?
• Are client documents excluded from model training, in writing?

Those five questions are the ones TC Bulletin will put to every platform in this category, and we will publish the answers as we get them.

Where the older platforms sit

The incumbents are not standing still. SkySlope has built its compliance positioning around its Smart Suite and Smart Assist tooling. Qualia, on the title and escrow side, has shipped AI-adjacent product and publishes steadily on wire fraud and regulatory topics. Dotloop, zipForm and TransactionDesk sit inside larger corporate structures where roadmap decisions are made further away from the coordinator.

Vendor sources referenced

• ListedKit
• Rebillion.ai
• DocJacket
• Trackxi
• Nekst
• SkySlope
• Qualia Insight

Sources cited

• Trackxi
• ListedKit
• Nekst

Key points

• Inside Real Estate rebranded kvCORE, BoomTown and Brokermint as BoldTrail in June 2024; Brokermint is now BoldTrail BackOffice.
• Dotloop is owned and operated by Zillow Group.
• zipForm, TransactionDesk, Authentisign and brokerWOLF sit under Lone Wolf Technologies.
• RealTrends now sits under HousingWire as RealTrends Verified.
• T3 Sixty's correct domain is t360.com.

Coordinators tend to learn about a change of ownership the way everyone else does: a login screen has a different logo on it one morning. The consolidation of the last few years is worth writing down plainly, because vendor comparison content across the web has not kept up and still names products that have been renamed.

Brokermint is BoldTrail BackOffice

Inside Real Estate consolidated its portfolio under the BoldTrail brand in June 2024, bringing kvCORE, BoomTown and Brokermint under one name. Brokermint now trades as BoldTrail BackOffice, and the brokermint.com domain redirects. Any guide still recommending Brokermint as a distinct product is out of date.

Dotloop is Zillow Group

Dotloop is owned and operated by Zillow Group. That matters less for day-to-day use than for procurement conversations at brokerages with a view on portal relationships.

zipForm and TransactionDesk are Lone Wolf

Lone Wolf Technologies is the parent of zipForm, TransactionDesk, Authentisign and brokerWOLF. For a coordinator, that means the forms tool, the transaction platform and the signature tool in a Lone Wolf stack share a roadmap and a support organisation. Lone Wolf maintains an active news and press page.

RealTrends is HousingWire

RealTrends now operates under HousingWire as RealTrends Verified. Its rankings and brokerage operations research continue, inside a larger newsroom.

One to get right. T3 Sixty's domain is t360.com. The Swanepoel Trends Report and the Real Estate Almanac, which contains the Tech 500 technology report, are published there. Citations to t3sixty.com are wrong.

Primary sources for this story

• BoldTrail
• Lone Wolf Technologies news and press
• Dotloop
• T3 Sixty

Sources cited

• BoldTrail
• Lone Wolf Technologies
• T3 Sixty

Key points

• Trackxi announced a two-way SkySlope integration in a post dated 19 February 2026.
• Trackxi launched its AI tooling in April 2025.
• The pattern to watch is coordination tools syncing with brokerage compliance systems rather than replacing them.

Trackxi published a two-way SkySlope integration in a post dated 19 February 2026. For coordinators who keep a visual deal tracker while the brokerage keeps its compliance file elsewhere, it removes a duplication that had no good workaround.

It also fits a pattern worth naming. The coordination tools are not trying to displace brokerage compliance systems; they are syncing with them. SkySlope holds the audit file, the coordinator's board holds the work, and the integration keeps the two from drifting apart. That division of labour is likely to define the category more than any single AI feature.

Trackxi launched its AI tooling in April 2025 and publishes across news, blog and podcast channels.

Primary sources for this story

• Trackxi news and blog
• SkySlope

Sources cited

• Trackxi