What was the scope of their involvement?
The project had highly-involved discovery and information architecture phases. We used analytics to review content and identify audience demographics. Subsequently, they did visual design during the development and implementation stages. Per our agreement, the team created the site’s skeleton on Drupal 7 but did not assist with content migration. While we have an in-house development team that does some Drupal work, their imported our events calendar data into the frontend. We expect to use this system until the eventual Drupal 9 launch.
What is the team composition?
There were 7 members on the team, but not all were engaged at every phase; only a couple people worked on discovery and information architecture. We moved into implementation and development with a separate team. The development team included: a backend developer, a senior developer, and a frontend developer. Andrew [Co-founder, Kalamuna] served as project manager. However, he was more involved in development than discovery and information architecture. Overall, Kalamuna’s resources were very stable with significantly less turnover than other companies.
How did you come to work with Kalamuna?
We had 6 companies submit proposals through a formal RFP cycle and met with 4 finalists. Coincidentally, Kalamuna submitted a proposal for another project the year before, but did not get the contract. But we chose them this time because their size was appropriate for the collaboration and scope. Furthermore, they had the requisite Drupal expertise and a good work culture. Prices were reasonable and cheaper firms did not possess the same skill levels.
How much have you invested with them?
We spent between $160,000 and $180,000.
What is the status of this engagement?
Work started September 2015 and the site launched July 2016.