After years building software, AI forced me to rethink a few assumptions
I spent years writing code at Microsoft and then ran my own tech company for a decade. Long enough that most problems in software development start to feel familiar.
Except one:
the handoff gap never really got better.
The work always started clean and slowly drifted off — not because anyone messed up, but because the system itself allowed it.
When AI arrived, it wasn't "another tool." It broke the old pattern.
Suddenly the layers we treated as separate — design, flows, implementation. These could be crossed in a single step.
That's what pushed us to rebuild Sketchflow and rethink how teams move from idea to product. And now we're integrating full code generation directly into that flow, both for web and mobile projects.
Two early observations from our own workflow:
AI is shifting real value upstream. The meaningful work becomes intent and structure, not pixel-perfect handoff documents.
Teams move faster when they stop recreating the same decisions twice.
We're still early in this process, but it already feels like a different rhythm of building.
More details coming soon at sketchflow.ai — and I'm genuinely curious how other teams are adapting as AI reshapes the edges of the product workflow.
