Fixed-cost, Monthly Maintenance Services
Tags: ruby, maintenance
Published: 2023-05-23 14:46:30

---
title: Fixed-cost, Monthly Maintenance Services
published: true
date: 2023-05-23 10:23:45 UTC
tags: ruby,maintenance
canonical_url: https://fastruby.io/blog/monthly-maintenance-services.html?utm_source=dev-to&utm_campaign=monthly&utm_medium=x-post
---

Ever since we started offering [productized Ruby and Rails upgrade services](https://fastruby.io) and [upgrade roadmaps](https://fastruby.io/roadmap), we’ve been interested in helping as many people and companies as possible.

Unfortunately, in the past we’ve had to turn down companies who wanted to work with us but couldn’t secure the minimum monthly budget to work with our experts.

I’m pleased to announce that we’re now offering new opportunities for startups and small businesses to work alongside our team.

In this article, I will share a few new options to collaborate with our team of experts who specialize in [technical debt](https://fastruby.io/blog/tags/tech-tebt) remediation.

<!--more-->

## Why

Recently I had the opportunity to connect with a lot of SaaS founders at [MicroConf](https://microconf.com/) ‘23 which made me realize that there are many entrepreneurs, startups, and small businesses out there that want to pay off technical debt by investing a small amount of money per month.

While teams understand the need to remediate their technical debt, this very often loses priority to shipping features, releasing patches, and addressing other tasks prioritized in their product roadmaps.

Although everybody would like to upgrade their app as fast as possible, sometimes that’s just not in the budget. Instead, a good alternative can be to gradually work through your technical debt with a slower-paced retainer model.

## What's included in our monthly maintenance services

Our fixed-cost, monthly retainer will include services to gradually reduce the technical debt in your application. Our services will include:

- [Ruby Upgrades](#ruby-upgrades)
- [Rails Upgrades](#rails-upgrades)
- [Dependency Management](#dependencies)
- [Performance Monitoring](#performance)
- [Tech Debt Management](#tech-debt)
- [Security Patches](#security)

### Ruby Upgrades

If your application could use a Ruby upgrade, we will submit a pull request that looks like this:

![Pull request to upgrade Ruby to 3.2](https://fastruby.io/blog/assets/images/ruby-upgrade-example.png)

(Source: [Upgrade to Ruby 3.2 on Points](https://github.com/fastruby/points/pull/290/files))

If your application is not properly configured to [dual boot](https://www.fastruby.io/blog/upgrade-rails/dual-boot/dual-boot-with-rails-6-0-beta.html) with [`next_rails`](https://github.com/fastruby/next_rails), we will submit a PR that looks like this:

![Pull request to set up dual booting in a Gemfile](https://fastruby.io/blog/assets/images/rails-upgrade-dual-boot-example.png)

(Source: [Set up dual booting on Benchmark.fyi](https://github.com/fastruby/benchmark.fyi/pull/8/files))

This will be the basis of our work around [dependency management](#dependencies).

We will make sure that your application can run with both versions of Ruby. If you are on Ruby 2.7, we will make sure that your test suite works with both [Ruby 2.7 and 3.0](https://www.fastruby.io/blog/ruby/upgrades/upgrade-ruby-from-2.7-to-3.0.html).

Once we fix all the errors in your test suite, we will make sure that your staging environment works with the next version of Ruby. If anything goes wrong, we will make sure we patch all issues before we deploy the change to production.

### Rails Upgrades

Similarly, we will gradually tackle Rails upgrade projects. We will use our years of experience to submit many, tiny pull requests that will upgrade your application taking baby steps.

We will make sure that your application can run with both versions of Rails. If you are on Rails 5.2, we will make sure that your test suite works with both [Rails 5.2 and 6.0](https://www.fastruby.io/blog/rails/upgrades/upgrade-rails-from-5-2-to-6-0.html).

Once we fix all the errors in your test suite, we will make sure that your staging environment works with the next version of Rails. If anything goes wrong, we will make sure we patch all issues before we deploy the change to production.

If you are curious about the dual booting technique, we have been running the Rails upgrade workshop at [RailsConf](https://railsconf.org/) since 2019. Here is a recording of the workshop we delivered at [RailsConf 2021](https://www.youtube.com/watch?v=Sid39aN_SKk)

### Dependency Management

While there are great tools out there that can quickly help you upgrade minor versions of your dependencies (e.g. [Depfu](https://depfu.com/)), there seems to be a missing link between what we do ([Ruby/Rails Upgrades](https://www.fastruby.io/)) and what they do (shipping automated pull requests, upgrading one minor version at a time).

That’s where we come in. We will work on minor and major version upgrades ([according to semver](https://semver.org/)) for all of your dependencies.

We will submit one PR at a time. This will give us the opportunity to properly test, deploy, and monitor any issues in production.

### Performance Monitoring

![Sample of a screenshot of NewRelic](https://fastruby.io/blog/assets/images/new-relic-sample.png)

If your application is not currently using an Application Performance Monitoring (APM) service (e.g. [New Relic](https://newrelic.com/)), we will set one up for you. We’ll consider your needs and budget, to make the best recommendation.

Once your APM is up and running, we will keep track of low performance and high memory load issues. We will share a monthly report with the top issues we noticed as [Ruby and Rails performance experts](https://www.fastruby.io/blog/tags/performance).

If you want a more in-depth analysis of your application’s performance, we can deliver our highly-rate and always insightful [Tune Report](https://www.fastruby.io/tune).

> While the Tune Report is not included in any of the monthly plans, our clients have found that they can recover their investment in about 3 months.

![Screenshot of a sample Tune Report, Rails performance optimization audit provided by FastRuby.io](https://fastruby.io/blog/assets/images/tune-report-screenshot.png)

### Tech Debt Management

![Screenshot of a sample rubycritic report of the Points open source Rails application](https://fastruby.io/blog/assets/images/ruby-critic-monthly-report.png)

As open source maintainers of technical debt projects like  [RubyCritic](https://github.com/whitesmith/rubycritic) and  [Skunk](https://github.com/fastruby/skunk) we know how important it is to keep track of your code complexity, churn, and code coverage metrics.

On top of that, we know how difficult it is to communicate the problems with consistently increasing technical debt:

- Reduced development velocity
- Constant regressions
- Undesired side effects when deploying small changes

We can help with that! Every month you will get a report on your technical debt, not just on the codebase, but also in your development workflow, infrastructure, and best practices.

In this report we will include any changes that were made to simplify complex code structures, enhance your development workflow, or anything else that was shipped to make your codebase easier to maintain.

Our goal is to gradually improve [code quality](https://fastruby.io/blog/tags/code-quality) without disrupting your development team’s operations.

If you don’t have a shared understanding of what “code quality” really is, we can help you define one that works for your team. After that we can help you “codify” your code quality definition with tools like `reek`, `rubocop`, and`rubycritic`.

### Security Patches

![bundle-audit results in the open source application hosted by FastRuby.io](https://fastruby.io/blog/assets/images/audit-fastruby-io-screenshot.png)

Picture this: On day one of our engagement our team will perform a quick security assessment of your codebase. This will give us an idea of the work to be done to secure your application from known exploits and potential attack vectors.

Every month we will make security patches that will [level up the security standards for your Rails application](https://www.fastruby.io/blog/rails/security/ruby-security-toolkit.html). Depending on the severity of the issues we find, we might prioritize this topic on day one.

## Pricing

Are you ready to make your application more maintainable?

Considering our 10+ years of experience upgrading applications, and more than [20,000 developer hours paying off technical debt](https://twitter.com/etagwerker/status/1658189454715019264?s=20), we believe we can offer meaningful updates to your codebase starting at $1,000 per month:

1. **Shito** : $1,000 per month
2. **Shohin** : $2,000 per month
3. **Komono** : $3,000 per month

Each package includes a maximum number of hours per month that we can invest in your application. When naming these packages, we decided to go with Bonsai types because we see a lot of similarities between pruning Bonsai trees and gradually paying off technical debt. 🌳

### Shito

This is a great package for organizations and companies that either don’t have a lot of technical debt or want to go slow.

Their test suite might be well-written, their Rails application might be a small monolith, or their development team would be overwhelmed with more than 2 pull requests per month.

### Shohin

This is a great package for organizations and companies that have some technical debt, know they need to fix it, and are ready to review from 2 to 4 pull requests per month.

Their test suite might need some attention, their Rails application might have between 50 and 150 models, or they’re one or two versions behind the latest stable release of Ruby and Rails.

### Komono

This is a great package for organizations and companies that are ready to ship 3x more than if they had chosen the [Shito](#shito) package.

Usually their Rails application is rather large, their main dependencies (Ruby and Rails) are a few versions behind, their test suite is flaky, or they need to move fast and upgrade things.

Depending on the plan that you pick, we will invest from 5 to 20 hours per month remediating technical debt in your application/s.

## Strategic Projects

We know that every now and then our clients will have one-off, strategic projects they will want to ship as soon as possible and we want to be able to help.

When that happens, we can offer our services on an hourly basis to ship value in the form of features, infrastructure upgrades, bug fixes, or anything that will make [a difference in our clients’ businesses](https://www.fastruby.io/blog/tags/case-study).

## Rescue Services

Our monthly packages don’t include rescue services. If your application needs to be rescued, we can certainly help! We’ve done this many times in the past and we are happy to get you out of a thorny situation.

For these projects, we need to start with a short, one-week retainer to kickstart the rescue project. This will give us time to assess the situation, come up with a rescue plan, and start executing it.

## How does it work?

We are used to working with teams of all sizes. From engineering teams of one to teams of 50+ software engineers, we see every engagement as a successful collaboration between our team and your team.

We thrive when we collaborate with our clients’ engineering team on a daily basis, so we will have a channel to communicate asynchronously. If you need to get on a call, we can do that too!

Any of the changes that we submit will be open for review and discussion. We will clearly explain why they are necessary, what the changes will do, and what impact they will have in your [tech debt](https://www.fastruby.io/blog/code-quality/calculate-tech-debt-using-skunk-on-github-actions.html) scorecard.

Communication is key to us! We provide you with a monthly report on your technical debt, including codebase, development workflow, infrastructure, and best practices. We are always open to hearing your thoughts and needs and answering your questions.

## Summary

Our commitment to helping people and businesses overcome their technical debt is stronger than ever.

We are excited to launch our new monthly maintenance packages tailored for non-profit organizations, startups and small businesses. We are certain we will gradually reduce technical debt in their applications.

Our technical debt remediation services, provided by a team of experts, include [dependency management](#dependencies), [Ruby upgrades](#ruby-upgrades), [Rails upgrades](#rails-upgrades),  [performance monitoring](#performance), [tech debt management](#tech-debt), and [security patches](#security).

These three affordable plans starting at $1,000 per month are cashflow-friendly, consistently add value to your codebase, and give you access to our team of [legacy code](https://www.fastruby.io/blog/upgrade-rails/legacy-rails-silently-judging-you.html) experts.

You can expect to see gradual improvements in your [code quality](https://www.fastruby.io/blog/tags/code-quality) and overall decreasing technical debt while keeping your development team’s velocity uninterrupted.

> “The typical development organization can increase their feature delivery efficiency by at least 25% by managing technical debt. That’s the equivalent of having **25% more developers without additional staffing costs or**** coordination needs**.”
> 
>  
> 
> (Source: [CodeScene Whitepaper](https://codescene.com/hubfs/calculate-business-costs-of-technical-debt.pdf))

What would you do if you had 25% more development efficiency? How much more could your development team deliver in a month?

Let us be your trusted partner in making your application more maintainable, secure, and efficient.

[Ready to pay off technical debt? Send us a message!](https://www.fastruby.io/#contactus)