Groundwork.
A four to six week engagement for organizations doing real work on systems that stopped keeping up. An honest assessment, one clarity document the whole staff runs on, a working tool built for how you actually operate, and a 90-day roadmap. You keep all of it.
- Your intake lives in a form, an inbox, and three spreadsheets, and things fall through.
- The board asks for numbers that take a week to assemble.
- Every staff member describes what you do a little differently to funders.
- The person who knew how something ran left, and it left with them.
- You are doing good work and cannot show it without starting over each time.
- Grant reporting takes longer than the program it reports on.
- You bought software nobody uses, because it was not built for how you work.
None of these are a messaging problem. They are what it looks like when an organization outgrows the systems it started with, and there has never been a quarter free enough to rebuild them.
Grant cycles fund the activity. Groundwork funds the infrastructure underneath it.
Program funding goes to activity. It finances what an organization does, a program, a hire, a season of work. When the cycle ends, the organization is structurally where it started. Nothing changed about how decisions get made, how the work gets described, or how any of it survives a departure. Organizations cannot staff or program their way past systems they have outgrown, and operational knowledge tied to one person's tenure is not infrastructure. It is one departure away from being lost.
Adding staff, on its own, cannot close it. Hiring a coordinator, a comms person, or a program manager is the reasonable move, and often the only lever available. But new people inherit the same stretched systems, the same undocumented processes, and the same messaging that lives only in the founder's head. Infrastructure is what turns headcount into capacity.
Groundwork builds the infrastructure underneath the work. A purpose-built tool does not expire at the end of a grant year. A message framework does not depend on any single person staying. A clarity document does not need to be relearned every time the team changes. This is a different category of spending, one that compounds instead of resetting at the next cycle.
Two organizations, and what they still run on.
The same three questions for each one. Where they were, what was built, and what is still in use now that we are gone.
Growth had outrun the systems. Athletes, families, coaches, and volunteers lived across lists that had grown up separately, and the website could not feed any of them.
A full operations platform: one people database covering athletes, families, and volunteers, plus communications, calendar, contact sync, and intake wired directly into the public site. Then the site itself.
The platform and the site, both in daily use by the chapter.
Inquiries arrived by email into a shared inbox. Proposals, room assignments, setup, and follow-up lived in separate places and separate heads.
An inquiry and booking system end to end: intake, proposals and contracts, availability and room logic, operations checklists for setup crews, invoicing, and post-event follow-up. Thousands of historical bookings migrated in. Alongside it, the clarity document the department describes itself with, and a six-month communications calendar it executes on its own.
All of it, in production, running the department's work now.
Four phases, four to six weeks, one organization at a time.
Diagnosis
A structured assessment that surfaces the real gaps across six organizational domains before a single framework gets written.
Clarity Framework
Message architecture and core narrative, built so every person on the team describes the work the same way in any room.
Tool Build
A custom operational tool designed around the organization's primary gap. Built for this organization specifically, not adapted from something generic.
Handoff
The engagement ends when the groundwork is complete. Every deliverable transferred, every tool taught, every priority sequenced into a 90-day roadmap the organization can execute on its own.
Four deliverables, designed to compound, not expire.
Every organization walks away with the same four pieces of infrastructure. Not a report. Not a slide deck. The kind of work that keeps functioning after the engagement closes.
Message Framework
Core narrative, positioning, audience-specific language, and the guidelines that keep it consistent across every funder report, every outreach email, every conversation.
Immediately usable.Organizational Clarity Document
A structured reference capturing mission alignment, role clarity, and operational priorities. Built to onboard and align new and existing team members, and to inform decisions at every level.
Built to scale.Custom Operational Tool
A purpose-built digital tool tailored to the organization's most pressing operational gap. Intake systems, communications workflows, AI-assisted dashboards, designed around this organization specifically.
Keeps working after we leave.90-Day Priority Roadmap
A clear, sequenced action plan with defined outcomes. Immediate direction and measurable next steps from day one after the engagement closes.
Day-one clarity.One engagement, and what is still standing six months later.
Infrastructure that did not exist before.
- →The kind of operational clarity most organizations your size never get the quarter to build
- →A tool built for your operation, not adapted from something generic
- →Language you can use immediately across fundraising, outreach, partnerships, and hiring
- →Less dependency on any single person holding everything together
- →A roadmap, not just a report
The operational gap is not an anomaly. It is the rule.
have all the foundational elements in place to maximize their impact.
A Stanford survey of more than 3,000 people across the sector, executives, staff, board members, and donors, found that only about one nonprofit in ten has all of it in place. The rest operate with structural gaps that quietly compound.
have three months or less of cash on hand.
More than half the sector runs without the reserve that would let it pause and rebuild, and 36% ended 2024 with an operating deficit, the highest in ten years of the survey. Organizations in that position cannot buy their way out of an operational gap. They have to be built out of it.
return from operationally healthy organizations versus struggling ones.
McKinsey's organizational health work found that healthy organizations deliver three times the returns of unhealthy ones. In nonprofits specifically, 91% of staff at healthy organizations report they are achieving their mission, against 60% at struggling ones.
The gap is not a sign that something went wrong at your organization. It is the ordinary result of building a program faster than the systems under it. Groundwork exists to close it on purpose, once, in a fixed window.
The same engagement,
run across a group
you select.
Most of this page is written for the organization doing the work, because that is who decides. If you are a funder, a fiscal sponsor, or a corporate partner, the same engagement runs across a small group you select, and Sonate handles execution inside each one.
You keep what belongs to you: the public launch, the solicitation, the selection, and the impact story at the close of the cycle. What you get back is a documented before-and-after for each organization rather than a report on dollars deployed.
The model is built to repeat. It scales across annual cycles, absorbs additional consultants as it grows, and produces the kind of specific evidence a committee or a communications team can actually use.
Engagements are scoped per organization. Founding rates apply while the first outcomes are being documented.
If any of that sounded like your week, that is enough to start.
Nothing to prepare and nothing to put together first. A short conversation is enough to tell whether this is the right thing for you right now. Engagements are scoped per organization.
Message sent.
It lands in our inbox now. We reply within one business day.