Almost EVERYONE who tried headless systems said they saw benefits. Download the state of CMS now!

Storyblok now on AWS Marketplace: Read more

O’Reilly Report: Decoupled Applications and Composable Web Architectures - Download Now

Empower your teams & get a 582% ROI: See Storyblok's CMS in action

Skip to main content

How Fundbox solved their content management issues

Fundbox is a financial platform for small businesses that offer fast and easy access to business credit. Since its founding in 2013, Fundbox has connected with nearly 300,000 small businesses in the U.S.

Fundbox migrated their website on top of Jamstack and chose Storyblok as their CMS after a pretty long research phase. The process took them 1/3 of the time compared to their previous experience, while solving their content management issues.


Section titled The challenge The challenge

In 2019, Fundbox began a rebranding process, including a full website redesign. As the website relaunch was mostly design-driven, the team didn’t initially focus much on the back-end technology. Together with an external agency, the team relaunched Fundbox in September 2019 after 4.5 months of work.

While the project accomplished the design aspect and provided a new front-end, the team soon realized they were stuck with a home-grown back-end CMS that didn’t feel like a big improvement, especially given the recent spend. The Django-based CMS wasn’t user-friendly for marketing, and it wasn’t state of the art for engineering, leaving both teams dissatisfied. The lack of seamless collaboration between and within teams was becoming a serious issue. Not long after the initial relaunch of the website, it was time to search for a better CMS solution…

Section titled Moving towards Jamstack Moving towards Jamstack

Alex Volkov, Marketing Solutions Architect at Fundbox, was certain that moving to Jamstack was the way to modernize their websites and deliver great performance. His challenge was convincing a team of marketers who didn’t know much about Jamstack that it was the best solution, especially given the results of the previous project. In other words, Alex had to prove why moving to jamstack and a headless CMS was worth the migration. Alex began a journey of helping key stakeholders understand the concept behind “headless” and Jamstack, and focused on the following business benefits to convince the skeptics:

  • Technology independence: Moving towards Jamstack and using Netlify allowed the development team to be freed from conventions of the backend, and make their technology choices completely independent of that.
  • Better website performance: This decoupled approach allowed them to build a faster frontend with better loading times and a greater UX.
  • Faster deployment: The headless architecture would ensure a speedy development, unlike the previous experience.
  • User-friendly CMS: Those with the most contact with the CMS, namely content creators and marketers, would have a much easier time getting things done.

Once everyone agreed on the benefits of Jamstack, it was time to actually settle on a future-proof CMS.

Section titled Finding the right CMS Finding the right CMS

The team’s experience in 2019 had led them to be especially cautious of their next step. They set out to find a flawless option by outlining some key requirements:

  • Support Jamstack and Vue/Nuxt
  • Preview content before publishing
  • Roll back changes easily
  • Ability to work in a componentized way that would fit the way they built with Vue
  • Flexibility in data structure, agility in adding/removing fields, data schemas
  • Fast! In both delivery of content and deployment
  • Ability to SSG the website
  • Great and easy workflows for the marketing and content team
  • Workflow management with an audit trail

Following these criteria, Alex and the team made a shortlist of possible candidates, which eventually led to them choosing Storyblok.

  • Quote from Alex Volkov, Marketing Solutions Architect

    "We wanted to move towards Jamstack, so we were looking at various headless systems and evaluating them in more detail. When comparing Storyblok with Contentful, GraphCMS, and DatoCMS, we soon realized that two main points set Storyblok apart:

    First, the visual editing experience for our marketing team was superior to others. Second, Storyblok’s component-based approach would allow Fundbox to create components that can be customized, nested, and filled with content."

    Alex Volkov
    Alex Volkov
    Marketing Solutions Architect

Section titled The result: Doing more in ⅓ of the time The result: Doing more in ⅓ of the time

After making the decision to go with Storyblok (with Nuxt.js and hosted by Netlify), Alex and the team got to work. Fundbox converted all of the website components to vue, migrated the data to storyblok schema and went live within 5 weeks.

As Alex put it: "Compared to last time, the switch to Storyblok took 1/3 of the time with a fraction of the costs."

The workflow issue was fixed immediately. Developers loved the hassle-free back-end experience and the component approach, while marketers loved the visual editor and the seamless content workflows.

Implementing Jamstack allowed the Fundbox team to build new sites in record-time, leading them to think about other web projects, including internal websites.

For marketers, the new workflows were essential, especially when compared to the previous collaboration issues. Additionally, Storyblok’s unique visual editor sealed the deal:

  • Quote from Alex Volkov, Marketing Solutions Architect at Fundbox

    “The Visual Editor was the actual winner for us. Having a live preview gives our editors a powerful editing experience.”

    Alex Volkov
    Alex Volkov
    Marketing Solutions Architect at Fundbox

Choose a better way to
manage your content