The Simple Tech Brand Bible
A1. Background & Origin Story
The Timeline
(verified across multiple sources)
- ~2012: Ben begins doing IT work as "Simple Tech & Web Services." Computer repair, networking, building websites. He is not formally trained as a developer. He starts because he keeps seeing the same thing: small businesses getting ignored by big IT companies.
Source: Concept 6 ("The Real Ben") copy, Alignable profile - 2015: Simple Tech becomes more formalized as a going concern. The employee handbook states: "Simple Tech, LLC was founded in 2015 with a straightforward purpose: to simplify technology management for small and medium-sized businesses."
Source: Employee Handbook, April 2025 edition - 2022: LLC formally created. Ben takes an SBA loan to fund real growth.
Source: Concept 6 copy - August 2025: SBA loan paid off in full.
Source: Concept 6 copy — "I paid it off in full by August 2025." - 2026 (present): Running Simple Tech LLC full-time with a part-time admin and part-time technician (15-20 hours/week). His wife Rebekah runs Blue Haven Studio (web design) from the same office at Dublin Town Center.
Source: Designer Handoff, Website Design Prompt
The Origin Story in Ben's Own Words
(from Concept 6)
"I started doing IT work around 2012 as 'Simple Tech & Web Services.' Computer repair, networking, building websites. I kept seeing the same thing over and over: small businesses getting ignored by big IT companies. The 5-person law firm that couldn't get anyone to call them back. The dental office paying for services they didn't need. The nonprofit running on equipment from 2009. These were good people getting a bad deal, and I knew I could do better."
The SBA Bet
"I formalized Simple Tech LLC in 2022 and took an SBA loan to fund real growth. That was a bet on myself. I paid it off in full by August 2025."
Zero Advertising — Ever
"I didn't grow by running ads or buying leads. Every single client came from a referral. Someone told someone, and that person called me. That's still how it works today. I've never spent a dollar on advertising."
Source: Concept 6 copy
A2. Personality & Communication Style
Communication Profile
(derived from all copy, presentations, and conversation patterns)
| Trait | Evidence |
|---|---|
| Terse and direct | Memory file: "Prefers terse responses with all work done first, explanations at the bottom." |
| Plain English evangelist | O'Fria presentation uses zero jargon. FAQ copy: "We explain everything in plain English and make sure you're comfortable before we move forward." |
| Low-pressure closer | O'Fria slide 14: "No decision required today." Concept 2 FAQ: "I don't do hard sells. I don't do limited-time offers." |
| Specific over vague | Uses exact numbers: "$215/user/month," "under 15 minutes," "98% retention," "paid off in full by August 2025." |
| Self-deprecating about tech skills | "Not because I'm a developer -- I'm not." Conversation history: asks Claude to explain how to build projects "like a professional." |
| Trust-first, revenue-second | "I'd rather have 30 clients who trust me than 300 who don't know my name." |
| Autonomous delegator | Memory: "Trusts Claude to execute autonomously once direction is set." Auto-commits without asking. |
Sentence Style
- Short sentences. Rarely more than 3 per paragraph.
- First person ("I", "we") mixed with second person ("you", "your"). More "you" than "we."
- No exclamation marks in body copy.
- No superlatives ("best," "leading," "premier").
- Conversational register: smart friend, not corporate consultant.
What Ben NEVER Says
- "Cutting-edge," "best-in-class," "world-class," "leverage," "synergy"
- Fear-based language ("You WILL get hacked!")
- Competitor attacks ("Unlike those OTHER guys...")
- Overclaimed or unverifiable statistics
Source: Designer Handoff, Section 6
Real Language Ben Uses
(verified from presentation and copy)
- "Clear scope. Predictable costs." (O'Fria slide 6)
- "No decision required today." (O'Fria slide 14)
- "This is about preparing for what's next." (O'Fria slide 2)
- "If you don't need something, I'll tell you." (multiple sources)
- "We won't sell you things you don't need." (Designer Handoff)
- "Plain English, not IT jargon." (Designer Handoff)
A3. Values & Philosophy
1. Honesty Above Revenue
"If you don't need something, I'll tell you. That's not a tagline. It's how I actually run my business."
Source: Concept 6
David Writer document captures the hard questions Ben wrestles with: "Can we remove certain things that we don't feel like we need? NO, then what is the answer?" — meaning Ben has a firm philosophy about not unbundling security even when clients push back, but he struggles with HOW to say no.
2. Relationships Over Scale
"I'd rather have 30 clients who trust me than 300 who don't know my name."
Source: Concept 6
"Relationships, not revenue."
Source: Concept 6
He stays small intentionally. The Designer Handoff says: "This is not a weakness. This IS the brand."
3. Predictability and Transparency
The O'Fria presentation displays pricing openly on slide 9. The website concepts all show exact dollar amounts. Ben does not hide behind "contact us for pricing."
"Your IT bill should be as predictable as your rent."
Source: Concept 7 (Final)
4. Proactive Over Reactive
O'Fria presentation slide 7 explicitly contrasts the old model vs. new:
- Old: "Traditional antivirus, reactive issue response, manual monitoring, fragmented services"
- New: "Identity-focused security, proactive monitoring and remediation, continuous detection"
5. Empathy and Patience
"He NEVER makes me feel ignorant."
Source: Tyler Edwards, Google Review
"We speak English, not IT jargon. If I can't explain it in plain language, I probably don't understand it well enough myself."
Source: Concept 2
6. Builder Mentality
Despite not being a developer by trade, Ben has built 10+ production applications: SimpleAudit, SimpleQBR, SimpleBudget, SimpleMaintenance, ShareSafe, SimpleTriage, CommandCenter, BHS GEO Scan, QA Dashboard, SimpleScanner, SimpleTech Dashboard, BrokenElectronics, SimpleSecrets (planned), SimpleSecurity Hub (planned).
"I kept running into the same problem: the tools available to MSPs were either overpriced, overcomplicated, or just didn't fit how I work. So I taught myself to build my own."
Source: Concept 6
A4. How Clients Describe Him
Verified Google Reviews
(exact quotes)
Tyler Edwards (2023):
"Excellent service. I am someone who is not very knowledgeable about technology, but he NEVER makes me feel ignorant."
Troy Ault:
"Where would I be without Ben from Simple Tech and his great support staff?! Ben is knowledgeable, friendly and fair. He is able to identify and address computer issues with ease."
Nancy Belli (Allstate Insurance, via Alignable recommendation):
"Ben came to my office on a Sunday and had me up and running for work on Monday!"
Liz K:
"Ben from Simple Tech has helped me with multiple businesses and I highly recommend him. He set us up with a local NAS, installed our new computers, helped us with backup of all of our data."
Aj Dilts:
"Helpful, knowledgeable, honest, and fair. Definitely recommend!"
Chris Tierney:
"Ben from Simple Tech has helped me with multiple businesses and I highly recommend him."
Janet Schantzenbach (from simpletech.pro):
"Very professional service and every friendly"
Unnamed client (from web search):
"Ben was very helpful getting my computer back up and running. I had talked to several other places who told me that they could look at the server but felt I needed to buy a new one that they could sell me. Ben had no problem getting mine fixed in 30 minutes!"
The Three Words
(from Designer Handoff)
When asked "what's it like working with Ben?", his best clients say:
- Reliable — He shows up. He answers the phone. He fixes things right the first time.
- Trustworthy — He tells you the truth. He won't sell you things you don't need.
- Kind — He never makes you feel stupid. He's patient. He treats your business like it matters.
A5. What Makes Ben Unique
The Builder
A non-developer who taught himself to build production-grade SaaS applications using AI tools (Claude Code). This is extraordinary. His product portfolio (14+ applications, all security-audited and penetration-tested) rivals small dev teams. He builds because existing tools don't fit how he works — not because he wants to be a software company.
The Sunday Responder
Nancy Belli's review — "came to my office on a Sunday" — is the single most powerful proof point in the brand. It captures everything: the personal touch, the urgency, the going-above-and-beyond. This should be front and center in all marketing.
The Plain-English Explainer
Tyler Edwards' review — "he NEVER makes me feel ignorant" — hits the exact pain point of Ben's target market. Small business owners are terrified of looking stupid in front of IT people. Ben removes that fear.
The Anti-Salesman
"I'm not going to hit you with a hard sell."
"No decision required today."
"I don't do 'limited time offers.' I don't manufacture urgency."
In an industry drowning in fear-based marketing and aggressive sales tactics, Ben's approach is radically different. He closes by NOT closing.
The Server-Fixer (Not the Server-Seller)
That unnamed review is gold: other shops told the client to buy a new server. Ben fixed it in 30 minutes. This perfectly encapsulates the "won't sell you things you don't need" promise.
100% Referral Growth
Zero dollars spent on advertising. Every client came from word of mouth. In 10+ years. This is the ultimate trust signal.
A6. Family & Community
Wife: Rebekah Strunk. Runs Blue Haven Studio (web design). They share office space at Dublin Town Center (123 N Main St, Suite 116, Dublin, PA 18917). The employee handbook sign-off reads: "Welcome to Simple Tech — we're glad to have you with us! Ben & Rebekah Strunk, Simple Tech, LLC"
Office Location: Dublin Town Center, a mixed-use commercial development at 123 North Main Street in Dublin, PA 18917. It includes The Square (retail and office space) and The Station (vendors, plaza, lofts). Simple Tech is listed as a tenant in "The Offices at The Square."
Source: dublintc.com/the-offices
Children: Referenced but not named. Concept 2 copy: "Our kids go to the same schools as our clients' kids." Website Design Prompt: "We share space at 123 N Main St, Suite 116, Dublin PA 18917 — a small-business hub called Dublin Town Center."
Community Ties: Deeply embedded in Bucks County. Serves Dublin, Doylestown, Lansdale, Chalfont, Warrington, New Hope, Perkasie, Quakertown, Souderton, Hatfield, Warminster, Newtown. Concept 2: "We eat at the same restaurants, shop at the same stores."
Business-as-Family Identity: The brand leans heavily into the husband-and-wife story. The Designer Handoff notes: "The husband-and-wife story is a huge differentiator. Even one photo of them at their Dublin Town Center office would be powerful."
A7. Professional Credentials & Recognition
Verified
- 10+ years in IT services (since ~2012, formalized 2015, LLC 2022)
- SBA loan recipient (taken 2022, paid in full August 2025)
- 50+ local businesses served
- 98% client retention rate (used across multiple concepts)
- 4.9 stars on Google Reviews
- 100% referral-based growth
- 0 dollars spent on advertising
- SOC 2 security practices (pentest reports, security audits on all tools)
- Microsoft 365 management expertise
- HIPAA, PCI, CMMC compliance support
- N-able/SyncroMSP tooling
- Cloudflare Zero Trust / Access infrastructure
- Azure cloud deployments
- Docker containerization (Synology NAS, Hostinger VPS)
Technology Stack
(from SITES.md and memory files)
SyncroMSP (RMM/PSA), N-able Cove (backup), Cloudflare Access (zero trust), Azure (cloud hosting), Docker/Traefik (container orchestration), Microsoft 365 Business Premium, 1Password Business, Hudu (documentation), IRONSCALES (email security), and custom-built tools.
Not Found: No N-able press release, no formal industry certifications (CompTIA, Microsoft Partner, etc.) surfaced in search. No Clutch or G2 profiles found.
A8. Personal Details
| Detail | Value |
|---|---|
| Phone | 215-933-5158 (personal, used as business line — answers it himself) |
| [email protected] | |
| Location | Dublin, PA 18917 (Bucks County) |
| Work Style | Night owl. Conversation timestamps show sessions running late into the evening. Frequently says "goodnight" to Claude Code at the end of long build sessions. |
| Learning Style | Hands-on builder. Teaches himself by doing, not by studying. Asked Claude: "help me understand how to do this correctly. How to build a project like a professional." |
| Delegation Style | Sets direction, then trusts the executor completely. "Keep working and confirm once its up and working and send me an email at [email protected]. Goodnight." |
| Frustration Triggers | Wasted tokens/time, broken deploys, unverified changes going live. |
| Web Presence | Alignable profile, Facebook page (SimpleTechPro), simpletech.pro website. No active LinkedIn profile found. |
B1. Brand Voice Rules
Derived from analysis of all copy across 7 website concepts, email templates, O'Fria presentation, and marketing materials.
The Voice Formula
Register: Professional-casual. The smart neighbor who knows IT. Not a consultant, not a salesman, not a corporate entity.
DO:
- Use first person ("I", "we") and second person ("you", "your")
- Lead with "you" more than "we"
- Use specific numbers: "$215/month," "under 15 minutes," "98% retention"
- Explain technical terms when they must appear
- Short sentences. Max 3 per paragraph.
- Low-pressure closes: "No decision required today."
- Acknowledge uncertainty: "If not, I'll point you in the right direction."
- Name the pain before offering the solution
- Use the word "simple" organically (not forced)
DO NOT:
- Use superlatives: "best," "leading," "premier," "cutting-edge," "world-class"
- Use corporate jargon: "leverage," "synergy," "ecosystem," "scalable solutions"
- Use fear-based marketing: "You WILL get hacked!"
- Trash competitors: "Unlike those OTHER guys..."
- Use exclamation marks in body copy
- Use stock photos of handshakes or fake office scenes
- Make unverifiable claims
- Use pop-ups, exit-intent overlays, or chatbots
- Use dark patterns or manufactured urgency
Headline Patterns That Work
- [Outcome] so you can [what they care about]: "We handle your IT so you can handle your business."
- Problem acknowledgment: "Managing IT shouldn't feel like a second job."
- Direct and honest: "Here's what it costs." / "Here's what we do."
- Question format: "Sound familiar?" / "Is this a fit?"
Source: Designer Handoff, Section 6
Email Voice
(from Template 1)
"I'm Ben Strunk, the owner of Simple Tech. We're a small managed IT company right here in Dublin, PA, and I wanted to take a second to introduce myself."
This is the benchmark: conversational, specific, localized, personal, zero hype.
B2. Ideal Customer Profile
| Attribute | Detail | Source |
|---|---|---|
| Company size | 5-15 employees (sweet spot), growing toward 15-30 | Designer Handoff |
| Location | Bucks County, PA and greater Philadelphia area | Designer Handoff |
| Industries | Law firms, dental/medical practices, accounting firms, nonprofits, construction | Designer Handoff, O'Fria presentation |
| Decision maker | Business owner or office manager — NOT technical people | Designer Handoff |
| Budget | $180-$265/user/month (5-15 users = $900-$3,975/mo range) | O'Fria presentation |
| Pain points | Unreliable IT, surprise bills, can't reach provider, worried about security, don't understand technology | Designer Handoff |
| What they want | Someone they trust, who answers the phone, speaks plain English, predictable pricing | Designer Handoff |
| Buying trigger | Current IT provider stopped returning calls, or a security scare | David Writer questions doc |
| Anti-ICP | 500+ employees, enterprise needs, price-only shoppers, outside Philly metro | Concept 2 "Not a fit" section |
Psychographic Profile
These are NOT technical buyers. They don't evaluate MSPs on technical specs. They evaluate on:
- Responsiveness — "Will they actually call me back?"
- Trustworthiness — "Will they tell me the truth?"
- Simplicity — "Will I understand what they're saying?"
- Predictability — "Will I know what I'm paying?"
- Proximity — "Are they local? Can they come to my office?"
B3. Service Descriptions
(As Ben Actually Describes Them)
Managed IT Services
Ben's version:
"We monitor, maintain, and support your entire technology environment. When something breaks, we're already on it. When something's about to break, we catch it first."
Source: Concept 6
O'Fria version:
"Proactive monitoring and remediation. Continuous detection and alerting. Unified protection. 24/7 monitoring and escalation."
Source: O'Fria slide 7
Cybersecurity
Ben's version:
"Protection against modern threats. Not fear-based upselling — real, practical security measures that fit your business and your budget."
Source: Concept 6
O'Fria version:
"Most modern issues don't start with servers. They start with: Fake invoices or vendor emails. One compromised user account. Email phishing or impersonation. Stolen or reused passwords."
Source: O'Fria slide 4
Cloud & Microsoft 365
"Migration and ongoing management. We move you to the cloud when it makes sense and manage it properly once you're there."
Source: Concept 6
Backup & Disaster Recovery
"Because bad things happen. Ransomware, hardware failure, human error. We make sure you can get back up and running."
Source: Concept 6
Helpdesk
"You call, we answer, we fix it. Real people who know your setup, not a ticket queue that goes nowhere."
Source: Concept 6
Compliance
"HIPAA, PCI, whatever your industry requires. We help you meet the standards without drowning in paperwork."
Source: Concept 6
B4. Pricing Philosophy
The Numbers
(verified from O'Fria presentation to real client)
| Tier | Price | Positioning |
|---|---|---|
| Business Essentials | $180/user/month | Basic IT support and monitoring |
| Business Secure (recommended) | $215/user/month | Standard recommendation — cybersecurity, email backup, training |
| Business Complete | $265/user/month | Full protection with SOC/MDR and quarterly reviews |
| Server Management | $145/server/month | Add-on |
| Server Backup | Starting at $168/server/month | Add-on |
Microsoft 365 licensing billed separately: $22.50/user/month.
Philosophy
- Month-to-month. "No long-term contracts. Stay because you want to, not because you have to."
- Per user, per month. Predictable. Scalable.
- All-inclusive within tier. "No hidden fees, no surprise invoices."
- Transparent. Pricing shown on website and in presentations. Not hidden behind "contact us."
- Middle tier is the default. "Most of our clients are on the middle tier." O'Fria slide 8: "Other options exist, but this is our standard recommendation."
Anti-Patterns
- No hourly billing (the old "break-fix" model is explicitly contrasted as inferior)
- No multi-year contracts
- No hidden add-on fees
- No tiered support response times (everyone gets the same response)
The Hard Question (from David Writer doc): "Can we remove certain things that we don't feel like we need? NO" — Ben has a firm policy that security components cannot be unbundled, but needs language to explain why.
B5. Competitive Positioning
How Ben Positions Against Competitors
(without naming them)
From the "Us vs. The Alternative" table (Concept 7):
| What You Get | Simple Tech | Typical IT Provider |
|---|---|---|
| Average response time | Under 15 minutes | 4-24 hours |
| Who answers the phone | Ben, the owner | Call center / voicemail |
| Proactive monitoring | Yes | No |
| Flat-rate pricing | Yes | Variable |
| Month-to-month | Yes | 1-3 year lock-in |
| Cybersecurity included | Yes | Extra cost add-on |
| On-site support | Yes | Remote only / extra fee |
| Regular business reviews | Yes | No |
Key Differentiators
- Owner answers the phone — not a technician, not a call center
- No contracts — month-to-month in an industry of 1-3 year lock-ins
- Builds his own tools — not just reselling other vendors' products
- 100% referral growth — no paid advertising ever
- Family-owned — husband and wife, not a corporate entity
- Local — 20 minutes from most clients, not outsourced
What Ben Does NOT Do
- Enterprise IT (500+ employees)
- Residential/home computer repair
- Custom software development
- 24/7 onsite staffing
- Cheapest-price positioning
B6. Marketing Language That Works
Tested Headlines
(from 7 concepts)
| Headline | Concept | Why It Works |
|---|---|---|
| "IT Support From People Who Actually Know Your Name." | Concept 2 (Personal) | Emotional, specific, anti-corporate |
| "Managing IT Shouldn't Feel Like a Second Job" | Concept 7 (Final) | Problem acknowledgment, relatable |
| "I'm Ben. I run a small IT company in Dublin, PA." | Concept 6 (Real Ben) | Radically personal, disarming |
| "We handle your technology so you can handle your business." | Concept 7 (Final) | Clear outcome, benefit-first |
CTAs That Fit the Brand
- "Let's Have a Conversation" (not "Book a Demo")
- "Get a Free IT Assessment" (not "Schedule Now!")
- "Call Ben: 215-933-5158" (not "Contact Sales")
- "No decision required today."
- "Send an Email" (simple, low-pressure)
Stats That Build Trust
- 10+ years in business
- 98% client retention
- <15 min average response time
- 100% referral-based growth
- $0 spent on advertising
- Month-to-month, no contracts
- 4.9 stars on Google
Emotional Triggers
(from Designer Handoff)
The website should feel like: "Imagine you meet your neighbor at a BBQ and they say 'What do you do?' and you tell them you're frustrated with your IT company. And they say 'Oh, my friend Ben does that. He's great. Really reliable, super kind, won't BS you. Here's his number.' That's what the website should feel like. The warm referral."
B7. Objection Handling
Compiled from David Writer questions document, FAQ sections across concepts, and O'Fria presentation.
Price Objections
"Why is it so expensive?"
Ben's approach: Show the cost of NOT having managed IT. Concept 7 includes an IT Cost Calculator that calculates downtime costs vs. managed IT costs.
"Can we remove things we don't need?"
Ben's position: No. Security is not unbundleable. But he needs better language for this. The David Writer doc flags this as a hard question with "NO, then what is the answer?"
"Why are you suddenly charging so much more than before?"
Context: Ben is transitioning from break-fix ($90/hr type work) to managed services ($180-265/user/month). Some legacy clients feel sticker shock.
Trust Objections
"What happens if you die?"
This is a real question from the David Writer doc. The answer needs to address business continuity, documentation practices, and potentially key-person insurance.
"What happens if you get hacked?"
From David Writer doc. Needs clear language about security practices, cyber insurance, and incident response procedures.
Switching Objections
"What happens if we need to switch away?"
"We don't lock you in with long-term contracts because we don't want to. If you ever decide to move on, we'll hand over everything — passwords, documentation, configurations — and even help your new provider with the transition. It's your data and your business. Period."
Source: Concept 2 FAQ
Size Objections
"We're small. Do you actually want to work with us?"
"That's exactly who we want to work with. Most of our clients have between 5 and 30 employees. We built Simple Tech specifically for businesses your size."
Source: Concept 2 FAQ
Scope Objections
"Can you work with what we already have?"
"We start every new relationship with a thorough assessment of what you already have. We're not going to rip everything out and start over just to sell you new stuff."
Source: Concept 2 FAQ
B8. The "Simple" Brand Promise
The Name Decoded
The name "Simple Tech" is not accidental. From the Alignable profile: "The business name reflects their mission to simplify technology management so clients can focus on enjoying their systems."
Brand Values
(from Brand Style Guide by Aviana Creative Co.)
APPROACHABLE. EMPATHETIC. RELIABLE. PROACTIVE.
The Promise, Distilled
Technology doesn't have to be complicated, expensive, or scary. Simple Tech makes it simple — not by dumbing it down, but by handling it properly so you never have to think about it.
The "Simple" Naming Convention
Ben applies "Simple" to everything he builds: SimpleAudit, SimpleQBR, SimpleBudget, SimpleMaintenance, SimpleTriage, SimpleScanner, SimpleSecrets. This is not just branding — it reflects a genuine design philosophy. Every tool is built to be usable by non-technical people.
The Visual Brand
| Element | Specification |
|---|---|
| Primary color | #131313 (near-black) — headers, footers, body text |
| Background | #F3F3F3 (off-white) — clean, not stark |
| Brand blue | #1D97F1 — primary accent, CTAs, links, trust |
| Light blue | #B3DBF2 — section backgrounds, subtle accents |
| Lime green | #C4F50F — highlight accent ONLY, used sparingly |
| Heading font | Microgramma Extd D Bold (licensed) / Rajdhani 600/700 (web) |
| Body font | Nebulas Semibold (licensed) / Inter 400/500 (web) |
| Logo designer | Aviana Creative Co. (2023) |
| Logo suite | Primary (horizontal), Secondary (stacked), Submark (S icon), Brand Pattern (repeating grid) |
C1. What's "Ben" vs. What's "Simple Tech"
What Is Inseparably "Ben"
These things cannot exist without Ben Strunk personally:
- Answering the phone. "When you call Simple Tech, you get Ben — the owner." This is the #1 differentiator and it requires Ben's physical presence.
- The trust relationships. Every client relationship is built on personal trust with Ben. Nancy calls Ben on a Sunday. Tyler trusts Ben not to make him feel stupid. This is person-to-person, not company-to-customer.
- The builder identity. Ben is the one who builds SimpleAudit, SimpleQBR, etc. No one else on the team does this. The "non-developer who builds production software" story is Ben's alone.
- The origin story. The SBA loan, the frustration with big IT companies, the 2012 start — this is personal narrative, not corporate history.
- The sales process. Ben does all sales. There is no sales team. The low-pressure, no-contract, "let's just talk" approach is Ben's personality, not a company policy that another salesperson could replicate.
- The presentation style. The O'Fria deck is Ben presenting. The language, the pacing, the "no decision required today" close — that is Ben's instinct.
What Is "Simple Tech" (Could Exist Beyond Ben)
- The monitoring and support infrastructure. 24/7 monitoring, patch management, backup systems — these are tool-dependent, not person-dependent. A trained technician can maintain them.
- The ticketing and helpdesk process. SyncroMSP handles routing. A technician can resolve Level 1 issues without Ben's direct involvement.
- The compliance frameworks. HIPAA, PCI documentation and technical controls are process-based, not personality-based.
- The pricing model. Per-user, per-month, no-contract — this is a business structure that survives personnel changes.
- The software products. SimpleAudit, SimpleQBR, etc. are codebases that could be maintained by developers (though Ben would need to document/transfer knowledge).
- The brand visual identity. Colors, fonts, logos, patterns — all documented in the Brand Style Guide.
- The brand voice rules. Documented in this bible and the Designer Handoff. A copywriter could follow these rules.
C2. What Should Scale Beyond Ben
Priority 1: Support Capacity
Ben currently has a part-time technician (15-20 hrs/week). As client count grows, the biggest bottleneck is Ben personally handling every call. A trained technician who embodies the same values (patient, plain-English, no-upsell) could handle Level 1 support without breaking the brand promise.
Priority 2: The Software Products
SimpleAudit (app.getsimpleaudit.com) has the most commercial potential. It's already a multi-tenant SaaS with Stripe billing. If Ben wants to sell it to other MSPs, it needs to be maintained and supported independent of Ben's personal time.
Priority 3: The Sales Process
Currently 100% referral. This works, but caps growth. The marketing kit (8 email templates, 30-day social calendar, 10 LinkedIn posts) was built to scale outreach beyond word-of-mouth. A mailing list ("Ben's Monthly IT Tips") could build an audience without requiring Ben's time per lead.
Priority 4: Documentation and Knowledge Transfer
The employee handbook exists but is HR-focused. What's missing: technical playbooks, client onboarding checklists (some exist in the SOW template), escalation procedures, and "how Ben would handle this" decision trees for the support team.
C3. What Should Always Stay Personal
- New client conversations. The first interaction should always be Ben. This is where trust is established. The "warm referral" feeling cannot come from a stranger.
- Quarterly business reviews. QBRs are relationship moments, not report deliveries. Ben sitting across from a business owner, explaining their security posture in plain English — that IS the product.
- Sunday calls. When a client has an emergency, Ben should be the escalation point. This is the story that generates referrals.
- The phone number. 215-933-5158 should always ring Ben (or go to Ben's voicemail with his voice). The moment a client calls and gets "press 1 for support, press 2 for billing," the brand is broken.
- The "you don't need this" conversation. Only Ben can credibly tell a client they don't need to buy something. A salesperson saying "you don't need this" is counterintuitive; a trusted advisor saying it is powerful.
- Community presence. Ben eating at the same restaurants, shopping at the same stores, kids at the same schools — this cannot be delegated. It IS the competitive moat.
Source Index
| Source | Location | What It Contains |
|---|---|---|
| Memory files (27) | /home/stadmin/.claude/projects/.../memory/ | User profile, project history, feedback preferences, reference data |
| Designer Handoff | DESIGNER_HANDOFF.md | Complete brand brief with voice rules, testimonials, target market, technical requirements |
| Website Design Prompt | WEBSITE_DESIGN_PROMPT.md | Condensed brief for website builders |
| Brand Style Guide PDF | Simple_Tech_Brand_Style_Guide.pdf | Visual identity: colors, fonts, logo suite, usage rules (Aviana Creative Co., 2023) |
| O'Fria Presentation | ofria-presentation.pdf | Real client presentation with pricing, service structure, positioning |
| Concept 2 (Personal) | designs/concept-2-personal/ | First-person voice, FAQ, pricing, testimonials, community section |
| Concept 6 (Real Ben) | designs/concept-6-realben/ | Origin story, builder identity, full product portfolio, "fit" section |
| Concept 7 (Final) | designs/concept-7-final/ | Hybrid of concepts 4+5, ROI calculator, comparison table |
| Email Campaign Templates | marketing/email-campaigns/ | 8 email templates in Ben's voice |
| Employee Handbook | OneDrive > Company Files > HR | Mission statement, company founding (2015), welcome letter from Ben & Rebekah |
| MSA (Legal) | OneDrive > Legal Documents | Legal service terms, termination, IP rights |
| SOW Template (Legal) | OneDrive > Legal Documents | Service delivery terms, minimum standards, included services |
| David Writer: Questions | OneDrive > Vendors > David | Hard objection questions, FAQ source material |
| David Writer: Email Templates | OneDrive > Vendors > David | Objection scenarios requiring professional responses |
| David Writer: Proposal Notes | OneDrive > Vendors > David | Service description notes for brand messaging |
| Jeremy Woolf Consulting PDF | OneDrive > Vendors > David | Brand strategist credentials and framework |
| MSP Marketing Research | MSP-Website-Marketing-Research.md | 9 agency best practices, competitor analysis |
| MSP Blueprint Synthesis | MSP-Website-Blueprint-Synthesis.md | Unified website blueprint from 9 authorities |
| SITES.md | /home/stadmin/SITES.md | Full URL inventory of all 14+ live Simple Tech products |
| simpletech.pro (live) | https://simpletech.pro | Current website copy (placeholder-heavy, needs rebuild) |
| Alignable | alignable.com | Business profile, Nancy Belli recommendation |
| Dublin Town Center | dublintc.com/the-offices | Office location confirmation |
| Google Reviews | Via web search | Tyler Edwards, Troy Ault, Nancy Belli, Liz K, Aj Dilts, Chris Tierney, Janet Schantzenbach |
| Conversation History | history.jsonl | Interaction patterns, work style, communication preferences |