Industry solution

Field Service & Trades

From the 2 a.m. no-heat call to the signed-off job, on one connected workspace

Booking, dispatch, licenses, equipment history, agreements and job costing for HVAC, plumbing, electrical and facilities contractors.

Products
8
Challenges
6
Concepts
15
Talk to us about Field ServiceAsk a question
A technician kneels beside an open furnace in a basement, checking a job on a phone.
AssetHandler(opens AssetHandler in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)CrewFoundry(opens CrewFoundry in a new tab)Kadaikodi(opens Kadaikodi in a new tab)Subscriber Bot(opens Subscriber Bot in a new tab)Botlit(opens Botlit in a new tab)FluidGrids(opens FluidGrids in a new tab)BigConsole(opens BigConsole in a new tab)

The problem

Why running a trades business is hard right now

Service contractors run on phones, whiteboards and memory. Calls pile up overnight, dispatch reshuffles by hand, licenses lapse unnoticed, equipment history hides in old tickets and parts leave the van without reaching an invoice.

HVAC, plumbing, electrical and facilities contractors sell response and trust. Demand follows the weather: a cold snap or a heat wave turns an ordinary day into a queue of no-heat or no-cool calls within hours, while the quieter shoulder seasons are when maintenance-agreement tune-ups have to get done. The work happens in basements, attics, crawl spaces and on rooftops, far from the office, by technicians whose licenses and certifications decide what they may touch.

Most shops run on a patchwork: a phone line and an answering service, a scheduling screen or a whiteboard, paper or photographed job tickets, a spreadsheet of licenses, a separate accounting package and the memory of senior technicians. Every hand-off between them is a place where a model number, a part, an hour or a renewal gets lost. Skilled technicians are hard to hire and slow to train, so every wasted drive, repeat visit and unbilled part costs twice.

Commercial and facilities work raises the bar again. Property and facility managers expect planned-maintenance visits on schedule, a response within the agreed time, not-to-exceed limits respected and a clean record for each unit they pay to maintain. That record is only as good as what the technician captured on site, and what the office could find afterwards.

Who this is for

  • Owner or general manager

    Margin per job, callbacks, agreement renewals, and whether growth is held back by technicians or by the office.

  • Service operations manager

    Emergencies reached first, arrival windows kept, and a board that reflects the day as it changes.

  • Dispatcher or customer service lead

    Knowing who is free, cleared and carrying the part before promising a customer an arrival window.

  • Service manager or training lead

    Licenses, refrigerant cards and apprentice hours kept current, and every callback traced to its cause.

  • Controller or office manager

    Every completed job invoiced with its parts and hours, overtime paid correctly, van stock reconciled.

  • Commercial and facilities account manager

    Planned visits done on schedule, response times kept, not-to-exceed limits respected and a clean record per unit.

A day in the life

The story behind the solution

A cold-snap week at Fairhaven Mechanical & Electric

Teresa runs service for a contractor with sixty technicians on the road, four dispatchers and a customer service team of six, working homes and light commercial buildings. In the second week of January the overnight low drops into single digits. The week below is fictional, but anyone who has run a trades business through peak season will recognize every moment of it.

  1. Monday, 5:40 a.m.

    Forty messages and no model numbers

    Teresa's phone shows the answering service's overnight summary: forty-three messages, most of them 'no heat'. Half do not match a customer record, none carry a model number, and one is from an 84-year-old homeowner in Ridgeview whose furnace quit at midnight. Customer service starts calling back at seven, promising afternoon slots without knowing how many technicians are free. By then the online form holds another twenty requests, some of them duplicates, and nobody can tell which callers are agreement members who were promised priority.

    How this is solved: Cold-snap booking: members first, fees paid, real capacity

  2. Monday, 7:30 a.m.

    The whiteboard cannot keep up

    Marcus, the lead dispatcher, has fourteen emergencies and thirty booked tune-ups and installs. Van 22 will not start in the cold and Van 9 is still at the shop for brakes. He moves magnets on the whiteboard, phones technicians one by one to ask which igniters are on their trucks, and sends Luis across town past Priya, who is driving the other way. Before nine, two customers call to ask where their technician is.

    How this is solved: A dispatch board that knows trucks, parts and people

  3. Monday, 10:15 a.m.

    The license nobody checked

    A gas-fired rooftop unit at the Corbin Street Shops, a retail building managed by a property firm, has no heat and a burned disconnect. Marcus sends Marco, the closest HVAC technician, with Tom, an electrical apprentice. At noon the service manager realizes Marco's gas-fitting license lapsed the week before, with the renewal still in his glovebox, and that Tom's paper log records supervised hours under a journeyman who was never on site. The job is re-sent with Luis, a licensed master mechanical technician, and Keisha, a licensed electrician, and the property manager asks why it took two trips.

    How this is solved: License levels, CE hours and apprentice ratios nobody tracks

  4. Monday, 1:30 p.m.

    Third visit, same furnace

    Priya reaches Linh Nguyen's house for another no-heat call. Linh tells her it is the third visit in five weeks. Priya can see today's ticket but not the last two, and learns from Linh that the flame sensor was cleaned in December and replaced after Christmas. The furnace is nineteen years old, the install manual is somewhere in the basement, and Linh wants to know whether she should just replace it. Across town, a rooftop unit at a dental office is getting its second refrigerant top-up in two months.

    How this is solved: The furnace nobody remembers

  5. Wednesday, 9:00 a.m.

    Renewals nobody is watching

    At the weekly meeting the owner, Dev Raman, asks how many maintenance agreements renew in February. Nobody can say without an export from the billing system. Last spring several dozen members lapsed because their stored card expired and no one called. Some members never got the fall safety check they paid for, and spring tune-up season, when every technician is also needed on the first cooling calls, is eight weeks away.

    How this is solved: Maintenance agreements that renew instead of lapsing

  6. Friday, 4:00 p.m.

    Tickets that never became invoices

    Grace Oyelaran, the controller, has a stack of completed tickets that cannot be invoiced: parts missing, signatures missing, hours that do not match the time clock. Luis used three igniters this week and billed two. The time-and-materials ticket for the Corbin Street Shops has no manager signature and runs past the not-to-exceed amount, so the property firm has disputed it. Payroll closes Monday with a week of cold-snap overtime, and Van 14 will start Monday without igniters because nobody wrote them on the restock sheet.

    How this is solved: Hours and parts that never reach an invoice

None of this is unusual; it is the ordinary friction of a trades business running at full stretch. The challenges below show how Burdenoff products are designed to share one record from the first message to the signed-off job, so that Teresa's team can meet the next cold snap with a board that already knows who is cleared, what is on each van and which members are owed a visit.

Challenges and how they are solved

6 problems, several products, one connected answer

Each challenge shows the problem as it happens, how the products are designed to hand work to each other, and the concepts that illustrate it. Share any challenge on its own.

Answers are in plain business terms. Choose Technical, or open any technical detail, to see how it works under the hood.

Challenge 1 of 6

Cold-snap booking: members first, fees paid, real capacity

Botlit(opens Botlit in a new tab)FluidGrids(opens FluidGrids in a new tab)Subscriber Bot(opens Subscriber Bot in a new tab)Kadaikodi(opens Kadaikodi in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)

The problem

When a cold snap or a heat wave hits, a contractor's promises start to collide. Agreement members were promised priority service, but nobody can tell who they are from a voicemail or a web form, so they wait in the same line as everyone else. Customer service offers afternoon slots without knowing how many technicians are actually free, and the ones that cannot be kept turn into apologetic calls. The diagnostic fee or trip charge is explained on the phone, forgotten and disputed later. Underneath it all, overnight messages arrive through an answering service without a matching address, a model number or the symptom in useful words, duplicate requests get booked twice, and a no-heat call from an elderly homeowner can wait behind a request for a replacement quote.

What it costs

Members lose the priority they paid for, surge days are overbooked, fees go uncollected and emergencies wait behind routine requests while the office re-keys messages.

How the products work together

Botlit is designed to answer customers on WhatsApp and web chat, ask for the symptom, address and a photo of the unit's label, and flag no-heat, no-cool and leak calls as emergencies. FluidGrids gives Subscriber Bot agreement members priority and pages the on-call technician and dispatcher about each emergency. Routine callers pay the diagnostic fee and book a Kadaikodi slot the MoveTheWheels board shows the crew can still keep.

How it works — technical detail

Technical detail

Botlit is designed to run a customer-facing agent on WhatsApp and web chat that triages each request against the contractor's approved guidance: it asks for the symptom, the address and a photo of the equipment label, and flags no-heat, no-cool and active-leak requests as emergencies. Botlit can start a FluidGrids workflow that looks the address up among the agreement members kept in Subscriber Bot, marks members for priority, and pages the on-call technician and dispatcher for each emergency with the conversation attached. Routine requests hand off to Kadaikodi, where the customer books a time slot for a service offering the contractor has configured and pays the diagnostic fee or trip charge at checkout; the slots offered are designed to follow the technician capacity left on the MoveTheWheels board. The booked job, with its symptom, photo and member flag, then passes to MoveTheWheels for dispatch.

The outcome it is designed for

A cold-snap morning starts with members recognized, emergencies already routed and routine calls booked into slots the crew can keep, with the fee paid.

The concepts behind it

Challenge 2 of 6

A dispatch board that knows trucks, parts and people

MoveTheWheels(opens MoveTheWheels in a new tab)AssetHandler(opens AssetHandler in a new tab)CrewFoundry(opens CrewFoundry in a new tab)

The problem

Dispatch still happens on a whiteboard or a calendar that shows only names and times. The dispatcher phones technicians to find out what is on their vans, learns at 7:30 that a van will not start, and places jobs from memory of who is closest. Technicians cross paths driving to opposite ends of town, one arrives without the part the job needed and makes a supply-house run, and arrival windows promised yesterday slip without anyone telling the customer until the customer calls to ask.

What it costs

Wasted drive time, missed arrival windows, second trips for parts and fewer completed jobs per technician on exactly the days demand is highest.

How the products work together

MoveTheWheels is designed to show the dispatcher every technician's day on one board: arrival windows, drive times, emergencies at the top, whose van carries the likely part and, from CrewFoundry, who is cleared for the job. AssetHandler shows which vans are off the road and when they return. The technician gets the job on their phone, and the customer is told a technician is on the way.

How it works — technical detail

Technical detail

MoveTheWheels is designed to hold the day as a dispatch board: one lane per technician and van, each job in its arrival window, emergencies at the top of the unassigned queue, and each technician's stops in order with estimated drive time and distance in view. Before a job is placed, the board shows which vans carry the likely part and which technicians are cleared for the job type, a clearance that comes from the CrewFoundry license register described in the next challenge. AssetHandler keeps the service vans as assets and shares which are off road and when each is back, so dispatch plans around them instead of discovering them in the yard. When a job is assigned, MoveTheWheels is designed to send it to the technician's phone with the address, window and equipment, and to send the customer an on-the-way message from the job's tracking status.

The outcome it is designed for

Jobs go to a technician who is cleared, close and carrying the part, vans that are down are planned around, and customers hear about changes before they have to call.

The concepts behind it

MoveTheWheels

Technician Dispatch Board and Arrival Windows

The trades dispatch board: technician lanes, arrival windows, an unassigned queue, and a placement panel that checks clearance, drive time and van stock before a job is assigned.

Works with CrewFoundry, AssetHandler, Kadaikodi

Concept pagefor Technician Dispatch Board and Arrival Windows on the MoveTheWheels website (opens in a new tab)

Challenge 3 of 6

License levels, CE hours and apprentice ratios nobody tracks

CrewFoundry(opens CrewFoundry in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)FluidGrids(opens FluidGrids in a new tab)

The problem

In the trades, who may do what depends on the license level and the jurisdiction: journeyman or master, a state license or a city one, a separate gas-fitting license, Section 608 refrigerant certification and backflow tester cards. Each renewal cycle needs a set number of continuing-education (CE) hours, and apprentices must log supervised hours toward their own license under a licensed journeyman, within the supervision ratio the jurisdiction allows. In most shops all of this lives in a spreadsheet, a folder of card photos and the service manager's memory. A license lapses while the renewal sits in a glovebox, CE hours turn out to be short a month before renewal, and apprentice hours are signed off under a journeyman who was never on the job.

What it costs

Work sent to the wrong person has to be redone or re-sent, apprentices' progress toward their own license is in doubt, and the firm cannot show a client who was on each job and what they held.

How the products work together

CrewFoundry is designed to hold each technician's licenses, certification cards and continuing-education hours, and to log apprentice hours under the journeyman who was there. FluidGrids warns the technician and service manager sixty days before an expiry or when those hours fall short. The MoveTheWheels board shows a technician with a lapsed license as not eligible for jobs that need it, and warns before an apprentice is sent without a journeyman.

How it works — technical detail

Technical detail

CrewFoundry is designed to hold each technician's licenses by trade, level and jurisdiction, with refrigerant and backflow cards, issue and expiry dates, and the CE hours earned against what the current renewal cycle requires. Apprentices' supervised hours are recorded against the journeyman who was on the job, toward the total their own license needs, and each crew is checked against the supervision ratio the firm has configured. Renewal and refresher courses sit in CrewFoundry learning paths. FluidGrids can run a daily check that warns the technician and the service manager sixty days before an expiry or when CE hours fall short. The register is designed to hand a clearance list to MoveTheWheels, so the dispatch board shows a lapsed license as not eligible for the job types that need it, and warns before an apprentice is placed without a licensed journeyman.

The outcome it is designed for

Expiries and CE shortfalls are handled weeks ahead, dispatch offers only cleared technicians, and apprentice hours carry the name of the journeyman who was actually on the job.

The concepts behind it

CrewFoundry

Trade License and Apprentice Hours Register

The register of licenses by trade, level and jurisdiction, continuing-education hours against each renewal cycle, and apprentices' supervised hours and supervision ratios, with expiries and dispatch holds in view.

Works with MoveTheWheels

Concept pagefor Trade License and Apprentice Hours Register on the CrewFoundry website (opens in a new tab)

MoveTheWheels

Technician Dispatch Board and Arrival Windows

Where the register's clearance shows up: a technician whose gas license has lapsed appears as not eligible for gas jobs, while the rest of their day stays on the board.

Works with CrewFoundry, AssetHandler, Kadaikodi

Concept pagefor Technician Dispatch Board and Arrival Windows on the MoveTheWheels website (opens in a new tab)

Challenge 4 of 6

The furnace nobody remembers

AssetHandler(opens AssetHandler in a new tab)Botlit(opens Botlit in a new tab)

The problem

A technician walks into a basement knowing only today's ticket. The history of that furnace (two earlier visits, a flame sensor cleaned and then replaced, a note that the venting looked marginal) lives in old tickets, another technician's memory and the homeowner's account. Model and serial numbers were never captured, so warranty status is a guess and the install manual is somewhere in a drawer. On commercial accounts the same gap hides a rooftop unit that is topped up with refrigerant every few weeks instead of having its leak found.

What it costs

Callbacks for the same failure, free return visits under labor warranty, missed replacement conversations, frustrated customers and refrigerant top-ups that treat the symptom.

How the products work together

AssetHandler is designed to keep a card for every furnace, air conditioner, water heater and panel at each address, showing the technician its age, warranty and past visits before work starts. Repeat failures under labor warranty are flagged as callbacks, a second repeat starts a repair-or-replace review and repeated refrigerant top-ups call for a leak inspection. Botlit answers technicians from your install manuals and past fix notes, showing its source.

How it works — technical detail

Technical detail

AssetHandler is designed to keep every piece of customer equipment as an asset tied to the customer's address, with make, model, serial, install date, refrigerant type and manufacturer and labor warranty dates. Every work order is raised against that unit, so its visit history, parts and readings are in front of the technician before work starts. A return visit for the same fault inside the labor-warranty period is flagged as a callback, and a second repeat starts a repair-or-replace review built from the unit's age, warranty and repair spend. Refrigerant added on each work order is logged per unit, and repeat top-ups raise a leak inspection. When the technician opens the unit, its make, model and past work-order notes are designed to pass to a Botlit agent whose knowledge base holds the contractor's install manuals and past fix notes; it answers with the passage it used, or says nothing matches, and the answer can be attached to the open work order.

The outcome it is designed for

Technicians start each job knowing the unit's history, repeat failures are escalated instead of patched again, and repair-or-replace conversations rest on the record.

The concepts behind it

AssetHandler

Installed Equipment Service History and Warranty Card

One card per address: every installed unit with its warranties, the visit timeline for each, and a callback flag when the same failure comes back inside the labor warranty.

Works with Subscriber Bot, Botlit

Concept pagefor Installed Equipment Service History and Warranty Card on the AssetHandler website (opens in a new tab)

Challenge 5 of 6

Maintenance agreements that renew instead of lapsing

Subscriber Bot(opens Subscriber Bot in a new tab)AssetHandler(opens AssetHandler in a new tab)FluidGrids(opens FluidGrids in a new tab)Kadaikodi(opens Kadaikodi in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)

The problem

Maintenance agreements are the steadiest revenue a residential contractor has and the base of most commercial accounts: members pay for spring and fall tune-ups, priority service and a discount, and commercial clients pay for planned visits on a schedule. But the agreements live in the billing system, the visits owed live on the schedule, and nobody sees both. Stored cards expire and renewals fail silently. Some fall safety checks are never booked. Spring tune-up season lands in the same weeks as the first cooling calls, and the member who had three callbacks renews without anyone calling first.

What it costs

Recurring revenue leaks away quietly, members who paid for visits never receive them, and tune-up season collides with emergency season.

How the products work together

Subscriber Bot is designed to show every maintenance agreement in one place: renewal date, whether the last payment went through and which visits are owed. Each morning FluidGrids finds renewals due, declined cards and owed visits for a person to act on, and approved members renew or update their card through Kadaikodi. AssetHandler turns owed tune-ups into visits on each covered unit, which MoveTheWheels routes by neighborhood before peak season.

How it works — technical detail

Technical detail

Subscriber Bot is designed to act as the contractor's agreement desk: each maintenance agreement is a recurring relationship with its plan, renewal date, payment status, covered equipment and the visits owed this season, grouped by area so owed tune-ups can be planned, with declined cards and members at risk listed for a person to approve the next step. A FluidGrids schedule runs each morning to find renewals coming due, declined cards and visits owed. For approved members, card-update and renewal links are designed to go through Kadaikodi checkout. AssetHandler turns each agreement's tune-ups into preventive-maintenance visits against the covered units, and batches of owed tune-ups, grouped by neighborhood, go to MoveTheWheels to be routed in the shoulder weeks before peak season.

The outcome it is designed for

Renewals are worked weeks before they fail, every member receives the visits they paid for, and tune-ups are booked into the quiet weeks instead of the peak.

The concepts behind it

Subscriber Bot

Maintenance Agreement Renewal and Tune-Up Desk

The agreement desk: tune-ups owed by area, covered equipment and visits owed for each member, with renewals and declined cards beside them for a person to act on.

Works with AssetHandler, MoveTheWheels, Kadaikodi

Concept pagefor Maintenance Agreement Renewal and Tune-Up Desk on the Subscriber Bot website (opens in a new tab)

Challenge 6 of 6

Hours and parts that never reach an invoice

MoveTheWheels(opens MoveTheWheels in a new tab)AssetHandler(opens AssetHandler in a new tab)CrewFoundry(opens CrewFoundry in a new tab)FluidGrids(opens FluidGrids in a new tab)BigConsole(opens BigConsole in a new tab)

The problem

The last mile of every job is paperwork. Residential jobs are priced from a flat-rate price book with options the technician presents on site, while commercial time-and-materials tickets need a signature and must stay under the client's not-to-exceed amount. Parts come off the van and are forgotten on the ticket; time on site, drive time and overtime are written from memory. The office rebuilds each ticket before invoicing, payroll reconciles hours against a separate clock, and nobody restocks the van until a technician arrives at a job without the part. The owner sees margin by job type only after month-end, if at all.

What it costs

Unbilled parts and hours, disputed commercial invoices, payroll corrections, extra supply-house runs, and margin nobody can see in time to act on it.

How the products work together

MoveTheWheels is designed to run each van as a small stockroom with a nightly restock list. AssetHandler records the price-book option or parts and hours with the customer's sign-off, and warns before a commercial job passes its not-to-exceed amount. When a job closes, FluidGrids flags van parts missing from the job, sends hours to CrewFoundry timesheets and the signed job for invoicing; BigConsole shows the owner margin and unbilled work.

How it works — technical detail

Technical detail

MoveTheWheels is designed to treat each service van as a stock location: parts scanned off the van against a job reduce its stock, and a nightly restock list is built for the shop. AssetHandler is designed to carry on each work order the flat-rate option the customer chose or, for commercial time-and-materials work, the parts and hours, with the customer's sign-off, and to warn the technician before a commercial work order passes its not-to-exceed amount. CrewFoundry keeps time entries with clock-in and clock-out, overtime and the job each hour belongs to. When a work order closes, FluidGrids can compare its parts lines with the parts scanned off the van and flag any mismatch, pass its hours to the CrewFoundry timesheet, send the signed work order to the accounting package where invoices are raised, and deliver its figures into a BigConsole data sink for the owner's console.

The outcome it is designed for

Every part and hour is on the job before it goes for invoicing, vans are restocked overnight, and the owner sees margin and unbilled work each week rather than after month-end.

The concepts behind it

How it fits together

How one service call moves through the products

Follow one job from the first message to the owner's weekly numbers. Each step is one product doing one thing and passing the job to the next; together they show how the products are designed to work as one system for a trades contractor.

  1. To Kadaikodi: renewal and card-update links for approved members

  2. To Kadaikodi: routine requests with symptom, address, photo and member status

  3. To CrewFoundry: the booked job and the kind of work

  4. To MoveTheWheels: the technicians cleared to take the job

  5. To AssetHandler: who is going, in which van, and when

  6. To FluidGrids: the finished job with its parts, hours and signature

  7. To BigConsole: each finished job's revenue, costs and callback flags

Step 1 of 8: Agreement reminders

How each hand-off works — technical detail

Technical detail

  1. 1. Subscriber Bot — Agreement reminders: Finds agreement members due a tune-up or a renewal, and those with a declined card, and queues each for a person to approve the next step.Hands to Kadaikodi: Card-update and renewal links for approved members.
  2. 2. Botlit — Intake and triage: Answers members and new customers on web chat and WhatsApp, collects symptom, address and a label photo, and flags no-heat, no-cool and leak calls as emergencies.Hands to Kadaikodi: Routine requests with symptom, address, equipment photo and member status.
  3. 3. Kadaikodi — Booking and fee: The customer books a time slot for a configured service offering, confirms the address and pays the diagnostic fee, trip charge or agreement renewal at checkout.Hands to CrewFoundry: The booked job with its trade and job type.
  4. 4. CrewFoundry — Clearance check: Maps the job type to the license it requires, using the firm's configured rules, and lists technicians on shift who hold it, with apprentice supervision checked and anyone lapsed on hold.Hands to MoveTheWheels: A shortlist of cleared technicians for the job, with holds marked.
  5. 5. MoveTheWheels — Dispatch and route: Places the job with a cleared technician whose van carries the part, orders the day's stops and is designed to send the job to the technician's phone.Hands to AssetHandler: The assigned job, technician, van and arrival window.
  6. 6. AssetHandler — Work on the unit: Opens the work order on the customer's unit with its history and warranty, and captures the price-book option or parts, labor, readings, refrigerant added and sign-off.Hands to FluidGrids: The completed work order with parts, hours, readings and signature.
  7. 7. FluidGrids — Close-out routing: Routes the closed work order: hours to CrewFoundry, parts checked against van scans, the visit to Subscriber Bot, the signed job to accounting, figures to a BigConsole data sink.Hands to BigConsole: Job revenue, parts, labor cost and callback flags, delivered into a data sink.
  8. 8. BigConsole — Owner's console: Shows margin by trade, branch and technician, callbacks, renewals and jobs not yet invoiced, with drill-down; Botlit agents can answer managers' questions from these figures.

Products in this solution

What each product brings

  • AssetHandler

    Customer equipment, work orders and service vans

    Is designed to keep a record of every piece of customer equipment and every visit to it, capture the sign-off and not-to-exceed amount on each job, log refrigerant by unit and show which vans are off the road.

    Technical detail

    Technical detail

    Its asset registry, warranty dates, work orders with parts and labor, and configurable fields are designed to keep every customer unit with its visit history, capture the sign-off and not-to-exceed amount on each work order, log refrigerant by unit and show which vans are off road.

    Visit AssetHandlerAll concepts

  • MoveTheWheels

    Dispatch, routing and van stock

    Is designed to give each job to a technician who is cleared for it, put each day's stops in order and run every van as a small stockroom with a nightly restock list.

    Technical detail

    Technical detail

    Its dispatch board, routes with ordered stops, driver and vehicle records and warehouse-and-inventory model are designed to place each job with a cleared technician and to run every van as a small stockroom.

    Visit MoveTheWheelsAll concepts

  • CrewFoundry

    Licenses, apprentice hours and timesheets

    Is designed to hold each technician's licenses, certification cards, continuing-education hours and supervised apprentice hours, plus renewal courses and the clock-in, overtime and job behind every hour, so dispatch sees who is cleared and payroll can be checked against the jobs.

    Technical detail

    Technical detail

    Its skills, certificates, learning paths and time entries are designed to hold licenses, cards, continuing-education hours and supervised apprentice hours, renewal courses, and clock-in, overtime and job attribution for payroll.

    Visit CrewFoundryAll concepts

  • Kadaikodi

    Online booking and payment

    Is designed to let customers pick a time slot, confirm their address and pay the diagnostic fee online, with agreement renewals paid through the same checkout.

    Technical detail

    Technical detail

    Treats service calls and tune-ups as bookable services with a duration and a price, so customers pick a time slot, confirm the address and pay a diagnostic fee at checkout, with renewals designed to go through the same checkout.

    Visit KadaikodiAll concepts

  • Subscriber Bot

    Maintenance agreement desk

    Is designed to track every maintenance agreement: its plan, renewal date, whether the last payment went through, the equipment it covers and the visits still owed, with members at risk of lapsing lined up for a person to decide the next step.

    Technical detail

    Technical detail

    Is designed to model each maintenance agreement as a recurring relationship with its plan, renewal date, payment status, covered equipment and visits owed, with lapse reasons and members at risk queued for a person to approve the next step.

    Visit Subscriber BotAll concepts

  • Botlit

    Customer intake and technician answers

    Is designed to answer customers on WhatsApp and web chat and sort emergencies from routine calls using your approved guidance, and to answer technicians from install manuals and past fix notes, showing where each answer came from.

    Technical detail

    Technical detail

    Is designed to run a customer-facing agent on WhatsApp and web chat that triages requests from approved guidance, and to answer technicians from install manuals and past fix notes, showing the passages it used.

    Visit BotlitAll concepts

  • FluidGrids

    Hand-offs between the products

    Can run the daily checks and hand-offs between the products: an emergency to the on-call technician, an expiry warning to the service manager, and a finished job's hours, parts and figures to payroll, invoicing and BigConsole.

    Technical detail

    Technical detail

    Can run the daily schedules and close-out automations that pass emergencies, expiries, renewals, parts and hours between products, and delivers job figures into BigConsole data sinks.

    Visit FluidGridsAll concepts

  • BigConsole

    Owner and manager consoles

    Turns the job, agreement and labor figures that FluidGrids passes along into one view for the owner: margin, callbacks and jobs not yet invoiced by trade and technician, with a click through to the jobs behind each number.

    Technical detail

    Technical detail

    Turns the job, agreement and labor figures that FluidGrids delivers into consoles with filters and drill-down, so owners see margin, callbacks and unbilled work by trade and technician.

    Visit BigConsoleAll concepts

One platform underneath: Burdenoff Workspaces

All eight products run on Burdenoff Workspaces: one sign-in for office staff and technicians, roles that decide who sees pricing, payroll or customer records, one record of who did what across every product, and one bill for the whole set.

Concept gallery

Every concept in this solution

15 concepts from 7 products. Each one links to its own page on the product's website, and every view has a link you can share.

Pitch kit

The Field Service solution in one minute

Trades contractors win on response and lose money in the hand-offs: the voicemail nobody decoded, the van without the part, the lapsed license, the callback nobody saw coming, the agreement that lapsed and the part that never reached the invoice. Burdenoff brings booking, dispatch, licensing, equipment history, agreements and job costing onto one workspace, with each product designed to pass the job to the next, so the office spends peak season serving customers instead of reconciling paperwork.

  • Botlit and Kadaikodi are designed to turn overnight messages into flagged emergencies and booked, paid service calls, with agreement members first.
  • MoveTheWheels is designed to dispatch only technicians CrewFoundry shows as cleared, with the part already on their van.
  • AssetHandler is designed to put every unit's history, warranty and refrigerant log in front of the technician before work starts.
  • Subscriber Bot is designed to keep maintenance agreements renewing and every owed tune-up scheduled before peak season.
  • FluidGrids and BigConsole show margin, callbacks and unbilled jobs each week, not after month-end.
Email it

Questions

Frequently asked

Is this a single field service management product?

No. It is eight Burdenoff products, each handling one part of the work, sharing one workspace, one sign-in and one record of who did what. FluidGrids feeding BigConsole, and Botlit reading BigConsole figures and starting FluidGrids hand-offs, are built in; the other hand-offs on this page show how the products are designed to work together.

Technical detail

Technical detail

No. It is a solution concept that combines several Burdenoff products: Kadaikodi for booking and payment, MoveTheWheels for dispatch and van stock, AssetHandler for equipment and work orders, CrewFoundry for licenses and time, Subscriber Bot for maintenance agreements, Botlit for customer and technician questions, and FluidGrids and BigConsole for hand-offs and reporting. They share one workspace, one sign-in and one record of activity. Apart from FluidGrids feeding BigConsole consoles and Botlit agents reading consoles and starting FluidGrids workflows, which are built into the products, the hand-offs on this page describe how the products are designed to work together.

Do we have to adopt all eight products at once?

No. Each product works on its own. You can start with the one aimed at your biggest problem, such as dispatch and van stock or equipment history, and add others later without a new sign-in, user list or separate bill.

Technical detail

Technical detail

No. Each product works on its own, so a contractor can start where the pain is sharpest, for example dispatch and van stock in MoveTheWheels, or equipment history and work orders in AssetHandler, and add the next product later. Because they share Burdenoff Workspaces, adding a product does not mean a new sign-in, a new user list or a separate bill.

Does it cover both residential service and commercial facilities work?

Yes. That is the intent: homeowners book and pay online in Kadaikodi and join maintenance plans in Subscriber Bot, while commercial work orders in AssetHandler carry the client's reference, not-to-exceed amount and signature, with planned visits scheduled per unit. BigConsole can split the numbers by residential and commercial work.

Technical detail

Technical detail

That is the intent. Residential calls can be booked and paid in Kadaikodi and covered by maintenance agreements in Subscriber Bot. Commercial work orders in AssetHandler can carry the client's reference, a not-to-exceed amount and a signature as configured fields, with planned-maintenance visits scheduled per unit, and BigConsole consoles can be filtered by residential or commercial work.

Does it tell us whether a technician is legally allowed to do a job?

No. CrewFoundry keeps the licenses, certification cards and hours your team enters and the rules you set, such as which jobs need which license, and MoveTheWheels uses them when assigning work. It does not interpret licensing law or guarantee compliance; your service manager stays responsible for what each jurisdiction requires.

Technical detail

Technical detail

No. CrewFoundry records the licenses, cards and hours your team enters and the rules you configure, such as which job types need which license and the apprentice supervision ratio you work to, and MoveTheWheels uses that record when jobs are placed. It does not interpret licensing law or guarantee compliance; your service manager remains responsible for what each jurisdiction requires.

Can the booking page or the customer agent carry our brand instead of the product's?

No. The products keep their own names and are set up, not rebuilt, for each business. You enter your services, prices, arrival windows, agreement plans, approved answers and job rules, but nothing is rebranded, private-labeled or custom-built.

Technical detail

Technical detail

No. Burdenoff products are offered under their own names and are configured, not rebuilt, for each business. You set up your services, prices, arrival windows, agreement plans, approved answers and job rules inside the products; they are not rebranded, private-labeled or custom-developed.

Is all of this available today?

No. The products are pre-launch or in early access, and several parts shown here, such as the dispatch board, van stock tracking, the license register, the equipment card and the agreement desk, are illustrated ideas, not finished features. We are glad to walk you through what exists today and what is planned.

Technical detail

Technical detail

Not yet. The products are pre-launch or in early access, and this page describes a solution concept: how they are designed to work together for trades contractors. Several surfaces shown here, such as the trades dispatch board, van stock tracking, the license register, the equipment card and the agreement desk, are illustrated ideas rather than finished features. We are glad to walk through what exists today and what is planned.

Related domains

Where these products also work together

All domains

Want to explore this for your organization?

Tell us about your setup. We will walk you through the products involved and scope a pilot around the challenge that hurts most.

Talk to usBrowse every domain

This is a solution concept: it shows how Burdenoff products are designed to work together in this industry. The images are illustrations of the concepts, not screenshots of the actual products, and every name and figure in them is sample data.