How this was built
The short version: an AI-written list of ideas was checked against primary sources, most ideas were dropped, and three tools were built.
Where the ideas came from
The starting point was a report written by an AI chat assistant. It ranked ten ideas for free tools that individual behavior analysts and behavior technicians could use without their employer. Its scores were its own opinion, and several of its facts could not be traced to a source.
What was checked
Each claim and each competitor in the report was looked up in a primary source: the certifying board's own pages, published studies, licence terms and the products themselves. Counts of certified people were confirmed. Several named products and one statistic could not be found at all. They are not used anywhere on this site.
One study's headline figure described people who had already left a job, not everyone in the field. The same paper also gives different percentages in different places, so no figure from it is used here.
What was dropped, and why
Of the ten ideas, five were dropped, one is on hold and two were merged into a single tool. Of the five that were dropped, three already have free tools that do the job. One would need a shared dataset about workplaces, which raises privacy, accuracy and fairness problems that a small free project cannot handle. One serves practices and billing teams, not individual practitioners.
What was built
- Real Hours: your week in hours and pay.
- Flight School: practice recording behavior against a known answer.
- StimulusLab: printable arrays with balanced positions.
A fourth idea, scripted practice for difficult conversations, is on hold. It needs review from people with clinical and lived experience before any of it could responsibly be released.
What has not been done
No practitioner was asked beforehand whether they want these tools. Whether they are useful will be judged by how much they are used after launch, and any that are not used will be removed. Anything that depends on judgment about practice, such as the recording rules and wording in Flight School, needs checking by practising clinicians. This page will say so when that has happened.
How AI tools were used
The research, the planning documents and the code were drafted with Claude, an AI assistant, and checked with automated tests. Prateek Kiran chose the goal and decides what is published. The assistant proposed or made many of the design choices. The decision log in the source repository records who made each one. Errors in a formula or a rule are bugs, and they are fixed in the open.
Rules the tools follow
- Everything runs in your browser. Nothing you type is sent anywhere.
- No accounts, no email sign-up, no cookies.
- No client information is ever needed, and none should be entered.
- The tools do arithmetic, practice and layout. They do not give clinical, ethical or legal advice.