Solanasis Docs

Website - Divi Prompt

9 min read

You are building a SINGLE-PAGE website (one-page “Home” landing page) for the company “Solanasis” using the EXISTING Divi “Professional” theme styling. Keep the Professional theme’s visual language (clean, modern, lots of whitespace, crisp sections, consistent button styles). Do NOT create multiple pages—everything must be on one page with anchored sections and a top nav that scrolls to each section.

BRAND / TONE

  • Voice: blunt, clear, confident, practical. “No fear marketing. No jargon.”
  • Feel: professional, calm, slightly edgy, “boring fundamentals done right.”
  • Do not add hype claims, fake case studies, fake logos, or made-up numbers.
  • Minimal stock imagery. If you need visuals, use subtle abstract/geometry backgrounds or simple line icons only.

GLOBAL REQUIREMENTS

  • One-page layout with these anchor IDs: services how-we-work results faq contact
  • Sticky top navigation with a right-side CTA button.
  • Mobile-first: clean stacking, readable spacing, no tiny text.
  • Accessibility: proper heading hierarchy (H1 once, then H2 sections), good contrast, descriptive button labels.
  • Animations: minimal/subtle only (optional fade-in), nothing flashy.

PRIMARY ACTIONS / LINKS

SITE STRUCTURE (in this exact order)

  1. TOP NAV (sticky)
  • Left: Text logo “Solanasis”
  • Nav links (scroll to anchors): Services (#services) · How We Work (#how-we-work) · Results (#results) · FAQ (#faq) · Contact (#contact)
  • Right CTA button: “Book a 30-min intro call” → https://go.solanasis.com/intro (or contact if placeholder)
  1. HERO (above the fold) Layout: two-column (left text, right minimal abstract visual or icon cluster; no stock people). H1 Headline (exact): “We fix the stuff everyone “means to get to.””

Subhead (exact): “Security gaps. Untested backups. Messy migrations. CRMs nobody uses. Tools that don’t talk. AI ideas that could backfire. Solanasis helps you sort it out with clear steps and real deliverables.”

CTAs:

Microcopy under CTAs (small text, exact): “No fear marketing. No giant decks. We’ll tell you what matters, what doesn’t, and what to do next.”

  1. WHY SOLANASIS EXISTS (punchy section) Section header H2 (exact): “Why Solanasis exists” Body text (exact, keep line breaks or bullets as appropriate): “Because “probably fine” is not a security plan. Because “we have backups” means nothing until you restore. Because migrations fail in slow motion. Because CRMs die from neglect and bad design. Because integrations should be maintainable—not magical. Because AI without guardrails becomes a liability.”

Closing line (exact): “The goal: make the basics solid so your team can move faster without stepping on landmines.”

Design: make this section visually distinct (slightly tinted background or a subtle professional theme variation). Keep it bold and readable.

  1. WHAT WE ACTUALLY DO (plain English) Use a clean text block + checkmark bullets.

Intro sentence (exact): “Most teams don’t need a “transformation.” They need a few critical things to be true:”

Bullets (exact):

  • “You know what’s risky (and what’s just noise).”
  • “You can recover when something breaks (tested, not assumed).”
  • “Your data can move without corruption, surprises, or lost history.”
  • “Your systems talk to each other without fragile automations.”
  • “Your CRM reflects reality—so people actually use it.”
  • “If you use AI, it’s controlled, monitorable, and doesn’t create new risks.”

Closing line (exact): “That’s our lane.”

  1. SERVICES (6 cards) [ANCHOR: services] Create a 2x3 (desktop) card grid. Each card includes: Title → one-liner → “What you get:” bullet list. Keep language EXACT.

CARD 1 — Security Assessment One-liner (exact): “A practical look at your real exposure—focused on what attackers and accidents actually exploit.” What you get:

  • “Findings ranked by severity + business impact”
  • “Clear fixes (quick wins + bigger moves)”
  • “A “30/60/90 day” action plan”
  • “Optional: we help implement the fixes”

CARD 2 — Disaster Recovery Verification One-liner (exact): “Backups aren’t a strategy until restores are tested. We validate coverage and prove recovery works.” What you get:

  • “Restore testing results (what worked, what didn’t)”
  • “Gaps and risk hotspots (RPO/RTO reality check)”
  • “A recovery runbook your team can follow under stress”
  • “Optional: tabletop exercise to pressure-test the plan”

CARD 3 — Data Migrations One-liner (exact): “Move data without breaking reporting, losing history, or creating permission chaos.” What you get:

  • “Migration plan + timeline + rollback approach”
  • “Field mapping / transform rules documented”
  • “Validation report (counts, sampling, parity checks)”
  • “Cutover checklist + post-migration cleanup plan”

CARD 4 — CRM Setup One-liner (exact): “A CRM your team actually uses—pipeline, automation, reporting, and cleanup done right.” What you get:

  • “Pipeline stages that match how you sell/serve”
  • “Clean fields + dedupe + ownership rules”
  • “Automation for follow-ups + handoffs”
  • “Dashboards leadership can trust + basic training”

CARD 5 — Systems Integration One-liner (exact): “Connect tools without duct tape. Secure, maintainable workflows with real error handling.” What you get:

  • “Clear “system of record” decisions”
  • “Secure integrations (least privilege, secrets handled correctly)”
  • “Logging + retries + failure alerts (so it doesn’t silently break)”
  • “Documentation + diagrams for handoff”

CARD 6 — Responsible AI Implementation One-liner (exact): “AI that’s useful in production and defensible when someone asks “how does this work?”” What you get:

  • “Use-case definition + risk boundaries (what it can/can’t do)”
  • “Guardrails (data boundaries, human review where needed)”
  • “Evaluation approach (quality checks, regressions)”
  • “Monitoring plan (so it stays reliable over time)”
  1. WHAT WORKING WITH US FEELS LIKE (expectations) Use a simple section with bold intro line + bullets.

Intro line (exact): “We’re not here to impress you with jargon. We’re here to get you outcomes. That usually means:”

Bullets (exact):

  • “We ask blunt questions early so we don’t waste your time later.”
  • “We keep access minimal and time-bound (least privilege, always).”
  • “We document as we go so you’re not dependent on a single person.”
  • “We aim for high leverage—the fixes that meaningfully reduce risk and friction.”
  • “We’ll tell you “don’t do this” if it’s unnecessary complexity.”
  1. HOW WE WORK (process section) [ANCHOR: how-we-work] Header H2 (exact): “How we work (and why it stays sane)” Intro paragraph (exact): “A lot of projects go sideways for predictable reasons: fuzzy scope, hidden dependencies, undocumented decisions, and changes that aren’t reversible. We run the opposite playbook.”

Create a 5-step layout (numbered steps or horizontal/vertical stepper).

Step 1 — Intro call (30 min) Text (exact): “We’ll get clear on what you’re trying to fix, what you’ve tried, and what “better” looks like. Why: Most problems are 20% technical and 80% clarity.”

Step 2 — Discovery (60–90 min) Text (exact): “We confirm scope, systems involved, access needs, constraints, and success criteria. Why: We’d rather discover landmines now than during cutover.”

Step 3 — Execution (assessment / verification / build) Text (exact): “We do the work in phases and keep it observable: what changed, what was tested, what still needs attention. Why: You shouldn’t have to “trust the process.” You should be able to see it.”

Step 4 — Readout + decisions Text (exact): “You get a clear summary, what matters, what doesn’t, and exactly what we recommend next. Why: The point is fewer unknowns and a plan you can execute.”

Step 5 — Implementation support (optional) Text (exact): “We can help execute the plan, collaborate with your MSP/internal IT, or hand off cleanly. Why: Some teams want speed; others want independence. We support both.”

  1. WHAT YOU GET (deliverables) Header H2 (exact): “What you get (deliverables that don’t disappear)” Lead line (exact): “Every engagement produces real artifacts you keep:”

Bullets (exact):

  • “A findings summary in plain language”
  • “A prioritized action plan (what to do first and why)”
  • “Runbooks / checklists (especially for recovery and handoff)”
  • “Diagrams (systems, data flows, integrations) where helpful”
  • “A short executive recap you can forward internally”

Closing lines (exact): “If you want us to implement, we’ll do it. If you don’t, you’ll still leave with clarity.”

  1. RESULTS (lightweight outcomes) [ANCHOR: results] Create a simple “Results you can feel” style section (NOT fake case studies). Header H2: “Results” Use 4–6 icon bullets or mini cards that summarize outcomes WITHOUT numbers and WITHOUT pretending these are client quotes: Examples you may use (keep them conservative and generic):
  • “Clear risk priorities (signal over noise)”
  • “Restores tested and repeatable”
  • “Clean data moves with validation”
  • “Integrations that fail loudly (not silently)”
  • “A CRM that matches reality”
  • “AI usage with boundaries + monitoring”

Do not add logos, testimonials, or fabricated metrics.

  1. FAQ (accordion) [ANCHOR: faq] Header H2: “FAQ” Use these Q/A pairs EXACTLY:

Q: “Do you work with our MSP / internal IT?” A: “Yes. We can validate, collaborate, and close gaps without stepping on toes.”

Q: “Can you just do the assessment and hand us the plan?” A: “Absolutely. Some teams want execution help; others want a clean roadmap.”

Q: “How disruptive is this?” A: “We design for minimal disruption: staged changes, reversible steps, and scheduling around operations.”

Q: “Do you sign NDAs?” A: “Yes.”

Q: “Do you do ongoing support?” A: “If it’s a fit. Many clients start with a project, then keep us around for quarterly checkups or specific initiatives.”

  1. CONTACT (simple + anti-spam) [ANCHOR: contact] Header H2 (exact): “Let’s make the basics solid.” Body (exact): “If you’re tired of “we should really…” moments, book a quick intro call. We’ll tell you what we’d do, what it would take, and whether we’re a fit.”

Buttons/links:

Add a contact form below with:

  • Prompt line: “What are you trying to improve?”
  • Checkboxes: “Security Assessment”, “DR Verification”, “Data Migrations”, “CRM Setup”, “Integrations”, “Responsible AI”
  • Dropdown: “Timeline” with options “ASAP”, “This month”, “This quarter”
  • Field: “Current tools (optional)”
  • Textarea: “Anything we should know?” (free text)

Anti-spam microcopy (small text, exact): “If you’re pitching services, you won’t get a reply.”

  1. FOOTER (short) Footer text (exact): “Solanasis — practical security + operational resilience + systems that work. © {Year} Solanasis. All rights reserved.”

FINAL CHECKS

  • Ensure nav anchor scrolling works perfectly.
  • Ensure only one page is created.
  • Keep spacing tight-but-breathable, Professional theme consistent, and no filler copy.

Graph View

Backlinks