Air Duct Cleaning Software

Air duct cleaning software for quotes that hold up on arrival.

The price was set from a guess about the house, then the crew found twice as many vents and a second furnace. We turn vent counts, property duct history, camera proof, and repeat cycles into software your office and crews share.

See our work

Bring one stuck workflow. Leave with a build, buy, repair, or wait recommendation.

Trusted by

Perceptional logoMusgrave GroupUrShipper logoBrux Dental SolutionsBella Skin Institute LogoEnergia RewardsDraftly logoTuneClub LogoSekou LMS logoLogo of food order management app gulaSnelwegDealsGrubly logoPSi logoInstantor Rewards logologo of Mobile app for events, membership clubs, and communitiesAldiFest retail campaign logoVidmattic logoEMS Connect logoWorx Squad logologo of Online Web App For Making Intrologo of Referral and Viral Marketing PlatformConcurrences logoGE logoTicketstop logo

The brief

Start with what is not working.

Good software decisions begin with the constraint, not a list of features or a preferred technology.

01

The quote was set from a guess about the house, and the real vent count only shows up when the crew arrives.

02

What the crew learned about a property last time lives in a notebook, a phone, or one person's memory.

03

The next cleaning is due years from now, and nothing reminds anyone when that date comes round.

Plain answer

RaftLabs builds air duct cleaning software around the property, not the single visit. The office records supply and return vent counts, the number of systems, access notes, and dryer vent runs at booking, so the quote matches the house. Camera photos before and after stay on the record, and the next cleaning date is set years ahead.

What to remember

  • Use this when quotes keep breaking on arrival because vent counts and system counts were never captured at booking.
  • The property record is the product: vents, systems, access, dryer vent runs, and camera proof stay attached for the next visit.
  • The first release should complete one useful path, from booking questions to a finished job with before and after photos.
  • Repeat work runs on a cycle of years, so the software must remember a customer long after the crew has forgotten the house.
  • Hire freelancers for one small, well-defined task; use one accountable agency party when the work needs coordination across screens, rules, data, and connections.

The first decision is not the software.

It is whether software is the right answer at all. We use four possible recommendations before discussing a development scope.

  • 01

    Buy

    Choose a maintained product when it already asks the right booking questions, prices by vent and system count, and keeps a usable history for each property. Paying for software you do not have to maintain is often the better trade.

    Run the build-vs-buy numbers

  • 02

    Repair

    Keep the existing product or spreadsheet setup when your team still trusts it and the records are complete. Start with evidence: where the property records live, how vent counts are captured, what is missing, and who can see and change what.

  • 03

    Own

    Own the system when the way you quote, record, and bring customers back is itself how the company makes money. Start with one complete path, from the first booking question to the reminder that fires years later.

  • 04

    Wait

    Do not turn a pricing method that is still changing into permanent software. Settle how you charge, by vent, by system, or a mix of both, name who owns the property records, and measure how often quotes break before paying for a product.

Not sure which path is yours? Bring it to a 30-minute call. Leave with the answer in writing.

Fit

Custom software should earn its maintenance burden.

A feature request is not enough. The case is real when the same problem shows up in broken quotes, lost property history, or customers who never come back.

A fit

Quotes keep changing on arrival because vent counts, system counts, and access were never captured at booking.

Crews revisit properties years later and start from nothing, because the duct history lives in old invoices and memory.

Repeat work matters to revenue, and no one can say which properties are due again this season.

Not a fit

A maintained product already records vent counts and property history in a way your office actually uses.

The pricing method is still unsettled, so the software would freeze rules you are about to change.

The brief is a feature list with no booking, quoting, or repeat-visit problem attached.

Not sure which side you are on? Use the first call to make that decision. A useful answer may be to buy, connect, repair, or wait.

Start with the property, not the appointment.

A duct cleaning job is easy to book badly. The customer calls for a price. Someone in the office gives a number based on a guess about the house. The crew arrives and finds twice as many vents, a second furnace in the attic, and a dryer vent that runs a long way to the roof. The job runs long, the price no longer matches the work, the customer argues, and the next appointment starts late.

The fix is not a better guess. It is asking the right questions before the price is promised: how many supply vents and returns, how many systems, how the crew reaches the equipment, and how the dryer vent runs. Those answers belong on a record for the property, not in the memory of whoever answered the phone. Years later, when the same house is due again, that record is what the next crew works from.

A second product hides inside the first. Customers see a quote and a pair of before and after photos. Your team lives in the other product: booking questions, pricing rules, crew notes, access details, photo records, and reminders set years ahead. Quotes that squeeze all of that into one line are where budgets break, so we quote your team's screens as their own job, with their own users, from the start.

Custom software makes sense when one owned system can hold that property record better than a product, a spreadsheet, or a process change. The first release should take the smallest useful path from the first phone call to a finished job with proof attached. It should not replace every tool at once.

We start where it hurts.

The booking screen is only one part of the job. The real scope includes the questions asked on the phone, the pricing rules, the notes the crew brings back from inside the house, the camera proof, and who brings the customer back years later.

Quotes set from a guess about the house

Replace the phone guess with booking questions that capture supply and return vent counts, the number of systems, access, and dryer vent runs before a price is promised. The quote is worked out from those answers, the same way every time, whoever answers the phone.

Property history that resets every visit

Give each address one record that keeps its vent counts, systems, access notes, and past jobs. When the crew returns years later, they open the record instead of starting from a blank page and a customer's memory.

Camera proof that never reaches the customer

Attach the before and after camera photos to the run they came from, on the property record. The customer sees the same duct before and after, the office can answer questions without calling the crew, and the next visit starts with a picture of the system as it was left.

Repeat cycles nobody is tracking

Set the next due date when each job closes: years ahead for duct cleaning, sooner for dryer vents, and on contract for commercial buildings. The office sees which properties are due this season instead of waiting for customers to remember on their own.

A product that needs a safe takeover

Audit an inherited system or a pile of spreadsheets, keep what is sound, and create a controlled path through the backlog. The first goal is not a rewrite. It is being able to trust the property records again. After recovery, ongoing maintenance keeps it that way.

Which one is yours?

Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

Verticals

One record, different kinds of duct work.

The jobs differ, but the same rule applies: capture the facts that set the price at booking, keep them on the property, and let the record drive the next visit.

Whole-home residential cleaning

One property record per home: supply and return counts by system, attic and crawlspace access, the reason for the cleaning, and before and after photos for each system. The quote, the crew's day, and the invoice all work from the same counts.

Dryer vent cleaning

A shorter job on a shorter cycle. The record holds the run length, the bends, and where the vent exits, so the price is right before the crew arrives and the yearly reminder fires on its own schedule, separate from the duct cleaning cycle.

Commercial buildings and property managers

One account, many buildings, each with its own systems, access notes, contract interval, and photo history. The manager approves work per building and can see what was cleaned, what it looked like, and when each address is due again.

Post-renovation and move-in work

Renovation dust and a new home are common reasons to book. The record notes the trigger, the condition found on camera, and the recommended next interval, so a one-off job becomes the start of a repeat relationship with that property.

Multi-unit and rental properties

Each unit keeps its own record under one landlord or manager account: its own vent count, its own access notes, and its own due date. Turnovers stop resetting the history, because the record belongs to the unit, not to the tenant who moved out.

Proof

The fifth attempt became a product customers could keep using.

UrShipper had already worked with four development vendors. Its founder describes the communication and decisions during the recovery.

The case study documents a 14-week recovery, five carrier connections, a Shopify fulfilment workflow, and client-reported results. It is one comparable project, not a promise that every inherited codebase can follow the same plan.

Read the UrShipper case study

Which workflow is costing you the most right now?

Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

Let the work pick the shape.

The way people work should decide the form of the software. The office books from a desk, the crew works inside the house with a camera in hand, and the customer only sees a quote and a set of photos. Those facts tell us what belongs in the first release.

One product may need several surfaces. Each one should support the same complete workflow, not start another feature list.

How it works

Close one expensive risk before opening the next.

Each stage answers a buyer question and leaves behind a decision you can inspect. The next stage only opens when the expensive uncertainty in the current one is small enough to accept.

  1. 01
    Understand

    Trace the real workflow

    Where is the cost or failure actually coming from?

    Follow one booking and one crew day from start to finish. Include the workarounds, the calls back to the office, the vents nobody counted, and the notes that never made it onto a record.

    Decision produced

    A map of one booking from phone call to finished job, with the questions asked, the pricing rules, the exceptions, and how often quotes change on arrival.

    Risk closed

    Paying to automate the booking screen while the quote still rests on a guess about the house.
  2. 02
    Shape

    Choose the first useful release

    What needs to exist together for one useful result to work?

    Choose the shape from the way the work happens, not from a preferred technology. Name the user, the device, the data, who can access what, the exceptions, and the result the first release must complete.

    Decision produced

    The first-release boundary: booking questions, the pricing rules, the property record, the crew view, and a clear definition of done for one complete job.

    Risk closed

    A small-looking feature list that quietly depends on pricing rules, photo storage, and reminder dates nobody has settled.
  3. 03
    Prove

    Review working software

    Will it hold up outside a controlled demo?

    Review the product against the agreed workflow, not a tour of finished screens. Book a job, quote it, send the crew, change the count on site, and close it with photos, using your own test properties.

    Decision produced

    Working checkpoints tested with realistic properties: a two-system home, a long dryer vent run, a commercial building with several addresses on one account.

    Risk closed

    Discovering during the first busy season that two-system homes or property manager accounts were never really handled.
  4. 04
    Transfer

    Release, measure, and hand over

    Did the new workflow improve the original constraint, and can another capable team operate it?

    Move a controlled set of properties or one crew first. Compare how often quotes hold on arrival, how complete the records are, and how much repeat work the reminders produce, before adding the next workflow.

    Decision produced

    A controlled release, a comparison against the starting point, operating notes, an account ownership map, and a recommendation for what should happen next.

    Risk closed

    Measuring activity instead of the business result, or depending on the original vendor to keep the system running.

What stays out of the black box

These are operating conditions to put in the engagement, not claims to take on faith.

The scope names one complete workflow

The user, the trigger, the decisions, the data, the exceptions, and what 'done' looks like. A screen list is not enough.

Progress is visible in working software

Reviews against the product at agreed checkpoints, while there is still time to act.

A scope change has a price before it has code

A new workflow or system connection shows its effect on cost and timing before anyone approves it.

Ownership exists throughout, not only at handover

Code, cloud, data, and provider access stay visible and under your control from day one.

The work is checkable without being technical

Checkpoints are working software you use yourself, reported in plain language.

Software for other home service trades.

Neighbouring trades keep the same kind of per-property record, and each one breaks in its own way when the record is missing. Each page below covers a different trade.

What it costs

Every project starts at $10K.

The first phase turns the costliest patched workflow into a scoped build with written acceptance criteria.

Starting investment

Starts at $10K

Workflow complexity, systems to connect, data migration, and user roles set the scope. After a 30-minute call, you get a written build, buy, repair, or wait recommendation plus first-phase direction. Free, whether or not you build with us.

Buy or own

Buy an existing productOwn custom software
Best fitIt already asks your booking questions and keeps a property history your office trustsYour quoting method and property records are how the company wins and keeps work
Manual workSetting it up and adjusting how you work can remove the problemStaff retype vent counts and visit notes between tools, and the retyping has a measurable cost
ConnectionsIt connects cleanly to your invoicing and payment toolsA critical connection, such as camera photos landing on the property record, cannot be done cleanly any other way
Repeat workIts reminders handle multi-year cycles and commercial contract datesYour repeat work mixes homes due in years, dryer vents due yearly, and contracts due each season

Work with us

Bring one stuck workflow. Leave with a decision.

In a 30-minute call, we will help you decide whether to buy, connect, repair, build, or wait. If custom software is not the sensible next move, that is still a useful answer.

  • One named workflow owner and one complete path for the first phase.
  • Scope, price, what 'done' looks like, and exclusions agreed before paid work starts.
  • Code, cloud, data, and provider access remain under your control.
  • Post-launch warranty cover for defects in the agreed scope.

Frequently asked questions

Straight answers to what buyers ask before they scope. Still stuck? .

Air duct cleaning software runs the office side of a duct cleaning company: booking questions, quotes, crew scheduling, job records, invoices, and reminders. Custom software is shaped around how your company prices and records the work, so vent counts, system counts, access notes, and camera proof live on the property record instead of in scattered notes and old invoices.

Most companies price by the system, with a stated number of vents included and a charge for each extra vent, or they price by the vent from the start. A second furnace or air handler is priced as more work, because it has its own trunk lines and returns. Dryer vent cleaning, sanitizing, and hard access, such as an attic or crawlspace, are priced as separate lines. The method matters less than stating it clearly before the crew arrives.

Ask for the number of supply vents and return grilles, the number of heating and cooling systems, the size of the home, and how the crew reaches the equipment, including attic and crawlspace access. Ask about the dryer vent: how long the run is and where it leaves the house. Ask why the customer wants the cleaning, whether there are pets, and whether renovation work just finished. Software makes these questions part of booking, so a price is never promised before the answers exist.

The crew updates the count on the job record while they are in the house, and the revised price is agreed with the customer before the extra work starts. The change, who approved it, and the new total stay on the record. That one habit removes most price arguments, because the customer saw the extra vents counted and agreed the price before anyone cleaned them.

Houses outlast the people in them. A property record holds the vent count, the systems, the access notes, and the photos for that address, whoever books the next visit. When the same house is cleaned again years later, the crew arrives knowing where the second furnace sits and which closet hides the attic hatch. For property managers, the record also separates one building from the next, so each address keeps its own history and its own due date.

Duct cleaning is work the customer cannot see, in a trade where low-price ads have made homeowners wary. A camera look inside the duct, saved as a before photo and matched with an after photo of the same run, shows exactly what was found and what was cleaned. The photos stay on the property record, settle questions about whether the work was needed or done, and give the next crew a picture of what the system looked like last time.

Most homes are cleaned again on a cycle of roughly three to five years, sooner with pets, allergies, or renovation dust. Dryer vents run on a shorter cycle, often yearly. Commercial contracts may run every year or every six months. The software sets a due date for each property when a job closes, by service type, and brings the property back to the office when the date comes round, so repeat work is found in the records instead of depending on the customer remembering.

A dryer vent is a separate run with its own facts: length, number of bends, where it exits, and its condition. It is often sold on the same visit as the duct cleaning, and it repeats more often. Keeping it on the same property record, with its own price line and its own due date, means the office can offer it at booking, the crew knows the run before they arrive, and the reminder fires on the dryer vent cycle, not the longer duct cycle.

Yes, when the record is built for it. One account can hold many service locations, each with its own systems, vent counts, access notes, contract interval, and invoice history. The property manager sees the history and the before and after photos for each building, approves work per location, and gets one clear account of what is due where. Commercial work is quoted per building, because layouts and access vary too much for a single standard price.

General HVAC software is built around installing and repairing heating and cooling equipment: breakdowns, parts, and service calls. Duct cleaning runs on different facts. The price turns on vent counts and system counts, the value sits in a property record that must stay accurate for years, the proof is camera photos, and the repeat cycle is measured in years, not weeks. This page covers that record and that quoting method, not equipment repair dispatch.

Buy an existing product when it asks the right booking questions, prices the way you price, and keeps a property history your office trusts. Have custom software made when your quoting method is itself how you win work, when the property record has to hold things the products leave out, such as camera proof tied to each run, or when staff keep retyping the same vent counts between tools. If your pricing method is still changing every month, settle it first and decide after.

The first paid phase may cover a bounded audit, a proof of concept, a recovery plan, or a small first release. The final price depends on how deep the workflow goes, how many kinds of users it serves, what it needs to connect to, whether records need moving over from spreadsheets or an older tool, and whether phones or tablets are involved for crews. The agreed phase is priced in writing before it starts.

Timing depends on scope: a bounded audit or proof of concept is a smaller engagement, while a system covering booking, quoting, crew work, photos, invoicing, and multi-year reminders takes longer. The schedule is set once the first workflow and what 'done' looks like are clear.

Yes. Takeover is a common first engagement, and it always starts with an audit: where the records live, how your data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live. Records that are complete and trustworthy move over as they are. Only the parts blocking reliable work get replaced. If you already paid another vendor and have nothing working, the audit tells you what you actually have before you spend more.

We need one person who owns the workflow, access to the people who book jobs and run crews, timely answers on pricing rules, and someone who can accept or reject each milestone. A weekly working session is usually enough once the scope is stable. Your team should not have to manage developers day to day. The team that scopes your project is the team that does the work: no handoff to another vendor after you sign, and you can talk to the people doing the work directly.

Ask for the quote to name everyone who will use the system, including your own team. Every platform has two products: what customers see, and what your people use all day: booking screens, pricing rules, crew views, managing users, and a record of who did what. When that second product is quoted as an 'admin panel' on a single line, it becomes the overrun. Our quotes treat your team's screens as their own scope, with their own users. Then the phase names the workflow, what 'done' looks like, the price, and the exclusions, all before paid work starts.

You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the workflow agreed at the start: book a job, quote it by vent count, send the crew, close it with photos. Progress is reported in plain language: what changed, what's next, and what it costs. Because you own the code, the accounts, and the operating notes throughout, nothing about the work is locked inside our heads. Our job is to make the work checkable; your job is to check it against your business.

You own the code built for you and control where it lives, the cloud accounts, the data, analytics, and third-party subscriptions. Outside services and open-source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over.

Every launch includes post-launch warranty cover for defects in the agreed scope, release support, and small screen corrections. After that, work can continue as another fixed phase or an ongoing product engagement. The code and accounts stay under your control either way.