Solanasis — Client Offerings One-Pager (PDF) Builder Questionnaire
Use this file to answer the essential questions I need to generate a tight 1–2 page PDF you can leave with clients (a “stripped-down website”).
How to use
- For each question, A is pre-selected as the recommended default.
- Change selections by moving the
[x]to your chosen option (leave others as[ ]). - Fill in any blanks where requested.
- Re-upload this file with your answers.
1) Who is this doc “for” (primary buyer)?
Why this matters: Sets tone, language, and what benefits we emphasize.
- A) Owner/CEO + Ops leader at an SMB/nonprofit (they feel risk + chaos personally)
- B) IT Manager / Sysadmin (hands-on, tool-focused)
- C) Board / exec committee (risk + governance)
- D) Mixed audience
2) Ideal client size
Why this matters: Keeps the promises, examples, and pricing believable.
- A) 20–500 staff (small enough to be messy, big enough to pay)
- B) 1–20 staff
- C) 500–2,000
- D) Any size
3) Primary client type
Why this matters: Tight positioning without shrinking your pipeline too much.
- A) SMBs + mission-driven orgs/nonprofits
- B) Only SMBs
- C) Only nonprofits
- D) Only regulated industries (health/finance)
4) The “one-line” outcome you want prospects to remember
Why this matters: This becomes the headline of the PDF.
- A) “Operational resilience: we find what will break, fix it, and prove it works.”
- B) “We do cybersecurity consulting.”
- C) “We modernize your tech stack.”
- D) “We build automations and AI.”
5) Your top 3–5 offerings to feature
Why this matters: This is the “menu” clients will remember.
- A) Security assessment + DR verification; Data migrations; Systems integration & automation; Responsible AI guardrails; Production readiness
- B) Security + DR only
- C) Integrations + migrations only
- D) AI + automation only
6) Your “flagship” entry offer (the first thing you want them to buy)
Why this matters: Makes the PDF actionable and converts interest into a first engagement.
- A) “Resilience & Security Baseline” (fast diagnostic + roadmap + verification)
- B) Ongoing fractional CISO retainer first
- C) One-off penetration test
- D) Custom project only
7) What should the flagship include?
Why this matters: Defines what’s “in” and prevents scope creep.
- A) Findings + prioritized roadmap + hands-on quick wins + verification tests
- B) Findings + roadmap only
- C) Hands-on work only
- D) Training/workshops only
8) How you want to structure the rest of your offers
Why this matters: Builds a clean value ladder (and optional recurring revenue).
- A) Baseline → Fix & Harden project(s) → Optional monthly operations retainer
- B) Only projects (no retainer)
- C) Only retainer
- D) Only hourly
9) Your implementation stance (trust signal)
Why this matters: Differentiates you from “advice-only” consultants.
- 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
10) What “proof” do you want in the doc?
Why this matters: Proof converts skeptics. Verification is your edge.
- A) Verification-based proof (restore tests, dry runs, checklists, acceptance criteria)
- B) Testimonials only
- C) Certifications only
- D) No proof section
11) Your core differentiators (pick the closest)
Why this matters: “Why you” in one tight block.
- A) Verification culture: backups restored, migrations rehearsed, integrations observable, AI guarded
- B) Lowest price
- C) Biggest team
- D) Niche tech specialty only (e.g., Microsoft/AWS-only)
12) Your process (how you actually work)
Why this matters: Helps clients feel the work will be controlled and professional.
- A) Discover → Map risk → Execute fixes → Verify → Document & handoff
- B) Traditional consult: assess → report → leave
- C) Agile dev sprints only
- D) Ad hoc
13) “What you get” deliverables format
Why this matters: Clients want artifacts they can keep using.
- A) One-page executive summary + prioritized backlog + runbooks + verification results
- B) Big formal report only
- C) Tickets in Jira only
- D) Loom videos only
14) Typical tools/environments you’ll support
Why this matters: Reduces sales friction while letting you standardize.
- 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
15) Your “line in the sand” on access & security
Why this matters: Signals maturity and reduces client anxiety about giving access.
- 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) No special stance mentioned
16) Pricing style for the PDF
Why this matters: Helps qualify leads without boxing you in.
- A) Ranges by package + “final scope after baseline”
- B) Starting-at prices only
- C) No pricing in the doc
- D) Hourly rates listed
17) Your typical budget bands (choose closest)
Why this matters: Sets expectations and avoids mismatched leads.
- A) Baseline: 15k; Implementation: 75k; Retainer: 10k/mo
- B) Baseline <20k; Retainer <$2k/mo
- C) Baseline 30k; Implementation 10k+/mo
- D) Unsure / varies wildly
18) Typical timelines you want to promise
Why this matters: “How fast” is a huge buying factor—keep it believable.
- A) Baseline in 2–3 weeks; Implementation 4–8 weeks (depending on scope)
- B) Everything in 1 week
- C) Everything in 6 months
- D) No timelines stated
19) What you explicitly don’t do
Why this matters: Saying “no” strengthens your positioning and reduces bad-fit leads.
- A) No commodity helpdesk; no “set it and forget it”; no magic integrations; no vague AI
- B) “We do everything”
- C) Nothing (don’t mention exclusions)
- D) Only security; nothing else
20) Guarantees / commitments
Why this matters: Avoid risky promises while still sounding strong.
- A) Verification-based commitments (“we’ll test restores / prove cutovers / provide acceptance criteria”)
- B) Outcome guarantee (“we guarantee no breaches”)
- C) Satisfaction guarantee only
- D) No commitments stated
21) Client responsibilities (set expectations)
Why this matters: Prevents delays and makes outcomes repeatable.
- A) One accountable owner, timely access/approvals, schedule for key people, change control
- B) Minimal client involvement
- C) Client does most of the work
- D) Not mentioned
22) Tone + look of the PDF
Why this matters: Ensures it feels like Solanasis—confident, not flashy.
- A) Plain, confident, “field-notes” professional (minimal design, strong headings, no fluff)
- B) Flashy / agency marketing
- C) Very corporate/sterile
- D) Casual/funny
23) Call to action you want at the bottom
Why this matters: The PDF should make the next step obvious.
- 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 link
- D) Newsletter signup
24) Contact block details (fill in)
Why this matters: Removes friction. Prospects should not have to hunt.
- 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): ______________________
Optional (adds punch if easy)
25) One short “origin story” reason Solanasis exists
Why this matters: Makes the doc memorable and human.
- A) “Because ‘probably fine’ is not a security plan…” (your raw/pro style)
- B) Standard corporate mission statement
- C) No story
If A or B, paste your 2–6 lines here:
26) 1–2 mini case studies (can be anonymized)
Why this matters: Concrete outcomes are persuasive.
- A) Problem → what you did → measurable result
- B) Vague testimonial only
- C) None yet
Case Study 1 (optional):
- Client type (anonymous): __________________________
- Problem: ________________________________________
- What we did: _____________________________________
- Result (numbers if possible): _____________________
Case Study 2 (optional):
- Client type (anonymous): __________________________
- Problem: ________________________________________
- What we did: _____________________________________
- Result (numbers if possible): _____________________
Notes / extra constraints (optional)
Add anything you want me to respect in the final 1–2 page PDF:
- Industries to avoid: ______________________________
- Compliance needs (if any): ________________________
- Preferred wording / banned phrases: _______________
- Anything else: ___________________________________