How Civic Dialog Works for Nonprofits

Civic Dialog connects nonprofits with volunteer software developers who build custom automation solutions at no cost. You don't need technical staff, a budget for consulting, or any knowledge of how software works. You need to know what's taking too long — and be willing to describe it clearly. Here's how the full process works.

1. Describe your need with the Discovery Wizard

The starting point is the Discovery Wizard — a structured intake process that walks you through describing a manual task in plain language. You're not writing technical requirements. You're answering questions like: What are you doing by hand right now? How often do you do it? What does the output look like? What would have to be true for this to be considered fixed?

Good candidates are tasks that follow a predictable pattern: pulling data from one place and putting it in another, generating reports from a spreadsheet on a schedule, sending notifications when something changes, formatting and sending a recurring email. If a staff member is doing the same sequence of steps repeatedly, it's likely automatable.

The wizard takes roughly fifteen to thirty minutes. It ends with a structured brief that describes the problem, the current process, the desired output, and an estimate of how much time the automation would recover. That brief is what goes to volunteer automators.

2. Your need goes on the Needs Wishlist

Once submitted, your need is published to the Needs Wishlist — a public listing that volunteer automators browse when looking for projects. The wishlist is searchable by category and tools, which means your need surfaces for developers whose skills are relevant to your specific problem.

You don't need to do any outreach. The platform handles discoverability. When an automator is interested, they submit a proposal.

3. Review proposals and choose an automator

Proposals are short statements from volunteer developers explaining their proposed approach, the tools they'd use, and a rough timeline. You can receive multiple proposals on a single need. You review them, ask follow-up questions through the platform if you want to, and select the match you're most comfortable with.

Before work begins, both sides confirm scope in writing: what the automator is building, what they're not building, what you need to provide (a data export, access to a system, a test case), and what success looks like. This step is required — it prevents the most common cause of project failure, which is discovering halfway through that both sides had different assumptions at the start.

4. The project runs through a structured workbench

Once scope is confirmed, the project moves into an eight-phase workbench: from requirements refinement through build, testing, deployment, and handoff. You and your automator both have access to the project view, which shows the current phase and what's happening in it.

Your involvement during the build phase is primarily to answer questions and test what you're sent. You don't need to understand how the automation works technically. You need to be able to tell the automator whether the output looks right — whether the report has the correct numbers, whether the email looks the way it should, whether the edge cases you care about are handled. That kind of feedback is the most useful thing you can provide.

Volunteer automators work on their own schedules. Projects aren't on a billing clock. If your automator needs a week to deal with something at their day job, that's normal and expected. The workbench keeps the project visible and recoverable.

5. Receive your automation

The final phases of the project cover deployment and handoff. Before the project closes, your automator documents how the automation works in plain language: what it does, how to run it, what to check if something looks wrong, and who to contact. The handoff is complete when your staff can operate the automation without the automator on a call.

Automations are designed to run on infrastructure your organization already has access to — Google Workspace, Airtable, a shared drive, a form tool — rather than requiring new software or ongoing vendor relationships. The goal is something your team can actually maintain.

6. Impact tracking

After the project closes, the platform asks you to self-report the time the automation saves per week. That figure feeds into impact tracking: annualized hours returned to mission work, estimated dollar value at a nonprofit salary rate, and a record of how many times the automation has run. These numbers appear on the platform's Impact Scoreboard and in your organization's project history.

The tracking is lightweight — there's no ongoing reporting burden. It's there because the cumulative numbers matter: to funders who want to understand operational efficiency, to board members who want to see the return on administrative capacity, and to the platform itself as evidence that volunteer time is being used well.

What this is and isn't

Civic Dialog is not a consulting firm. Automators are volunteers — they're contributing their skills because they want to, not because they're under contract. That means timelines are flexible and there are no service guarantees. What it does mean is that you get serious technical work done at no cost, by people who are genuinely interested in solving your problem.

The platform is free for nonprofits. There are no subscription fees, no paywalls on any feature, and no vendor lock-in on what gets built. Civic Dialog is a nonprofit and is in the process of obtaining 501(c)(3) status in New York.