Blog How we work with you on projects

Good project communication should make the work easier, not become another job to manage. We keep decisions visible, write down the details, and schedule a meeting only when a live conversation will help.

Getting started

Before we write code, we spend time understanding what you are trying to accomplish. "Build a website" or "make an app" describes the output. We need to understand the business problem behind it. Who are your users? What does success look like? What has been tried before? Answering those questions helps us define the right project before development begins.

Everything lives in Basecamp

We use Basecamp for project communication. Everyone who needs the context gets access. Basecamp holds the files, discussions, to-do lists, decisions, and progress updates in one place.

You do not have to dig through email for a decision from three weeks ago. If it affects the project, it goes in Basecamp, where anyone can check the current status and the record behind it.

Weekly check-ins (when they make sense)

For larger projects, we use a weekly call to demonstrate the work, discuss what is next, and make decisions together. We keep the agenda focused and the call short. For smaller projects, we skip them and handle everything asynchronously in Basecamp.

We record every call. If someone can't make it, they can watch it later. We also post a summary in Basecamp with the key decisions and action items, so nobody has to scrub through a 30-minute recording for one decision.

Writing first, meetings second

When a tricky problem comes up, we write it down before scheduling a call. We explain the problem, lay out the options, and make a recommendation. Everyone gets time to consider the tradeoffs instead of making a snap decision in a meeting.

Writing first also gives our developers longer blocks of uninterrupted work. When a live conversation is necessary, everyone arrives with the same context and time to form an opinion.