Client Build · Sign Fabrication
Aplos AI

One system from first inquiry to installed sign.

The Cube Signs, an Atlanta sign fabrication shop, was running on a template website, text messages, and memory. Every inquiry looked the same, every client update was typed by hand, and nothing showed the state of the pipeline. We replaced all of it with one system the owner runs himself.

How the shop was running before we built this

Custom signage is a quoting business: a storefront channel-letter job and a quick vinyl banner arrive through the same contact form, but one can be worth many times the other. The shop had no way to tell them apart, no pipeline, and no system for keeping clients informed while their sign moved through design, fabrication, permitting, and install.

Every lead equal

No qualification, no scoring

Inquiries arrived through a generic template-site contact form with no questions about project type, budget, or timeline. A high-value storefront job and a tire-kicker got the same follow-up, in whatever order they were noticed.

Typed by hand

Client updates on memory

Signs take weeks: design approval, fabrication, permits, install. Clients who wanted to know where their sign stood called or texted, and every answer was a manual message. Updates happened when the owner remembered, not when the status changed.

No pipeline

Jobs tracked in his head

There was no view of active jobs by stage, no dollar total on the pipeline, and no queue of new leads. Marketing had the same problem: a portfolio of finished work sat on a phone instead of feeding the website or social channels.

A lead-to-install system the owner configures himself

One application: a new marketing site feeding a scored lead queue, a project Kanban, automatic client updates on every status change, and a social composer for the shop's own work photos. Every setting the business might outgrow, from pipeline stages to scoring rules to message templates, is editable in a settings screen. No developer needed after handoff.

An inquiry moving through the system

  1. Capture

    The customer supplies project type, timeline and budget through the intake form.

  2. Prioritize

    Configured scoring rules place the inquiry in the owner's lead queue.

  3. Move the job

    The owner changes the project stage on the board as the work progresses.

  4. Update the customer

    The stage change triggers the configured customer message.

Simplified workflow diagram based on the delivered capabilities described below. It illustrates the handoffs, not a customer record or a measured outcome.
HOT / WARM / COLD

Lead Intake & Scoring

A public intake form asks what a sign buyer actually knows: project type, timeline, budget range. Every submission is scored automatically and lands in the lead queue as HOT, WARM, or COLD, so the owner works the storefront job before the banner inquiry. A honeypot field silently drops form spam, and the questions and scoring weights are editable in Settings.

Stack: Next.js form routes, configurable scoring rules in Supabase, honeypot spam filtering.

Visual pipeline + $ total

Leads Board & Project Kanban

New leads queue in their own board; accepted jobs become cards on a drag-and-drop Kanban that follows the shop's real stages from design through install. The dashboard shows a live dollar total for the pipeline and a live count of new leads. Moving a card is what triggers the client update, so keeping the board current and keeping clients informed became the same action.

Stack: Supabase (PostgreSQL) with row-level security, optimistic Kanban UI, live aggregate stats.

Status change → email

Automatic Client Updates

When a job changes stage, the customer gets told without anyone typing a message. Today that is email from a verified sending domain, and the completion email links straight to the shop's Google listing to ask for a review. WhatsApp is built in with six Meta-approved templates. The shop's number was registered with Meta on 9 November 2026, and WhatsApp sending starts once Meta finishes activating the account. Bounced addresses are suppressed automatically so the shop's sending reputation stays clean.

Stack: Resend with bounce-suppression webhook, Meta WhatsApp Cloud API, per-stage templates editable in Settings.

FB + IG from one pane

Social Composer

Finished signs are the shop's best marketing, so posting them had to be trivial: upload a photo, write a caption, publish to Facebook and Instagram from one screen. Every upload is re-encoded server-side to a format Instagram accepts, so phone photos post without mysterious failures. We staged twenty drafts from the shop's own portfolio. The shop has not started publishing from the composer yet.

Stack: Meta Graph API via OAuth, server-side image conversion with sharp, draft queue with one-click publish.

Replaced the template site

Marketing Website

A new site on the shop's own domain, built around a gallery of the shop's own work instead of stock photos (50 photos across six sign types as of November 2026, managed from Settings), a process section that sets expectations for how a custom sign actually gets made, and LocalBusiness structured data for Atlanta local search. The intake form is the site's front door, so the website and the lead system are one thing, not two.

Stack: Next.js static marketing pages, LocalBusiness JSON-LD, same app and domain as the dashboard.

No developer after handoff

Owner-Editable Settings

Branding, pipeline stages, notification templates, lead-scoring rules, and the intake form's own options are all editable from a settings screen, and changes flow through to the public form immediately. The business can rename a stage, reword a message, or reweight its scoring without calling anyone. That is what made the full handoff honest.

Stack: Config layer in Supabase read by both the dashboard and the public site, per-table row-level security.

Full stack
Next.js TypeScript Supabase PostgreSQL Resend WhatsApp Cloud API Meta Graph API Vercel

The workflow is useful beyond sign shops

This project connects an inquiry to a job record, an assigned stage, and customer updates. The same questions apply in other service businesses: who owns the next step, where the current status lives, and when a customer should hear from you.

This case study documents the delivered system. It does not establish a measured increase in revenue or prove that a particular industry is the best acquisition channel.

Explore a custom client portal or connect an existing workflow. Features, integration access, and handoff are agreed for each project.

The first 12 weeks, from the shop's own data

The system went live on the shop's own domain in August 2026, replacing the template site outright. The counts below come from its database, read on 9 November 2026, and cover 17 August to 9 November. They are totals only. No customer details are shown.

8

Inquiries through the new form

Each one scored on arrival: 6 HOT, 2 WARM. Five asked for the work as soon as possible. Budgets ran from under $500 up to the $2,000–$5,000 band.

4

Jobs tracked on the board

Three are marked complete. Moving a job to a new stage sends the customer that stage's update from the owner's own template. Three of the four jobs get their updates by email.

100%

Owned by the client

Code repository, database, hosting, domain, and every connected account were handed over. Fixed project price, no required monthly fees to Aplos, no dependence on us to operate it.

WhatsApp updates are not sending yet. The shop's business number was verified and registered with Meta on 9 November 2026. Sending waits on Meta to finish activating the account. Until then, customer updates go by email. The fourth job is set to WhatsApp, so its updates are waiting too.

What we cannot tell you yet. Nobody logged response times before the build, and the system does not record when the owner first replies to a lead. So there is no before-and-after response time on this page, and no count of quotes won back. Eight real inquiries are the honest number.

Client Build · Sign Fabrication

Running your shop on texts
and memory? Let's fix that.

We scope, build, and hand off custom software for service businesses. Fixed price, you own the code, and nothing is required after delivery. Book a free 30-minute audit call and we'll tell you exactly what we'd build for your workflow.

Book a free call