A full service, retainer-based design company, Limn focuses on creating effective partnerships with the businesses they work with. Their design solutions distinguish their partners from the fray by clearly illustrating their mission, values, and goals with compelling design solutions. Their design solutions distinguish their partners from the fray by clearly illustrating their mission, values, and goals with compelling design solutions.
Last updated May 13, 2026
Project summary: We needed a partner who could handle ambiguity early, then execute predictably once requirements were clarified. Delivery discipline and communication quality were both important.
The collaboration felt grounded in outcomes rather than vanity features. They pushed back when something added complexity without user value, which we appreciated. Internal adoption has been better than expected, partly because workflows now match how teams actually work. A few visual elements can still be refined, but functionally the system is in a strong place.
Well-structured codebase with sensible conventions, making internal maintenance easier
Initial discovery could have been shorter; first two weeks felt documentation-heavy
Project summary: We needed a partner who could handle ambiguity early, then execute predictably once requirements were clarified. Delivery discipline and communication quality were both important.
Good execution with realistic expectations. They did not overpromise, and that made planning much easier on our side. We had one integration issue with a third-party API rate limit that impacted timelines briefly, but they implemented retry handling and monitoring quickly. End result: reliable delivery and a solid foundation for phase two.
Well-structured codebase with sensible conventions, making internal maintenance easier
Initial discovery could have been shorter; first two weeks felt documentation-heavy
Project summary: We needed a partner who could handle ambiguity early, then execute predictably once requirements were clarified. Delivery discipline and communication quality were both important.
Communication quality was one of the stronger parts of this engagement. We always had visibility into progress, blockers, and next steps. Their engineers challenged assumptions respectfully and prevented a couple of costly feature detours. There were minor delays during final data migration, but they staffed up and recovered most of the schedule quickly.
Good domain understanding, thoughtful architecture choices, and clean handoff documentation
Some change requests required formal reprioritization, which was correct but slowed quick tweaks