Services
Tools, workflows
and teaching.
We build custom design tools, connect project knowledge with AI workflows, and teach teams how to use them. Start with a project, a repeated task, or a method you want to develop.
01 / Custom tools
Design methods
made usable.
We develop Grasshopper definitions, scripts and browser tools around your parts, rules and project files. Turn a repeated modelling task into a method your team can use, inspect and maintain.
- Define the task and test a focused prototype with your examples.
- Build the interface, checks and connections to your existing software.
- Hand over the tool with documentation, training and agreed support.
02 / AI workflows
Shared knowledge.
Connected workflows.
We help your team build workflows with AI: organise project knowledge, connect the tools you already use, and give assistants the sources they need. Together we choose one useful task, test it on a real project and make the results easy to review.
- Bring project notes, documents and decisions into a searchable knowledge base.
- Connect AI assistants and tools with agreed access and human review.
- Test a pilot with your team and hand over a workflow you can maintain.
03 / Teaching & workshops
Learn through
your own projects.
Jan teaches Rhino and Grasshopper, Monoceros, Python and C# scripting, and AI-assisted tool development. Bring a project or a task you want to understand; the programme is adapted to your experience and goals.
- Universities: guest lectures, studio teaching and practical courses.
- Teams: workshops around your files, repeated tasks and design methods.
- Individuals: focused sessions, with an exercise and notes to keep.

Jan’s teaching and supervision includes UCL Bartlett, IAAC, the University of Toronto and the Academy of Architecture Amsterdam. Available online or in person.
Explore past workshopsA place to begin
Two-week
office diagnostic
Not sure where to start? Jan reviews a live project with your team, maps repeated work and develops one small pilot.
- Week 1: interviews with four to six people and a written task map.
- Week 2: three candidate pilots, followed by development of the smallest agreed one.
- Handover: a team workshop, documentation and a recommendation for the next step.
We agree the scope, consultant time, participation, access and fee in a written proposal. Two weeks describes the programme. Further development and ongoing support are scoped separately.
How the work proceeds
How we work
- 01
Discuss the need
We discuss your project and identify a task to work on first.
- 02
Agree the scope
Write down the outputs, checks, responsibilities, fee, and limits.
- 03
Work on real examples
Build and test with your files. Review the result with the people who will use it.
- 04
Handover and support
We document the tool and train your team before handover. The proposal specifies any ongoing support.
Discuss your project with us
Tell us about the work you need help with and the software your team uses.


