How Civic Dialog Works for Automators

Civic Dialog is a matching platform for volunteer software developers — called automators — who want to build real automation solutions for nonprofits. Projects are scoped, structured, and come with built-in impact tracking. Here's how the full process works, from signing up through closing a project.

1. Create your automator profile

When you sign up, you build a profile that describes your technical background: the languages, frameworks, and automation tools you work with. This isn't a resume — it's a lightweight record that helps the platform surface relevant needs and helps nonprofits understand who they're working with. You can update it at any time.

2. Browse the Needs Wishlist

The Needs Wishlist is a public listing of automation needs posted by nonprofits. Each need comes from the Discovery Wizard — a structured intake process that helps nonprofits translate operational pain into a clear, scoped brief. By the time a need reaches the wishlist, it includes a description of the current manual process, what the desired output looks like, how often the task runs, and an estimate of time saved.

You can filter by category, complexity, or tools involved. Most needs are small enough to complete in a few weeks of part-time work — a data transformation, a recurring report, an intake form that feeds a spreadsheet, a notification system. The point isn't to rebuild a nonprofit's entire tech stack. It's to eliminate one specific thing that shouldn't require human time.

3. Submit a proposal

When you find a need that matches your skills, you submit a proposal. This is a short statement: what you think the solution looks like, the tools you'd use, and a rough estimate of the timeline. You don't need to commit to a full spec upfront — the proposal is about demonstrating that you understand the problem and have a viable approach.

Nonprofits can receive multiple proposals on a single need. They review them, ask follow-up questions if they want to, and select the match they're most confident in.

4. Get matched and confirm scope

When a nonprofit selects your proposal, the platform facilitates the introduction. Before work begins, both sides confirm scope in writing: what you're building, what you're not building, what success looks like, and what the nonprofit needs to provide (data exports, access credentials, a test environment). This step exists to prevent the most common source of project failure: misaligned expectations at the start.

5. Work through the project workbench

Once scope is confirmed, the project moves into the eight-phase workbench. The phases run from requirements through deployment and handoff, and both sides have visibility into the current state of the project at all times. You log progress as you move through phases; the nonprofit can see where things stand without needing to send status emails.

The workbench is designed for async, part-time work. There's no expectation of daily availability. The structure replaces the need for constant check-ins — the phases make clear what's done and what's next.

6. Deploy and hand off

The final phases of the workbench cover deployment, user testing, and handoff documentation. The nonprofit tests the automation against real data before it goes live. You document how it works — what it does, how to run it, what to do if something breaks — in plain language that a non-technical staff member can actually use. Handoff is complete when the nonprofit can operate the automation independently.

7. Your impact record

When a project closes, the nonprofit self-reports the time saved per week. That figure feeds into the platform's impact tracking: annualized hours returned to mission work, estimated dollar value at a nonprofit salary rate, and a record of the automation's ongoing run history.

Your automator profile accumulates a record of every project you've completed: what you built, what tools you used, and the measured impact. That record is yours — it's a portfolio of real end-to-end work, including requirements gathering, scoping, build, deployment, and user handoff. Most side projects don't get that far. These do.