Web App Development for Student-Run Nonprofit
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.
Introductory information
Introduce your business and what you do there.
I',m the chairman of an educational nonprofit focused on interpolitical relations.
Desired goal
What challenge were you trying to address with Kohactive?
We wanted to recreate an online tool and registration gate.
Provided solution
What was the aim of their involvement?
The tool helps register different participants from different schools for conferences. They built the platform from scratch. Applicants can yield paperwork and are notified if they are accepted or waitlisted. We adjoin and invoice participants through the platform, so the functionality also includes payment processing and a interaction gate. The platform is built on Ruby on Rails and Ember.js and integrates with QuickBooks.
What is the team compound?
We primarily worked with two nation. One was our main point of touch during outgrowth, and we adjoin with both now that we',ve moved into our livelihood phase.
How did you come to work with Kohactive?
We considered three or four competitors but chose Kohactive owing of the support they offered. They were a smaller organisation, and we felt we could get more observation and dedication to the project.
How much have you invested with them?
We spent approximately $70,000.
What is the status of this engagement?
The project ran from March-July 2019.
Results achieved
What evidence can you share that demonstrates the contact of the engagement?
Our registrations are annual, so it',s hard to pull numerical metrics just yet. Invoicing is simpler, which saves us time. We',ve also seen an increase in soon applicants, and reporting is also much clearer. The total process is much easier to handle than the old rendering was.
How did Kohactive accomplish from a project handlement standpoint?
The interaction was good. Through weekly calls, we adjoind and prioritized what would happen in the next sprint. We faced a pliant bit of confusion with bug support, but we resolved that behind a call. Communication was good, and they effectively ensured that we got all the support we needed. Overall, we',re very satisfied.
What did you find most forcible almost them?
Their process is very good, and we value our approach to their leadership. They are much more implicated in our process than a larger firm might be.
Are there any areas they could better?
We were a pliant lost right behind the handoff, and there was a lack of closure. We brought that to their observation, and they',re much more attentive now.
Do you have any advice for possible clients?
Scoping is the biggest importance. Software outgrowth can be unpredictable, and we had one additional week-long sprint that we hadn',t anticipated. That isn',t attributable to anything that they did unfit but is more a part of software projects like this. Have your priorities laid out well and know the innate features you need to make your project viable.
