Contents
At CoralTree we believe in the time-tested adage by Steve Jobs: "real artists ship". The best way to build great software is to keep shipping it. We release Basil updates regularly, because steady progress creates stronger products, higher motivation to innovate, and happier customers.
Shipping frequently isn’t about rushing. It’s about staying responsive, building trust, and making room for both user feedback and team-driven innovation.
Frequent Releases Create Momentum
When updates are infrequent, teams tend to over-plan, over-engineer, and wait for the “perfect moment" to release. But perfect moments rarely exist. And when they do, the changes often feel disconnected from what users actually need.
With Basil, we release small, focused improvements continuously. For example, we’ve shipped dozens of updates in the past few months that improved:
- User experience across team management, files, tasks, and chat
- Support for bulk updates and regional file storage
- AI tools to speed up eSignature workflows
Each of these was a result of listening to both our intuition and our users, and then moving quickly to improve the experience.
Feedback Suggests Direction. But Teams Drive Innovation.
Customer feedback plays a role in shaping what we build. If a feature isn’t working as expected, or something slows down a user's workflow, we want to hear about it.
But innovation comes from within. Some of Basil’s most valuable features didn’t come from requests. They came from our team thinking deeply about product workflows and asking: "how can we make this easier?" or "wouldn't it be cool if users could do this?"
By combining external input with internal product thinking, we stay grounded in real-world needs while pushing our product experience forward.
Small Releases Are Safer, Smoother, and Easier to Adopt
Shipping smaller updates allows us to test and refine incrementally. For example, when we introduced bulk updates, we rolled them out in stages, each monitored and improved based on usage. And our ambitious AI roadmap involves phasing releases into well-defined components, running beta tests, and releasing to general audiences after we are confident with the safety and efficiency of each feature.
This approach reduces risk, shortens learning curves, and helps our users adapt naturally without needing to relearn how to use our features. Over time, these small, stable steps add up to major gains in usability.
Users Feel the Progress
Frequent updates build a rhythm of progress that users can feel. Every time Basil gets better - whether it’s a faster load time, a smoother workflow, or a smarter AI tool - our users gain more confidence that they’ve chosen software that’s alive, improving, and listening.
This constant stream of improvements helps users trust that bugs will get fixed and new capabilities will keep showing up. More importantly, it makes users feel supported and respected. They don’t need to file a support ticket or escalate an issue to get results - they simply see the product getting better, week after week.
It’s not just the big features that matter. It’s the feeling that Basil is moving with them. That sense of momentum, of visible care, is what turns satisfied users into loyal advocates.