Four-week programme · November 2026
Become an Agentic Structural Engineer
Pick one repetitive workflow from your own work. In four weeks, build an AI agent that does it for you — while the engineering decisions stay yours.
Registration closes
Built in the course: ETABS torsion iteration
Muhanned Othman, a structural engineer in Dubai, built this agent in the course. It runs the ACI 318-19 torsion stiffness-modifier iteration in ETABS until every beam passes, and its results match a benchmark he calculated by hand. Beams that still fail stay with him.
Who it's for
- You're a practising structural engineer with a workflow you repeat on every project.
- Its inputs are already digital files, like IFC models, PDFs or spreadsheets, and you can check its result yourself.
- You want to hand off the repetitive part and keep making the engineering decisions.
Not for you if
- You want a general overview of AI rather than a working agent for one workflow.
- You want someone to build the tool for you. In the course, you build it.
How it works
You finish with a working agent that runs one real workflow from your own projects — from the project files it starts with to the deliverable it hands back. It does the repetitive part; you set the assumptions, make the engineering decisions, and validate every result. The target is 30% less time on that workflow, measured against the baseline you time yourself before week one.
-
Before we start
Pick your workflow
Choose one repetitive workflow from your own projects, write down how you do it today, and time one run.
You leave with your baseline: the time one run takes you today.
-
Week 1
Design the workflow
Map the steps, the decisions, and the points where you approve. Then design your agent around them and prove the tools on a small model.
You leave with a flowchart of your workflow and its approval points, and a toolchain that runs.
-
Week 2
Understand the data
Define the data structure your workflow runs on — what every step takes in and hands on — then fill it with data from your IFC models, PDFs or spreadsheets.
You leave with your workflow's data in code, filled from your own project files and checked on screen.
-
Week 3
Connect the tools
Reach your calculation tools the three ways an agent can — an API it calls, a command it runs, an MCP server that describes itself — and add the checks that stop it from ever handing you an unverified answer.
You leave with an engineering tool your agent can call, with checks on inputs, units and results.
-
Week 4
Run the agent
Watch a roof-optimization skill built and run from IFC to a verified report and drawings. Then write the skill for your own workflow: instructions, references and scripts, with checks and the points where you review.
You leave with an agent that runs your workflow, a deliverable you've verified, and the time it saves against your baseline.
See the Week 4 demo
Watch an agent design a timber roof
From an IFC model to a checked design, a report and drawings, stopping wherever the engineer has to decide.
Your instructor
Mohamed Adil
I'm a structural engineer who taught myself to code and, since 2023, have built the tools I always wished I had. The biggest is Awatif, an open-source tool for 3D frame analysis in the browser, with 185+ stars on GitHub.
I built this course because the fastest way for an engineer to save time today is an agent they build for their own workflow, driving the tools they already trust. Some ideas along the way worked and some flopped; it's all on the blog.
Questions
Do I need to know how to code?
No. The agent writes the code. Week 2 covers what you need to read and check it, starting from what a data type is.
Which workflow should I pick?
One you repeat on your projects, whose inputs are already digital files, like IFC models, PDFs or spreadsheets, and whose result you can check yourself. Time one run before Week 1: that's the baseline your agent is measured against. If you'd rather not use your own project, follow the timber roof example instead.
Does it work with ETABS or the software I already use?
The agent drives the tools you already trust; it doesn't replace them. If your software has an API, the agent can use it, the way Muhanned's agent runs ETABS. Week 3 covers the three ways an agent reaches a tool: an API, a command line, and an MCP server.
What do I need to install?
VS Code, Git, Node.js, uv and the ChatGPT Codex extension, which needs a paid ChatGPT plan. A prep video walks you through each one before Week 1. Check first that you're allowed to install software on your work machine.
What if I can't make a Saturday?
Every session is recorded and posted afterwards. The sessions are demos: you watch, and the building happens in that week's assignment on your own workflow, with the two private reviews to keep you on track. So you can take the whole course from the recordings.
Can my company pay?
Yes. I send an invoice with your company name and VAT number, and a team can book several seats on one invoice. Message me to arrange it.
Not ready yet?
Get the newsletter: new agent examples from structural engineering, and the next cohort's dates.