Solanasis Fractional CIO / Portfolio / PDF Workflow Handoff Bundle — Master Index (2026-03-19)

Executive Summary

This bundle turns the recent discussion into a working handoff for another AI or operator. It covers three connected tracks:

  1. Bridge revenue via fractional platforms and communities
  2. Website / positioning / personal-brand architecture
  3. Executive bio PDF generation and Claude Code automation

The most important conclusion is this:

Purpose of This Document

This master file exists to orient another AI quickly. It tells the next system:

  • what the user is trying to achieve,
  • what has already been researched,
  • what is verified versus inferred,
  • what separate files to open next,
  • and what still needs verification or implementation.

Discussion Context

User goals

  • [User-stated] Find practical bridge revenue through fractional consulting sites, communities, Slack/Discord-style groups, and related ecosystems.
  • [User-stated] Decide how to position Dmitri publicly: CTO vs CIO vs CISO, with a desire to keep things simple and credible.
  • [User-stated] Decide whether Solanasis needs a separate personal portfolio site or whether a founder-specific layer is enough.
  • [User-stated] Build a professional one-page executive bio PDF pipeline that Claude Code can automate reliably.
  • [User-stated] Generate a strong Claude Code prompt to build the site, while first asking clarifying questions to surface the best proof and positioning.

Existing local artifacts from earlier turns

  • [User-stated / file present] /mnt/data/solanasis_fractional_sites_master_list_deep.csv
  • [User-stated / file present] /mnt/data/solanasis_fractional_priority_paths.csv
  • [User-stated / file present] /mnt/data/solanasis_fractional_sites_research.xlsx
  • [User-stated / file present] /mnt/data/My Style Voice for AI.md
  • [User-stated / file present] /mnt/data/solanasis_fractional_consulting_research_handoff_playbook_2026-03-18.md

Bundle Map

Open these files next depending on the task:

  1. Fractional platforms / positioning / bridge revenue

    • solanasis_fractional_platforms_and_positioning_playbook_2026-03-19.md
  2. Website / personal brand / portfolio site

    • solanasis_fractional_website_strategy_and_claude_code_prompt_2026-03-19.md
  3. Executive bio PDF tooling / Claude Code automation

    • solanasis_executive_bio_pdf_workflow_and_tooling_2026-03-19.md

Key Facts and Verified Findings

Fractional platforms and revenue

Website / positioning

  • [Assistant-stated but unverified] “Fractional CIO” is the best umbrella title because Dmitri’s value spans security, resilience, systems, migrations, AI, and executive cleanup, which is broader than CTO and broader than CISO alone.
  • [Verified] One current consulting-site resource explicitly says independent consultant websites differ from larger firm sites and that personal branding is central for independent consultants.
    Source: https://www.melisaliberman.com/blog/consulting-website-examples
  • [Verified] One current fractional-branding source says neither personal-name branding nor company-name branding is inherently better, and that the right choice depends on business model and values.
    Source: https://www.jasonfaber.ca/blog/how-to-brand-yourself-as-a-fractional-consultant

PDF / automation / Claude Code

Major Decisions and Conclusions

  1. Default lane

    • [Assistant-stated but unverified] Use Fractional CIO as the primary public lane.
    • [Assistant-stated but unverified] Use CISO as a wedge when the buyer is security/risk-led.
    • [Assistant-stated but unverified] Use CTO selectively when the buyer is startup/product/engineering-led.
  2. Brand architecture

    • [Assistant-stated but unverified] Keep Solanasis as the main commercial site.
    • [Assistant-stated but unverified] Add a founder/fractional-CIO page first rather than building a fully separate personal site immediately.
    • [Tentative / speculative] Launch a lightweight personal domain later if Dmitri’s personal brand starts pulling significant opportunity flow beyond Solanasis.
  3. PDF generation

    • [Assistant-stated but partially verified] Stop using generic “print the website page” hacks as the primary method.
    • [Assistant-stated but strongly supported by official docs] Build a dedicated print pipeline with:
      • structured source content,
      • a print-specific template,
      • and deterministic export via Playwright/Puppeteer, Typst, or Docs export.

Reasoning, Tradeoffs, and Why It Matters

Why “Fractional CIO” is the lead lane

  • [Assistant-stated but unverified] CTO is too product/engineering-coded for the full Solanasis offer.
  • [Assistant-stated but unverified] CISO alone is too narrow for the broader value stack.
  • [Assistant-stated but unverified] CIO better covers systems, governance, vendor sprawl, resilience, migrations, and practical AI.

Why not build two full sites immediately

Why a dedicated PDF pipeline matters

  • [Assistant-stated but supported by sources and user experience] Print-specific templates are more reliable than website-to-PDF hacks because browser print behavior, website layout, and ad-hoc export workflows often produce inconsistent results.
  • [Verified] The official tool docs support controlled header/footer and print-media workflows, which is exactly what the user needs for consistent one-page executive bios.

Phase 1 — Revenue and positioning

Open the fractional platforms file and:

  • finalize top-3 platform positioning,
  • choose the default title,
  • tighten bio/case-study assets,
  • and shortlist the highest-value platforms from the local CSV.

Phase 2 — Website

Open the website file and:

  • choose architecture (likely Solanasis + founder page first),
  • answer the clarifying questions batch,
  • synthesize the positioning,
  • build copy and structure.

Phase 3 — Executive bio PDF

Open the PDF/tooling file and:

  • choose the generator stack,
  • create structured content inputs,
  • build one premium template,
  • and produce exportable one-pagers.

High-value current sources

Local companion files

  • /mnt/data/solanasis_fractional_sites_master_list_deep.csv
  • /mnt/data/solanasis_fractional_priority_paths.csv
  • /mnt/data/solanasis_fractional_sites_research.xlsx
  • /mnt/data/My Style Voice for AI.md

Risks, Caveats, and Red Flags

  • [Verified] Canva automation is real, but private integrations require Canva Enterprise and public integrations require review; this makes it higher-friction than local HTML/Typst/Docs workflows for immediate execution.
    Sources: https://www.canva.dev/docs/connect/ and https://www.canva.dev/docs/connect/creating-integrations/
  • [Verified] Google Docs PDF export is limited to 10 MB.
    Source: https://developers.google.com/workspace/drive/api/guides/manage-downloads
  • [Verified] gws is publicly available but explicitly not an officially supported Google product, so it should be treated as useful-but-risky infrastructure for production-critical workflows.
    Source: https://github.com/googleworkspace/cli
  • [Assistant-stated but unverified] Over-positioning as CTO may pull lower-fit engineering-heavy work instead of the broader operational-resilience/CIO work Dmitri seems to want.
  • [Assistant-stated but unverified] A premature separate personal site can dilute attention unless there is already enough thought-leadership or personal-brand pull to justify it.

Open Questions / What Still Needs Verification

  1. Which of the 53 platforms in the deep CSV are actually still open and active for Dmitri’s exact lane as of today, beyond the top few that were rechecked?
  2. Which platform’s buyer mix best matches wealth-management-adjacent, nonprofit, or professional-services buyers?
  3. Whether Dmitri wants a pure one-page founder site, a Solanasis founder page, or a hybrid with two linked properties.
  4. Whether Claude Code in Dmitri’s actual environment already has access to Playwright, Typst, LibreOffice, Google credentials, Canva credentials, or gws.
  5. Whether Dmitri has enough named proof/case studies to publish, or whether the first version must use anonymized founder/operator stories.

Suggested Next Steps

  1. Finalize the default role label and bio stack from the fractional platforms file.
  2. Answer the website clarifying questions and generate copy/site structure.
  3. Choose the PDF stack and build one premium template.
  4. Convert the website copy + PDF template into reusable structured content.
  5. Apply the resulting positioning consistently across:
    • Solanasis website
    • LinkedIn
    • platform profiles
    • executive bio PDF
    • capability statement

Handoff Notes for Another AI

  • The user prefers outputs that are detailed, structured, operational, and useful immediately.
  • The user wants downloadable Markdown artifacts and often wants work broken into modular files.
  • The user’s likely best lane is Fractional CIO with security/resilience as the wedge, but this remains a positioning inference, not a verified fact.
  • Use the local file My Style Voice for AI.md when drafting public-facing copy.
  • Treat the prior CSV/XLSX platform research as a working dataset, but do not assume every row is equally current; re-verify anything you rely on heavily.

Reviewer Notes and Improvements Made

Self-review performed; no separate reviewer agent was available in this workflow.

Improvements made in this bundle relative to the raw conversation:

  • separated verified facts from positioning inferences,
  • added current-source verification for the most load-bearing claims,
  • flagged where earlier recommendations were strategy opinions rather than externally verified facts,
  • split the work into multiple files by major aspect,
  • and made the output easier for another AI to continue without the original chat history.

Optional Appendix — YAML-style Summary

user_goal:
  primary:
    - generate bridge revenue through fractional platforms and communities
    - decide public positioning lane
    - build a credible founder/fractional site
    - automate premium executive bio PDFs
  secondary:
    - keep the system simple
    - avoid brand confusion
    - reuse one set of structured assets across platforms
 
recommended_default_lane:
  status: assistant-stated-but-unverified
  value: Fractional CIO
 
brand_structure:
  status: assistant-stated-but-unverified
  value: hybrid
  notes:
    - Solanasis = commercial vehicle
    - Dmitri Sunshine = trust engine
 
top_verified_platforms:
  - Fractional Jobs
  - Shiny
  - Catalant
 
pdf_stack_priority:
  - HTML/CSS + Playwright/Puppeteer
  - Typst
  - Google Docs + Drive export
  - PPTXGenJS + LibreOffice
  - Canva only if integration friction is acceptable
 
key_local_files:
  - solanasis_fractional_sites_master_list_deep.csv
  - solanasis_fractional_priority_paths.csv
  - solanasis_fractional_sites_research.xlsx
  - My Style Voice for AI.md