I’ve spent most of my career working in architectural practice and using Revit on real projects.
And over the years I’ve built up a fairly long list of things that make me think:
There has to be a better way of doing this.
Repetitive tasks. Too many clicks. Workflows that are harder than they need to be. Things that are easy to get wrong simply because they rely on someone remembering to do them the same way every time.
A few years ago, I started trying to solve some of those problems myself.
First with Dynamo.
Then pyRevit.
And eventually by learning to build native Revit tools in C#.
From individual solutions to Flow
What started as a few solutions to individual problems has gradually grown into Flow by Adapt — a growing suite of Revit tools built around real architectural workflows.
The thinking behind it is pretty simple:
Find the friction. Make the workflow better.
Sometimes that means automating something repetitive. Sometimes it means making a complicated process easier to understand. And sometimes it’s just about taking something that already works and making it quicker, clearer or more consistent.
Flow now includes tools for project setup, workspace management, content, modelling, documentation and model QA.
More importantly, the individual tools have gradually started to become part of something bigger, with a common interface and shared framework behind them.
Built in practice
Most of this has stayed within our architectural practice while I’ve continued building, using and refining it.
That’s an important part of what Flow is.
The tools aren’t being developed around hypothetical workflows. They grow from the problems we encounter while actually working in Revit — and they continue to change as we use them.
Built in practice. Designed for real Revit workflows.
Starting to share Flow
I’ve now reached the point where I’d like to start sharing some of it.
FlowByAdapt.com is live, along with Flow.Help, a dedicated help and documentation site that also connects directly to the tools through F1 in Revit.
This isn’t really a product launch.
Flow is still evolving, and there’s plenty more I want to explore.
Instead, I’ll use Flow Insights to share some of the tools, the problems that led to them, and probably a bit of what I’ve learned going from Dynamo scripts to developing a much larger native Revit toolset along the way.
Over the next few weeks I’ll start looking at some of the individual workflows in more detail.
What would you change?
I’m also interested in the problems other Revit users encounter.
If you could fix one repetitive, frustrating or unnecessarily complicated Revit workflow, what would it be?