Why We Built Coherence: A Founder's Perspective
The story behind Coherence - from the frustrations that sparked the idea to the principles that guide how we build.
It Started with Frustration
Like most founders, I didn't set out to build a CRM. I set out to solve a problem that was driving me crazy.
I was running a consulting practice, and every day felt like a battle against my own tools. My inbox was a mess of client conversations mixed with newsletters and spam. My CRM (which I'd paid good money for) sat mostly empty because updating it was a chore. My calendar, notes, and task list lived in three different apps that didn't talk to each other.
I wasn't running my business. I was managing my software.
The Moment of Clarity
One afternoon, a longtime client called to follow up on a proposal I'd sent. Simple enough - except I couldn't find the proposal. It was buried somewhere in my email, attached to a thread I couldn't locate because I'd forgotten the subject line.
I spent 15 minutes searching while my client waited. Embarrassing? Absolutely. But more than that, it was clarifying.
I realized the problem wasn't my organizational skills. The problem was that my tools were designed for individual tasks, not for the connected way work actually happens.
The Principles Behind Coherence
That frustrating afternoon led to a set of principles that guide everything we build:
1. Your data should connect automatically
If you send an email to a client, that email should automatically appear in that client's record. You shouldn't have to log it, file it, or copy-paste a link. The connection should just exist.
2. Your workspace should match your business
Every business is different. A consulting firm tracks engagements and deliverables. An agency tracks campaigns and retainers. A service company tracks jobs and crews. Your tools should adapt to your vocabulary, not force you into someone else's.
3. AI should handle busywork, not make decisions
We're not trying to replace human judgment. We're trying to eliminate the tedious work that keeps you from using that judgment. Summarize long email threads. Suggest where records should link. Extract action items. The boring stuff.
4. Simple to start, powerful when you need it
You should be able to connect your email and start working in minutes. But when you're ready to build custom workflows, create complex views, or integrate with other tools, that power should be there.
What We Learned Building This
Building Coherence taught us a lot:
Users don't want features - they want less friction. Every feature we've added has been evaluated through one lens: does this reduce friction in someone's workday?
Defaults matter more than options. It's tempting to make everything configurable. But great defaults mean users get value immediately, without having to set anything up.
Email is still the center of gravity. Despite all the new communication tools, email remains where most business relationships live. Any system that ignores email is fighting reality.
The Road Ahead
We're just getting started. Coherence today handles email, contacts, calendars, tasks, and custom modules. But our vision is bigger:
- Deep integrations with the other tools your business runs on
- Automation that handles routine processes end-to-end
- Mobile experiences that don't feel like an afterthought
- APIs that let you extend Coherence in ways we haven't imagined
Most importantly, we're committed to building this with you - our users. Every feature we ship is informed by real conversations, real frustrations, and real workflows.
Join Us
If you've ever felt like your tools are fighting against you instead of working for you, Coherence might be what you've been looking for.
We'd love to have you along for the ride.