This resource is intended to introduce you to (or refresh you on) the tools we use at various project stages.

Basecamp

For communication and sharing deliverables

We use Basecamp for all project communication. It keeps conversations in threads related to each deliverable. It’s visible to all parties, to ensure that messages don’t get missed, conversations are transparent – and we can easily pull in the right expert to respond to any questions. It has a “Docs & Files” area where you can upload relevant documents for us, like brand guidelines, logos, and customer research.

It also keeps all conversations and project updates transparent for anyone joining the project later on, because they can catch up on previous discussions and decisions. You can respond to Basecamp messages directly from your inbox, or you can log in to see all threaded conversations, and reply.

Hive

For project management

We use Hive to transparently manage the project from start to finish. Every single task required to complete your website project exists within Hive—our team’s tasks, and your review rounds. You can see where your project is at, at any time, via Hive’s Gantt chart view.

You do not need to edit or learn how to use Hive to use the Gantt chart. We share a view-only version with you so that you can see what step the project is currently on, what’s next, and what remains before launch.

It’s important to remember that the dates shown in the Gantt chart are a projection based on default estimated turnaround times on each deliverable. If your review rounds take longer, or if your site is quite large and deliverables require more time to create, all of the other tasks’ dates will continue to push out.

Figma

Design tool for sitemap, UX prototypes, and UI design mockups

This is the tool we use for all of our design deliverables. You need to create a free account to use it. All feedback on the sitemap, UX wireframes, and UI mockups is collected via Figma comments. Learn more about how we use Figma.

BugHerd

For collecting feedback, QA, and bug reporting

BugHerd is used in the content and QA stages. For content collection, we install BugHerd so you can log tickets if you get stuck, can’t find something, or have questions.

In the QA stage you will also be putting in tickets, this time on your new development site. You’ll put in tickets anywhere that you spot a bug or something that doesn’t look or function right. We’ll collaborate through those tickets, assigning them back to you to review once the work is done. We also use BugHerd to collect launch requirements.

You will receive information on how to use BugHerd when it’s introduced to your project.

Google Calendar and Meet

For meetings

We use Google Calendar, and its integrated Google Meet feature, to book and run meetings throughout the project. You can join a Google Meet without an account or app—it works right in your browser. Google Meet also provides the ability for us to record project meetings for documentation purposes, and both of our teams can share recordings with other team members as needed.

We prefer that our Account Manager schedules most, if not all, meetings on behalf of everyone involved, to ensure our team’s availability and preparedness. But we may also accept meetings scheduled by your team (on your preferred platform) if our team has confirmed that we are available at the chosen date and time.

Google Drive, Docs, and Sheets

For documents and collaboration

We use Google Sheets to share the keyword rankings audit in the SEO Setup stage. We also may use sheets to collect some of your content. If you don’t have a Google account, it’s free to sign up.

Loom

For sharing how-to videos

We use this tool to make demo videos for you during QA, such as how to edit a part of a page, or where to find a setting that you want to change. You don’t need an account to view the videos in Loom.

If you’re having trouble with any of these tools, contact your Account Manager to get support.