We design and build software for the web and mobile devices. That means interface design, copywriting, branding, front-end development, back-end development, and everything in between. Most importantly, our job is to solve for the customer's problem. What do they actually need? Everything stems from there.
Building great software is not about raising (and spending) a bunch of money, hiring people you don’t need to do jobs you made up, or trying to "go 10x" and "change the world". It's about building tools that help us do other things more quickly and efficiently. It’s about identifying the right things to work on and putting that work in front of real people. That’s what we care about. That’s what we’re good at.
We're John, Chance, and Garrett. We've been working together for more than three years. Along the way we've found a shared philosophy on how software ought to be made. We truly care about how software fits into the bigger picture - in our business, in our clients' businesses, and in the world we all share.
You can reach us by e-mail at email@example.com. Otherwise, see you around.
It doesn’t have to be this way. Some problems are truly complex, but the software made to address the problem shouldn't add layers of complexity. We avoid introducing complexity by maintaining focus on the real customer problem at hand, and identifying the right things to work on. Everything else is secondary.
Design doesn't mean making things pretty. It's not about pixel perfect wireframes or choosing the right button color. It's about communicating clearly. It's about getting the point across. As humans we communicate primarily with words, so we start every design with the copy - What are we trying to say?
Feedback is critical to the success of any product, not just software. A product dies when it is hidden away for months in development. The only way to get feedback is to put something in the customer's hands.
Form definitely follows function, but first we have to figure out what function is supposed to be. Before writing any code or sketching any interface, we uncover and clearly define the customer problem we're solving for and why it needs to be solved. We call this process "Discovery", and it helps us make sure we don't waste our time or our clients' money. Discovery comes first.
We want to work with you, not for you. Collaboration and the sharing of ideas are critical to this process. Just as engineering and design are important, domain knowledge is invaluable to the success of a product.