Case study: how the Ohio Cattlemen’s Association built its monday CRM together with us
The Ohio Cattlemen’s Association, a nonprofit that works alongside the Ohio Beef Council, wanted its contacts, emails and event work in one place for a team of about eight. Instead of us building it for them, we built it together: a 45-hour collaborative build from June to July 2026, with their team working on screen shares with us and their administrator trained to run the system on their own.
| Organization | Ohio Cattlemen’s Association and the Ohio Beef Council |
| Team | About eight staff |
| Type of build | Collaborative build, with training |
| Time | 45 hours, including 5 hours of support after the project |
| Dates | June to July 2026, finished in August 2026 |
What did they need?
The association works closely with the Ohio Beef Council, and the two keep separate contacts and email. On our first call, the team asked for:
- One place for contacts, with the two organizations kept apart where they need to be
- Email activity tracked against each contact
- Tasks and projects for their events, like field days
- An administrator who could run it and train the rest of the staff, without calling us for every change
Why a collaborative build?
We offer two ways to build. In a full build, we build it and then train you. In a collaborative build, your team builds it with us on regular screen shares, which takes a few weeks longer.
The association chose the collaborative build, because the goal wasn’t just a working CRM. It was a team that knows how its CRM works. When your own administrator has built the boards with you, they can change them later without starting from scratch.
Two decisions that kept it simple
To be honest, two of the most useful things we did were choosing what not to add.
- The plan they already had. The association was on monday.com’s Pro plan for nonprofits. With a small team and simple permissions, we agreed Pro was enough, rather than moving up to Enterprise.
- CRM without extra project tools. Their events needed tasks and timelines, but not complex dependencies between projects, so monday CRM on its own covered it.
Both decisions kept the system smaller, cheaper to run and easier for the team to learn.
How did the project run?
| Step | What happened |
|---|---|
| Discovery call | The team described how they work and what they needed, in May 2026 |
| Workflow form | We sent our workflow form for their staff to fill in, so the scope would match how they actually work |
| Account set up | Done on day one, 2 June 2026 |
| Build | Three milestones built together on screen shares, through mid-July 2026 |
| Training | Our sessions alongside monday.com’s own courses, so the administrator could train the rest of the staff |
| Support | Five hours set aside for questions after the project |
What changed?
The association’s contacts, email activity and event work now sit in one CRM that its own team helped build and knows how to change. The project finished in August 2026, with support hours still set aside for questions after launch.
What should another small nonprofit take from this?
- Let your team build it with you if you want them to own it afterwards.
- Have your staff fill in the workflow form. The people who do the work know where things actually break.
- Don’t buy more plan than you need. A small team with simple permissions often doesn’t need the top plan.
- Leave out what you won’t use. A smaller system is one your team will actually use.
Frequently asked questions
What is a collaborative monday.com build?
Your team builds the system with us on regular screen shares, instead of us building it and handing it over. It usually takes four to five weeks, and your team learns the system as it’s built.
Can one monday CRM serve two related organizations?
Yes. The Ohio Cattlemen’s Association and the Ohio Beef Council work together but keep separate contacts and email, and one CRM can be set up to keep them apart where they need to be.
Does a small nonprofit need monday.com Enterprise?
Not always. With a small team and simple permissions, the Pro plan was enough for this association.
How long does a nonprofit CRM take?
This collaborative build ran from June to July 2026. See how long a monday.com implementation takes for more real timelines.
Does Wild 6 work with other nonprofits?
Yes. Nonprofits and foundations are a big part of our work. See how we set up monday.com for nonprofits.
Thinking about the same for your nonprofit?
Book a 30-minute call with me. Bring a quick recording of how your team works today, and I’ll tell you honestly whether a full build or a collaborative build fits you better. You can also compare partners in our list of the best monday.com consultants for community foundations and nonprofits.
