The Chief Automation Officer

I signed up for Zapier on March 5, 2014. I was Chief Operating Officer at Stupid Cancer at the time. Back then, I couldn't tell you what a cloud computing stack was, but I had one, and Zapier unlocked many doors and flipped on many light switches for me, professionally.

Three months after joining Zapier, Slack hit the market, and I was off to the races with automation. Suddenly every business data point was funneling into Slack as it quickly became the brain of Stupid Cancer. I have blogged in the past about Slack, so I will avoid doing that here. As a result, Slack dinged all day long at Stupid Cancer, and it still does in my various current roles.

When Wade Foster, Zapier CEO, posted this on LinkedIn, I felt seen:

Without realizing it, I have spent most of the past decade becoming a well-tuned Chief Automation Officer. It’s subtly been the hallmark of my career.

One of my favorite byproducts of automation is just how amazed people are at the very nature of it. There is little budget or margin of error for trying things out in the nonprofit world, especially with fundraising tools. Most fundraising platforms are awful and siphon much-needed funds out of charities to line their pockets. They would argue that they make it possible for nonprofits to be successful, and that's a debate I would love to have. I digress. People are amazed when you connect multiple apps, and data moves around 24/7.

With Zapier, we could suddenly do more than our out-of-the-box fundraising platform could do alone. I was not left wanting seven features and having to settle for four. I could have it all.

• I didn't need to export donors and import them into Mailchimp.

• I didn't need to watch my email for Stripe donations; I could get a Slack notification.

• I didn't need to create a to-do list task manually; Zapier took care of it.

My pivot to the private sector has created more meaningful automation opportunities in recent years. Now operating a membership-based company, my automation is focused on moving people through different states, such as lead, contact, active member, and former member. These states affect how we interact with you and your place in our cloud stack.

I wish I could say I spent a lot of time making flow charts and thinking about the end-to-end journey of my data. The reality, though, is most of my Zaps are born out of acute necessity and team inspiration. Perhaps one day, I’ll start keeping notes.

One consideration when running through the paces of creating automation is where Zapier fits alongside an app’s internal workflow system. Zoho Campaigns comes to mind in this example. I might use Zapier to get you from Facebook Leads to a Zoho Campaigns Mailing list with additional information. Still, I will let Zoho Campaigns read your contact record and qualify you for an email workflow. Keeping track of these relationships is essential so you don’t create loops or unforeseen automatic enrollment.

Automation can be daunting if you don’t know where to start. Services like Upwork have professionals for hire on a short-term basis to get you started. Once you start seeing what’s possible and connecting the dots between your workflows and cloud apps, you’ll get back those wasted hours doing things manually.

---

Further reading:

• The emergence of the chief automation officer

• Chief Automation Officers Are The Answer … But What Is The Question?

Nurture Fundraisers Using CauseVox, Zapier, and ConvertKit

Fundraising is a crucial part of a non-profits existence. The biggest opportunity for a non-profit is leveraging its community to fundraise on its behalf. The hardest part is maintaining the attention of community members and empowering them to feel confident in their efforts.

For a year now, I've been using CauseVox as my primary fundraising tool for the Testicular Cancer Foundation. I really enjoy CauseVox because it puts a lot of the controls on the admin side, rather than having to go through an account manager or some other contact on the provider side.

Exploring CauseVox Zaps on Zapier

About 6 months ago, CauseVox began teasing their Zapier beta integration. As a Zapier lover and full-blown nerd, I'd been waiting for the integration to go live to see what kind of pathways I would have access related to fundraisers. A few weeks ago, the news came through that the integration was live. Excitement ensued.

The CauseVox options are simple and to the point. Did we A) Get a new fundraiser or B) Get a new donation?

With this info, I can do a lot of cool things.

One of the main features that really (I mean really) expensive fundraising platforms up-charge for is communicating with fundraisers within the platform. Campaign updates, direct emails, drip emails, etc. There's a ton of options.

My first Zap using CauseVox is to bridge the gap between a lack of communicating with fundraisers and using an email marketing platform I live in all day long, ConvertKit.

Using ConvertKit

With ConvertKit, I can create drip email sequences to walk my fundraisers along a series of emails that convey important information, emotion, and reinforce why they are so important to our organization. (Fundraisers...if you are reading this, we love you!)

CauseVox has the ability to send a welcome email, which is fantastic. I haven't yet decided if I will keep this email active or send them all to ConvertKit for the entire email series. (On one hand, it's a safe bet that the email will always send, but on the other hand, I would love to have the open rate and click metrics that ConvertKit provides.)

Creating a Drip Email Sequence

Currently, our email series is broken up like this:

Email 1: Welcome to Fundraising

Email 2: More about CauseVox and tactical points around fundraising (includes link to proprietary PDF about fundraising)

Email 3: Where the money goes / why this is so important

Final Thoughts

I am curious to see how the response is to our new series of emails. With all communications, the last thing you want to do is be over communicative and have someone lose interest entirely. By looking at my ConvertKit open and click rates, I'll see which emails are most effective and which need some fine tuning.

Non-Profits: Technology is The Biggest Donation You Aren’t Leveraging

Any non-profit COO or CTO will tell you that finding the technology that appropriately addresses their needs is tough to come by. The existing platforms with the non-profit in mind often cost upwards of $25,000 to engage. There are several problems with this situation. First, it is impossible to know that a CRM/donor database/360° fundraising platform will meet your needs long-term. Second, these platforms will lock you in for a year at least, and the much-needed updates will never come. Lastly, these platforms are insular systems without API or any means of connecting them to other solutions. (San Francisco, feel free to help us out here.)

I’m lucky to work in a non-profit vertical that spans from the tiny side-project to the multi-million dollar behemoth fundraising machine. In a space where we’re all working towards the same goal, it’s interesting how organizations leverage technology to carry out their mission.

Over the past six years at Stupid Cancer, we have stopped and started with so many different platforms my staff now cringes any time I tell them I’ve found something new. It’s true that I’ve probably worn out my welcome by having them help me test new things, but old habits die hard. When it was just Matthew and myself, we had to compensate for the lack of staff. It was the wild west of free trial exploration, and I learned a lot from it.

As we’ve grown over the past few years and hired staff to help us, my instinct remains to take a tech-forward approach.

I am also a big believer in putting automated systems in place where appropriate and removing the human element. There is no reason to try to do things better than computers. I see it way too often in this community of limited resources. It will only reduce your capacity for upward growth.

We recently did an internal exercise where we measured how much time each staff member spent on their respective duties. While they mostly landed as we thought they would, there were some instances where outside forces were pulling us away from getting out jobs done. In any company — especially a growing one – this is bound to happen. Ultimately, we took a look at the results and have begun to figure out how to mitigate these distractions by adding articles to our Zendesk FAQ, for example.

In this world of highly scrutinized non-profit budgets, there is so much time and money that can be saved by utilizing low-cost platforms like Zapier or IFTTT (Which doesn’t cost anything at all). I actually find most SaaS-based companies are willing to give deep discounts just based on your merit.

Google and Slack are two examples of companies that reward 501(c)(3) organizations with a lifetime subscription to their platform for free. If a platform doesn’t offer free or discounted services, offer to create compelling content for them that will be mutually beneficial.

We recently received a lovely donation from a platform we had used in the past that was in transition. The temporary separation was a mutual agreement, as they changed their core product offering. When the dust settled on their end, we jumped right in line to sign up.

As the maturation of Stupid Cancer continues from a tiny startup non-profit to million dollar organization, I remain vigilant in making sure we stay nimble and unburdened by the unnecessary.

How to Be Less Busy with Slack

The Beginning

In the early days of Stupid Cancer (formerly I'm Too Young For This! Cancer Foundation), we had two employees and a small team of "executive" volunteers. Everyone was spread out around the country, and keeping in touch was critical.

Back then, in 2010, Yammer was the gold standard of the emerging corporate social networks. The design took cues from Facebook, Twitter, and LinkedIn. It was a great tool that ultimately became the backbone of the organization.

Yammer was eventually acquired by Microsoft, which is when the product kind of lost its way. Upgrades and tweaks became less and less, and the pricing structure also changed, for the worse. We made the decision to migrate platforms in early 2014, to Bitrix24.

Bitrix24 was fine for a time. It had the threaded posts, just like Yammer. It also had tasks, which was new and interesting. The team was underwhelmed by their mobile app, which wasn't as good as Yammer's had been. The search resumed.

Enter Slack

Slack is a communications platform, with an emphasis on chat, search, and integrations. It's hard to put my finger on exactly what I like most about Slack. Perhaps it's a 3-way tie between the custom emoji's, Slackbot responses, and custom loading messages.

I originally intended on making this blog post purely about how I use Slack (IE: Integrations), but I felt it was relevant to discuss where the team was coming from.

The initial kickback was that Slack didn't have the threaded chat view like we were all accustomed to. There was an initial flood of conversations that were disjointed and hard to navigate if you'd been away from Slack for a few hours. Keeping track of ideas was like nailing jello to a wall.

Upon further inspection, it was our Slack naivety that contributed to the mess. We suffered from what I would call "FOCC" (Fear of Creating Channels). Slack channels are essentially chatrooms that live in the left navigation of your Slack app. You can star the important ones, and they get pinned to the top of the list. DM's and private groups live under them.  You can learn more here.

Our watershed moment came when channels went from being just chatrooms, which is how our Internet brain works, to actually being channels. I will list below some of my channels and their purpose. (Keep in mind we're a non-profit that serves young adults with cancer.)

My Slack Channels

#discussion

We have broken conversation-based channels into buckets based on our programs and projects. There is also a channel to list items throughout the week that you'd like to discuss at the weekly staff meeting.

#development

This channel integrates with a Trello board. Any time a change is made on that board, it's reflected in this Slack channel. It's a great way of keeping everyone in the loop on a critical part of our operation.

#rss

I have tried several RSS-feed-based channels. They can be helpful in keeping you up-to-date on your favorite blogs and news sources. I have a channel that syndicates everything we post to our Tumblr, which is a syndication of our Facebook page via IFTTT. (Inception, anyone?)

#incoming-money

This channel is my favorite, for obvious reasons. We have a web store that uses PayPal Pro, and two incoming donation sources that send emails when donations are received. I send information from all three sources to #incoming-money via Zapier.

#outgoing-money

This channel lets the team know when bills have been paid. Using Zapier's email channel, we can capture bill pay notification emails from bill.com or Capitol One and have them post to this channel. It keeps information flowing and helps the finance and ops team in the loop.

#random

This channel syndicates all the inquiries into our Zendesk. It also shows Mailchimp subscribes, unsubscribes, and campaign activity. It should probably be called #customerservice.

#feed-instagram

Another great Zapier fueled channel is our Instagram channel. In this channel, we track images posted on IG with #stupidcancer. It's a great way to source content for our Facebook wall, and see what conversations are happening related to our brand.

#feed-twitter

Just like above, except this channel syndicates all mentions of @StupidCancer.

#feed-reddit

Reddit has an active /r/cancer community. With this RSS integration, we can see what kind of conversations are happening and source content for our FB wall.

#giphy

Slack has a great direct integration with Giphy that I've taken advantage of since we upgraded our Slack plan from free to paid. Once enabled, you can write things like "/giphy blogging" and get an image like this one on the right.

In Closing

This story has a happy ending. Slack has quickly become the pulse of the organization. It's our Death-Star-for-good, making us incredibly efficient. I'm told threaded conversations are in the pipeline, which will make my team members happy.