# Detailguild

*/Startups/Detailguild*

## Startup Overview

This platform serves frontend engineering and design teams by automatically verifying coded UI builds directly against source Figma design tokens. It eliminates the manual back-and-forth of visual QA, catching unapproved layout shifts, typography mismatches, and incorrect spacing values before code reaches staging.

Where legacy handoff utilities like Zeplin only document static specifications, and visual testing suites like Percy only flag regressions against prior code snapshots, this system enforces absolute design fidelity against the creative source of truth. It operates fully autonomously by deploying natively inside existing continuous integration workflows. Every code commit triggers an inspection of the compiled frontend components, instantly failing builds that violate the canonical Figma tokens without requiring human intervention.

## Startup Founding Hypothesis

**Approach**: that verifies frontend builds against Figma design tokens
**Competitors**:
- [Zeplin](/Competitors/Zeplin)
- [Percy](/Competitors/Percy)
- [Manual visual QA](/Competitors/Manual_visual_QA)
**Differentiator2x2**: fully autonomous and deployed natively inside existing continuous integration workflows

## Startup Solution Coordinate

**Solution**: [Design Token Verifier](/Agents/Design_Token_Verifier)

## Startup Position2x2

```mermaid
quadrantChart
title Visual QA & Design Verification
x-axis Separate Platform --> Native CI Integration
y-axis Manual Verification --> Fully Autonomous
quadrant-1 Continuous Verification
quadrant-2 Standalone Automation
quadrant-3 Manual Handoff
quadrant-4 CI-Integrated Diffing
Manual visual QA: [0.1, 0.1]
Zeplin: [0.25, 0.3]
Percy: [0.8, 0.45]
Detailguild: [0.9, 0.9]
```

## Startup Offer

**Proof**:
- Targeting a 90% reduction in manual UI review cycles for component library maintainers.
- Aiming to flag 99% of rogue hardcoded hex values and padding overrides before they merge into the main branch.
- Intended to complete parallel DOM-to-token verification in under 90 seconds per build.
**Tiers**:
- Name: Solo Project · Price: ~$30–$60/mo · Inclusions: 1 active repository, up to 500 CI build verifications per month, and standard Figma token synchronization.
- Name: Engineering Team · Price: ~$150–$300/mo · Inclusions: Up to 10 active repositories, 5,000 build verifications per month, automated pull request commenting, and custom token nomenclature mapping.
- Name: Scale · Price: custom: ~$12k–$25k/yr · Inclusions: Unlimited repositories and builds, intended self-hosted CI runner support, and dedicated configuration assistance.
**Guarantee**: If Detailguild approves a pull request that explicitly violates a published Figma design token and causes a production visual regression, we refund that month's service fee.
**Business Function**: ProvideService
**Objection Handlers**:
- Objection: Designers constantly tweak Figma files, breaking our builds. Rebuttal: Detailguild only validates against explicitly published Figma token libraries, completely isolating your CI from work-in-progress canvas edits.
- Objection: Snapshot testing already catches visual changes. Rebuttal: Snapshots only tell you pixels changed; Detailguild explicitly flags when code deviates from the design system's source of truth.
- Objection: This will slow down our deployment pipeline. Rebuttal: The token verification analyzes the compiled CSS and DOM statically in parallel with your unit tests, designed to add zero net blocking time to your pipeline.
- Objection: We use proprietary variable names that don't match Figma standard exports. Rebuttal: The configuration file supports explicit alias mapping, tying your internal code nomenclature directly to the design tokens.
**Pricing Architecture**: Tiered
**Agent Checkout Support**:
- agentic-commerce-protocol

## Startup Brand

**Voice**: Authoritative developer documentation register marked by exacting brevity.
**Tagline**: Stop frontend design drift before the code merges.
**Icon Concept**: caliper
**Palette Intent**: electric-signal
**Visual Identity**: The visual identity contrasts deep terminal black with bright neon syntax-highlighting green, using monospaced typography and precise pixel-grid layouts to evoke continuous integration environments.
**Archetype Reference**: the-ruler

## Startup Buyer Chain

**Chain**: Detailguild → Engineering Manager → Frontend Developer
**Gtm Motion**: Acquires individual frontend developers through a free-tier CI pipeline integration that runs basic token checks on individual pull requests. Expands to paid organizational tiers when engineering directors mandate cross-repository validation rules and centralized reporting for team-wide design system compliance.
**Agent Channel**: Intended for listing in the Model Context Protocol (MCP) tool registry and as a GitHub Copilot Extension, enabling autonomous developer agents to discover and execute Figma design token validation during automated build routines.
**Primary Channel**: Organic discovery in the GitHub Marketplace and npm registry when frontend engineers search for CI actions related to Figma tokens, design systems, or visual regression testing.

## Startup Customer Journey

```mermaid
flowchart LR; A[GitHub Marketplace] --> B[CI Pipeline Integration]; B --> C[Pull Request Token Check]; C --> D[Rogue Hex Value Flag]; D --> E[Figma Token Synchronization]; E --> F[Cross-Repository Validation Rules]; F --> G[Centralized Compliance Report];
```

## Startup Proof Points

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**Pilot Goals**:
- 14-day design system integration pilot to demonstrate parallel DOM-to-token verification running alongside existing unit tests with zero net pipeline delay.
- 30-day staging rollout with a scaling frontend team to intercept and document rogue hardcoded padding overrides before they merge into the main branch.
**Target Metrics**:
- Target: 90% reduction in manual UI review cycles for component library maintainers.
- Aim: 99% catch rate of rogue hardcoded hex values before main branch merges.
- Target: 90 seconds maximum parallel DOM-to-token verification time per build.
- Aim: 0 added net blocking minutes to existing deployment pipelines.
**Target Case Studies**:
- Mid-market B2B SaaS frontend team deploying a new component library, moving from manual design QA to automated pull request token verification.
- Consumer fintech design system maintainers, eliminating visual regressions caused by hardcoded hex values and padding overrides during rapid scaling.
- Enterprise e-commerce platform migrating to strict design token architectures, mapping custom internal code nomenclature directly to published Figma libraries without slowing CI pipelines.
**Testimonial Targets**:
- Lead Frontend Engineer expressing relief that snapshot testing fatigue is gone because PR comments now explicitly identify token deviations rather than just changed pixels.
- Design System Manager validating that Figma canvas edits no longer break production builds because the CI strictly reads from explicitly published token libraries.
- Staff Software Engineer confirming that custom token nomenclature mapping allowed their legacy codebase to adopt strict design compliance without renaming internal variables.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Figma restricts access to its design token API or radically changes the schema, breaking the core verification pipeline. · Mitigation Status: unmitigated
- Severity: high · Description: Visual verification processes add excessive latency to continuous integration pipelines, prompting engineering teams to disable the tool. · Mitigation Status: in-progress
- Severity: moderate · Description: False positives on dynamic components and complex states degrade developer trust and lead to alert fatigue. · Mitigation Status: in-progress
- Severity: moderate · Description: Incumbents like Percy or Chromatic integrate native Figma token parsing, neutralizing the primary differentiation. · Mitigation Status: unmitigated

## Startup Competitors

- [Zeplin](/Competitors/Zeplin) — Design Handoff
- [Percy](/Competitors/Percy) — Visual Testing
- [Manual Visual QA](/Competitors/Manual_Visual_QA) — Status Quo
- [Chromatic](/Competitors/Chromatic) — UI Review
- [Applitools](/Competitors/Applitools) — Incumbent

## Startup Solution Stack

- [Design Compliance Service](/Services/Design_Compliance_Service) — Service-as-Software
- [Token Verification Agent](/Agents/Token_Verification_Agent) — Agent
- [UI Inspection Worker](/Agents/UI_Inspection_Worker) — Agent
- [DOM Extraction Engine](/Software/DOM_Extraction_Engine) — Software
- [Figma Sync API](/Software/Figma_Sync_API) — Software

## Startup Story Brand

**Hero**:
- **Need**: to serve as the reliable bridge between design intent and shipped code
- **Want**: to prevent design drift and hardcoded overrides in the production codebase
- **Identity**: the lead frontend engineer managing a design system
**Plan**:
- Step: Publish tokens · Detail: Release a versioned Figma token library to establish the source of truth for your design system.
- Step: Review reports · Detail: Check the automated pull request comments for specific token deviations or hardcoded padding overrides.
- Step: Merge code · Detail: Approve the build once the verification engine confirms 100% alignment with the design system.
**Guide**:
- **Empathy**: Production-ready components are won in the pull request — but visual regressions often hide behind passing unit tests.
**Problem**:
- **Villain**: manual visual QA
- **External**: CSS regressions and rogue hex values slip into the main branch because Percy snapshots only flag change, not design system violations
- **Internal**: You feel like a pixel-policing bottleneck instead of an engineer building scalable architecture
- **Philosophical**: Why should engineering teams accept guesswork in UI implementation when design tokens provide a mathematical source of truth?
**Success**: Every merge matches the design system perfectly, and manual visual reviews are eliminated from the engineering workflow.
**One Liner**: Manual visual QA costs engineering teams hours of design drift. Detailguild verifies frontend builds against Figma tokens so code always matches the design system.
**Positioning**:
- **So That**: frontend builds align perfectly with published Figma design tokens
- **Unlike**: Zeplin or Percy snapshot testing
- **For Whom**: lead frontend engineers managing design systems
- **Category**: Automated design token verification
**Call To Action**:
- **Direct**: Verify build
- **Transitional**: Download sample validation report
**Failure Stakes**:
- Production visual regressions
- Fragmented design system adoption
- Manual UI review bottlenecks
**Transformation**:
- **To**: the engineer who automates UI consistency across every repository
- **From**: a developer fixing broken padding in CSS files
**Controlling Idea**: Design systems are code, and code must be verified by CI automation.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Manual visual QA costs engineering teams hours of design drift. Detailguild verifies frontend builds against Figma tokens so code always matches the design system.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: ea81d97a1dfd7d6c

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Automated design token verification for lead frontend engineers managing design systems. Unlike Zeplin or Percy snapshot testing — frontend builds align perfectly with published Figma design tokens.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: 7c4bddae8fca7df3

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: CSS regressions and rogue hex values slip into the main branch because Percy snapshots only flag change, not design system violations
Solution: Manual visual QA costs engineering teams hours of design drift. Detailguild verifies frontend builds against Figma tokens so code always matches the design system.
Customer: lead frontend engineers managing design systems
Unlike: Zeplin or Percy snapshot testing
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 011f6611c1031c1d

## Startup Token M E D D P I C C

**Pain**: CSS regressions and rogue hex values slip into the main branch because Percy snapshots only flag change, not design system violations
**Metrics**: Target: Every merge matches the design system perfectly, and manual visual reviews are eliminated from the engineering workflow.
**Rendered**: Pain: CSS regressions and rogue hex values slip into the main branch because Percy snapshots only flag change, not design system violations
Economic buyer: Engineering Manager
Metrics: Target: Every merge matches the design system perfectly, and manual visual reviews are eliminated from the engineering workflow.
Competition: Zeplin or Percy snapshot testing
**Mechanism**: spine-derived-v1
**Competition**: Zeplin or Percy snapshot testing
**Economic Buyer**: Engineering Manager
**Vocab Fingerprint**: cdd158541dedfe70

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Automated design token verification for lead frontend engineers managing design systems

lead frontend engineers managing design systems — CSS regressions and rogue hex values slip into the main branch because Percy snapshots only flag change, not design system violations Manual visual QA costs engineering teams hours of design drift. Detailguild verifies frontend builds against Figma tokens so code always matches the design system.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: b921b75951d6f773

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Automated design token verification. Manual visual QA costs engineering teams hours of design drift. Detailguild verifies frontend builds against Figma tokens so code always matches the design system. Serves lead frontend engineers managing design systems.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: 4d44d406f03041b3

## Neighborhood

### Candidate solutions

- [Source Heavy Plate Welders](/Problems/Source_Heavy_Plate_Welders) — candidate solution for · Problems

### Composed of

- [Bead Profile Validation Service](/Services/Bead_Profile_Validation_Service) — composes · Services
- [Weld Joint Extraction API](/Software/Weld_Joint_Extraction_API) — composes · Software
- [Torch Kinematics Vision Engine](/Software/Torch_Kinematics_Vision_Engine) — composes · Software
- [Structural Code Parser Agent](/Agents/Structural_Code_Parser_Agent) — composes · Agents
- [Visual Defect Scoring Agent](/Agents/Visual_Defect_Scoring_Agent) — composes · Agents
- [Bead Profile Agent](/Agents/Bead_Profile_Agent) — composes · Agents
- [Torch Angle Engine](/Software/Torch_Angle_Engine) — composes · Software
- [Code Adherence Agent](/Agents/Code_Adherence_Agent) — composes · Agents
- [Weld Tolerance Service](/Services/Weld_Tolerance_Service) — composes · Services
- [Joint Geometry API](/Software/Joint_Geometry_API) — composes · Software
- [Figma Sync API](/Software/Figma_Sync_API) — composes · Software
- [Token Verification Agent](/Agents/Token_Verification_Agent) — composes · Agents
- [Design Compliance Service](/Services/Design_Compliance_Service) — composes · Services
- [UI Inspection Worker](/Agents/UI_Inspection_Worker) — composes · Agents
- [DOM Extraction Engine](/Software/DOM_Extraction_Engine) — composes · Software

### What it offers

- [Detailguild Weld Validator](/Services/Detailguild_Weld_Validator) — offers · Services
- [Weld Integrity Screen](/Services/Weld_Integrity_Screen) — offers · Services
- [Design Token Verifier](/Agents/Design_Token_Verifier) — offers · Agents

### Embodies

- [Service-as-Software](/Theses/Service-as-Software) — embodies · Theses
- [Agent](/Theses/Agent) — embodies · Theses

### Who it serves

- [Bulk Material Handling & Conveyance OEMs](/CompanyTypes/Bulk_Material_Handling_&_Conveyance_OEMs) — serves · CompanyTypes

### Competitors

- [Indeed Sponsored Jobs](/Competitors/Indeed_Sponsored_Jobs) — competes with · Competitors
- [LinkedIn Recruiter](/Competitors/LinkedIn_Recruiter) — competes with · Competitors
- [Onsite Coupon Testing](/Competitors/Onsite_Coupon_Testing) — competes with · Competitors
- [Onsite Coupon Tests](/Competitors/Onsite_Coupon_Tests) — competes with · Competitors
- [Tradesmen International](/Competitors/Tradesmen_International) — competes with · Competitors
- [Workday Recruiting](/Competitors/Workday_Recruiting) — competes with · Competitors
- [Specialized Trade Recruiters](/Competitors/Specialized_Trade_Recruiters) — competes with · Competitors
- [Percy](/Competitors/Percy) — competes with · Competitors
- [Zeplin](/Competitors/Zeplin) — competes with · Competitors
- [Applitools](/Competitors/Applitools) — competes with · Competitors
- [Chromatic](/Competitors/Chromatic) — competes with · Competitors
- [Manual Visual QA](/Competitors/Manual_Visual_QA) — competes with · Competitors

### Similar Startups

- [Visionhaven](/Startups/Visionhaven) — similar · Startups
- [Glowmill](/Startups/Glowmill) — similar · Startups
- [Buttonpark](/Startups/Buttonpark) — similar · Startups
- [Visera](/Startups/Visera) — similar · Startups
- [Figma Variables](/Startups/Figma_Variables) — similar · Startups
- [Brandorb](/Startups/Brandorb) — similar · Startups
- [Designerloom](/Startups/Designerloom) — similar · Startups
- [Defectiveframe](/Startups/Defectiveframe) — similar · Startups
- [Tessellateslate](/Startups/Tessellateslate) — similar · Startups
- [Defectoff](/Startups/Defectoff) — similar · Startups
- [Mold](/Startups/Mold) — similar · Startups
- [Anchevision](/Startups/Anchevision) — similar · Startups
- [Finalatelier](/Startups/Finalatelier) — similar · Startups
- [Fidelityvision](/Startups/Fidelityvision) — similar · Startups
- [Bloomlayout](/Startups/Bloomlayout) — similar · Startups
- [Canvashybrid](/Startups/Canvashybrid) — similar · Startups
- [Artisanlens](/Startups/Artisanlens) — similar · Startups
- [Qualab](/Startups/Qualab) — similar · Startups
- [Accespoke](/Startups/Accespoke) — similar · Startups

### Similar Customers

- [Product Design Managers](/Customers/Product_Design_Managers) — similar · Customers