Solanasis Docs

solanasis_offerings_pdf_questionnaire_v2

11 min read

Solanasis — Client Offerings PDF (1–2 pages) Questionnaire (v2)

Goal: You answer this once, then I generate a clean, no-flash, high-clarity 1–2 page PDF you can hand to clients (a “stripped-down website”).

How to fill this out (fast)

  • Each question has A pre-selected as the recommended default.
  • You can:
    1. Switch the selection by moving [x] to another option, and/or
    2. Add notes for any option, and/or
    3. Write a Custom / Override Answer (use this if none of the options fit, or if you want different wording).

Tip: If you’re in a hurry, just keep A for most questions and add notes/overrides where you care.

Section 0 — Basic identity (needed for the PDF header)

0.1 Company name (confirm)

  • A) Solanasis
  • B) Solanasis Solutions
  • C) Solanasis Group
  • D) Other: ______________________

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

0.2 Tagline / positioning line (pick one)

  • A) Operational Resilience, Proven.
  • B) Security, resilience, and operations—done right.
  • C) Make the messy stuff reliable.
  • D) Other (write your own)

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

0.3 Your “voice” for the PDF (tone + vibe)

  • A) Plainspoken, confident, slightly edgy, zero fluff (professional “field-notes” vibe)
  • B) Formal/corporate (risk & governance language)
  • C) Friendly/approachable (less intense)
  • D) Other

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

0.4 Words/phrases to avoid (so it doesn’t sound generic)

  • A) Avoid buzzwords; no “synergy,” “best-in-class,” “cutting edge,” “revolutionary,” “AI-powered everything”
  • B) Fine with standard consulting language
  • C) Lean heavily into security jargon
  • D) Other: ___________________________________

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

Section 1 — Audience + fit (controls the whole narrative)

1.1 Primary buyer / reader

  • A) Owner/CEO + Ops leader at an SMB/nonprofit
  • B) IT Manager / Sysadmin
  • C) Board / exec committee
  • D) Mixed audience

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

1.2 Ideal org size

  • A) 20–500 staff
  • B) 1–20 staff
  • C) 500–2,000
  • D) Any size

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

1.3 Primary client type

  • A) SMBs + mission-driven orgs/nonprofits
  • B) Only SMBs
  • C) Only nonprofits
  • D) Only regulated industries (health/finance)

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

1.4 Service area / delivery mode (important expectation-setting)

  • A) Mostly remote, on-site available as needed
  • B) Remote only
  • C) Local/on-site heavy (e.g., Colorado Front Range)
  • D) Other

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

1.5 “We are a great fit if…” (pick the strongest framing)

  • A) You want someone to find what will break, fix it, and prove it works
  • B) You need a security check-the-box assessment
  • C) You need a dev shop / app features
  • D) Other

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

1.6 “We’re not a fit if…” (prevents bad leads)

  • A) You want cheap/fast/hand-wavy work, or “set it and forget it”
  • B) You want 24/7 helpdesk + device support
  • C) You want a pentest-only vendor
  • D) Other

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

Section 2 — The core message (headline + outcomes)

2.1 One-line headline outcome for the PDF

  • A) Operational resilience: we find what will break, fix it, and prove it works.
  • B) Cybersecurity consulting for SMBs.
  • C) We modernize and integrate your systems.
  • D) Other

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

2.2 Top 3 outcomes clients get (choose the set that matches)

  • A) Fewer nasty surprises, faster recovery, clear operational control (runbooks + verification)
  • B) Compliance readiness and audit confidence
  • C) Faster shipping (dev velocity) and automation
  • D) Other

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

2.3 Top “pain statements” to include (pick the ones you want in the PDF)

  • A) “We have backups” but nobody has tested a restore
  • B) Migrations fail in slow motion
  • C) Integrations are fragile / undocumented / ‘magic’
  • D) AI tools got adopted with no guardrails
  • E) Leadership can’t get a straight answer about risk
  • F) Too many tools, too little ownership

Notes (optional):

  • Add/edit pains you want emphasized:

Custom / Override Answer (optional):

Section 3 — Offers (what you actually sell)

3.1 Offers to feature (choose one set)

  • A) Security assessment + DR verification; Data migrations; Systems integration & automation; Responsible AI guardrails; Production readiness
  • B) Security + resilience only
  • C) Integration + migrations only
  • D) Other bundle

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

3.2 Your “flagship” entry offer (the first thing you want them to buy)

  • A) Resilience & Security Baseline (fast diagnostic + roadmap + verification)
  • B) Fractional CISO retainer first
  • C) One-off pentest first
  • D) Custom project only

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

3.3 Baseline: pick the modules you want listed (choose ~4–7)

  • A) Backup/restore verification (real restore test)
  • B) Identity & access review (least privilege, admin sprawl)
  • C) Endpoint + SaaS posture snapshot (quick hardening targets)
  • D) Logging/monitoring reality check (what you can/can’t see)
  • E) Incident response readiness (roles, runbook, tabletop)
  • F) Vendor/tool sprawl audit + ownership mapping
  • G) Cloud/network exposure review (basic, practical)
  • H) AI usage inventory + guardrails plan
  • I) Compliance mapping (lightweight)

Notes (optional):

  • Any modules you want to add/remove or rename:

Custom / Override Answer (optional):

3.4 Baseline: what should it include?

  • A) Findings + prioritized roadmap + hands-on quick wins + verification tests
  • B) Findings + roadmap only
  • C) Hands-on only
  • D) Training/workshops only

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

3.5 After baseline: how do you structure ongoing work?

  • A) Baseline → Fix & Harden project(s) → Optional monthly operations retainer
  • B) Only projects (no retainer)
  • C) Only retainer
  • D) Only hourly

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

3.6 Fix & Harden project types to list (pick up to ~5)

  • A) Disaster recovery hardening + restore drills
  • B) Security hardening (identity, endpoints, SaaS, configs)
  • C) Migration planning + cutover rehearsal + execution
  • D) Integration cleanup (remove fragility, add observability, document)
  • E) “Production readiness” uplift (monitoring, backups, runbooks, ownership)
  • F) Responsible AI implementation (policies, guardrails, evals, rollout)
  • G) Tool rationalization (reduce spend + reduce risk)

Notes (optional):

  • Anything you want renamed / re-framed:

Custom / Override Answer (optional):

3.7 Monthly retainer: what does it cover? (pick 3–6)

  • A) Quarterly verification drills (restore/cutover checks)
  • B) Runbook + documentation upkeep
  • C) Risk register / backlog management + prioritization
  • D) Security monitoring / alert triage (lightweight)
  • E) Vendor/security reviews for new tools
  • F) On-call incident response availability
  • G) Automation/cleanup capacity (small improvements monthly)

Notes (optional):

  • Anything you do not want in a retainer:

Custom / Override Answer (optional):

Section 4 — Differentiation + proof (why Solanasis)

4.1 Implementation stance (your differentiator)

  • A) We don’t just advise—we do the hands-on work and leave it maintainable.
  • B) Strategy-only / advisory
  • C) Mostly subcontract
  • D) Mostly training

Notes (optional):

  • A notes:
  • B notes:
  • C notes:
  • D notes:

Custom / Override Answer (optional):

4.2 Your proof style

  • A) Verification-based proof (restore tests, dry runs, checklists, acceptance criteria)
  • B) Testimonials only
  • C) Certifications only
  • D) No proof section

Notes (optional):

  • Any specific proof artifacts you want highlighted (screenshots, runbooks, checklists):

Custom / Override Answer (optional):

4.3 Your core differentiators (choose up to 3)

  • A) “Prove it works” culture (restore tests, rehearsals, acceptance criteria)
  • B) Practical, non-theoretical engineering (no theater, no fluff)
  • C) Strong documentation/runbooks as a deliverable, not an afterthought
  • D) Security + operations combined (not siloed)
  • E) Responsible AI with guardrails (useful, defensible, maintainable)

Notes (optional):

  • Anything you want removed because it feels too generic:

Custom / Override Answer (optional):

4.4 Credibility block: what should we say about “who we are”?

  • A) Founder-led, senior engineering, small team, high accountability
  • B) Big-team vibe (even if subcontracted)
  • C) No team details; keep it purely offer-based
  • D) Other

Notes (optional):

  • If you want: list titles/roles (no names needed):

Custom / Override Answer (optional):

Section 5 — Delivery details (how it works in real life)

5.1 Process (how you work)

  • A) Discover → Map risk → Execute fixes → Verify → Document & handoff
  • B) Assess → report → leave
  • C) Agile dev sprints only
  • D) Other

Notes (optional):

  • Any step names you prefer:

Custom / Override Answer (optional):

5.2 “What you get” deliverables format

  • A) Executive summary + prioritized backlog + runbooks + verification results
  • B) Big formal report only
  • C) Tickets in Jira only
  • D) Loom videos only

Notes (optional):

  • Specific deliverables you always want included:

Custom / Override Answer (optional):

5.3 Typical tools/environments you’ll support

  • A) Meet you where you are (Google/M365; AWS/Azure; common CRMs; sane defaults)
  • B) Only Microsoft stack
  • C) Only Google stack
  • D) Only startups/dev teams

Notes (optional):

  • If you want to name tools you commonly touch (Okta, Google Workspace, M365, Azure AD/Entra, AWS, etc.), list here:

Custom / Override Answer (optional):

5.4 Access & security stance (important for trust)

  • A) Least-privilege access, read-only first, scoped creds, audit trail, NDA as needed
  • B) Whatever access is fastest
  • C) Client must grant full admin day 1
  • D) Not mentioned

Notes (optional):

  • Any non-negotiables (password managers, MFA, etc.):

Custom / Override Answer (optional):

5.5 Communication cadence (sets expectations)

  • A) Weekly update + shared backlog; async updates in between
  • B) Daily standups
  • C) “Reach out as needed”
  • D) Other

Notes (optional):

  • Preferred tools (email, Slack, Teams):

Custom / Override Answer (optional):

Section 6 — Pricing + timeline (qualification without overcommitting)

6.1 Pricing style shown in the PDF

  • A) Ranges by package + “final scope after baseline”
  • B) Starting-at prices only
  • C) No pricing in the doc
  • D) Hourly rates listed

Notes (optional):

  • If you want to include “starting at” language, specify it:

Custom / Override Answer (optional):

6.2 Typical budget bands (choose closest)

  • A) Baseline: 15k; Implementation: 75k; Retainer: 10k/mo
  • B) Baseline <20k; Retainer <$2k/mo
  • C) Baseline 30k; Implementation 10k+/mo
  • D) Unsure / varies wildly

Notes (optional):

  • If you want different numbers, paste them here:

Custom / Override Answer (optional):

6.3 Timelines (what you’re comfortable promising)

  • A) Baseline in 2–3 weeks; Implementation 4–8 weeks (scope-dependent)
  • B) Everything in 1 week
  • C) Everything in 3–6 months
  • D) Don’t state timelines

Notes (optional):

  • Any hard constraints (vacations, capacity, lead time):

Custom / Override Answer (optional):

Section 7 — Commitments, boundaries, and fit

7.1 What you explicitly don’t do (protects your positioning)

  • A) No commodity helpdesk; no “set it and forget it”; no magic integrations; no vague AI
  • B) “We do everything”
  • C) Don’t mention exclusions
  • D) Other

Notes (optional):

  • Add exclusions you want stated:

Custom / Override Answer (optional):

7.2 Commitments / guarantees (strong but not reckless)

  • A) Verification-based commitments (restore tests, cutover rehearsals, acceptance criteria)
  • B) Outcome guarantee (“no breaches”)
  • C) Satisfaction guarantee only
  • D) No commitments stated

Notes (optional):

  • If you want a specific guarantee line, paste draft text:

Custom / Override Answer (optional):

7.3 Client responsibilities (to make projects succeed)

  • A) One accountable owner, timely access/approvals, schedule key people, change control
  • B) Minimal client involvement
  • C) Client does most of the work
  • D) Not mentioned

Notes (optional):

  • Any “must-have” responsibilities:

Custom / Override Answer (optional):

Section 8 — Call to action + contact block (must be complete)

8.1 Call to action at the bottom

  • A) Book a 30‑min intro call + “We’ll tell you if we’re not the right fit.”
  • B) Email us for a quote
  • C) Buy now / checkout
  • D) Newsletter signup

Notes (optional):

  • If you have specific CTA wording, paste it:

Custom / Override Answer (optional):

8.2 Contact block contents

  • A) Website + email + booking link
  • B) Email only
  • C) Phone + email
  • D) All channels

Fill these in:

  • Website: ______________________________
  • Contact email: _________________________
  • Booking URL (intro call): _______________
  • Phone (optional): ______________________

Notes (optional):

  • Any preferred formatting (e.g., “hello@”, “social@”, etc.):

Optional (adds punch if you have it)

O.1 “Why Solanasis exists” origin lines (2–6 lines)

  • A) Use the raw/pro style (“Because ‘probably fine’ is not a security plan…”)
  • B) Standard corporate mission statement
  • C) Skip this section

Paste your lines (optional):

O.2 Case studies (can be anonymized)

  • A) Problem → what you did → measurable result
  • B) Vague testimonial only
  • C) None yet

Case Study 1:

  • Client type (anonymous): __________________________
  • Problem: ________________________________________
  • What we did: _____________________________________
  • Result (numbers if possible): _____________________

Case Study 2:

  • Client type (anonymous): __________________________
  • Problem: ________________________________________
  • What we did: _____________________________________
  • Result (numbers if possible): _____________________

O.3 Constraints / preferences I should respect in the PDF

  • Industries to avoid: ______________________________
  • Compliance needs (if any): ________________________
  • Preferred wording / banned phrases: _______________
  • Anything else: ___________________________________

Graph View

Backlinks