Pros
Most people care, work hard, and have good intentions. This leads to an environment of trust within your team.
Plenty of avenues to give feedback (both formal and informal).
There is a purpose behind your work (helping church partners).
Catered meals and retreat.
Cons
When I started at Church Community Builder we relied upon common sense and pushed authority & autonomy to those doing the work. Strategic direction still originated from the leadership/product team, however, tactical leadership was handled by those doing the work (and we had no middle-management). This was true for all teams (development, customer success, etc).
Unfortunately, the company has grown into a sluggish bureaucracy. There are far too many "middle-managers" who provide little to no value on a daily basis. As a result, managers attempt to prove value by implementing change, creating policies, and adding processes.
This is incredibly demoralizing for those who just want to get the work done. Meetings, approvals, committees, etc. are barricades to progress, and they give a false sense of job security for middle-managers. Let your employees take risks, own their decisions, make mistakes, and learn.
I'm sorry to say, but Church Community Builder has turned into the kind of environment the CEO says he used to hate.
A final note on salary... I see several reviews talking about "below average" compensation. That's not entirely true across the board... At certain leadership levels, you have access to see salary bands for roles. Generally, the customer-facing roles (customer success, on-boarding, implementation) are in much lower salary compared to management and software development.
As a Developer, I was paid very well (better than most) but I certainly wasn't the best Developer. If you're fortunate to be perceived as valuable by the Leadership Team (as I was) you'll probably have a competitive salary.
