Updated 14 days ago
Branding Standard#
Every tool Springpod puts in front of users represents our brand. AI tools can generate beautiful interfaces — but they default to generic styling. This guide ensures everything looks and sounds like Springpod.
Visual identity#
Colors#
| Usage | Color | Hex |
|---|---|---|
| Primary (buttons, headers) | Springpod Teal | #0BB3B7 |
| Secondary (accents, links) | Springpod Blue | #446DF6 |
| Dark (text, dark backgrounds) | Springpod Navy | #16254C |
| Background | White | #FFFFFF |
| Light background | Light Gray | #E4ECF7 |
| Text | Springpod Navy | #16254C |
| Error/warning | Red | #FF475A |
| Success | Teal (dark) | #0A8F93 |
| Accent warm | Orange | #F7936F |
| Accent cool | Purple | #7F7EFF |
Consistent colors are the fastest way to make a tool feel "ours." Without defined colors, every AI-generated tool looks different — and none of them look like Springpod.
- Open your tool next to the Springpod website or an existing branded product
- Compare the main colors — buttons, headers, links, backgrounds
- If the colors do not match the table above, update them before shipping
- Most AI tools let you set colors in a theme or CSS file. Paste the hex codes from the table.
Typography#
| Usage | Font | Size |
|---|---|---|
| Headings | Poppins SemiBold (600) | 32px / 24px / 20px |
| Body text | Inter Regular (400) | 16px |
| Small text / captions | Inter Regular (400) | 14px |
| UI elements | Inter Medium (500) | 14px |
Mismatched fonts make a tool look unfinished. Using Springpod's standard fonts — Poppins for headings, Inter for body — ties everything together visually.
Logo usage#
- Primary logo: Springpod wordmark (teal on white, white on navy)
- Favicon: Springpod "S" mark
- Minimum clear space: Equal to the height of the "S" mark on all sides
- Do not stretch, rotate, recolor, or place on busy backgrounds
- On dark backgrounds, use the white version of the logo
A misused logo damages brand perception. These rules exist because designers tested what works.
Tone of voice#
Springpod's voice is friendly, encouraging, and clear — especially for students. We avoid jargon and corporate-speak.
| Do | Do not |
|---|---|
| "Let's get you started" | "Please initiate the onboarding process" |
| "Something went wrong — try again in a moment" | "Error 500: Internal Server Exception" |
| "You're all set!" | "Process completed successfully" |
| "We couldn't find that page" | "404 Not Found" |
| "This experience is no longer available" | "Resource has been deprecated" |
| "Great work — you've completed this step" | "Task execution confirmed" |
Every piece of text a user reads is Springpod speaking. Our brand is friendly and approachable, so error messages should be too — not robotic or technical.
- Read every piece of text in your tool out loud
- Does it sound like something Springpod would say to a student?
- Check buttons, error messages, confirmation text, empty states, and loading messages
- Replace anything that sounds generic or overly technical with Springpod's brand voice
AI-generated content guidelines#
When AI generates text that users see (chatbot responses, summaries, recommendations), it must:
AI defaults to a neutral, slightly formal tone. Adjust the prompt to match Springpod's friendly, encouraging voice.
- Generate 5 sample outputs from your AI feature 2. Read each one against the tone of voice table above 3. If any output sounds off-brand, adjust the system prompt to include tone instructions 4. Re-test until the outputs consistently match Springpod's voice
Springpod's AI disclosure policy:
- Student-facing AI features must include age-appropriate disclosure, e.g.: "This feedback was created with the help of AI. A real person reviewed it before it reached you."
- Internal tools do not require AI disclosure but should note it in the Build Log.
- B2B/partner-facing tools should mention AI where it adds trust (e.g., "AI-assisted matching").
AI should never say "I guarantee" or "This will definitely work." Use language like "Based on the available information" or "This suggests."
AI can be wrong. Promises create legal and trust liability when the output turns out to be incorrect.
Springpod's brand is warm and informal for student-facing content. Use friendly language, celebrate progress, and keep things conversational — but avoid slang that may not translate across audiences.
Checking your build against brand#
Use this quick checklist before shipping any Orange+ build:
- Take a screenshot of your tool's main page
- Place it next to a screenshot of the Springpod website
- If they do not look like they belong together, adjust colors, fonts, and logo placement
- This 30-second visual comparison catches most branding issues
Was this page helpful?