Custom Software for Sign Companies

Four businesses under one roof

Most trades do one thing and do it repeatedly. A sign company does four things in sequence, and each one has a different rhythm, a different bottleneck, and a different person who owns it.

There is a design studio that produces artwork and proofs. There is a permitting function that deals with a different set of rules in every jurisdiction you work in. There is a fabrication shop with machines, materials, and a queue. And there is an install crew that needs a bucket truck, a traffic plan, and a site that is actually ready. A single job passes through all four.

The trouble is that each of those functions tends to keep its own record. Design lives in a folder and an email thread. Permits live in a spreadsheet and a stack of PDFs. Production lives on a whiteboard. Installs live in a shared calendar. Nobody is being careless — each system is reasonable on its own. But the job exists in all four at once, and there is no single place that says where it actually is.

Ask any sign shop owner what is holding up a specific job and watch what happens. The answer takes three phone calls, because the answer is genuinely not written down anywhere.

The permit is the long pole, and it is not on the schedule

Permitting is the part of the sign business that most software ignores completely, and it is usually the longest and least predictable stretch of the job.

Every municipality has its own sign ordinance. One caps square footage by storefront width. One prohibits internal illumination in a historic district. One wants a sealed drawing, one wants a landlord letter, one wants photos of the existing conditions. Review times range from a week to two months, and the same city can be fast in the spring and slow in the fall. A rejection often comes back not as a no but as a reduction, which means the artwork the customer approved is now the wrong size.

Treating this as a single status field on a job — “permit pending” — throws away everything useful. What is worth building is a real record:

• A jurisdiction library holding what each city actually requires, what it has rejected you for before, and its realistic review window, so the person preparing a submittal is not rediscovering it.
• Applications tracked per sign rather than per job, because a multi-sign site can have one element approved and another kicked back.
• Documents attached to the application — drawings, landlord authorization, site photos, the fee receipt — instead of scattered across a drive and an inbox.
• Follow-up dates that surface on their own, since most permit delay is not the city being slow but nobody calling to check on week four.
• A link between permit outcome and artwork version, so a size reduction forces the drawing and the fabrication order to be revised rather than quietly diverging.
• Permit duration recorded per jurisdiction over time, which turns your quoted lead times from a guess into an average you can defend.

The operational consequence of not tracking this well is specific and expensive. The shop starts fabricating on the assumption the permit will land, the permit comes back reduced, and you have material cut for a sign that cannot be installed. The alternative failure is just as costly: the shop waits for certainty that never gets communicated, and the queue sits idle while a job that was approved two weeks ago goes unnoticed.

Proofs, revisions, and the version the shop actually built

The design side of a sign company has a problem that print shops and agencies share and that almost nothing handles well: the artwork changes, and the change has to reach everyone who depends on it.

A proof goes out. The customer wants the logo bigger. A second proof goes out. The customer forwards it to their landlord, who wants a different color. A third proof goes out and gets a thumbs-up in a reply to the second email. Now there are three files, one approval, and an ambiguous chain — and the shop is going to pull whatever is newest in the job folder, which may or may not be right.

The fix is to make approval a structured event rather than a message. Each proof is a version. Each version is sent from the system. The approval attaches to the exact file the customer saw, with a date and a name. The production order can only reference an approved version. That single constraint eliminates the most expensive mistake a sign shop makes, which is fabricating the wrong thing correctly.

There is a commercial benefit alongside the operational one. When revision rounds are counted automatically, you can see which customers routinely take six rounds and whether your pricing reflects it. Most shops quote as though every job takes two. Some take eight, and nobody bills for the difference because nobody counted.

The shop floor is a queue with real constraints

Fabrication is where a sign company's capacity actually lives, and it is rarely visible as a number. The work is genuinely mixed — a channel letter set, a monument sign, a set of vehicle wraps, and a hundred yard signs are all in the building at once, and they compete for different resources.

The router, the printer, the plotter, the paint booth, and the welder are separate constraints. A job might be waiting on aluminum that has not arrived, or on an LED module on backorder, or simply on a person. Scheduling by due date alone ignores all of that, which is why jobs promised for the same week routinely collide.

What makes the queue legible is modeling the stages a job passes through and what each one needs:

• Production stages tracked per job — design, permit, material ordered, fabrication, paint or finish, wiring, staging, install — so "where is it" has an answer without a phone call.
• Material requirements generated from the approved drawing rather than assembled by hand, including substrate, LEDs, power supplies, hardware, and paint.
• Purchase orders tied to the job, so a backordered component shows up as a job at risk instead of a surprise on install day.
• Machine and station capacity visible, since a week with three router-heavy jobs is not the same as a week with three vinyl jobs.
• Shop labor recorded against the job, which is the only way to know whether a sign type you quote by feel is actually profitable.
• Staging and completion confirmed before the install is scheduled, so a crew never rolls out to hang something that is still in paint.

Job costing in a sign shop is unusually revealing when you finally get it. Shops that measure it often find that the small, high-volume work carries the business while the large, prestigious installs run thin once permit labor, revision rounds, and crane time are counted honestly. That is the same argument laid out in job costing software for small contractors.

Installation, survey, and the site that was not ready

The install is where the accumulated assumptions of the previous three stages get tested at once. The crew arrives with the sign, the truck, and the crew size the office estimated, and finds that the wall is brick rather than EIFS, the electrical stub is twenty feet from where the sign goes, or the parking lot cannot take the lift.

Almost all of that is knowable earlier. The site survey — the visit someone made weeks ago to measure the storefront and photograph the wall — usually captured it. The problem is that the survey lives as photos on a phone and notes on a form, and it never reaches the crew or the estimator in a form they can act on.

Making the survey a structured part of the job record changes what the install can assume: mounting surface, height, power availability and distance, access constraints, whether a lift or crane is needed, and whether traffic control applies. The crew leaves with a work order that reflects the actual site rather than a hopeful one, and the estimator prices lift rental before it becomes an unbilled cost. The dispatch half of this is common to every trade that sends crews out, and is covered in field service scheduling software for small companies.

The service book nobody is billing properly

Every sign a company installs becomes a maintenance liability and a maintenance opportunity. LEDs fail. Power supplies burn out. A face cracks in a storm. A cabinet needs relamping. For shops with a few hundred signs in the field, this can be a real recurring revenue line, and it is usually the least organized part of the business.

The reason is that service depends on knowing what you installed. When a customer calls about a sign that is half dark, the useful questions are what modules are in it, what power supply, when it went up, whether it is still under warranty, and whether this is the third failure on the same cabinet. If that history is not attached to the sign, the answer is a truck roll to go and look.

• An asset record per installed sign, carrying its location, components, install date, photos, and the original job it came from.
• Warranty terms tracked per sign, so a service call is billed or absorbed on purpose rather than by whoever answers the phone.
• Service history against the asset, which turns a pattern of repeat failures into either a supplier conversation or a design change.
• Scheduled maintenance for customers on a contract, including lighting checks and cleaning, generated rather than remembered.
• Multi-site customers viewable as a portfolio, since a franchise or retail chain wants to see all of their locations at once, not one ticket at a time.

Why the packaged options frustrate people

There are real sign-industry products, and plenty of shops run on them without complaint. The frustrations that push owners toward building something are consistent:

• Permitting is either absent or a single status field, which means the longest phase of the job is managed in a spreadsheet beside the software.
• Proof approval is handled by email, so version control depends on discipline rather than the system.
• Estimating assumes one sign per job, which breaks immediately on a multi-sign site or a rollout across twenty locations.
• Installed signs are not tracked as assets, so the service side has no history to work from.
• Production scheduling is a due-date list rather than a model of the stations and materials a job actually needs.
• National account work — the same sign package at fifty sites, each with its own survey, permit, and date — has no structure at all.

The honest framing is that custom is not automatically the right answer. A shop doing mostly banners, vinyl, and vehicle graphics on short turnarounds should buy something off the shelf and get back to work. The case for building gets strong when permitted electrical signs, multi-site rollouts, and a service book all run at the same time, because that combination is exactly what packaged products handle by making you keep three spreadsheets beside them. That test is the subject of custom software versus off-the-shelf.

What this connects to

A system for a sign company earns its keep by joining things that are currently separate:

• Accounting, so deposits, progress billing, supplier bills, and service invoices post without being retyped into a second system.
• Supplier ordering, so a bill of materials produced from the approved drawing becomes a purchase order with the same part numbers.
• A customer portal where a property manager or franchise owner can see proof versions, permit status, and install dates without calling.
• The design files themselves, so the approved artwork and the production order point at the same version rather than at a folder.
• Payroll and shop labor, so hours land against the job that consumed them instead of into a weekly total.

The accounting link is worth building properly rather than bolting on. A sign company generates deposits, progress payments, retainage on commercial work, supplier bills per job, and a steady trickle of small service invoices, and hand keying all of that is both the most repetitive job in the office and the place a quiet error repeats for months. That is what a QuickBooks integration is meant to remove.

Built around how your operation actually runs

Brad Walker has spent more than twenty years building operational software, working with contractors and fabrication-driven businesses from his base in Wake Forest, NC. Sign work always starts with the same questions: how does an approved proof become a production order, who owns the permit and what happens when it comes back reduced, what does the crew know before they leave the shop, and what do you know about a sign two years after it went up. The answers decide what gets built and what gets left alone.

Engagements are fixed price, with the scope agreed before development starts. You know what you are getting, what it costs, and when your shop and your crews will have it.

Frequently asked questions

If nobody can tell you where a job is without making three phone calls, or the shop has ever built the wrong version of an approved proof, that is a fixable systems problem. Start the conversation. The first step is a discovery call to map how a proof becomes a permit, a fabrication order, and an install in your business today, and where it is costing you.