Skip to main content

Custom software for Indianapolis businesses

A service agreement signed in Carmel sets off a chain: visits owed, a van sent, a part used, a renewal due. We build software that carries an Indianapolis heating firm's agreement through every link.

Software for heating, cooling and plumbing firms

A homeowner in Carmel signs a service agreement with a heating and plumbing firm, and from then on she expects a tune-up before the cold comes. In the first cold week of autumn, when her furnace will not light, she expects a technician who knows her system and carries the part. She is one of several hundred customers with an agreement, and many of them call that same week. Later she expects a renewal offer before the agreement runs out. At the firm, her agreement sits in a spreadsheet, her visit on a whiteboard and the part in a technician's memory of his van.

With software built for the firm, her agreement lists the visits she is owed and when. In September she is offered a tune-up on a day a technician is already in her neighborhood, because the schedule is built by neighborhood and nobody crosses the county twice in a day. When she calls about the furnace, the dispatcher sees her history, which of the twelve vans is closest and what it carries, and chooses who goes. The part fitted in her basement comes off the van's stock and onto the reorder list. Sixty days before her agreement lapses, her name is on a renewal list, and the owner decides what she is offered. If the firm's scheduling product already does part of this, that part stays and we build what is missing. Scope and price are fixed in a brief before building starts.

Homeowners like her fill the new streets of Marion, Hamilton, Hendricks and Johnson counties, and a carrier's shipper or a remodeler's client depends on a firm's records as she does. For the heating firm, Lafayette is the likely first step beyond those counties, with Bloomington after it. For that step the software gains one thing, a Lafayette route: agreements signed there are grouped into tune-up days for a van kept there, and the dispatcher in Indianapolis sends it out with the other twelve. A homeowner in Lafayette who signs is then offered her September visit as the one in Carmel was.

What you receive

  • Internal tools that replace spreadsheets and manual steps.
  • Customer portals where your clients see their own information and act on it.
  • Connections between systems that do not talk to each other.
  • A first product, from an idea to a release real users can try.

How it runs

  • We map the work: who uses it, what they need to get done, the records and rules involved.
  • We define the smallest useful release and check whether an existing product can do part of the job.
  • We build in pieces you can review, testing real tasks, permissions and what happens when something fails.
  • We release and hand over, with operating notes and a plan for what comes next.
Everything that is included

Scope and investment

Start with the brief: $2,500. We write down what the software has to do, list the screens and give you a fixed price and a timeline. The $2,500 is credited in full when you complete the build with us.

Work you can inspect

The Tucker CPA website home page, built by Butler Agency

Tucker CPA

We built the brand, the website and a national content system for a new CPA firm, and we handle its SEO.

Read the case study
The Beyond the Bedside Foundation website home page, built by Butler Agency

Beyond the Bedside Foundation

A website for a new children’s foundation, built for families, student volunteers and supporters.

Read the case study

Questions before we start

The first cold week of autumn swamps our phones every year. What would the software change about that week?

Not the number of calls. It changes what your dispatcher knows when each one comes in: whether the caller has an agreement, which van is nearest and whether the part is on it. The September tune-ups are tracked too, so before the cold arrives you can see which agreement customers have not had theirs.

We already pay for scheduling software. Why build anything?

Perhaps you should not. We look at what it does first. Firms usually come to us for the piece it handles badly, such as agreements with different visit counts, and we build only that and connect it.

Can technicians use it in a basement with no signal?

Yes. The visit, the customer's history and the checklist are stored on the phone and sent when the signal returns. Nothing a technician enters is lost in between.

What would you like your business to do next?

Tell us where the work gets stuck or where you want to grow. We will help you choose a practical first step.

Discuss your project