WHY I BUILT IT
Managing one build is easy. You keep it in your head. Five or six at once is a lot more than five or six times the work: a spreadsheet for prices, a calendar, a list of parts to order, a message thread with every customer, a folder of receipts. And none of them know about each other.
I was looking for a solution for about 5 years, but no software matched what I needed. Having built full production software for Dingwall, I felt comfortable building one for myself. However, keeping something this big to myself seemed wasteful, so I decided to make it available to others.
A product like that needed a name, but it turns out it’s surprisingly difficult to find a suitable name that hasn’t been taken already. In the end I invented one: Quarterseen. It’s a play on “quartersawn”. Sounds fitting to me, but let me know if you think it’s stupid.
WHAT IT DOES
I’ll skip the obvious stuff like invoices. Here’s what was custom-built for shops like mine.
Your price list turns into a calculator on your website. All your options and upcharges, plus the rules between them: this option only on that model, a ceruse finish costs more when it’s combined with metallic. A customer builds their instrument, sees the price and sends it to you. It lands in your list of enquiries, with the full spec. My own calculator at padalka-guitars.com/order runs on it.
The schedule redraws itself. You put the builds in order and set your pace and your days off. It works out every start and finish date from that. One build starts late and everything behind it moves. I used to keep a Gantt chart, but it’s static, so things often snowballed.

Build schedule (sample shop). Hatched bars are builds not started yet. The green band is a week the shop is closed.
Parts follow the specs. The hardware selected in the specs is tied to your inventory, and a shopping list is generated based on what’s missing or running low. You can mark what’s ordered and received right there.
Customs paperwork. That’s one of my favorites. I kept missing some fields in those documents, so I made this to draft the commercial invoice and the Lacey declaration from the build’s specs. Behind it is a list of 46 guitar woods (and growing) with their scientific names, where they grow and their CITES status. You confirm which species each of your woods is once, and from then on it fills in.
A client portal. Each customer gets their own link: where their build is, the design to approve (or a box to say why not), the specs, invoices and what’s left to pay. It carries your shop’s name.
Customers kept losing their spec sheets, asking me to resend their mockups and order forms. Now it’s all in one place.

Build #241 in the client portal
Books that take receipts by email. Forward a receipt to your shop’s address and it shows up as a line waiting for you to confirm, with the receipt attached. When the bank line comes in, the two get matched. It keeps more than one currency, so getting paid in USD and spending in your local currency doesn’t make a mess of the year. Wise accounts sync by themselves.

Books (sample shop). The highlighted line came from a forwarded receipt.
THE BETA
I’m opening the beta to 10 builders. For now it’s tuned for instrument building. A general version for other makers will come later.
Free during the beta. There’s no end date yet. It ends when it’s ready.
Half price after launch, for as long as you stay. The price isn’t set yet. I’ll ask the beta builders what they think is fair before I set it.
I set up your price list. Send me whatever you have now: a spreadsheet, a PDF, a photo of a page.
Start with your next build. You don’t have to move your whole backlog over on day one.
In return, use it on real builds and tell me what doesn’t work.
If you want in, write to me through the form on quarterseen.com. Tell me what you build and roughly how many a year.
— Simon
P.S. Quarterseen is made for small shops. If you run a bigger one and need a system built around how you work, like the one at Dingwall, I still do that too. Same way to reach me.
