# Fimple Brand Voice Guidelines

## Communication Style
- **Overall Tone:** Authoritative, professional, and forward-thinking. The tone is inherently B2B-focused, prioritizing clarity, precision, and technological sophistication. It reflects a brand that is a reliable partner in complex financial infrastructure.
- **Personality:** Visionary, technical, and enabling. Fimple positions itself as the architect of future banking; the voice should sound like an expert guide leading clients through digital transformation.
- **Vocabulary:** High-tech, industry-standard terminology (e.g., "Composable," "Cloud-native," "API-first," "Ecosystem"). The language is precise, avoiding fluff in favor of functional descriptions that highlight utility and scalability.

## Content Patterns
- **Common Themes:** Digital transformation, modularity, banking infrastructure, scalability, and the "future-proofing" of financial services. 
- **Structural Approaches:** Content is highly organized and categorized. The brand uses a hierarchical structure (Platform, Solution, Resources, Company) to ensure information is easily accessible. There is a strong emphasis on "Use Cases" to bridge the gap between technical features and business outcomes.
- **Call-to-Action (CTA) Style:** Action-oriented and empowering. CTAs are direct, focusing on enablement rather than hard-selling (e.g., "Build Your Product," "Shape Your Future," "Become a Partner").

## Audience Interaction
- **Addressing the Audience:** The brand addresses its audience as professional peers—developers, financial institution leaders, and fintech innovators. 
- **Relationship Style:** A partnership-based approach. The brand positions itself as an extension of the client’s team, providing the tools (SDKs, documentation, modules) necessary for the client to build their own success.
- **Formality:** Professional and respectful, yet modern. It avoids overly stiff corporate jargon, opting instead for a "developer-friendly" clarity that respects the intelligence of the technical reader.

## Guidelines & Examples

### Do's and Don'ts
- **Do:** Use active, precise language. Focus on how the technology empowers the user to build or transform.
- **Do:** Maintain a modular, structured approach to information. Use clear headings and logical categorization.
- **Don't:** Use overly flowery or vague marketing language. Avoid hyperbole; let the technical capabilities speak for themselves.
- **Don't:** Forget the developer perspective. Ensure that even high-level business copy acknowledges the "API-first" or "Cloud-native" nature of the platform.

### On-Brand Phrases
- "Shape your future."
- "Composable banking framework."
- "Built for the future of finance."
- "Seamlessly integrate, rapidly scale."
- "Empowering the next generation of financial services."

### Content Types
- **Technical Documentation:** Highly structured, logic-driven, and accessible via the Developer Hub.
- **Educational/Insightful:** Thought leadership content found in the "Insight Hub," focusing on industry trends like Embedded Finance and Banking-as-a-Service (BaaS).
- **Product-Centric:** Clear, module-based descriptions that outline specific utility (e.g., "Loan Management," "Credit Scoring") without unnecessary complexity.