How we started
Simplicity matters. If we had to distill the combined learnings of decades of experience building software and leading talented teams and organizations into two words, that's it. Simplicity is explicit, cohesive, single-purpose, understandable.
Yet, our common tools, paradigms, and languages push us towards complex solutions. It's so easy to add that one line of code where it doesn't belong, add that tiny implicit dependency, or ignore that pesky "edge case."
We started Simply Stated because there is a better way. It's been around forever. But without a modern ecosystem, easy integration into existing stacks, and tooling to make your friends jealous, it never quite caught on. We built Simply Stated to fill that gap, to solve our embarrassment at our industry's inability to quickly ship software that actually works, and to help you bring the users who depend on you a better experience than they ever thought possible.
Interested in helping us build better ways to build systems? Reach out!
