->

Website maintenance

Updated September 2026

Website maintenance billed for Hours Actually Used.

Website maintenance billed for Hours Actually Used.

Website maintenance billed for Hours Actually Used.

Website maintenance billed for Hours Actually Used.

Rango is a website maintenance partner for B2B SaaS, fintech and infrastructure teams.

Rango is a website maintenance partner for B2B SaaS, fintech and infrastructure teams.

Rango maintains B2B websites on Webflow, Framer, Next.js and WordPress. Fixes, content edits, design changes and motion work handled by The People Who Build, not a support desk reading from a script.

Rango maintains B2B websites on Webflow, Framer, Next.js and WordPress. Fixes, content edits, design changes and motion work handled by The People Who Build, not a support desk reading from a script.

Rango maintains B2B websites on Webflow, Framer, Next.js and WordPress. Fixes, content edits, design changes and motion work handled by The People Who Build, not a support desk reading from a script.

Every quarter you are billed for Only The Hours Used and never for Hours Nobody Worked, so a quiet quarter costs you

Every quarter you are billed for Only The Hours Used and never for Hours Nobody Worked, so a quiet quarter costs you

Every quarter you are billed for Only The Hours Used and never for Hours Nobody Worked, so a quiet quarter costs you

less than a busy one. The smallest plan tops out at $600.

less than a busy one. The smallest plan tops out at $600.

less than a busy one. The smallest plan tops out at $600.

Website maintenance services

Everything a live site needs, From Uptime To Growth.

Everything a live site needs, From Uptime To Growth.

Everything a live site needs, From Uptime To Growth.

01

Monitoring and uptime

We watch uptime, forms, redirects and error rates with automated checks, so problems reach us before they reach your buyers. If the site does go down, we pick it up the same working day rather than at the start of the next sprint.

02

Security and updates

Dependencies, plugins, CMS versions and certificates kept current, with every update tested on a branch before it touches the live site.

03

Backups and recovery

Automated backups with a restore we have actually run, so recovery is a procedure we have tested rather than a hope.

04

Fixes and content edits

Broken layouts, dead links, failing forms and copy changes. Same day on anything down, two working days on everything else.

05

Performance and Core Web Vitals

Images, fonts, scripts and render paths kept inside budget, measured on real field data rather than a one-off lab score.

06

Accessibility upkeep

New pages checked for contrast, focus order, labels and keyboard paths against WCAG 2.2 AA, so compliance does not drift after launch.

07

Technical SEO upkeep

Redirects, canonicals, sitemaps, schema and metadata kept correct as pages come and go, so the site does not quietly lose ground.

08

New pages and components

Landing pages, sections and components built in the system the site already uses, so what you add matches what is already there.

09

Design and visual updates

New sections, refreshed pages and visual fixes handled by designers, drawn from the system the site already uses, so what you add in month nine still looks like what launched.

10

Motion and interaction

Scroll, hover and transition work kept smooth on real devices, tuned so it supports the page rather than showing off, with reduced-motion settings respected.

Monitoring and uptime

We watch uptime, forms, redirects and error rates with automated checks, so problems reach us before they reach your buyers. If the site does go down, we pick it up the same working day rather than at the start of the next sprint.

Security and updates

Dependencies, plugins, CMS versions and certificates kept current, with every update tested on a branch before it touches the live site.

Backups and recovery

Automated backups with a restore we have actually run, so recovery is a procedure we have tested rather than a hope.

Fixes and content edits

Broken layouts, dead links, failing forms and copy changes. Same day on anything down, two working days on everything else.

Performance and Core Web Vitals

Images, fonts, scripts and render paths kept inside budget, measured on real field data rather than a one-off lab score.

Accessibility upkeep

New pages checked for contrast, focus order, labels and keyboard paths against WCAG 2.2 AA, so compliance does not drift after launch.

Technical SEO upkeep

Redirects, canonicals, sitemaps, schema and metadata kept correct as pages come and go, so the site does not quietly lose ground.

New pages and components

Landing pages, sections and components built in the system the site already uses, so what you add matches what is already there.

Design and visual updates

New sections, refreshed pages and visual fixes handled by designers, drawn from the system the site already uses, so what you add in month nine still looks like what launched.

Motion and interaction

Scroll, hover and transition work kept smooth on real devices, tuned so it supports the page rather than showing off, with reduced-motion settings respected.

How it works

How maintenance works, From Audit To Report.

Before a plan starts

We check speed, accessibility, technical SEO and broken paths on your live site, then send you the list with what to fix first. No charge, and no obligation to carry on.

01

A free health check

Before day one

How we work together

We work inside your own hosting, repository and CMS, and you talk to the engineers and designers doing the work in a shared Slack or Teams channel.

02

Access and one shared channel

Day one

The guardrails

Work lands on a branch with its own preview link, so you see the change on your own site before anyone else does. Outages skip the queue and ship the same day.

03

Every change through a preview

Every change

What you get

At the end of each quarter: hours used and what they went on, uptime, Core Web Vitals and accessibility checks, and what we recommend next.

04

A report you can check

Every quarter

Before a plan starts

We check speed, accessibility, technical SEO and broken paths on your live site, then send you the list with what to fix first. No charge, and no obligation to carry on.

01

A free health check

Before day one

How we work together

We work inside your own hosting, repository and CMS, and you talk to the engineers and designers doing the work in a shared Slack or Teams channel.

02

Access and one shared channel

Day one

The guardrails

Work lands on a branch with its own preview link, so you see the change on your own site before anyone else does. Outages skip the queue and ship the same day.

03

Every change through a preview

Every change

What you get

At the end of each quarter: hours used and what they went on, uptime, Core Web Vitals and accessibility checks, and what we recommend next.

04

A report you can check

Every quarter

Before a plan starts

We check speed, accessibility, technical SEO and broken paths on your live site, then send you the list with what to fix first. No charge, and no obligation to carry on.

01

A free health check

Before day one

How we work together

We work inside your own hosting, repository and CMS, and you talk to the engineers and designers doing the work in a shared Slack or Teams channel.

02

Access and one shared channel

Day one

The guardrails

Work lands on a branch with its own preview link, so you see the change on your own site before anyone else does. Outages skip the queue and ship the same day.

03

Every change through a preview

Every change

What you get

At the end of each quarter: hours used and what they went on, uptime, Core Web Vitals and accessibility checks, and what we recommend next.

04

A report you can check

Every quarter

AI moves the routine work. People Decide What Ships.

AI moves the routine work. People Decide What Ships.

AI moves the routine work. People Decide What Ships.

Illustration of a designer working on a laptop in a dark office at night

Claude triages the queue

Claude drafts the first read on an incoming issue, so the engineer picking it up starts with context instead of a blank ticket.

Illustration of a designer working on a laptop in a dark office at night

Claude triages the queue

Claude drafts the first read on an incoming issue, so the engineer picking it up starts with context instead of a blank ticket.

Illustration of a designer working on a laptop in a dark office at night

Claude triages the queue

Claude drafts the first read on an incoming issue, so the engineer picking it up starts with context instead of a blank ticket.

Routine fixes, faster

Dependency bumps, copy changes and repetitive fixes move quickly with AI assistance, and every change is still reviewed by a person before it ships.

Routine fixes, faster

Dependency bumps, copy changes and repetitive fixes move quickly with AI assistance, and every change is still reviewed by a person before it ships.

Routine fixes, faster

Dependency bumps, copy changes and repetitive fixes move quickly with AI assistance, and every change is still reviewed by a person before it ships.

Our engineers, in your Slack

Our engineers, in your Slack

Our engineers, in your Slack

The people who maintain your site sit in your Slack or Teams. Questions go straight to whoever is doing the work.

The people who maintain your site sit in your Slack or Teams. Questions go straight to whoever is doing the work.

The Rango team in Rango t-shirts
Illustration of a phone screen built from page layout blocks

Launch pages without a redesign

Campaign and landing pages are built from sections your site already has, so a launch page goes live without reopening the design.

Illustration of a phone screen built from page layout blocks

Launch pages without a redesign

Campaign and landing pages are built from sections your site already has, so a launch page goes live without reopening the design.

Illustration of a phone screen built from page layout blocks

Launch pages without a redesign

Campaign and landing pages are built from sections your site already has, so a launch page goes live without reopening the design.

Illustration of a laptop on a desk at night showing a chat interface

Readable by search and AI

Schema, metadata and headings are kept current as pages change, so Google and AI answer engines keep reading the site correctly.

Illustration of a laptop on a desk at night showing a chat interface

Readable by search and AI

Schema, metadata and headings are kept current as pages change, so Google and AI answer engines keep reading the site correctly.

Illustration of a laptop on a desk at night showing a chat interface

Readable by search and AI

Schema, metadata and headings are kept current as pages change, so Google and AI answer engines keep reading the site correctly.

Choosing a website maintenance partner

Rango

Freelancer

In-house hire

Choosing a website maintenance partner

Rango

Freelancer

In-house hire

What It Costs

What It Costs

Hours used, capped $600 to $3,010 a quarter.

Hours used, capped $600 to $3,010 a quarter.

An hourly rate, when they are free.

An hourly rate, when they are free.

A salary, plus the overhead.

A salary, plus the overhead.

Response Time

Response Time

Same day if the site is down.

Same day if the site is down.

Whenever they pick up the message.

Whenever they pick up the message.

Fast, until they are on leave.

Fast, until they are on leave.

Who Does The Work

Who Does The Work

The team that builds on the platform.

The team that builds on the platform.

One person, one skill set.

One person, one skill set.

One person, with many other jobs.

One person, with many other jobs.

How It Starts

How It Starts

A free health check, then a plan.

A free health check, then a plan.

You describe the problem each time.

You describe the problem each time.

It lands on an existing backlog.

It lands on an existing backlog.

Unused Hours

Unused Hours

Never billed. You pay for time worked.

Never billed. You pay for time worked.

You pay the hours they invoice.

You pay the hours they invoice.

Paid either way.

Paid either way.

When Something Breaks

When Something Breaks

Monitoring catches it before you do.

Monitoring catches it before you do.

You notice, then you tell them.

You notice, then you tell them.

You notice, then you file a ticket.

You notice, then you file a ticket.

Who You Talk To

Who You Talk To

The engineers, in your Slack.

The engineers, in your Slack.

One person, when they are free.

One person, when they are free.

Your own team, if not busy.

Your own team, if not busy.

Design And Motion

Design And Motion

Designers and motion in the same plan.

Designers and motion in the same plan.

Usually code, rarely design.

Usually code, rarely design.

Whatever that one hire covers.

Whatever that one hire covers.

Platforms Covered

Platforms Covered

Webflow, Framer, Next.js and WordPress.

Webflow, Framer, Next.js and WordPress.

Usually one platform.

Usually one platform.

Whatever they were hired for.

Whatever they were hired for.

Where Access Lives

Where Access Lives

Your hosting, repo and CMS.

Your hosting, repo and CMS.

Sometimes their own accounts.

Sometimes their own accounts.

Your accounts, your team.

Your accounts, your team.

Work that holds up between releases.

Work that holds up between releases.

Work that holds up between releases.

We report against Core Web Vitals and WCAG 2.2 AA every quarter, so you can see what actually moved instead of taking our word for it.

We report against Core Web Vitals and WCAG 2.2 AA every quarter, so you can see what actually moved instead of taking our word for it.

  • Uptime monitoring

  • Same-day outage response

  • 48-hour standard response

  • Security and dependency updates

  • Automated backups

  • Tested restores

  • Core Web Vitals reporting

  • Broken link checks

  • Form and redirect checks

  • WCAG 2.2 AA checks

  • Schema and metadata upkeep

  • Staging before live

  • Quarterly report

  • Dedicated Slack channel

Platforms we cover, and we stay stack agnostic

We work in whatever your site is already built on.

We work in whatever your site is already built on.

We work in whatever your site is already built on.

Webflow, Framer, Next.js or WordPress: we work in your own repo, hosting and CMS, and ship every change through a branch and a preview before it goes live. Automated checks watch uptime, errors and search health, and Claude and Cursor move us through routine fixes faster.

Webflow logo

Webflow

Framer logo

Framer

Next.js logo

Next.js

WordPress logo

WordPress

Vercel logo

Vercel

GitHub logo

GitHub

Claude logo

Claude

Cursor logo

Cursor

Cloudflare logo

Cloudflare

Sentry logo

Sentry

Better Stack logo

Better Stack

Google Search Console logo

Google Search Console

Google Analytics logo

Google Analytics

Lighthouse logo

Lighthouse

Figma logo

Figma

Slack logo

Slack

Maintenance Plans

Maintenance plans, Priced Per Quarter.

Essential

Up to 12 hours a quarter at $50 an hour

Billed quarterly for hours used

UP TO $600 / QUARTER

Growth

Up to 32 hours a quarter at $47 an hour

Monitoring, fixes and new pages

UP TO $1,504 / QUARTER

Scale

Up to 70 hours a quarter at $43 an hour

Dedicated Slack and a quarterly review

UP TO $3,010 / QUARTER

Frequently asked questions

Straight Answers. No fluff.

How does website maintenance billing work?

Plans are quarterly and you are billed for the hours we actually work. If a quarter is quiet, you pay less. Unused hours are never charged. The smallest plan is capped at $600 a quarter, and anything beyond your plan size is agreed with you before we start it.

How much does website maintenance cost?

Essential is up to 12 hours a quarter at $50 an hour, so $600 at most. Growth is up to 32 hours at $47, so $1,504. Scale is up to 70 hours at $43, so $3,010. The rate drops as the plan grows, and you are only billed for the hours you use.

Which platforms do you maintain?

Webflow, Framer, Next.js and WordPress. We build on all four, so the people maintaining your site have shipped on the platform it runs on rather than learning it on your time.

How quickly do you respond when something breaks?

Same day if the site is down or a form has stopped working, and two working days for everything else. You get a dedicated Slack or Teams channel, so requests reach the people doing the work rather than a ticket queue.

What counts as an hour of maintenance?

An hour is time spent on your site: a bug fixed, a section built, a page updated, a dependency tested and shipped. Review, testing and the preview link are part of that hour, not billed on top. Anything under fifteen minutes is logged as fifteen. Every hour is recorded against a named task, and the quarterly report shows what each one went on.

Do we have to have built the site with you?

No. We take on sites we did not build. We start with a free health check covering speed, accessibility, technical SEO and broken paths, then agree what to fix first before a plan starts.

Can we change or cancel a plan?

Yes. Plans renew each quarter, and you can move up, move down or stop at the end of any quarter. There is no notice period and no long contract to sign.

What do we get at the end of each quarter?

A report showing the hours used and what they went on, uptime, Core Web Vitals and accessibility checks, plus what we recommend next. It is written so you can judge the plan on its own numbers.

Who owns the site and the accounts?

You do. The site stays in your own hosting, repository and CMS accounts and we work inside them. Nothing is held on our side, so ending a plan is a matter of removing our access.

What is not covered by a maintenance plan?

A maintenance plan does not cover a full redesign, a platform migration or building a new product surface such as a web app. Those are scoped as separate projects. Paid media, content strategy and third-party licence fees also sit outside the plan. If a request turns out to be project work rather than maintenance, we tell you before we start rather than quietly spending your hours on it.

If you’re considering
Working Together