StringLogix
Brand Guide
Standards for colour, typography, logo usage, tone of voice and design principles — for consistent representation across all touchpoints.
Who We Are
StringLogix is a custom software development agency focused on German and European B2B businesses. We build tailored software solutions — CRM systems, web applications, automation platforms, marketplaces and AI integrations — that replace manual processes and generic tools with systems built exactly for each client's needs.
Technical partner for European businesses that need custom software — not an agency selling templates or repackaged SaaS.
German and EU SMEs, Mittelstand companies, and B2B businesses across industries who need purpose-built digital systems.
Direct. Technical. Dependable. We communicate with precision and without unnecessary jargon or overselling.
We build software that solves the actual problem — with clear scope, transparent pricing and full ownership transfer.
Logo Usage
The StringLogix logo is a wordmark: a pink dot followed by the company name in uppercase. The dot always appears in StringLogix Pink (#ff0f7b). The wordmark uses uppercase lettering with a 0.08em letter-spacing.
On white — primary
On Navy — reversed
On dark — reversed
Do not: Change the dot colour · Place on a background that reduces contrast below 4.5:1 · Distort proportions · Add drop shadows, gradients or effects · Use in lowercase
Brand Colours
The StringLogix palette is built around three primary brand colours. Use them consistently across all materials.
Colour use rule: Pink is used sparingly — it draws the eye. Reserve it for one primary action, the logo dot and key accent moments. Never use pink for large background areas of body content. Navy is the dominant brand colour for structure and authority. Blue is for links, informational elements and secondary CTAs.
Type System
StringLogix uses two typefaces that complement each other: Playfair Display for high-impact headlines and Inter for all body content, UI and labels.
Used for: hero headlines, major section titles, document cover titles. Do not use for body text, UI labels or anything under 18px.
Used for: all body text, navigation, UI labels, kickers, captions, tables. Default for everything that is not a major display heading.
Kicker labels (e.g. "01 — BRAND OVERVIEW"): Inter 700, 10–11px, letter-spacing 0.14–0.18em, uppercase, colour: #ff0f7b. Minimum body text size: 13px. Line height: 1.5–1.7 for body, 1.1–1.2 for headlines.
How We Communicate
StringLogix speaks like a skilled engineer who understands business — direct, specific and without padding. We write for decision-makers, not an audience we need to impress.
Say what we do clearly. No vague promises, no buzzword filler. "We build CRM systems" not "We deliver transformative digital experiences."
Use concrete details wherever possible. Features, examples, outcomes. Specificity builds trust in a technical audience.
We are approachable and human, but we do not use casual language in client-facing copy. No exclamation marks in headlines.
We state our expertise clearly without self-congratulation. The work demonstrates the capability, not the words.
Write about the client's problem and outcome first, then introduce what we do. "Your sales team wastes four hours…" not "Our CRM module…"
Acknowledge German B2B norms: compliance, data protection, process clarity, ownership. These are features, not footnotes.
We build custom CRM systems for German B2B companies — designed around your actual sales process, not forced into an off-the-shelf template.
We're a passionate team of digital innovators leveraging cutting-edge technology to transform your customer relationship journey!
Source code is fully transferred to you on delivery. You own everything — no vendor lock-in, no ongoing licence dependency.
We believe in empowering our clients with full ownership of their digital assets through our comprehensive IP transfer solutions.
Visual Design Principles
These principles guide how StringLogix-branded materials look and feel — web pages, documents, presentations and UI design.
Every visual element serves a purpose. We do not add decorative elements for style alone.
Content breathes. Generous padding and spacing are not empty space — they create hierarchy and aid comprehension.
Page structure is predictable: kicker → heading → subtext → content. Users should never have to work out where they are.
Each page section has one clear call to action. Pink buttons signal the primary action; secondary actions use outlined or text styles.
Heavy visual weight belongs to navy (#1a1a2e) — headers, section strips, footers, CTA blocks. Pink provides contrast, not weight.
All designs must work from 360px viewport width upward. Breakpoints: 900px, 680px, 460px, 360px.
✓ Do
- Use navy (#1a1a2e) for primary backgrounds and document headers
- Use the pink dot + "STRINGLOGIX" wordmark consistently
- Use Inter for all body text and UI at 13px minimum
- Keep CTA buttons in StringLogix Pink on dark sections
- Use kicker labels (uppercase, pink, spaced) to introduce each section
- Maintain 4px pink top bar on document cover pages
- Use semantic HTML and proper heading hierarchy (H1 → H2 → H3)
- Ensure text contrast meets WCAG AA (4.5:1 minimum)
✗ Don't
- Use pink as a large background colour for body content sections
- Change the colour of the logo dot from #ff0f7b
- Place text on low-contrast backgrounds (navy text on blue, etc.)
- Use Playfair Display for body copy or UI elements
- Add drop shadows, gradients or effects to the logo
- Use more than two typefaces in any single design
- Use brand blue (#2563eb) as a background colour
- Squeeze whitespace to fit more content — restructure instead
CSS Tokens & Asset Paths
Reference for developers implementing the brand in code.
/* CSS Custom Properties — app.css */ --navy: #1a1a2e; /* Navy — primary brand colour */ --pink: #ff0f7b; /* Pink — accent & CTA colour */ --blue: #2563eb; /* Blue — secondary accent */ /* Asset paths (relative to /assets/) */ img/stringlogix-mark.png /* Logo mark — 26×30px */ img/og-image.png /* OG share image — 1200×630px */ css/app.css /* Main stylesheet */ /* Google Fonts load string */ https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700 &family=Playfair+Display:wght@400;700&display=swap
Questions about brand usage?
Get in touch if you need brand assets, usage guidance or design support.