Our client, a large financial services corporation based in Boston, wanted to create a website for a new service for small and mid-sized employers across the US. Their challenge: while they knew what they wanted the offering to be, they weren’t sure how to translate that offering into a website, and then didn’t know if the required integrations with their current systems would be possible by their target launch date. (Oh, did we not mention that they wanted the site branding, design, content development and construction to be completed in less than 7 months?)

pod, plus our user experience (UX) design partner BlackPepper, and our visual design/branding partner Stoltze Design, dove right in. Since the timeline was very aggressive, we took a two-staged approach: designing, building and launching the public marketing site first, and then designing, building and launching the private site for enrolled customers. As much as possible, we overlapped phases. We helped the client to make decisions about their offering, and how the website would present that offering to their prospective customers and enrolled customers. Once the “what” and “how” were decided, pod built the site in Drupal.

The Digital Public Library of America (DPLA) has the institutional backing to make the digital heritage of the United States of America available to all. With the Alfred P Sloan Foundation’s support, DPLA needed a trusted partner to make their vision a reality: to aggregate data from hundreds of US private and public institutions, reliably publish data through an API, and usefully present content on their website.

With proven experience of creating and developing data-intensive websites, pod designed the overall architecture, and provided technical oversight and implementation of the API and ingest engine.  pod orchestrated the process of selecting and engaging the website’s frontend designer, and managed a development team to create data-driven mobile-friendly responsive layouts.  We delivered an expandable solution, from start-to-finish,
on time and on budget.

Our client, a small healthcare services company, had landed their largest contract to-date. The new contract would expand our client’s services more than three-fold over the next year, by requiring that they provide services geared towards enhancing their clients’ Centers for Medicare & Medicaid Services (CMS) Star Rating while producing better patient health outcomes. In order to capitalize on this opportunity, our client needed to rapidly implement new features into their existing application without disrupting the operation of several dozen clinicians and pharmacists that use the system to complete their core daily workflow.

Our project management and development team members collaborated with our client, leveraging knowledge that the pod team had for the subject matter and the technical landscape. Our team worked with the client to quickly understand the most important success criteria for the project and to establish a roadmap and a timeline to achieve success.

pod team members drove the Star initiative from inception to completion by working directly with our client’s clinical subject matter expert, senior leadership, and account management teams to ensure the final product would meet CMS requirements as well as meet utilization guidelines by clinicians out in the field.

The Berkman Center for Internet & Society wants to keep linked content on the internet accessible.  Links can fail because of denial of service attacks, censorship, or link rot.  Reliably accessing linked content is a problem for Internet users everywhere. The Berkman Center approached pod to build tools for website creators to keep content they’ve linked to available.

pod designed and implemented plugins for the most popular open source content management systems (Drupal, WordPress) and web servers (Apache, Nginx).

A local financial services client employs over 900 people across the globe. They decided to move their custom enterprise HR system to the cloud-based Workday Human Capital Management platform because it satisfied almost every one of their requirements to support the employee lifecycle. It did not however quite fit their compensation functionality requirements. In order to make the switch, they needed help figuring out how to execute the tricky integration between their legacy compensation system and Workday.

pod chose to use SQL Server Integration Services and developed clients for Workday’s REST API, using Custom Script tasks in C#. This made sense because the technology stack already had a broad footprint across the organization. The ease of managing and scheduling recurring tasks in SQL Server, plus pod’s deep integration experience made this an easy choice.