You don’t need an architect
You don’t need an architect. But you do need at least one person who thinks architecturally.
Common titles:
Team lead
Senior Dev
Architect
Principal
But, title isn't important.
What's important: At least one person should be responsible for the long-term, and the big picture.
Ideally, this person shouldn’t rule from an ivory tower.
Instead, they should foster conversations that assure we make solid architectural decisions *as a team*.
Another useful role for this person: Optimize developer velocity.
Look for opportunities to improve code quality, reviews, collaboration, processes, tooling, continuous integration, deployments, etc.
The goal: Help everyone deliver higher quality code, and move faster.