Tex V1 is a chat on our tax knowledge base. While it ships, I keep the team on the next question: what if the assistant knows your clients, and then your working day? Each user test writes the brief for the next horizon.
V1 looks like the AI chat users already know. My designers struggle to ship what feels like a copy. So I split the work into three horizons. V1 needs only basic UI, which frees time to research and explore V2 and V3.
Trade-off: V1 ships with basic UI, on purpose.
Answer tax questions with sources, in a chat users already know.
Connect Tex to client data. Ask across all clients, or zoom into one.
An assistant across the working day. Research first, with a thesis.
We test V1 with 10 customers. It is easy to use, and the sources build trust. But the best ideas point past the chat.
Users ask for it before we build it.
Advisers compare returns by hand. Five years means five screens. A designer on my team designs a query layer on client data, under my supervision: ask across all clients, then zoom into one.
I lead the V2 test as a team. Users want it. They also need to find it, and they ask how Tex gets its answers and what happens to client data.
Trade-off: more reach means more to explain.
Users in the V2 test. They see clear value: advice opportunities in their own client data, time saved and better client service.
For V3, an intern on my team writes his thesis on AI in tax work. We set the research question and scope together, and I am his company supervisor. He maps one working day and gives each part its own design principle.
The research includes a usability test of the first concept. Adoption depends on five conditions. After his thesis, Nextens hires the researcher as UI Engineer. How I grow people.
Professionals test the first concept in May and June 2026. They want Tex to do the prep work and leave the decisions to them.
V1 is live and V2 is in beta. The V3 research is done.
Users point past the product they have. Their ideas are your next research question, if you listen for them.
A team that ships a copy needs a future to work on. Once mine had one, the problems stopped coming up in our 1:1s.
Related: making the design system readable for AI, in Operationalising the design system.