Why we built this

One of us is a board certified behaviour analyst. The other builds software. We are married, and we are the parents of a son on the autism spectrum.

That combination is how this started. Working in the field and living with it at home are different vantage points on the same problem, and both of them kept pointing at the same gap: the tools available for relational training were thin, and the good ones were expensive, closed, or built for a research setting rather than a caseload.

The gap

Relational training is well supported by evidence and badly supported by software. Practitioners who want to run it end up hand-building stimulus sets in spreadsheets, printing cards, and rebuilding data sheets for every learner. The theory is decades old; the tooling never caught up.

What we wanted was unglamorous: something that would take the repetitive construction work off a practitioner's plate and leave every clinical decision exactly where it belongs.

What that means for the product

RFT App drafts; you author. That boundary is not a hedge, it is the design. The tool is good at structure, consistency, and volume. It is not qualified to decide what a particular learner should be working on, and it does not try to.

It also means we are careful about what we claim. We are not publishing clinical guidance, and the explainer content on this site is educational material about a scientific literature, written to be accurate and cited properly.