The system keeps records. Humans verify.
QA NOTE is the maintenance record and report system at the client boundary. From request intake through agent handoff, human verification, and monthly report publishing — the entire maintenance process becomes a record that can't be reconstructed anywhere else.
Why we exist
The time spent filing requests, retracing what happened, digging through inboxes at month's end — we eliminate every friction caused by missing records.
A world where "it's fixed" is a record, not a claim. Intake, agent fixes, human verification, published reports — we create that cycle.
Brand Position
QA NOTE is the maintenance record system that turns requests and reports at the client boundary into records for verification and billing. Our competitor is not another QA tool, but digging through the inbox at month's end.
Four values that run through the brand
We deliver complex problems in the most concise form. What a bug report needs is not a thousand words of explanation, but a single screenshot.
Every request, fix, and verification becomes a reconstructable record. Published reports never change — that's what makes them evidence.
QA is not a boring, cold task. The warmth of the tool melts the friction in team communication. Solid yet light.
Report the moment you discover a bug, right where you are. Without leaving the browser, without losing context.
Logo usage guidelines
Clear Space
Maintain at least 50% of the logo mark height as clear space around the logo. Minimum size: 24px digital, 8mm print. Do not overlay other graphic elements on the logo.
Color system
Primary — Warm Coral
Warm Coral
#E8624A
Key color. CTA, emphasis, brand signature.
Coral Hover
#D4553E
Hover/active state.
Coral Tint
#FFF0ED
Badge, background emphasis, icon background.
Coral Deep
#B8422E
Dark mode secondary, text link.
Neutral — Surface
Canvas
#F7F7F5
Page background
White
#FFFFFF
Card, container
Border
#EEEEEE
Divider, card border
Ink
#1A1A1A
Headline, body text
Semantic — Status
Open
#E8624A
Received (= key color)
In Progress
#C08A20
In progress
Resolved
#2D9D5A
Verified
Closed
#999999
Reported
The meaning of Warm Coral: QA is not a cold, mechanical task. Warm coral flips the image of QA with the surprise of "a dev tool that feels this warm?" Solid yet light, bold yet casual — we aim to be a tool that makes you think "let me give this a try."
Typography system
Geist / Pretendard
English: Geist (Vercel) — Korean: Pretendard. Both are variable fonts for consistent weight control.
Every fix on record, ready to bill.
The system keeps records. Humans verify
Intake right in the browser
A screenshot is worth a thousand words
From intake to report — your agent ships the fix, QA Note keeps the record.
QA NOTE v2.0 · Last updated 3 days ago
How we speak
We don't beat around the bush. We say 'maintenance records,' not 'innovative solution.'
File the issue. The system keeps the record.
Optimize your workflow with our innovative AI-powered QA automation solution.
We understand the pain of QA, but we don't dwell on it. Wit over humor.
How do I explain this bug? → Just capture it.
Bug reporting is really hard and painful work. We're here to help.
Instead of unverifiable claims like 'industry's only,' we prove with specific features.
Auto-collects console logs, network requests, and React component trees.
Maximize your team's productivity with the world's best QA tool.
Closing the gap between "it's fixed" and billing evidence with records is our identity.
Intake, agent fixes, human verifies, the report remains.
Strengthen team communication with our enterprise-grade collaboration platform.
Target-specific key messages
“No record, no billing. Now it's one publish click.”
Pain: Digging through the inbox every month-end to reconstruct maintenance work
“Take issues in your own tools; the record keeps itself.”
Pain: Bouncing between terminal and dashboard just to leave a paper trail
“You are the one who confirms "it's fixed."”
Pain: Every fix confirmation hanging on your own eyes and hands
“Report it, and watch it move.”
Pain: Total silence after 'we'll look into it'
“Revision requests scattered across chat and email, unified into one record.”
Pain: Organizing scattered requests by hand and still having nothing to show at month's end
Contextual taglines
The system keeps records. Humans verify.
Default tagline for all communication. Can be used standalone.
Every fix on record, ready to bill.
Core product value in one sentence. For landing pages, ads, and contexts with sufficient background.
Every maintenance record in one place.
Where functional description is needed. App stores, extension descriptions, etc.
Stop explaining. Send the record.
Where emotional resonance is needed. SNS, campaigns, events, etc.
Visual language principles
Distinguish areas with background color contrast rather than borders. Canvas → White → Tint layer hierarchy.
The solid, casual impression comes from large text and tight tracking. weight 700, tracking -2px.
Bold and simple,
precise and casual.
Light background is the default. We prioritize a light, approachable impression. Dark option only available in the dashboard.
Real-world application examples
CTA Buttons
Issue Status
QA NOTE Brand Identity Guide v2.0 — Internal Use
