← Back to Case Studies

FiscalNote: Engineers for a Flagship Product Rewrite

Legal and Policy TechnologyUnited States
FiscalNote policy software cover for our staff augmentation case study

Project overview: engineers on a flagship rewrite

FiscalNote helps organizations track legislation, regulation, and policy. We staffed full-stack engineers on a months-long rewrite of the flagship product, in Ruby on Rails, WordPress, PHP, and Python, with frequent releases to production.

About FiscalNote

FiscalNote builds software that helps organizations follow legislation, regulation, and policy. Government affairs and legal teams use it to see what government is doing and decide what to do about it.

The challenge: a rewrite already in motion

FiscalNote was sequentially rewriting large portions of its flagship product. The effort ran for months, with frequent releases to production, in a fast environment with a high bar for the code. Four to five teams of engineers were working on different features, sometimes on the same parts of the product. That takes technical skill and clear communication between teams.

At the same time the company was tightening its budget. It needed a firm that could supply engineers, including people who had already worked together, at a price that could flex with the work.

Who we staffed

The engagement ran from January 2021 through March 2022. It covered custom software development and staff augmentation.

We started with a self-sufficient team of full-stack engineers on Ruby on Rails, including an engineering manager. The team had worked with that manager before, so FiscalNote got a group that already knew how to work together. The engagement later expanded to PHP and WordPress development and to Python.

In all, five to six Maxiom software engineers worked on the main project and on additional work that was added as the year went on. FiscalNote continued the engagement past the first months and expanded it to other projects.

How the rewrite shipped

The deliverable was frequent releases to production, behind feature flags, in a DevOps-enabled codebase. About 20 to 25 other engineers were committing to that same codebase at the same time. The Maxiom engineers had to land changes without blocking the teams already in the repository.

They worked in the tools FiscalNote already used: Gmail, Slack, Jira, Miro, and Confluence. Project management followed FiscalNote's process, with suggestions when that process could be improved.

One later request was a niche combination, WordPress together with React.js. We placed an engineer for that skill set.

What FiscalNote reported

The VP of Engineering reported very good code quality, and a strong working relationship with QA, internal staff, and product management. Pace and turnaround on time-sensitive bugs stood out.

Engineers for a rewrite

Need more engineers on a product rewrite? We can add staff augmentation, a dedicated development team, or backend developers, and we can stay with the build and the releases.

Rewriting a product and short on engineers?

Tell us the codebase, the release cadence, and which skills are missing. On a 30-minute call we will tell you how a team would join the work.

Project inquiry

Tell us what you are trying to ship

Response within 1 business day

The Challenge

FiscalNote was rewriting large portions of its flagship product and releasing to production often. Several engineering teams were working on overlapping features at the same time, and the company needed more engineers, including technical leadership, on terms that fit a tighter budget.

Our Solution

From January 2021 through March 2022 we staffed a self-sufficient team of full-stack engineers and an engineering manager. The work started in Ruby on Rails and expanded to PHP, WordPress, and Python. Five to six Maxiom software engineers worked inside FiscalNote's existing process.

Technologies Used

Staff AugmentationRuby on RailsPHPWordPressPythonReact.jsDevOpsFeature Flags

Client Testimonial

Their pace of development and responsiveness (turnaround on time-sensitive bugs, etc) was also exceptional.

VP of Engineering

FiscalNote

Services Provided

Why Maxiom?

Ready to start? Back to the inquiry form

Frequently asked questions

What is FiscalNote?

FiscalNote builds software that helps organizations follow legislation, regulation, and policy.

What did Maxiom do for FiscalNote?

We staffed a rewrite of large portions of the flagship product from January 2021 through March 2022. The team started in Ruby on Rails, with an engineering manager, and later added PHP, WordPress, and Python.

How many engineers did Maxiom provide?

Five to six software engineers, working with four to five FiscalNote teams that were building overlapping features. About 20 to 25 other engineers were committing to the same codebase.

How did releases work?

Frequent releases to production, behind feature flags, in a DevOps-enabled codebase.

Which tools did the team use?

FiscalNote's own tools: Gmail, Slack, Jira, Miro, and Confluence. The team worked inside the process FiscalNote already had.

What did FiscalNote say about the engineers?

The VP of Engineering reported very good code quality, a strong relationship with QA, internal staff, and product management, and exceptional pace and bug turnaround.

Did the engagement stay on the first project?

FiscalNote continued it past the first months and expanded it to other projects. One later request was WordPress together with React.js, and we placed an engineer for that skill set.

Can Maxiom add engineers to a product rewrite?

Yes. Through Maxiom.dev we provide staff augmentation and dedicated development teams.