Yeah, I basically agree with everything you said! More specifically:
We tested with the small nonprofits using the same hacked software we used for DBT (literally a static page with an iframe to our webapp)
We were in fact making financial transaction errors (e.g. double charging donors) since our database was not designed for scale, so we had to rebuild our backend. We had no in-house engineers, so we paused development until we hired engineers who have rearchitected the backend.
We’re trying to launch with mid-sized nonprofits using the improved technology we built for the small-nonprofits.
Our sales calls have revealed pretty similar feature requests from every mid-sized nonprofit (e.g we need a CRM integration). Many of these features are in our roadmap, but I agree with you that it would be even better to build it for a specific charity that is willing to sign rather than based on “generic” tech.
We’re already focused on getting 3-5 “case studies” from mid-sized nonprofits, but I’ve been reflecting recently on going to greater lengths to build custom features for those organizations, and after reflecting on your comments I’m updating further in that direction.
We did a lot of this custom work for DBT—we stopped developing generic features and almost worked like a dev shop to meet their needs (although we’ve slowed developing custom features for that charity as we are no longer learning as much from them).
Yeah, I basically agree with everything you said! More specifically:
We tested with the small nonprofits using the same hacked software we used for DBT (literally a static page with an iframe to our webapp)
We were in fact making financial transaction errors (e.g. double charging donors) since our database was not designed for scale, so we had to rebuild our backend. We had no in-house engineers, so we paused development until we hired engineers who have rearchitected the backend.
We’re trying to launch with mid-sized nonprofits using the improved technology we built for the small-nonprofits.
Our sales calls have revealed pretty similar feature requests from every mid-sized nonprofit (e.g we need a CRM integration). Many of these features are in our roadmap, but I agree with you that it would be even better to build it for a specific charity that is willing to sign rather than based on “generic” tech.
We’re already focused on getting 3-5 “case studies” from mid-sized nonprofits, but I’ve been reflecting recently on going to greater lengths to build custom features for those organizations, and after reflecting on your comments I’m updating further in that direction.
We did a lot of this custom work for DBT—we stopped developing generic features and almost worked like a dev shop to meet their needs (although we’ve slowed developing custom features for that charity as we are no longer learning as much from them).