What You’ll Learn
- When This Step-by-Step Method Is the Right Fit
- Step 1: Pick One Workflow Worth Automating
- Step 2: Map How the Workflow Actually Runs Today
- Step 3: Optimize Before You Automate
- Step 4: Choose the Right Automation Tool
- Step 5: Build and Test in Parallel
- Step 6: Measure Results and Iterate
- A Worked Example: Automating Donor Acknowledgment
- Common Mistakes to Avoid
- Frequently Asked Questions
- Your Next Steps
- Sources
When This Step-by-Step Method Is the Right Fit
This guide is for nonprofit teams that want to automate a real workflow themselves, in the right order, rather than buy software and hope it sticks. It works best when you have a recurring, manual process that eats staff time every week and follows mostly predictable rules.
Automation has room to help at almost every nonprofit. McKinsey research has found that roughly 60% of jobs include at least 30% of activities that could be automated with current technology. For lean nonprofit teams, that 30% is often the difference between staff spending their week on data entry and spending it on programs.
The method below is deliberately tool-agnostic and sequential. The single most important rule is that optimization comes before automation. The rest of this guide walks the six steps in order, then applies them to a concrete example.
Step 1: Pick One Workflow Worth Automating
Start by choosing a single workflow that is high-frequency, rule-based, and currently manual. Resist the urge to automate everything at once: one well-chosen workflow teaches your team the method and delivers a visible win that builds support for the next one.
Score candidate workflows against four questions: How often does it run? How much staff time does it consume? How consistent are the steps each time? And how damaging is it when it fails? A process that runs daily, follows a predictable path, and currently depends on one person’s memory is an ideal first target. Common nonprofit candidates include donor acknowledgment, new-volunteer onboarding, grant-deadline reminders, and monthly report assembly.
Avoid starting with a workflow that requires heavy human judgment at every step or that changes shape with every case. Those are poor first automations and tend to sour a team on the whole effort.
Step 2: Map How the Workflow Actually Runs Today
Before changing anything, document how the workflow actually runs right now, every step, every tool, every handoff, and every decision point. Map the real process, not the one in the staff handbook, by sitting with the person who does the work most often.
This step almost always surfaces surprises: undocumented shortcuts, steps that exist only in one person’s head, and decision branches that different staff handle differently. That key-person dependency is a known nonprofit risk. NTEN’s research has repeatedly found that a majority of nonprofits report their technology and operations capacity as chronically understaffed, which is exactly how single-person workflows form. Writing the process down is the first step to removing that risk.
Capture the map as a simple numbered list or a flowchart. You will use it in the next step to decide what to fix before any software is involved.
Step 3: Optimize Before You Automate
Fix the process before you automate it: remove redundant steps, standardize the decision rules, and make ownership clear. Software applied to a broken process does not fix the process, it just makes it fail faster and at greater scale.
This is where many automation projects quietly fail. Organizations that document and improve their core processes before adding new technology consistently get more value from that technology than those that buy first and clean up later, a pattern McKinsey has documented across sectors. For a deeper walkthrough of this stage, see our guide on how process optimization works for nonprofits.
Optimization does not have to be elaborate. Cutting two unnecessary approval steps, agreeing on a single email template, and writing down the rule for handling exceptions is often enough to make a workflow safe to automate. Scottship Solutions completes process development before automating any workflow where an error would affect donors or compliance.
Step 4: Choose the Right Automation Tool
Match the tool to the workflow rather than the other way around. Most nonprofit automations fall into three buckets: native automation already inside your CRM or accounting system, connector tools such as Zapier or Make that link separate apps, and Microsoft Power Automate for organizations standardized on Microsoft 365.
For a workflow that lives entirely inside one platform, the built-in automation is usually the cheapest and most reliable option. For a workflow that moves data between systems, such as a donation in your payment processor triggering a thank-you in your CRM, a connector tool is a better fit. For a side-by-side comparison of the leading options, see our roundup of the best workflow automation software for nonprofits.
Whatever you choose, confirm it integrates with the systems you already run and that it stays within the budget your board has approved. The cheapest automation is the one that uses a tool you already pay for.
Step 5: Build and Test in Parallel
Build the automation for your one workflow, then run it in parallel with the manual process for two to four weeks before you rely on it. Parallel operation catches the edge cases your map missed, the unusual donor, the international address, the refund, without putting real relationships at risk.
Start small: automate the most repetitive step first, confirm it behaves correctly, then extend it. Keep a human checkpoint on any step that involves judgment or money until you have seen the automation handle a full cycle cleanly. Document what the automation does so it is not, in turn, locked in one staff member’s head.
Only switch off the manual process once the automation has run a complete cycle, including month-end or a full giving period, without errors.
Step 6: Measure Results and Iterate
Decide how you will measure success before you start, then check the numbers afterward. One or two metrics is enough: time saved per week, error rate, or turnaround time from trigger to completion.
Across Scottship Solutions engagements, optimized and automated workflows typically cut staff time on the affected process by 20 to 40% and reduce error rates substantially, because documented decision rules replace each person’s own interpretation. Capturing a simple before-and-after measure also gives you the evidence to justify the next automation to your leadership and board.
Automation is not set-and-forget. Revisit each automated workflow on a schedule, after a tool update, a staffing change, or a new reporting requirement, so the automation keeps matching how the work actually needs to run.
A Worked Example: Automating Donor Acknowledgment
Donor acknowledgment is the workflow most nonprofits should automate first, because it runs constantly and directly affects retention. Research from Bloomerang and the Fundraising Effectiveness Project consistently shows that fast, personal acknowledgment is one of the strongest predictors of whether a first-time donor gives again.
Walking the six steps: (1) Pick it, acknowledgment is high-frequency and rule-based. (2) Map it, you may find gifts are thanked in 3 to 5 days through a manual export that only one staff member knows how to run. (3) Optimize it, agree on one tax-compliant template, set a 48-hour target, and define how unusual gifts are handled. (4) Choose a tool, use your CRM’s native automation if the gift is recorded there, or a connector if your payment processor and CRM are separate. (5) Build and test, run the automated thank-you alongside the manual one for a month and check every message. (6) Measure, track acknowledgment time before and after and watch repeat-gift rates over the following year.
The same six steps apply to volunteer onboarding, grant-deadline tracking, and monthly board reporting. Once your team has run the method once, the second and third workflows go much faster.
Common Mistakes to Avoid
- Automating before optimizing. The most expensive mistake. Clean the process up first, or you will automate the mess.
- Starting with a judgment-heavy workflow. Processes that need human discernment at every step are poor first automations. Begin with rule-based work.
- Skipping the parallel test. Switching off the manual process on day one means edge cases hit real donors and grantors instead of a test log.
- No metrics. If you did not measure before, you cannot prove the automation worked or justify the next one.
- Letting the automation become the new key-person dependency. Document how it works so the knowledge does not simply move from a person’s head into an unlabeled tool.
Related guides: AI and automation for nonprofits, how process optimization works, and the best workflow automation software for nonprofits.
Frequently Asked Questions
The first step is to pick a single workflow worth automating, not to buy software. Choose one process that is high-frequency, rule-based, and currently manual, such as donor acknowledgment or grant-deadline reminders. Score candidates by how often they run, how much staff time they consume, how consistent the steps are, and how damaging failure is. Starting with one well-chosen workflow teaches the method and delivers a visible win.
Yes. Optimization should always come before automation. Software applied to a broken process does not fix it, it makes it fail faster and at greater scale. Before adding any tool, remove redundant steps, standardize the decision rules, and clarify who owns each step. Organizations that improve their processes before adding technology consistently get more value from that technology, which is why Scottship Solutions completes process development before automating donor or compliance workflows.
Automate high-frequency, rule-based workflows first. The most common starting points for nonprofits are donor acknowledgment and stewardship, new-volunteer onboarding, grant-deadline reminders, and monthly report assembly. These run often, follow predictable steps, and usually depend on one person’s manual effort today. Avoid starting with workflows that require human judgment at every step or change shape with each case, because they make poor first automations.
Nonprofit automations usually rely on one of three tool types: the native automation already built into your CRM or accounting system, connector tools such as Zapier or Make that link separate apps, and Microsoft Power Automate for organizations standardized on Microsoft 365. For a workflow inside one platform, native automation is cheapest and most reliable. For a workflow that moves data between systems, a connector tool fits better. Choose the tool that integrates with what you already run.
Decide on one or two metrics before you start, then compare before and after. The most useful measures are staff time saved per week, error rate, and turnaround time from trigger to completion. Across Scottship Solutions engagements, optimized and automated workflows typically cut staff time on the affected process by 20 to 40% and reduce errors substantially. A simple before-and-after measure also gives you the evidence to justify the next automation to leadership.
Your Next Steps
- Name your most painful recurring workflow. Ask your team which weekly task they dread most or which one most often goes wrong. That is your first automation target.
- Map it in 30 minutes. Sit with the person who runs it and write down every step, tool, and decision point. Compare it to any existing documentation.
- Optimize before you shop for tools. Remove redundant steps and agree on the decision rules before evaluating any software.
- Run a two-week parallel test. Build the automation, run it alongside the manual process, and only switch over after a clean full cycle.
- Schedule a free consultation with Scottship Solutions, and we will help you pick the right first workflow, optimize it, and automate it with tools that fit your budget.
Sources
- McKinsey & Company, Operations, automation, and process improvement research
- McKinsey Global Institute, Automation potential and the future of work
- NTEN, Nonprofit Technology Enterprise Network: operations and capacity research
- Bloomerang, Fundraising Effectiveness Project: donor retention data
- Zapier, Workflow automation guides and use cases
Work With Scottship
Scottship Solutions helps nonprofits move from manual, key-person workflows to optimized, automated systems that any trained staff member can run. We work exclusively with nonprofits and small businesses, so the recommendations fit lean teams and approved budgets, not enterprise overhead.
Our approach pairs process development with AI and automation, guided by our 5 Levels of AI framework: optimize the process first, then automate the predictable steps, and reserve staff time for the judgment and relationships that only people can handle. Schedule a free consultation to map your highest-leverage workflow and build a plan to automate it in the right order.
