Using what we learned from model testing, I redesigned Support Plans as a more adaptive, personalized experience. Instead of giving every user the same static checklist, the system could use their screening results, household details, expenses, and eligible programs to generate guidance tailored to their situation.
We selected the o3 model because it produced the strongest balance of reasoning, structure, readability, and token efficiency. Its reasoning capabilities helped the product go beyond repeating program instructions—it could organize related tasks, remove unnecessary duplication, account for user context, and present next steps in a more useful order.