Piano Service Management Software

Piano service software for every piano on its own cycle, every day on one route.

Each piano's history and next due date live in notes that get lost, and the evening goes to chasing payments and returning calls. We turn that round into one owned system that holds the record, the return cycle, the route, and the price book for every piano.

See our work

Bring one stuck piano service workflow. Leave with a 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

Each piano's history and next due date live in notes that get lost between visits.

02

You started to care for pianos, not to chase payments, play phone tag, and spend evenings on admin.

03

A new booking lands across town between two visits on the same street, and the day scatters.

Plain answer

Piano tuning software runs a piano technician's own service business in one place. Each piano carries its own record, with make, measurements, and service history. Return tunings sit on six or twelve month cycles, new work books near where you already are, and pitch raises and repairs price from one book.

What to remember

  • Use this when piano records, return cycles, routes, and prices live apart and the gaps cost visits or unpaid work.
  • The first release should complete one path, such as one full round from due list to paid invoice, not collect disconnected features.
  • The piano is the record, not the client: make, measurements, and history travel with the piano when it moves rooms or owners.
  • Quote the team's own screens as their own scope: the due list, the piano record, reminders, and invoicing are a second product, not a single admin-panel line.
  • Hire freelancers for one small, well-defined task; use one accountable agency party when the work needs coordination across records, routes, reminders, and billing.

The first decision is not what to build.

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 handles the core workflow and the remaining gaps can be solved with configuration, a connector, or a small process change. Gazelle covers piano records, route-smart scheduling, and invoicing, PianoCal covers the intelligent calendar and drive times, and Mazurka Suite and Vivace cover the phone-first round. Compare them against your real round before paying for anything custom.

    Run the build-vs-buy numbers

  • 02

    Repair

    Keep the existing product when users still get value from it and the code can be understood safely. Start with evidence: where the code lives, how your data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live.

  • 03

    Build

    Own the system when the way you run the round shapes your margin, your evenings, and whether work gets billed at all. Start with one complete path, such as one full round from due list to paid invoice, and the system connections that path cannot work without.

  • 04

    Wait

    Do not turn a changing policy into permanent software. Stabilise the rules, name the workflow owner, and measure the cost of the current process 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

Piano service software should earn its maintenance burden.

A feature request is not enough. The case is real when the same constraint shows up in time, errors, margin, or customer experience.

A fit

Each piano runs on its own cycle, and the due list, the route, and the record live in different places.

A technician or small team can name a workflow owner and what 'done' looks like for the first release.

Site accounts, pitch work, or pricing rules differ by piano and no maintained product holds them cleanly.

Not a fit

A maintained product fits with reasonable configuration and process change.

The team wants software to settle an unresolved operating policy.

The brief is a feature list with no piano, visit, or business result 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 round, not the software.

A piano service problem usually starts as a memory problem. Each piano's history and next due date live in notes that get lost: a notebook in the van, a phone full of texts, a card file from years ago. What was done to the piano two visits back, which measurement mattered, and when it comes due again get settled from memory, standing at the piano. You started to care for pianos, not to chase payments, play phone tag, and spend evenings on admin, yet the admin is where the evening goes.

The cost is spread across the week where nobody counts it. A piano missed off the due list is a client who drifts to whoever reminds them first. A day booked by habit instead of by area burns driving time between stops. Work finished at the piano and invoiced days later is detail already fading, and some of it never gets billed at all because the pitch raise or the small repair was never written down.

The neighbouring sector has its own view. The music industry page speaks to music education and the schools and teachers who book lessons, which is a different business from caring for the instruments themselves. This page is the technician's side: the piano record, the round, and the billing. The wider pattern is the same one behind field service management software and the field service view: one person, one route, one record per job, repeated every week. The two views meet at the visit, and neither one replaces the other.

A second product hides inside the first. Clients see a visit and an invoice; you live in another set of screens: the due list, the route order, the piano record, reminders, the price book, and a record of who did what. Quotes that squeeze all of that into an "admin panel" line item are where budgets most often break. On a real platform, your own screens are routinely the most underestimated part of the build, so we quote them as their own job, with their own users, from the start.

Piano service management software makes sense when one owned system can remove that constraint better than a product, connector, or process change. The first release should take one path, such as one full round from due list to paid invoice, from start to finish. It should not replace every tool at once.

We start where it hurts.

The interface is only one part of the job. The real scope includes the rules, the data, the connections to your other systems, what happens when things fail, who can see and change what, and who runs it after release.

One record for every piano

Make, model, serial number, size, and measurements sit on the piano's own record with its full service history: tunings, pitch raises, repairs, regulation, and voicing. The next visit starts from the record, not from memory.

Return tunings on their own cycle

Each piano sits on the cycle you set for it, commonly six or twelve months. Finish a visit and the next due date is set, the piano joins the due list, and the reminder goes out when it comes due.

New work booked near the work you have

Bookings are offered near where you already are that day, so a new tuning tightens the route instead of scattering it. The day reads in driving order, with the extra driving shown before anyone commits.

One price book for pitch and repair work

The tuning, the pitch raise, common repairs, regulation, and voicing each carry your price and your time, set once. Visits price from the book, and work with no price is flagged instead of billed at nothing.

The invoice finished at the piano

The visit becomes the invoice before you leave, priced from the work you just recorded. Payment by card, cash, or check is recorded on the spot, so the evening is yours again.

Which one is yours?

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

Workflows

One record from due date to paid invoice.

Some of this work only exists in one corner of the trade. The same rules apply: configure first, build only the part the maintained products cannot cover, and start with one complete path.

The solo round

One technician, several areas, a book of pianos on mixed cycles. The phone holds the day, the records, and the billing, so the notebook stops being the office.

A small team on one book

Two or more technicians working the same clients need one shared due list and one record per piano, so a piano covered by a colleague keeps its measurements and its history intact.

Schools, churches, and venues

One site, several pianos, several rooms. Each piano is tuned, recorded, and priced on its own record and its own cycle, and the site gets one account and one invoice for the visit.

The neglected piano brought back

A piano years overdue needs a pitch raise before the fine tuning, and often a follow-up visit to settle. The record holds the plan, the estimate the client approved, and the history that explains the price.

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 part of the round is costing you the most right now?

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

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 round

    Where is the cost or failure actually coming from?

    Follow one technician and one full round from due list to paid invoice. Include the workarounds, manual judgement, duplicate entry, waiting, and failure paths that a tidy process diagram usually misses.

    Decision produced

    A map of the round, exceptions, owners, systems, and the baseline cost or delay worth changing.

    Risk closed

    Paying to automate the visible symptom while the expensive constraint remains.
  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, the system connections, who can access what, the exceptions, and the result the first release must complete.

    Decision produced

    The right mix of web, mobile, desktop, browser extension, connected device, wearable, or behind-the-scenes connection work, with the first-release boundary and a clear definition of done.

    Risk closed

    A small-looking feature list that quietly depends on several interfaces, systems, and owners.
  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. Record changed assumptions and test what happens when data is missing, access is wrong, or a connected system fails.

    Decision produced

    Working checkpoints tested with realistic data, real user types, system connections, recovery plans, and the people who will use or run the system.

    Risk closed

    Discovering the important gaps during migration or after customers depend on the release.
  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 pianos or areas first. Compare time, errors, completion, or another agreed measure with the starting point before adding the next workflow.

    Decision produced

    A controlled release, comparison with the baseline, operating notes, account ownership map, and a recommendation for what should happen next.

    Risk closed

    Measuring development 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. You see the round working, not a slide deck about it.

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.

You can judge the work without being technical

Checkpoints are working software you use yourself, reported in plain language. If a step fails, you see it fail in the product, not in a status report.

Piano service and the neighbouring view.

The technician's book is one side of the visit. The wider field pattern and the music sector keep their own sides, and each page below speaks to one of them.

What it costs

Every project starts at $10000.

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

Starting investment

Starts at $10000

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

Buy or own

Buy a maintained productOwn custom software
Best fitHandles your round with reasonable setup, and its pricing makes senseThe way you run the round is itself the advantage
Manual workConfiguration and process changes can remove the constraintRepeated manual work has a measurable cost
ConnectionsExisting connections work with reasonable setupA critical connection to your accounting or messaging system cannot be done cleanly any other way
Platform routeConfigure a maintained product when its cycle, route, and billing model fitsOwn custom software only when the differentiating process, site accounts, or cost of constraint justifies build and support

Work with us

Bring one stuck piano service 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 round scoped 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.

Common questions

Piano tuning software runs the technician's own service business in one place. Each piano carries its own record, with make, measurements, and service history. Return tunings sit on the cycle you set for that piano, new work books near where you already are, and each visit turns into an invoice priced from one book. It is the trade side of the work, not a tuning app a piano owner uses to tune the piano themselves.

The piano itself: make, model, serial number, size, and the measurements that matter for the work, such as string and parts details you note as you go. The service history sits on the same record: every tuning, pitch raise, repair, regulation, and voicing visit, with what you found and what you did. Photos of the piano and its condition sit there too, so the next visit starts from the record, not from memory.

Every piano gets its own cycle, set by you for that piano. A home piano commonly sits on a six or twelve month cycle, a teacher's studio or a church piano may need a shorter one, and a piano that is rarely played may sit on a longer one. Finish a visit and the next due date comes from that piano's cycle. The due list is the week already worked out, and the reminder goes out when the piano comes due, not when you happen to remember it.

When a client books, the system looks at where you already are that day and offers times near those visits first. A new tuning on a street you are already visiting tightens the day; a booking across town is offered on a day you are already in that area, or flagged for the extra driving before anyone commits. The day reads as one route in driving order, not a grid of slots scattered across the map.

Clients book from a link you share, picking from openings you control: your working days, your areas, and the times that fit the route. You approve the booking, or let regular clients confirm on their own, and the visit lands on the piano's record and your calendar at once. The back and forth of calls, texts, and missed messages is what goes away; you still handle the exceptions yourself.

A piano left untuned for years drops below standard pitch, and one fine tuning cannot bring it back in a single pass, because raising one string changes the tension on the others. A pitch raise is the first rough pass that brings the piano close to pitch before the fine tuning. In the price book it sits as its own priced service next to the tuning, so the quote names it plainly instead of being argued about at the piano.

You set your prices once: the standard tuning, the pitch raise, common repairs, regulation, and voicing, each with the time it takes. A visit prices itself from that book as you record the work, and bigger work becomes an estimate the client approves before it starts. Work with no price set is flagged for you to price, never billed at nothing and never quoted from memory.

The system sends the reminder for you when the piano's cycle comes due: a message to the client with a link to book, tied to that piano and its last visit. Clients who do not book get a follow-up on the schedule you set. Appointment confirmations and a reminder before the visit go out the same way, so you drive out knowing the client will be there.

Yes, when offline work is part of the scope from the start. The day's route, the piano records, and the invoice screens live on the phone and keep working in a basement practice room or a hall with thick walls. Changes save on the device and sync when the signal returns, and you can see what has synced and what is still waiting.

Each piano keeps its own record and its own cycle, even when several pianos sit at one address. A school with pianos in several rooms gets one visit that covers each piano in turn, with the work and the price recorded per piano, and one account for the site. The site record holds the rooms and the contact; the piano records hold the instruments.

Buy a maintained product when it handles your round with reasonable setup and its pricing makes sense. Gazelle covers piano records, route-smart scheduling, reminders, and invoicing for piano technicians, PianoCal covers the intelligent calendar and drive-time scheduling, and Mazurka Suite and Vivace cover the phone-first round and the shop. Own custom software when your cycles, site accounts, or pricing rules do not fit any maintained product, or when the way you run the round is itself the advantage. If the rules of the round are still changing every week, wait and settle them first.

For a small, well-defined task with someone technical managing it, freelancers are often cheaper. The pattern that goes wrong is a non-technical buyer coordinating several freelancers becoming the project manager, the tester, and the person who discovers the pieces do not fit. A piano software company earns its fee when the work needs coordination across records, routes, reminders, and billing: one accountable party, one phase price, and checkpoints against the whole round. If your need is one screen or one fix, hire the freelancer.

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 data needs moving over, whether phones or tablets are involved, any compliance requirements, and the condition of existing code. The agreed phase is priced in writing before it starts.

You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the round agreed at the start. Progress is reported in plain language: what changed, what is 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.