We design products
people actually
use.
Research, design, and development for complex products. We work with teams building software where the interface is the product and first-day adoption is the measure of success.
Find the real problem. Build the right solution.
We embed in your world — users, workflows, organizational dynamics — and surface an evidence-based foundation you can build on with conviction.
Explore Discovery →Make complex systems feel obvious.
Designed for the dispatcher at 2am and the analyst navigating live data. Every decision validated against real behavior.
Explore Design →Ship the design.
A design partner in the room through build — catching the hundred small decisions that shape how a product actually feels.
Explore Development →Why Flying Circle
Complexity is our craft.
Twenty years designing for seventeen-step workflows, specialist users, and live high-stakes data. Government platforms. Enterprise insurance. Real-time traffic systems. Products where precision in the interface directly impacts outcomes.
We challenge assumptions early, protect the user experience when scope shifts, and stay engaged through launch — because we care that it works as well in practice as it does in prototype.
Frequently Asked
What's the typical project timeline?
Projects vary based on scope and complexity. Discovery typically takes 6–12 weeks. Design phases run 8–16 weeks depending on the breadth of the interface. Development timelines depend on your engineering resources and feature scope, but we usually allocate 12–24 weeks for substantial products. We always build in iteration time post-launch.Do you work with distributed teams?
Yes. We have a fully remote team and have worked successfully with clients across time zones. We use a combination of async documentation, recorded walkthroughs, and scheduled sync sessions to keep everyone aligned. For certain phases—particularly discovery and early design—we often recommend in-person time for richer research and ideation, but we structure projects to minimize this where possible.Can you work within our existing design system?
Absolutely. We prefer to work within existing systems when they're well-documented and serve the use case well. We also audit and improve systems when constraints are limiting the product experience. Our goal is always to ship faster and more consistently by respecting the frameworks you've already invested in.What if we want to keep one phase and skip the others?
We can do this, but with caveats. Discovery informs design. Design informs development. Skipping phases means you're building on less evidence. That said, if you've already done solid research or have an in-house design team, we can absolutely jump to the phases where we add the most value—usually development or augmenting design with research validation.How do you handle handoff after a project ends?
Thorough handoff is non-negotiable. We provide detailed design systems documentation, component libraries, development best practices, and architectural patterns. We also run training sessions with your team and build in a post-launch support period where we're available for questions and refinements as your team takes the reins.
Have a complex product?
Tell us what you're building. We'll tell you where design can make the biggest difference.
No pitch deck required. Just a direct conversation about your product and where you want to take it.
Let's Talk