ClearStamp — pre-flight permit screen for sign companies

1. One-liner

Reads a sign drawing and catches the zoning and submittal errors that get permits rejected — before you file.

2. Trend signal — why now?

Sign companies bleed weeks on permit rejections, and the rejections are almost never about craftsmanship — they’re paperwork and zoning-math nits caught too late. The industry says so out loud: “Discovering a zoning conflict after the permit drawings are complete is one of the most expensive mistakes a sign company can make,” and “if zoning requirements are only checked after the design is finished, your chances of passing the first-round review drop sharply” (thesignpack.com, 2026). A standard San Diego sign permit runs 2–4 weeks, but “stretches to 12 weeks or more for applications requiring revisions” (permitplace.com). One quote in the wild: a restaurant owner “missed her planned opening date by three weeks because her sign wasn’t ready… three weeks of lost revenue she’ll never recover.”

What changed in the last 12 months is the tech, not the pain. Multimodal LLMs crossed the line on reading drawings: in a 2026 benchmark, “Gemini 2.5 Pro demonstrated nearly perfect extraction accuracy” for parsing dimensions and tolerances from engineering drawings, and CV pipelines hit “85–92% accuracy for simple building geometry” (businesswaretech.com, llamaindex.ai). A sign drawing is far simpler than an MEP set — a cabinet, dimensions, a façade, a setback. Reading it and checking it against a municipal sign ordinance is now a tractable problem.

And money already moves here. The solar industry proved the exact playbook one vertical over: Wattmonk’s PlanSetIQ sells a pre-submission AHJ check “trained on 125K+ approved submissions across 12.5K+ AHJs,” and installers pay because each rejection costs $2,000–$5,000 in rework. In signs, the equivalent spend today is human permit-expediting shops (Stratus, Tyko, National Sign Team, PermitPlace) and an early lookup tool, PermitPal (“40+ sign companies, 7,000+ cities”). The category is being colonized vertical by vertical right now — signs is wide open for the checking layer, not just the lookup layer.

Provenance:

• Signal 1 (Demand): Sign companies lose weeks and eat rejection rework because zoning/submittal errors are caught after design — repeated in industry writeups — https://www.thesignpack.com/how-to-fix-the-sign-permit-drawing-bottleneck/ — 2026-06-03
• Signal 2 (Feasibility): Multimodal LLMs now read drawing dimensions/layouts with near-perfect/85–92% accuracy — https://www.businesswaretech.com/blog/benchmarking-ai-on-tables-and-engineering-drawings-results-findings — 2026-06-03
• Signal 3 (Economic): The pre-submission permit-check model already monetizes one vertical over (solar PlanSetIQ at $2–5K/rejection avoided) and signs has paid expediters + an early lookup tool — https://www.energyscaperenewables.com/post/solar-pe-stamp-turnaround/ , https://permitpal.io/ — 2026-06-03 Category: Tech-unlock

3. The opportunity

The pain is a moment: the drawing is done, the crew is half-scheduled, and the package is about to go to the city. Right now nobody checks it against the actual ordinance and the actual submittal checklist for that jurisdiction. So 15–30% of the time it bounces — wrong setback, façade-area over the cap for that zone, missing landlord letter, missing title-block field, outdated form — and the company loses 2–4 weeks plus rework time per bounce.

Two kinds of incumbents exist, and both leave the wedge open:

• Permit expediters (Stratus, Tyko, National Sign Team) are people. They’re expensive, slow, and don’t scale to a 40-store rollout where you need 40 jurisdictions checked this week. They’re a service, not a button.
• PermitPal does lookup — “what are the sign rules in city X?” — returning wall/monument/window/EMC rules with citations. Genuinely useful, and a real competitor. But lookup is not the same job as checking your specific drawing. PermitPal tells you the speed limit; ClearStamp tells you your truck is 8 inches too tall for the bridge you’re about to drive under.

ClearStamp owns the pre-flight QC moment: ingest the proposed drawing + site survey photos + the address, pull that jurisdiction’s sign code and submittal checklist, and return a redline — pass/fail per rule, with the exact failing dimension and the citation. That’s the thing that saves the $2–5K bounce, and it’s the thing nobody in signs sells yet.

4. Target market

• Primary customer: Operations / permitting managers at mid-size custom sign companies (10–150 employees) doing multi-location and franchise rollout work — the segment that hits a new AHJ on every single job and feels rejection pain at volume. Secondary: national signage program managers and franchisors’ facilities teams.
• Why they buy: In their words — “the most common reason for delays is submitting an incomplete or inaccurate application package,” and “a missing landlord approval, an incorrect measurement on a site plan, or a forgotten local form can get your entire application rejected.” They don’t want a research project; they want a green light before they file.
• Rough TAM reasoning: ISA represents ~2,300 member companies; the broader US sign/graphics industry is tens of thousands of firms. The reachable beachhead is the few thousand companies that do permitted on-premise signage at multi-site scale. A few hundred paying $300–1,500/mo is a clean $1M–$3M business; this does not need the whole industry.
• Why now for them: NEC/IFC/IBC editions and local sign ordinances keep churning (e.g., 2026 NEC adoption rolling out by state), franchise rebrands and new-store rollouts are active, and labor for in-house permitting clerks is scarce and expensive. The drawing-reading tech only became reliable in the last year.

5. Product sketch (MVP)

• Upload a sign drawing (PDF/image) + site survey photos + the install address; ClearStamp resolves the AHJ.
• Pulls that jurisdiction’s on-premise sign ordinance + submittal checklist into a structured ruleset (wall/monument/window/EMC area caps, height, setback, illumination limits, required forms).
• Redline report: per-rule PASS / FAIL / NEEDS-HUMAN, each flag tied to the failing dimension and the ordinance citation — verify in one click.
• Façade-area and setback math computed from the drawing + photo measurements, checked against the zone’s cap.
• Submittal-completeness checklist: landlord letter, title-block fields, engineering stamp (where wind-load applies, e.g. Florida 1609), correct local form version — flag what’s missing before filing.
• Multi-site batch mode: drop 40 locations, get 40 redlines ranked by rejection risk.
• “Confidence + cite” UI on every call so a human reviewer can trust or override — never a silent auto-approve.

6. AI angle — what’s load-bearing

Remove the AI and there is no product — just a PDF and a 60-page municipal code. Two AI jobs carry it: (1) vision — reading the drawing and site photos to extract real dimensions, sign type, and façade geometry, which only became reliable with 2025–26 multimodal models; (2) retrieval + reasoning — mapping a specific extracted measurement to the specific clause of a specific city’s ordinance and deciding pass/fail with a citation. A human paralegal can do this in 30–60 minutes per site; the product collapses it to minutes and makes the 40-site batch tractable. The accumulating moat is the structured-ruleset-per-AHJ library and the log of which flags actually predicted real rejections — that data is the asset.

7. Localization angle (if any)

N/A — this is a US-first play. The wedge IS hyper-local (every US municipality has its own sign ordinance), but the market is US. There’s a future international cut (UK/Australia planning consent for signage), but US sign-permit fragmentation is the deepest, best-documented, highest-spend version of the problem and the right beachhead. Don’t dilute v1 by chasing geographies.

8. Business model — path to $1M–$5M ARR

• Pricing: Tiered SaaS. Solo/small shop $149/mo (limited checks); growth $499/mo; rollout/enterprise $1,500/mo for multi-site batch + API. Plus optional per-site overage credits.
• ACV: Blended ~$6,000–$9,000/yr; rollout customers materially higher.
• Rough math to $1M ARR: ~140 customers at a $600/mo blended average × 12 = ~$1M. Entirely reachable inside the ISA membership + franchise-program world.
• Rough math to $5M ARR: ~600 customers blended, OR land 30–50 multi-site/national-program accounts at $1,500–4,000/mo and fill the long tail with the $149–499 tiers. The expediter spend it displaces is far larger than the subscription, so pricing has headroom.
• Expansion path: per-site usage as rollout volume grows; add fire/EV/HVAC sign-adjacent permit types; sell the AHJ-ruleset API to the very expediters it competes with.

9. Go-to-market wedge — first 100 customers

• ISA Sign Expo (2026/27) + the ISA member directory. This is the one room where every target buyer physically shows up. Scrape/segment the ~2,300-member directory for multi-location shops; book demos against a live rejection-saved number.
• Loom-the-rejection cold outreach. Pull recent rejected sign-permit applications from public AHJ permit portals (many post plan-check comments publicly), run ClearStamp on that exact drawing, and send the shop a 90-second video: “your job that bounced last month — here’s the flag we’d have caught.” Few outreaches are more visceral than showing someone their own avoidable loss.
• Wedge against PermitPal’s gap, not its strength. Target shops already sold on “we need software for permitting” — they’ve felt the pain enough to buy lookup. Pitch the checking layer they still don’t have. Co-exist or displace.
• Franchisor / national-program partnerships. A handful of franchise facilities teams mandate the sign vendors for hundreds of locations. Land 2–3 programs and you’ve seeded dozens of sign-company users downstream.
• r/signmaking, Signs101 forum, and ISA regional chapters for credibility and inbound — secondary, not the engine.

10. Build complexity — justification

Medium. The vision extraction and ordinance retrieval run on off-the-shelf multimodal models + a RAG layer — no custom model training for v1. The real work is operational: building and maintaining the structured ruleset for each AHJ (start with the 50–100 jurisdictions where rollout volume concentrates, expand on demand) and tuning the redline to a precision the customer trusts. A small team ships a credible v1 covering a few high-volume metros in ~3–4 months; national coverage is an ongoing data operation, not a v1 blocker.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Reads public ordinances + customer’s own drawings. No regulated practice; it advises, the human files.
Ethical — no harm / dark patterns	✅	Reduces wasted resubmittals; “needs-human” + citations prevent false confidence.
Market exists (evidence above)	✅	Paid expediters, PlanSetIQ (solar), PermitPal (signs) all prove spend.
1–5 person team can build this	✅	Off-the-shelf models + RAG + a ruleset ops process.
Launchable with <$50K / ₹40L	✅	Inference + scraping/structuring cost; no capex.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	16/20	$2–5K per rejection, weeks of delay, lost store-opening revenue. Real, recurring, money-on-the-table. Not quite “daily hair-on-fire” — it’s per-job, and shops have lived with it.
Demand evidence	15	11/15	Strong adjacent proof (PlanSetIQ paid in solar; PermitPal paid in signs; live expediter market) and loud industry complaints. Docked because direct evidence of demand for the checking layer (vs lookup) in signs is inferred, not yet observed.
Build feasibility	15	11/15	Vision + RAG are off-the-shelf; the AHJ-ruleset library is real, grinding ops work and the accuracy bar for trust is high.
Distribution clarity	15	11/15	ISA directory + show + public rejected-permit Looms is a concrete, named playbook. Conversion still unproven.
Revenue mechanics	15	11/15	Pricing benchmarks against expediter spend and PlanSetIQ; ACV and customer counts to $1M are modest and credible.
Time to first revenue	10	7/10	Pilot-able in weeks once a couple of metros are covered; needs a short ruleset build before the first paid check.
Defensibility	10	5/10	Soft moat: accumulating AHJ rulesets + rejection-prediction data + workflow lock-in. But PermitPal is well-placed to add checking, and the pattern is being cloned vertical-by-vertical. Speed and data depth are the only moats.
Total	100	72/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · domain-expertise-required — needs someone who can wrangle multimodal extraction reliability AND someone who actually understands sign permitting (ex-permitting manager or expediter as a co-founder/advisor is close to mandatory).

Key assumptions to validate (3–5)

1. Assumption: Sign companies will pay for checking their own drawing, not just looking up rules (i.e., ClearStamp is a different wallet than PermitPal). How to test: 20 discovery calls with multi-site sign permitting managers; show the redline demo; ask for a paid pilot commitment.
2. Assumption: Vision extraction on real-world sign drawings + phone site photos is accurate enough that the redline is trusted, not second-guessed. How to test: Run 50 historical drawings (with known approve/reject outcomes) through the pipeline; measure flag precision/recall against actual plan-check comments.
3. Assumption: A small set of high-volume AHJs (50–100) covers enough of a beachhead customer’s jobs to be worth paying for. How to test: Pull a pilot customer’s last 200 jobs, map jurisdictions, confirm the top-N coverage hits ≥70% of their volume.
4. Assumption: Public AHJ portals expose enough rejected-permit detail to power the Loom cold-outreach engine. How to test: Audit 5 target-metro portals for accessible plan-check comments.

Risk flags

1. Competitive / fast-follower risk: PermitPal already has the sign-company relationship and could bolt on drawing-checking. This is the single biggest risk — the moat is data depth and speed, not a defensible secret.
2. Accuracy-trust risk: One confidently-wrong PASS that leads to a rejection burns trust fast in a small, gossipy industry. The “needs-human + citation” design is a mitigation, not a cure.
3. Ruleset-maintenance treadmill: Ordinances change; coverage is a perpetual ops cost. Under-investing here quietly degrades the product.
4. Channel-conflict / buyer-substitution risk: Some shops will prefer to outsource the whole headache to a human expediter rather than run software in-house.

14. Structured verdict

Score:                  72/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder (multimodal/RAG) + sign-permitting domain co-founder or advisor
Time to revenue:        8–12 weeks (after a 2-metro ruleset build)
Capital to launch:      $15–35K (inference, data structuring, design partner pilots)
Top 3 assumptions to validate first:
  1. Sign companies pay for drawing-CHECKING, not just rule-LOOKUP — 20 discovery calls + paid-pilot ask
  2. Vision extraction precise enough to be trusted — 50 historical drawings vs known approve/reject outcomes
  3. Top 50–100 AHJs cover ≥70% of a beachhead customer's job volume — map a pilot's last 200 jobs
Kill criteria:
  - Abandon if <30% of 20 discovery calls will commit to a paid pilot after seeing the redline demo
  - Abandon if flag precision on the 50-drawing historical test is below ~85% (too many false flags = ignored product)
  - Abandon if PermitPal (or a funded entrant) ships equivalent drawing-checking before your v1 lands 10 paying customers

15. Next step — 1-week validation sprint

• Day 1–2: Build a throwaway demo — manually structure the sign ordinance for ONE high-volume metro, wire a multimodal model to extract dimensions from 5 real sign drawings, and produce a redline for each.
• Day 3–4: Pull 10 publicly-rejected sign-permit applications from that metro’s portal, run them through the demo, and record 90-second Looms showing the flag that would have caught each rejection. Cold-send to the shops that filed them + 15 multi-site sign companies from the ISA directory.
• Day 5: Decide go/no-go on a falsifiable bar: ≥4 of ~25 outreached shops book a call AND ≥1 verbally commits to a paid pilot. Below that, the checking-layer demand isn’t there yet — revisit when more AHJ data is cheap to assemble.