From idea to instrument, and everything after it
A luthier’s tools divide in two, and the division is easy to miss because both halves answer to the same word.
The first is about how you go from idea to a buildable instrument. Plans and templates from Stewart-MacDonald, the Guild of American Luthiers, or any number of small plan-sellers. Hand-drawn schemata for traditional builders. CAD/CAM for those with a CNC router — Vectric, Carbide Create, Fusion 360. AutoCAD for headstock templates. Some builders work entirely on paper; some live in software; most are somewhere in the middle. This is the conversation that dominates the Official Luthier’s Forum, The Acoustic Guitar Forum, the ProjectGuitar threads. It’s the visible-craft conversation — how you turn a customer’s brief into a physical fingerboard slot, a body cavity, a neck profile.
The second is quieter, much more recent, and visibly more frustrating to the people having it. It’s about the business: the shared Gmail that started elegant and broke as the builds stacked up, the Notion page that did the job for the first two and then went stale, the January bank reconciliation that takes a fortnight because deposits arrived by transfer, by card and in cash, and the supplier orders to Stewart-MacDonald and LMI and Allied Lutherie that you can never quite remember whether arrived.
These two conversations get conflated because both involve tools — and increasingly, software. But they answer entirely different questions. The design conversation answers “how do I produce this shape correctly?” The business conversation answers “how do I keep the business straight while my hands are full?”
There’s exactly one luthier-positioned tool that takes the second question seriously today: Shopflow, built at Glaser Instruments in Nashville. It’s a real product with real users, built mostly around the instrument-repair workflow — estimates, work orders, customer status notifications, ship-out. It works well for that. For a custom luthier doing six or twelve builds a year, with commission cycles measured in months and customer relationships measured in years, it tends to feel slightly like the wrong shape — and at $100–200 per month per shop, the wrong price for the shape it is.
This article is about what the right shape looks like.
What a custom build actually looks like
For anyone reading this who isn’t a builder, here’s roughly what a custom guitar commission entails. If you live this every day, skip the next few paragraphs.
A customer reaches out — usually an Instagram DM, sometimes an email, occasionally a contact form. They have an idea: a parlor for fingerstyle, an OM for travel, a dreadnought for the band, a custom electric in a specific finish, an archtop for jazz. The first conversation does double duty as both a sales chat and a fit diagnostic. What do you play now, what works about it and what doesn’t, where does this instrument fit in the rest of your stable, what’s the budget, and when do you need it ready?
If the conversation goes anywhere, you talk tonewoods. Top: Sitka, Adirondack, Engelmann, cedar, redwood, sometimes torrefied. Back and sides: rosewood (Indian, occasionally Brazilian for those with the paperwork), mahogany, koa, walnut, maple, occasionally something more unusual. Neck: mahogany or maple typically. Fingerboard: ebony, rosewood, occasionally a stabilised wood. Bridge: usually matched to the fingerboard. Then bracing pattern, body depth, neck profile, scale length, nut width, headstock shape.
Hardware follows the wood. Tuners (Gotoh, Hipshot, Schaller, Waverly when budget allows), bridge pins, nut and saddle material, strap buttons, end pin, pickup if applicable. For electrics: pickups (Seymour Duncan, DiMarzio, Bare Knuckle, your own winder if you do that), tailpiece, control layout, the electronics.
You give a price; a deposit of around a third lands; the build joins your queue. From that moment forward, the customer’s sense of how long they’ll wait is anchored to whatever you most recently said to them.
Then sourcing, where a typical luthier uses four or five primary suppliers in a year plus another half-dozen for occasional bits: Stewart-MacDonald for tools, parts and hardware; LMI, Allied Lutherie or RC Tonewoods for tonewoods; Hipshot, Gotoh, Schaller or Waverly direct for tuners and hardware; and sometimes a small local sawyer for the figured pieces nobody else has. Every one of them maintains its own portal, its own SKU naming, and its own lead times — which they communicate with varying degrees of honesty.
Fabrication takes months of top and back joining, thicknessing, bracing, side bending, body assembly, neck construction, neck-set, fingerboard work, fret installation and dressing, binding and purfling, bridge installation, finish (lacquer, French polish, oil), setup. Twelve weeks at a minimum for a clean acoustic build; longer for a complicated electric or a fancy inlay.
While the build is happening, the customer waits, and they wait wanting photos. Luthier customers, more than most, expect to see the build in progress — the wood selection, the bookmatching, the bracing pattern, the headstock shape, each new finish coat as it goes on. A good cadence is one substantive update a fortnight, plus photo bursts at the moments worth marking. A bad one is the apologetic batch of photos that arrives weeks late.
Then setup, photographs, hand-off, sometimes a follow-up setup six months later as the neck settles in, and then the final invoice. The customer becomes a brand ambassador in a community where word travels far and fast, or they go quiet in ways you’ll never quite understand.
Multiply that by ten or twenty builds a year, with each one at a different stage. That’s the business problem.
Where the tools you’re using now stop working
If you finish fewer than five instruments a year, your existing tools are probably fine. The spreadsheet stays manageable, the DMs stay answerable, the supplier orders are infrequent enough to remember, and your head holds it all.
The friction tends to start somewhere between the fifth and fifteenth build — though concurrent builds, not sequential ones, are what really shift the threshold. Five builds done one after the other is one experience; five builds at different stages of completion happening at once is another entirely.
The failure modes are predictable:
The deposit chase. An agreed deposit hasn’t landed, and the back-and-sides set can’t be booked until it does. You don’t want to nag and you don’t want to start a back-and-forth — but tonewood is not a stable commodity, and the figured set you both agreed on can be sold to someone else while the chasing waits its turn.
The spec-change you can’t find again. A changed mind about the rosette — not the herringbone, the abalone one — arrives in a passing DM. Weeks later, with the bound body on the bench ready for the rosette channel, the conversation is half-remembered but the thread is nowhere to be found, and nobody wants to admit to having forgotten.
The supplier order that never arrived. Three orders placed in one sitting arrive on different schedules, and the late one goes unnoticed until the body is almost glued up — because the confirmation emails are buried among dozens of others, and only some of them ever get opened.
The photos that never make it to the customer. The rosette inlay against the bound spruce, the X-bracing at glue-up, the dovetailed neck joint, the first coat of nitro — all photographed, all things the customer would have loved, none of them sent. The phone has the originals; the laptop doesn’t sync; one of you ends up wondering whether the other has gone quiet.
The “where are we with #047” question. Someone — your partner, your apprentice, the bookkeeper — asks for an update on a specific build. You know the answer in your bones, but you can’t condense it into a sentence, and you can’t point them at a screen that says it for you, because the answer lives in your head and a dozen text threads.
The January reconciliation. The books need to close, but deposits and finals arrived by card, by transfer and in cash, and builds in flight straddle the tax year — the work in one year, the final payment in the next. Reconciling it from spreadsheets costs evenings.
If any of those land too close to recent experience, the tools you have probably aren’t up to the volume any more. Not because they’re bad — they aren’t. Because they were never built to carry this kind of load.
Five jobs for the right tool
Set the design side aside and the list of real jobs is short. Here’s how a luthier would describe them.
One. One place for everything you’ve decided about this build. The tonewood choices, the bracing pattern, the customer’s hand size and reach preference, the conversation about whether they want a cutaway, the photos at each stage, the planned scale length, the colour swatch for the binding. Not eight tabs and not a phone full of unsynced photos, but one workspace that follows the build from first email to setup. Everyone on the team sees the build; the customer sees the bits you’ve chosen to share.
Two. A spec sheet that lets you change your mind. Most parts-list software was built for factories, where the spec is locked before production begins. A custom build is different. The customer might switch from Sitka to Adirondack in week three. You might decide on a different bridge style halfway through. The tuners are a decision that can sit open until you’re ready to order them. The spec sheet has to bend with the build — substitutions allowed, quantities movable, supplier choice deferred until you actually decide.
Three. A way to share the build that isn’t a DM thread. Luthier customers expect photos. They also expect to feel close to the build. A proper customer-facing surface — branded, curated to what you want to share, fast on a phone — beats a DM thread for both of you. The DM thread can stay as the casual chat; the portal becomes the build’s home. The internal notes — the “customer has changed their mind about saddle compensation three times” notes — stay invisible to them.
Four. Sourcing that knows you don’t have one supplier. Stew-Mac is one supplier and LMI another, then Hipshot, Gotoh, your local sawyer, the specialist who sells you mother-of-pearl, the small mill that sets aside Sitka tops once a year — all different, all with their own portals, their own SKU systems, their own lead times. Software that treats orders as one-PO-per-supplier and asks you to do that workflow forty times a year is software that nobody on the workbench actually uses.
Five. Payments and books that close the loop themselves. A deposit when the customer commits, an interim payment when you’re halfway, and the final on hand-off — three Stripe transactions per build, ten or twenty builds a year, sometimes one in cash, sometimes a wire transfer from overseas. At the end of the year your accountant gets a tidy export instead of a panicked email and a folder full of bank statements.
That’s the job description. There are sixth and seventh nice-to-haves — calendar integration, time tracking, demand forecasting against your supplier history — but the five above are what actually moves the work forward.
The build number — and what it has to remember
Luthiers number their builds. Some do it sequentially (#001, #002, #003), some by year (2025-04, the fourth build of 2025), and some with their own coding tied to model, customer or material. The convention is yours and the function is the same: the build number is the instrument’s identity for the rest of its life, and the customer will still be calling it by its number decades later.
What the build number has to remember has grown over the last few years. It used to be enough to know the tonewoods, the spec, and the date. Today, reasonably, customers expect more.
The Brazilian rosewood back-and-sides set has CITES paperwork. You should have it. The customer’s grandchild may need it one day, and the Sitka top came from a specific small mill; the figured maple was the off-cut from a particular sawyer. The bridge pins are mammoth ivory; here are the certificates. The finish is nitrocellulose; some countries want to know that. The customer cares; the next owner will care more.
This is a record-keeping problem that nobody really designed for in 2005, when many of today’s independent luthiers came up. It’s a record-keeping problem now. And it’s only getting more important — every year a new wood species comes onto a CITES list, every year customers ask sharper provenance questions.
A build-management tool that takes the build number seriously is one where the number anchors everything: the spec sheet, the supplier orders (including the paperwork that came with them), the photos, the payments, the customer’s record. Decades from now, if the customer’s grandchild wants to know what woods are in their grandfather’s guitar, you can answer.
Our Owner’s Card was built for exactly this — a provenance handover document with photo, serial number, materials notes, and aftercare, attached to the build for the life of the instrument. The Card travels with the instrument; the build number is its anchor. Twenty years from now, when the instrument comes back to you for a re-fret, the documentation is still there.
What to look for, and what to avoid
When you start evaluating software, here’s what to actually look for — and the tells that a tool is answering someone else’s question.
Look for: a tool that thinks in commissions, not tickets. Good luthier software treats each build as a long-form thing with a beginning, a middle, and a hand-off. Its current stage is obvious. So is what it’s waiting on, and when it’s due. Avoid: anything built around the ticket. Repair-shop tools are designed for discrete jobs that open, get worked, and close in a short window. A custom build doesn’t shape-fit that model — and forcing it into one is the single biggest mismatch when luthiers try repair-shop tools for their custom work.
Look for: a spec sheet that bends. You can substitute a part, change a quantity mid-build, leave a supplier decision unresolved until you’re ready to make it. Avoid: rigid parts catalogues. Inventory and MRP software often demands you pre-define every SKU before any line can go on a build. That model fits someone making a hundred identical mandolins. It doesn’t fit one-offs.
Look for: a portal built for the relationship. The customer can follow progress, send a message, and pay an invoice from one branded surface. Avoid: anything that turns the customer into a ticket-requester. Tools that funnel customer messages into a “submit a request” form reframe the relationship as a service contract. A luthier’s client is closer to a patron than a customer; the software should know the difference.
Look for: many suppliers, one ordering surface. A guitar build sources from four or five places at minimum. The right tool aggregates what you need across builds and prepares a separate order for each supplier in one workflow. Avoid: one purchase order at a time. If the tool forces you to create POs one supplier at a time, you’ll do that dance forty times a year and stop using the feature by month three.
Look for: pricing that doesn’t penalise teamwork. A flat monthly fee with everyone included. Avoid: per-seat pricing. Per-seat charges punish you for inviting your apprentice, the finisher who does your final coats, the weekend cover for setups. A two-person studio shouldn’t pay more than a one-person one just because you taught someone else how to do the fretwork.
Look for: a vendor who’ll tell you when they’re the wrong choice. Software companies built by makers will name the cases where you should use something else. Avoid: feature pages with everything ticked. If a sales page claims design, manufacturing, accounting, CRM, marketing and inventory in one tool at hobby pricing, the boxes that look ticked are the shallow ones.
The Lightspeed integration angle
If you also do tech work, repairs, or sell parts and strings from a small shop alongside your custom builds, your inventory question gets more complicated. Many luthiers who run mixed practices use Lightspeed R-Series for the shop floor.
The integration question matters here. A custom-build tool that doesn’t talk to your POS forces you to maintain two sources of truth for the same parts. The bone nut blank on your shop shelf and the bone nut blank on a customer’s BOM are the same nut blank, but you’ll be counting them twice — once for inventory and once for the build — and reconciling them by hand.
A custom-build tool that does talk to your POS treats them both as the same single source of truth. The nut blank leaves stock the moment it’s assigned to a build. The price you paid for it flows through to the customer’s spec sheet automatically. Reorder triggers fire when shop stock dips below threshold. None of it needs thinking about; the totals just stay coherent.
If you’re a pure custom builder with no shop floor, this doesn’t matter for you. If you have any kind of retail or repair operation running alongside, the integration is the difference between maintaining one inventory and maintaining two.
When a spreadsheet is still enough
Be straight with yourself before you spend anything.
If you build four or five instruments a year, your customer list is short, your supplier list is stable, and your accounting is uncomplicated — a well-structured spreadsheet and a shared Gmail might genuinely be enough. Plenty of one-person workshops below five builds a year run fine without specialised tools.
The question worth asking is whether you’re at five builds and steady or five builds and accelerating. If steady, keep the spreadsheet. If accelerating — if next year is realistically eight or twelve or twenty — the time to put a system in is while you have two builds in the queue, not after the friction has already cost you a season. Migration is much harder when you’re full of in-flight commissions than when you have the headroom to set things up properly.
There’s also the quality-of-life dimension, which doesn’t show up in any financial. Even at the same volume, the gap between knowing exactly where every build is without having to think about it, and being fairly sure a build is at the finish stage but having to go check, is a real one. Some makers carry the whole studio in memory happily; others find it wearing. Both are legitimate ways to run a shop.
Where Vidual Projects fits
If you’ve read this far, here’s how our features map to a luthier’s workflow.
Every build gets its own home. One page per commission — timeline, conversation history, internal notes, spec sheet, supplier orders, payment schedule, photos, calendar dates. The whole team works from the same surface, while the customer sees a curated portal view rather than the workshop chaos.
The spec sheet (we call it the worksheet) is built for one-off commissions, not factory parts lists. Swap a tonewood, change a tuner spec, leave the bridge decision open until you’ve seen the back-and-sides set in person. It links to suppliers, reads stock from Lightspeed if you have it, and flags shortages before they become problems. The longer story sits in tracking every part from order to workbench.
Concierge handles the sourcing side. It pulls together what you need across every active build, groups by supplier — Stew-Mac in one card, LMI in another, Hipshot, Gotoh, your local sawyer — and prepares the order ready for you to send. We don’t send anything on your behalf; the brand always presses the final button. Why ordering is harder than it looks goes deeper, alongside the worksheet-Concierge-Demand loop.
The Activity page — our kingfisher view, in the journal’s vocabulary — sorts your builds by what needs attention this week: awaiting a customer reply, stalled, payment overdue, approaching a delivery date, or flagged in your gut. Glide above twenty builds; dive to the three that need you this morning.
The customer portal is shaped for the maker-patron relationship, not for support tickets. Your customer sees their build — the photos you’ve chosen, the invoice, the next milestone — and messages you about them. The internal notes stay invisible to them. The whole surface is designed around the fact that for the kind of customer who commissions a custom instrument, the relationship is part of what they’re paying for.
Payments run through Stripe Connect, or Nexi XPay if you’re working in Europe. Deposit, interim, final — the customer pays directly, the books update automatically via Xero or QuickBooks. Three transactions, zero manual reconciliations.
Direct Messages give you a channel to your collaborators — the finisher, the inlay artist, the fret-dressing specialist, the small mill that sets aside Sitka tops once a year — living in the same tool as the builds. Reference a build inside a chat with a slash-picker, so the question about a 12-fret cap inlay sits next to the build it is about. It replaces the Instagram-DM thread that nobody scrolls back through.
An iOS native app puts the workshop in your pocket. The Lightspeed integration handles the shop floor if you run one. The trial is thirty days, no card required. Pricing is Maker £12.99 / Studio £34.99 / Atelier £69.99 monthly, scaled by active projects rather than seats — every feature in at every tier, every team member included, no per-head surcharge.
The shape of the tool
A lutherie workshop doesn’t need a CRM, doesn’t need an ERP, doesn’t need anything with the word “enterprise” in the title — because none of those tools are the right shape for a workshop where the most important relationship in the business is between a maker and the person who’ll play the instrument for the next forty years. What it needs is a tool shaped like a well-organised workshop apron: everything within reach and nothing in the way.
If that’s the kind of tool you’ve been hoping someone would build, take it for a spin. The trial runs thirty days, no card required. If we’re not the right fit, we’d rather say so on a demo call before you’ve sunk an evening into setup.
Vidual Projects is available now at vidual.app. 30-day free trial, no credit card required. £12.99 / £34.99 / £69.99 per month after that, every feature, every team member, no per-seat surcharges.