SBK Brand Voice¶

SBK Consulting — Technology Service Partner for Small Businesses and Non-profits

Brand Identity¶

Positioning Statement¶

SBK Consulting is a vendor-neutral technology service partner for small businesses (10-500 employees) and non-profit organizations that need strategic IT guidance, security expertise, and technology solutions—without the conflicts of interest inherent in traditional MSP and VAR relationships.

Primary Identity: Advisory-first. We guide decisions before we build solutions.

Extended Capability: When guidance leads to action, we deliver—from process transformation to custom software development through our Innovate pillar.

Core Differentiators¶

Differentiator	Statement	Proof
Vendor Neutrality	Zero vendor conflicts since 2010	No reselling, no commissions, no kickbacks
SMB + Non-profit Focus	Right-sized for your organization	Enterprise expertise at accessible pricing
Advisory-First	We advise, we don't sell	Revenue from guidance, not product markup
Outcome Guarantee	Pass audits first try	100% first-time compliance pass rate
Full-Lifecycle Partner	From strategy to implementation	Advisory → Architecture → Build → Optimize

The Innovate Pillar: Building What We Advise¶

When Advisory Becomes Action¶

SBK's Innovate pillar extends our advisory-first positioning into execution. We don't just tell you what to build—we build it with you.

Core Focus Areas:

Focus	Description	Business Outcome
Process Transformation	Redesigning workflows through technology	Operational efficiency, reduced manual burden
Intelligent Workflows	Automation that thinks, not just executes	Faster decisions, consistent execution
Business Optimization	Technology solutions aligned to metrics	Revenue growth, compliance posture, customer satisfaction
Custom Software Development	Purpose-built applications when off-the-shelf fails	Solutions that fit your process, not the reverse

Advisory-to-Build Philosophy¶

1. Advisory Assessment  →  Understand before recommending
2. Architecture Design  →  Plan before building
3. Selective Build      →  Build only what creates value
4. Continuous Optimize  →  Improve based on real outcomes

Key Principle: We build because we advised it—not because we have developers to keep busy.

Voice Parameters¶

Tone Spectrum¶

tone_spectrum:
  formality: 0.70      # Professional, not stuffy
  technicality: 0.55   # Accessible to C-suite, credible to engineers
  energy: 0.60         # Active urgency without panic
  authority: 0.85      # Enterprise-grade expertise
  warmth: 0.45         # Approachable but not soft
  directness: 0.80     # Call out the problem clearly

Voice Traits¶

Trait	Description	Example
Truth-Teller	Call out vendor conflicts others won't	"Is your IT advisor on your payroll? Or your vendor's?"
Cost-Conscious	Fight unnecessary IT spending	"Your IT budget has 30-40% waste. We find it."
Protective	Shield clients from predatory practices	"Stop getting sold to."
Expert	Deep knowledge without arrogance	"Federal Reserve-tested security expertise"
Partner	In it together, not transactional	"Your extended team, not your vendor"
Builder	Execute what we advise	"We don't just plan. We ship."

Voice Rules¶

Always¶

Lead with vendor neutrality as core differentiator
Expose the conflict of interest in traditional IT advisory
Be direct about what clients don't need
Focus on outcomes over features
Use evidence and metrics to prove claims
Speak to SMB and non-profit realities (budget constraints, lean teams)
Frame development work as advisory-led (we build because we advised it)
Connect technology solutions to business metrics (revenue, compliance, satisfaction)

Never¶

Recommend products we profit from (we don't have any)
Hide the vendor conflict problem in the industry
Oversell or push unnecessary services
Speak like an enterprise vendor to enterprise buyers
Promise what can't be delivered
Use jargon without explanation
Position development as separate from advisory (it's the natural extension)
Build technology for technology's sake (only build what creates measurable value)

Signature Phrases¶

Opening Hooks¶

Context	Phrase
Universal	"Is your IT advisor on your payroll? Or your vendor's?"
Cost Focus	"Your IT budget has 30-40% waste."
Action	"Stop getting sold to."
Compliance	"Pass audits first try."
Trust	"Zero vendor conflicts since 2010."

Proof Statements¶

"No reselling, no commissions, no kickbacks—pure advisory."
"100+ years combined expertise, zero products to sell."
"Family-run since 2010."
"100% US-based certified team."
"24/7 support availability."
"We don't just plan. We ship."
"Advisory-led development. Build only what creates value."

Calls to Action¶

Audience	CTA
General	"Get Honest Advice"
Executive	"Schedule a No-Pitch Consultation"
IT Manager	"See How We're Different"
Finance	"Find Your IT Waste"
Compliance	"Get Audit-Ready"
Transformation	"See What's Possible"
Development	"Build What You Actually Need"

Voice Gears (Audience Adaptation)¶

Executive Gear¶

gear: executive
adjustments:
  formality: +0.10
  authority: +0.10
vocabulary_shifts:
  vendor: "conflict of interest"
  cost: "unnecessary spend"
  advice: "independent guidance"
emphasis:
  lead_with: "Your IT advisor works for you, not vendors"
  prove_with: "Zero kickbacks, independent recommendations"
cta: "Schedule Executive Consultation"

IT Manager Gear¶

gear: it_manager
adjustments:
  technicality: +0.15
  directness: +0.10
vocabulary_shifts:
  solution: "what you actually need"
  vendor: "sales quota"
  recommendation: "unbiased assessment"
emphasis:
  lead_with: "Stop fighting vendor-driven recommendations"
  prove_with: "Technical expertise without sales pressure"
cta: "See How We're Different"

Non-Profit Gear¶

gear: nonprofit
adjustments:
  warmth: +0.15
  formality: -0.10
vocabulary_shifts:
  cost: "mission dollars"
  budget: "donor investment"
  ROI: "mission impact"
emphasis:
  lead_with: "Protect your mission and your donors"
  prove_with: "Non-profit budget realities, enterprise-grade security"
cta: "Maximize Every Security Dollar"

CFO/Finance Gear¶

gear: finance
adjustments:
  directness: +0.20
  authority: +0.10
vocabulary_shifts:
  cost: "vendor markup"
  savings: "identified waste"
  budget: "IT spend accountability"
emphasis:
  lead_with: "Your IT budget has 30-40% waste"
  prove_with: "No markups, transparent pricing, quantified savings"
cta: "Find Your IT Waste"

Healthcare Gear¶

gear: healthcare
adjustments:
  authority: +0.15
  technicality: +0.10
vocabulary_shifts:
  compliance: "HIPAA readiness"
  security: "patient data protection"
  audit: "OCR audit readiness"
emphasis:
  lead_with: "HIPAA compliance, not complexity"
  prove_with: "75-90 days to audit-ready, 100% pass rate"
cta: "Get HIPAA-Ready"

Technical/Development Gear¶

gear: technical_development
adjustments:
  technicality: +0.25
  formality: -0.05
  directness: +0.15
vocabulary_shifts:
  software: "purpose-built solution"
  automation: "intelligent workflow"
  project: "outcome-driven engagement"
  development: "advisory-led build"
emphasis:
  lead_with: "Build what you need, not what's available"
  prove_with: "Advisory first, architecture second, code third"
  secondary: "We understand the problem before we write a line of code"
cta: "Build What You Actually Need"

Process Transformation Gear¶

gear: process_transformation
adjustments:
  authority: +0.10
  energy: +0.10
  technicality: +0.05
vocabulary_shifts:
  process: "workflow optimization"
  change: "measurable transformation"
  tool: "enabling technology"
  manual: "automation opportunity"
emphasis:
  lead_with: "Transform how work gets done"
  prove_with: "Measurable outcomes: revenue, compliance, satisfaction"
  secondary: "Technology serves the process, not the reverse"
cta: "See What's Possible"

Content Type Guidelines¶

Website Copy¶

Short, punchy sentences
Lead with differentiation
One idea per paragraph
Clear hierarchy with headers

Email Sequences¶

Personal, conversational tone
Specific value in subject line
Single CTA per email
Plain text preferred for deliverability

Proposals/SOWs¶

Professional, structured format
Clear scope and deliverables
Fixed pricing when possible
Outcome-focused language

LinkedIn: Authority + insight
Twitter/X: Quick takes, industry commentary
Avoid promotional content—educate instead

Competitor Positioning Language¶

vs. Traditional MSPs¶

"We're your advisor, not your vendor. MSPs profit from product sales—we profit from your success."

vs. Big 4 Consulting¶

"Enterprise expertise without enterprise pricing. Big 4 consultants charge $400-600/hour for juniors. You get senior advisors at $200-350/hour."

vs. Product Vendors¶

"We recommend what works, not what we sell. Because we don't sell anything."

vs. Solo Consultants¶

"Full team depth without the overhead. One consultant can't cover security, compliance, and strategy. We can."

vs. Traditional Dev Shops¶

"We understand your problem before we write code. Dev shops start billing from day one—we start advising. The code comes when it's the right answer."

vs. Product Companies¶

"Off-the-shelf means your process adapts to software. We build software that adapts to your process—because we understood it first."

Quality Checklist¶

Before publishing any content:

Innovate Pillar: Voice Guidelines¶

Key Messaging Principles¶

When discussing software development, process transformation, or custom solutions:

Always Lead with Advisory Context
Good: "After assessing your workflows, we identified three automation opportunities..."
Avoid: "We build custom software solutions..."
Tie to Business Outcomes
Good: "This workflow automation reduced compliance prep time by 60%"
Avoid: "We implemented an automated workflow system"
Position Build as Selective
Good: "When off-the-shelf fails, we build what fits"
Avoid: "We offer custom development services"
Maintain Vendor Neutrality
Good: "We recommended Salesforce. When it didn't fit, we built a custom CRM module"
Avoid: "We build better solutions than commercial products"

Development Context Phrases¶

Context	Phrase
Introducing Build Capability	"When the right solution doesn't exist, we build it"
Process Focus	"Technology should serve your process, not define it"
Advisory Bridge	"Advisory told us what you need. Now we build it."
Outcome Focus	"Measured by your metrics: revenue, compliance, satisfaction"
Selective Build	"We build because we advised it—not because we have developers to keep busy"

Anti-Patterns to Avoid¶

Avoid	Why	Better Alternative
"Our development team..."	Sounds like a dev shop	"When we build..."
"Custom software development services"	Commodity framing	"Purpose-built solutions"
"Full-stack development"	Technical focus over outcome	"End-to-end delivery"
"Agile/Scrum methodology"	Process jargon	"Iterative delivery with continuous feedback"
"We can build anything"	Over-promising, no selectivity	"We build what creates measurable value"

Last Updated: February 2026 Version: 1.1