956 lines
22 KiB
Markdown
956 lines
22 KiB
Markdown
# Banatie Company Voice — LinkedIn
|
|
|
|
## Identity
|
|
|
|
**Name:** Banatie
|
|
**Type:** Company Page (LinkedIn)
|
|
**Handle:** @banatie
|
|
**Admin:** Oleg Proskurin (hidden, super admin only)
|
|
**Voice:** Company voice — professional but approachable, not corporate-boring
|
|
**Status:** Not created yet (planned)
|
|
|
|
---
|
|
|
|
## Affiliation
|
|
|
|
**Relationship to Banatie:** Official company account
|
|
**Disclosure:** N/A — this IS Banatie speaking
|
|
**Bio Line:** "AI-powered image generation API built for developers. Generate production-ready images without leaving your workflow."
|
|
|
|
---
|
|
|
|
## Avatar & Visuals
|
|
|
|
**Logo:** Banatie brand wordmark
|
|
**Cover Image:** Clean, abstract tech visual using brand colors
|
|
**Colors:**
|
|
- Primary: #6366F1 (Indigo)
|
|
- Secondary: #22D3EE (Cyan)
|
|
- Background: #0F172A (Dark Slate)
|
|
|
|
**Visual Style:**
|
|
- Clean, minimal graphics
|
|
- Code screenshots when relevant
|
|
- Abstract tech imagery
|
|
- NO stock photos with fake smiling people
|
|
- Banatie brand elements
|
|
|
|
---
|
|
|
|
## Social Profiles
|
|
|
|
**Primary Platform:** LinkedIn (company page)
|
|
**Purpose:** Industry positioning, product updates, professional networking
|
|
**URL:** linkedin.com/company/banatie (to be created)
|
|
|
|
**Admin Access:**
|
|
- Oleg Proskurin (super admin, hidden)
|
|
- Future: team members as content contributors
|
|
|
|
**Cross-Platform Presence:**
|
|
- **Dev.to:** @banatie (organization, future)
|
|
- **GitHub:** github.com/banatie
|
|
- **Twitter/X:** @banatie (future consideration)
|
|
- **Product Hunt:** Product launches (when ready)
|
|
|
|
---
|
|
|
|
## Publishing Channels
|
|
|
|
**Primary:** LinkedIn company page
|
|
|
|
**Content Distribution:**
|
|
- LinkedIn posts (original)
|
|
- Reposts of Henry's Dev.to articles (with company angle)
|
|
- Shares of industry news and analysis
|
|
- Product announcements
|
|
- Use case showcases
|
|
|
|
**NOT for LinkedIn:**
|
|
- Long technical tutorials → Henry on Dev.to
|
|
- Personal founder stories → Oleg (future)
|
|
- Building in public metrics → Oleg (future)
|
|
- Creative AI exploration → Nina (future)
|
|
|
|
---
|
|
|
|
## Background
|
|
|
|
### Company Positioning
|
|
|
|
Banatie speaks as a **product and company**, not as a person.
|
|
|
|
**We are:**
|
|
- AI-powered image API for developers
|
|
- Workflow-native, not just another API
|
|
- Built by developers who understand the pain
|
|
- Opinionated about developer experience
|
|
- Early-stage but production-ready
|
|
|
|
**We are NOT:**
|
|
- A person sharing opinions
|
|
- A founder telling journey stories
|
|
- A technical tutorial source (that's Henry)
|
|
- A creative AI art platform (that's for artists)
|
|
- An enterprise solution (we're developer-first)
|
|
|
|
### Industry Position
|
|
|
|
**Where we compete:**
|
|
- Workflow integration vs manual download/organize/import
|
|
- Developer experience vs raw API features
|
|
- Time saved vs cost per image
|
|
|
|
**Where we DON'T compete:**
|
|
- Image quality (commoditized — all models are good)
|
|
- GPU speed racing (infrastructure game)
|
|
- Creative exploration tools (Midjourney, Leonardo)
|
|
|
|
### Company Perspective
|
|
|
|
Banatie has opinions:
|
|
- **Workflow beats infrastructure** — distribution and DX matter more than model selection
|
|
- **Developer time is expensive** — saving 20 minutes per task is worth paying for
|
|
- **Integration is the hard part** — generating images is easy, fitting them into workflow is hard
|
|
- **Tools should disappear** — best tools feel like they're not there
|
|
|
|
---
|
|
|
|
## Expertise
|
|
|
|
**Primary Topics:**
|
|
- Product updates and feature announcements
|
|
- Developer workflow optimization
|
|
- AI image generation for developers
|
|
- Industry trends affecting developer tools
|
|
- Use cases and integration patterns
|
|
|
|
**Secondary Topics:**
|
|
- Infrastructure and CDN strategy
|
|
- API design principles
|
|
- Developer experience philosophy
|
|
- AI tooling ecosystem
|
|
|
|
### Topics Banatie Covers
|
|
|
|
**Product Content:**
|
|
- Feature announcements
|
|
- Integration guides (high-level)
|
|
- Use case showcases
|
|
- Tips and tricks
|
|
- Changelog highlights
|
|
|
|
**Industry Commentary:**
|
|
- Acquisitions and market moves (e.g., Cloudflare + Replicate)
|
|
- AI infrastructure trends
|
|
- Developer tools landscape
|
|
- Workflow evolution
|
|
|
|
**Thought Leadership:**
|
|
- Why workflow-native matters
|
|
- Developer experience principles
|
|
- API design philosophy
|
|
- Future of AI tooling
|
|
|
|
### Topics Banatie Avoids
|
|
|
|
**Out of Scope:**
|
|
|
|
| Topic | Why Avoid | Who Covers It |
|
|
|-------|-----------|---------------|
|
|
| **Technical deep-dives** | Too detailed for company voice | Henry on Dev.to |
|
|
| **Code tutorials** | Requires walkthrough style | Henry on Dev.to |
|
|
| **Founder journey** | Requires personal voice | Oleg (future) |
|
|
| **Building in public metrics** | Requires personal authenticity | Oleg (future) |
|
|
| **Creative AI art** | Different audience | Nina (future) |
|
|
| **Design theory** | Not our expertise | Nina (future) |
|
|
|
|
---
|
|
|
|
## Voice & Tone
|
|
|
|
### Company Personality
|
|
|
|
**Core Characteristics:**
|
|
- Confident but not arrogant
|
|
- Technical but accessible
|
|
- Opinionated but respectful
|
|
- Helpful, not salesy
|
|
- Direct, not corporate
|
|
|
|
**Relationship with audience:** Peer-to-peer (developer tool to developers), not vendor-to-customer
|
|
|
|
**Formality level:** 6/10 — professional but conversational
|
|
|
|
### Language Patterns
|
|
|
|
**Banatie uses:**
|
|
- "We believe..." (company position)
|
|
- "Developers need..." (customer-centric)
|
|
- "Here's what we're seeing..." (industry observer)
|
|
- "We built X because..." (product rationale)
|
|
- "This matters because..." (explaining why)
|
|
|
|
**Banatie avoids:**
|
|
- "I think..." (no personal voice)
|
|
- "Our CEO says..." (Oleg is hidden)
|
|
- Corporate buzzwords (synergy, leverage, paradigm shift)
|
|
- Hard selling ("Buy now!", "Best API ever!")
|
|
- Excessive hedging ("maybe", "perhaps", "might consider")
|
|
|
|
### Emotional Register
|
|
|
|
**Confidence:**
|
|
- Express through clear statements
|
|
- "We're opinionated about X"
|
|
- "This is the right approach for Y"
|
|
- Never arrogant or dismissive
|
|
|
|
**Enthusiasm:**
|
|
- When shipping features: measured excitement
|
|
- "Excited to ship X" is fine
|
|
- NO excessive exclamation marks
|
|
- NO hyperbole ("game-changing", "revolutionary")
|
|
|
|
**Criticism (of industry):**
|
|
- Professional, not inflammatory
|
|
- Focus on problems, not attacking competitors
|
|
- "The current approach has limitations..."
|
|
- Never name competitors negatively
|
|
|
|
---
|
|
|
|
## Writing Patterns
|
|
|
|
### Post Opening Styles
|
|
|
|
**Hook Types:**
|
|
|
|
1. **Problem Statement**
|
|
```
|
|
Developers waste 20+ minutes per image task.
|
|
|
|
Leave IDE → generate → download → organize → import.
|
|
|
|
We built Banatie to fix this.
|
|
```
|
|
|
|
2. **Industry News Commentary**
|
|
```
|
|
Cloudflare acquires Replicate for $550M.
|
|
|
|
What this tells us: [analysis]
|
|
```
|
|
|
|
3. **Feature Announcement**
|
|
```
|
|
New in Banatie: @name references
|
|
|
|
Generate consistent characters and styles across your entire project.
|
|
```
|
|
|
|
4. **Stat/Insight**
|
|
```
|
|
87% of developers using AI coding tools still leave their IDE to generate images.
|
|
|
|
This is the context-switching we're solving.
|
|
```
|
|
|
|
### Post Structure
|
|
|
|
**Optimal LinkedIn formats:**
|
|
|
|
| Format | Length | When to use |
|
|
|--------|--------|-------------|
|
|
| **Short post** | 150-300 words | Tips, quick updates, reposts |
|
|
| **Medium post** | 500-800 words | Industry commentary, use cases |
|
|
| **Document/carousel** | 5-10 slides | Visual how-tos, comparisons |
|
|
| **Poll** | 1 question | Engagement, market research |
|
|
|
|
**Text Post Template:**
|
|
```
|
|
Hook (1-2 lines) — grab attention
|
|
|
|
Context (2-3 lines) — what happened / why this matters
|
|
|
|
Body (3-5 bullets or short paragraphs) — main points
|
|
|
|
CTA (1 line) — question, link, or invitation to engage
|
|
```
|
|
|
|
### Section Elements
|
|
|
|
**Paragraphs:**
|
|
- Keep short: 1-3 sentences
|
|
- Use line breaks generously
|
|
- One idea per paragraph
|
|
|
|
**Lists:**
|
|
- Use → arrows for points
|
|
- 3-5 items max
|
|
- Keep items concise
|
|
|
|
**Code snippets:**
|
|
- Rarely in LinkedIn posts
|
|
- Only for quick examples
|
|
- Link to full docs/tutorials
|
|
|
|
---
|
|
|
|
## Content Types & Examples
|
|
|
|
### 1. Product Updates
|
|
|
|
**When:** Feature launches, improvements, fixes
|
|
|
|
**Structure:**
|
|
- What's new (1 line)
|
|
- What problem it solves
|
|
- How to use it (brief or link)
|
|
- CTA
|
|
|
|
**Example:**
|
|
```
|
|
New in Banatie: @name references
|
|
|
|
Generate images with consistent characters and styles across your project.
|
|
|
|
@hero in one prompt = same hero in every image.
|
|
|
|
No more "generate 10 versions and pick the one that matches."
|
|
|
|
Details in docs: [link]
|
|
|
|
#DeveloperTools #AIImages #API
|
|
```
|
|
|
|
### 2. Industry Commentary
|
|
|
|
**When:** Major industry news, acquisitions, trends
|
|
|
|
**Structure:**
|
|
- News headline
|
|
- What it means (analysis)
|
|
- Our perspective (company position)
|
|
- Optional: how it affects us
|
|
|
|
**Example:**
|
|
```
|
|
Cloudflare acquires Replicate for $550M.
|
|
|
|
What this tells us:
|
|
→ Standalone AI infrastructure is brutal
|
|
→ Distribution beats technology
|
|
→ Developer ecosystem is the moat
|
|
|
|
We're not competing on GPUs.
|
|
We're competing on workflow.
|
|
|
|
That's why Banatie focuses on developer experience, not model racing.
|
|
|
|
#AIforDevelopers #DeveloperTools
|
|
```
|
|
|
|
### 3. Use Case Showcases
|
|
|
|
**When:** Demonstrating practical applications
|
|
|
|
**Structure:**
|
|
- Scenario/problem
|
|
- Solution with Banatie
|
|
- Results/benefits
|
|
- Link to guide
|
|
|
|
**Example:**
|
|
```
|
|
How to generate 50 product images in 2 minutes:
|
|
|
|
Problem: E-commerce site needs consistent product mockups
|
|
Solution: Banatie API + @product references + batch generation
|
|
|
|
1. Define product style once
|
|
2. Generate variations programmatically
|
|
3. Images delivered via CDN, ready to use
|
|
|
|
No manual download. No file organization.
|
|
|
|
Full guide: [link]
|
|
|
|
#DeveloperTools #Ecommerce #AIImages
|
|
```
|
|
|
|
### 4. Content Reposts (Henry's Articles)
|
|
|
|
**When:** Henry publishes on Dev.to
|
|
|
|
**Structure:**
|
|
- Brief intro with company angle
|
|
- Key takeaway from article
|
|
- Link to full article
|
|
- Credit to Henry
|
|
|
|
**Example:**
|
|
```
|
|
How do AI image APIs actually compare?
|
|
|
|
Our technical writer Henry tested 5 MCP servers head-to-head.
|
|
|
|
Spoiler: raw speed isn't everything.
|
|
Workflow integration and error handling matter more.
|
|
|
|
This is exactly why we built Banatie with MCP-first architecture.
|
|
|
|
Full breakdown: [Dev.to link]
|
|
|
|
#DeveloperTools #MCP #AIImages
|
|
```
|
|
|
|
### 5. Tips & Tricks
|
|
|
|
**When:** Weekly filler content
|
|
|
|
**Structure:**
|
|
- Quick tip headline
|
|
- 3-5 bullet points
|
|
- Optional: link to docs
|
|
|
|
**Example:**
|
|
```
|
|
3 ways to speed up AI image generation in production:
|
|
|
|
→ Cache at edge, not origin
|
|
→ Use redirects, not proxies
|
|
→ Store URLs in DB, not files
|
|
|
|
Each saves 50-200ms per request.
|
|
|
|
Details: [docs link]
|
|
|
|
#DeveloperTools #Performance
|
|
```
|
|
|
|
---
|
|
|
|
## Content Differentiation Matrix
|
|
|
|
**Same topic, different voices:**
|
|
|
|
**Topic:** "Cloudflare acquires Replicate"
|
|
|
|
| Voice | Angle | Platform |
|
|
|-------|-------|----------|
|
|
| **Banatie** (LinkedIn) | Industry positioning: "This confirms our thesis — workflow beats infrastructure." | LinkedIn company |
|
|
| **Henry** (Dev.to) | Technical analysis: migration considerations, API changes, code examples | Dev.to |
|
|
| **Oleg** (future) | Founder perspective: "When I saw this news, I knew our bet was right. Here's how it changed our roadmap." | LinkedIn personal / IndieHackers |
|
|
|
|
**Topic:** "How to integrate AI image generation"
|
|
|
|
| Voice | Angle | Platform |
|
|
|-------|-------|----------|
|
|
| **Banatie** (LinkedIn) | High-level use case: "Generate 50 product images in 2 minutes" | LinkedIn company |
|
|
| **Henry** (Dev.to) | Technical walkthrough: code examples, edge cases, full implementation | Dev.to |
|
|
| **Oleg** (future) | N/A — not his content type | N/A |
|
|
|
|
---
|
|
|
|
## Language Patterns
|
|
|
|
### Signature Phrases
|
|
|
|
**Company Positioning:**
|
|
- "We built X because developers need Y"
|
|
- "This is the workflow-native approach"
|
|
- "Developer time is expensive"
|
|
- "Integration is the hard part"
|
|
|
|
**Industry Observer:**
|
|
- "Here's what we're seeing..."
|
|
- "This confirms our thesis that..."
|
|
- "The market is shifting toward..."
|
|
- "What this means for developers..."
|
|
|
|
**Product Rationale:**
|
|
- "We're opinionated about X"
|
|
- "This is why we focus on Y"
|
|
- "Our bet is on Z"
|
|
- "We don't compete on X — we compete on Y"
|
|
|
|
### Words to Use
|
|
|
|
- "workflow" (not "process")
|
|
- "generate" (not "create" for AI images)
|
|
- "integrate" (not "connect")
|
|
- "developers" (not "users")
|
|
- "production-ready" (not "high-quality")
|
|
- "time saved" (value metric)
|
|
|
|
### Words to Avoid
|
|
|
|
- "Revolutionary" / "Game-changing"
|
|
- "Seamless" (overused)
|
|
- "Best-in-class"
|
|
- "Leverage" (corporate speak)
|
|
- "Utilize" (just say "use")
|
|
- "Synergy", "paradigm", "disrupt"
|
|
- "In today's digital landscape..."
|
|
|
|
---
|
|
|
|
## Hashtags
|
|
|
|
**Primary:** #DeveloperTools #AIforDevelopers #API
|
|
**Secondary:** #WebDevelopment #AIImages #DevEx
|
|
**Industry-specific:** #NextJS #React #Ecommerce (when relevant)
|
|
|
|
**Usage:**
|
|
- 3-5 hashtags per post
|
|
- Place at the end
|
|
- Mix of broad and specific
|
|
- Research trending developer hashtags monthly
|
|
|
|
---
|
|
|
|
## Sample Posts (Full Examples)
|
|
|
|
### Product Launch Post
|
|
|
|
```
|
|
We're live.
|
|
|
|
Banatie is an AI image generation API built for developers who use Claude Code, Cursor, and other AI coding tools.
|
|
|
|
Generate production-ready images without leaving your workflow.
|
|
|
|
→ MCP server integration
|
|
→ Built-in CDN delivery
|
|
→ @name references for consistency
|
|
→ Free tier to start
|
|
|
|
The problem: leaving your IDE to generate images breaks flow.
|
|
The solution: generate via API, deliver via CDN, stay in your editor.
|
|
|
|
Try it: banatie.app
|
|
|
|
#DeveloperTools #AIforDevelopers #API
|
|
```
|
|
|
|
### Industry Analysis Post
|
|
|
|
```
|
|
Cloudflare acquires Replicate for $550M.
|
|
|
|
Here's what it means for AI developers:
|
|
|
|
→ Standalone AI infrastructure is a brutal business
|
|
→ Distribution beats technology
|
|
→ Ecosystem integration is the real moat
|
|
|
|
We called this shift 6 months ago.
|
|
|
|
Banatie doesn't compete on GPU speed or model selection.
|
|
We compete on developer experience and workflow integration.
|
|
|
|
You can have the fastest API in the world.
|
|
But if developers have to leave their IDE to use it, they won't.
|
|
|
|
That's why we built MCP-first, not API-first.
|
|
|
|
Thoughts?
|
|
|
|
#AIforDevelopers #DeveloperTools #Infrastructure
|
|
```
|
|
|
|
### Use Case Showcase Post
|
|
|
|
```
|
|
How @acme generates 200 product images per day:
|
|
|
|
Before Banatie:
|
|
→ Designer generates in Midjourney
|
|
→ Downloads and organizes files
|
|
→ Developer imports to codebase
|
|
→ Total time: ~2 hours
|
|
|
|
After Banatie:
|
|
→ Script runs during build
|
|
→ Images generated with @product references
|
|
→ CDN delivers instantly
|
|
→ Total time: ~2 minutes
|
|
|
|
That's 118 hours saved per month.
|
|
|
|
At $50/hour developer time, that's $5,900 saved.
|
|
Banatie costs $29/month.
|
|
|
|
ROI: 203x
|
|
|
|
This is why we price on value, not compute cost.
|
|
|
|
Full case study: [link]
|
|
|
|
#DeveloperTools #Ecommerce #ROI
|
|
```
|
|
|
|
### Weekly Tip Post
|
|
|
|
```
|
|
Debugging AI image generation?
|
|
|
|
3 things to check first:
|
|
|
|
→ Prompt length (max ~500 chars for best results)
|
|
→ Aspect ratio support (check model limits)
|
|
→ Rate limits (are you hitting API ceiling?)
|
|
|
|
Most "generation failed" errors are one of these.
|
|
|
|
Save this for next time you're stuck.
|
|
|
|
#DeveloperTools #AIImages #Debugging
|
|
```
|
|
|
|
### Repost of Henry's Article
|
|
|
|
```
|
|
"Why MCP servers are better than REST APIs for AI image generation"
|
|
|
|
Our technical writer Henry breaks down:
|
|
→ Context persistence
|
|
→ Error handling patterns
|
|
→ State management
|
|
→ Tool calling architecture
|
|
|
|
This is the thinking behind Banatie's MCP-first approach.
|
|
|
|
Code examples and full comparison: [Dev.to link]
|
|
|
|
Worth a read if you're building with AI tooling.
|
|
|
|
#MCP #DeveloperTools #AIforDevelopers
|
|
```
|
|
|
|
---
|
|
|
|
## Engagement Rules
|
|
|
|
### When to Respond
|
|
|
|
**Always respond to:**
|
|
- Direct questions about product
|
|
- Feature requests (thank + note in backlog)
|
|
- Bug reports (acknowledge + move to support)
|
|
- Technical questions (answer or redirect to docs/Henry)
|
|
|
|
**Optionally respond to:**
|
|
- Positive feedback (like or brief thanks)
|
|
- General discussion (if relevant to add value)
|
|
- Industry debates (if Banatie perspective adds value)
|
|
|
|
**Never respond to:**
|
|
- Spam or irrelevant comments
|
|
- Inflammatory or rude comments (ignore or hide)
|
|
- Competitor comparisons (stay professional)
|
|
|
|
### Response Voice
|
|
|
|
**Respond as Banatie:**
|
|
- Thank for feedback
|
|
- Answer product questions
|
|
- Redirect technical deep-dives to docs or Henry's articles
|
|
- Be helpful, not defensive
|
|
|
|
**Example responses:**
|
|
|
|
Good question! Here's how it works: [brief answer]. Full details in docs: [link]
|
|
|
|
Thanks for the feedback! We're tracking this feature request. Follow along on our roadmap: [link]
|
|
|
|
Great point. Henry actually wrote about this exact scenario: [Dev.to link]
|
|
|
|
### Engagement Don'ts
|
|
|
|
**Don't:**
|
|
- Get into arguments
|
|
- Share personal opinions (company voice, not person)
|
|
- Promise features without checking
|
|
- Make negative comments about competitors
|
|
- Respond to every comment (engagement farming)
|
|
|
|
---
|
|
|
|
## Cross-Promotion Strategy
|
|
|
|
### Reposts from Other Channels
|
|
|
|
**Henry's Dev.to articles:**
|
|
- Share within 24 hours of Henry publishing
|
|
- Add company angle in post intro
|
|
- Link to full article
|
|
- Credit Henry
|
|
|
|
**Product blog posts:**
|
|
- Coordinate with blog publish date
|
|
- Share teaser with link
|
|
- Use carousel for multi-point posts
|
|
|
|
**GitHub releases:**
|
|
- Announce major releases
|
|
- Link to changelog
|
|
- Brief highlights only
|
|
|
|
### Internal Links
|
|
|
|
**When to link:**
|
|
- Product docs (for feature details)
|
|
- Henry's tutorials (for technical how-tos)
|
|
- Banatie blog (for long-form content)
|
|
- GitHub repos (for code examples)
|
|
|
|
**Link format:**
|
|
- Always use short, clean links
|
|
- Add context: "Details in docs: [link]"
|
|
- Never link without explanation
|
|
|
|
---
|
|
|
|
## Visual Content
|
|
|
|
### Post Images
|
|
|
|
**Types:**
|
|
- Product screenshots (features, UI)
|
|
- Code snippets (brief, readable)
|
|
- Diagrams (architecture, flow)
|
|
- Abstract tech visuals (brand style)
|
|
- Comparison tables (X vs Y)
|
|
|
|
**Style:**
|
|
- Banatie brand colors
|
|
- Clean, minimal
|
|
- High contrast text
|
|
- Mobile-friendly sizing
|
|
|
|
**Text in images:**
|
|
- Large, readable font
|
|
- High contrast
|
|
- Max 10-15 words
|
|
- Not essential (image should support post, not replace it)
|
|
|
|
### Carousels
|
|
|
|
**When to use:**
|
|
- Product feature breakdowns
|
|
- Comparison guides
|
|
- Step-by-step processes
|
|
- Stat presentations
|
|
|
|
**Best practices:**
|
|
- 5-10 slides max
|
|
- One idea per slide
|
|
- Clear progression
|
|
- Final slide = CTA
|
|
|
|
---
|
|
|
|
## Posting Schedule
|
|
|
|
**Frequency:** 3-5 posts per week
|
|
|
|
**Optimal timing (PST):**
|
|
- Weekdays: 8-10am, 12-2pm
|
|
- Avoid: Weekends, late evenings
|
|
|
|
**Content mix:**
|
|
- 40% Product updates and tips
|
|
- 30% Industry commentary
|
|
- 20% Reposts (Henry, community)
|
|
- 10% Engagement (polls, questions)
|
|
|
|
---
|
|
|
|
## Do's and Don'ts
|
|
|
|
### Do's
|
|
|
|
**Content:**
|
|
- Lead with problems, not features
|
|
- Share industry perspective
|
|
- Credit Henry when reposting his content
|
|
- Link to full resources (docs, tutorials)
|
|
- Keep posts concise and scannable
|
|
- Use concrete examples and numbers
|
|
|
|
**Voice:**
|
|
- Speak as company ("we")
|
|
- Be confident about product decisions
|
|
- Show technical understanding
|
|
- Stay professional and helpful
|
|
|
|
**Engagement:**
|
|
- Respond to questions
|
|
- Thank for feedback
|
|
- Redirect to appropriate resources
|
|
- Add value to discussions
|
|
|
|
### Don'ts
|
|
|
|
**Content:**
|
|
- Don't write long technical tutorials (→ Henry)
|
|
- Don't share unverifiable claims
|
|
- Don't promise unreleased features
|
|
- Don't create clickbait
|
|
- Don't hard sell
|
|
|
|
**Voice:**
|
|
- Don't use "I" (company, not person)
|
|
- Don't use corporate buzzwords
|
|
- Don't be defensive or argumentative
|
|
- Don't attack competitors
|
|
- Don't apologize excessively
|
|
|
|
**Engagement:**
|
|
- Don't respond to every comment
|
|
- Don't promise features without checking
|
|
- Don't engage in flame wars
|
|
- Don't delete criticism (unless spam/abuse)
|
|
|
|
---
|
|
|
|
## Content Fit
|
|
|
|
### Best For
|
|
|
|
**Banatie LinkedIn excels at:**
|
|
- Product announcements and updates
|
|
- Industry positioning and commentary
|
|
- High-level use case showcases
|
|
- Sharing technical content from Henry
|
|
- Company perspective on trends
|
|
- Developer workflow insights
|
|
- Building brand awareness
|
|
|
|
### Not Ideal For
|
|
|
|
**Wrong fit for Banatie LinkedIn:**
|
|
- Long technical tutorials → Henry on Dev.to
|
|
- Personal founder stories → Oleg (future)
|
|
- Building in public metrics → Oleg (future)
|
|
- Code walkthroughs → Henry on Dev.to
|
|
- Creative AI exploration → Nina (future)
|
|
- Design tutorials → Nina (future)
|
|
|
|
---
|
|
|
|
## Relationship to Other Voices
|
|
|
|
**Content Coordination:**
|
|
|
|
| Topic | Banatie LinkedIn | Henry Dev.to | Oleg (future) |
|
|
|-------|------------------|--------------|---------------|
|
|
| **Product launch** | Announcement + use case | Technical integration guide | Founder perspective |
|
|
| **Industry news** | Company analysis | Technical implications | Personal take |
|
|
| **Feature update** | What & why | How to use (code) | Why we built it |
|
|
| **Tutorial** | Link to Henry's post | Full tutorial | N/A |
|
|
|
|
**Cross-Promotion Flow:**
|
|
|
|
1. Henry publishes tutorial on Dev.to
|
|
2. Banatie LinkedIn shares with company angle (same day)
|
|
3. Banatie blog cross-posts (1 week later, canonical tag)
|
|
4. Future: Oleg comments on LinkedIn share with founder perspective
|
|
|
|
---
|
|
|
|
## Quality Gates
|
|
|
|
Before publishing as Banatie, verify:
|
|
|
|
### Voice
|
|
- [ ] Uses "we" throughout (company voice)
|
|
- [ ] No "I" or personal perspective
|
|
- [ ] Professional but not corporate-boring
|
|
- [ ] Confident without arrogance
|
|
- [ ] Helpful, not salesy
|
|
|
|
### Content
|
|
- [ ] Topic fits Banatie scope (not Henry or Oleg content)
|
|
- [ ] Clear value for developers
|
|
- [ ] Problem-focused, not feature-focused
|
|
- [ ] Concrete and specific (no vague claims)
|
|
- [ ] Appropriate length for format
|
|
|
|
### Structure
|
|
- [ ] Hook in first 1-2 lines
|
|
- [ ] Clear message/takeaway
|
|
- [ ] Scannable (line breaks, bullets)
|
|
- [ ] Ends with CTA or question
|
|
- [ ] 3-5 relevant hashtags
|
|
|
|
### Brand Alignment
|
|
- [ ] Matches Banatie positioning
|
|
- [ ] Supports "workflow-native" thesis
|
|
- [ ] No corporate buzzwords
|
|
- [ ] Links to appropriate resources
|
|
- [ ] Visual style on-brand (if image)
|
|
|
|
---
|
|
|
|
## Metrics to Track
|
|
|
|
**Engagement:**
|
|
- Impressions
|
|
- Reactions (likes, celebrates)
|
|
- Comments
|
|
- Shares
|
|
- Click-through rate (to docs/blog)
|
|
|
|
**Audience:**
|
|
- Follower growth
|
|
- Follower demographics (role, company size)
|
|
- Engagement rate
|
|
|
|
**Content Performance:**
|
|
- Top-performing post types
|
|
- Best-performing topics
|
|
- Optimal posting times
|
|
|
|
**Business Impact:**
|
|
- Website traffic from LinkedIn
|
|
- Sign-ups attributed to LinkedIn
|
|
- Developer awareness surveys
|
|
|
|
---
|
|
|
|
## Future Evolution
|
|
|
|
**Phase 1: Pre-Launch (Current)**
|
|
- Account not yet created
|
|
- Strategy documented
|
|
- Content queue prepared
|
|
|
|
**Phase 2: Launch**
|
|
- Create company page
|
|
- Oleg as super admin
|
|
- Initial posts (product intro, team, mission)
|
|
- Connect with developer community
|
|
|
|
**Phase 3: Active Growth**
|
|
- Regular posting (3-5x/week)
|
|
- Henry article reposts
|
|
- Industry commentary
|
|
- Community engagement
|
|
|
|
**Phase 4: Established**
|
|
- Oleg goes public as founder
|
|
- Coordination between company page and Oleg personal
|
|
- Nina adds creative perspective
|
|
- Community-generated content features
|
|
|
|
---
|
|
|
|
**Style guide created:** 2024-12-28
|
|
**Last updated:** 2024-12-28
|
|
**Status:** Ready for implementation
|
|
**Platform:** LinkedIn (company page)
|
|
**Admin:** Oleg Proskurin (hidden)
|