Cicada prepared for Simbex
Proposal Prepared May 2026
Proposal overview

Putting leadership in the driver's seat.

A 4 week, lightweight Claude adoption plan for the Simbex marketing team; built around the workflows we walked through together.

Duration
4 weeks
Marketing seats
2
Live workflows
3+

What you will see in this proposal

  • 1The opportunity, in plain language.
  • 2A week by week plan.
  • 3What success looks like at day 30.
The opportunity

From bottlenecks to leverage.

Simbex marketing wants more visibility, faster site updates, and steady outbound. Claude becomes the leverage layer that sits between meetings, the website, and the inbox.

  • iSite updates in seconds, not sprints. Static HTML, GitHub backed, instantly publishable; no WordPress drag.
  • iiPersonalized outbound at scale. 100+ tailored emails generated; queued for review in inbox.
  • iiiMeetings become content. Fireflies transcripts feed LinkedIn drafts, blog posts, and follow ups automatically.
  • ivLeadership stays in control. Claude drafts; humans approve; everything is versioned and reversible.
Week 1

Foundation.

Provision the tools, prove the loop, ship one page end to end. By Friday of week one, Lauren can change a live page in under a minute.

Architecture, at a glance

Source
Local files
→
Version control
GitHub repo
→
Live
Static site

Deliverables

  • ✓Claude Teams seats provisioned for Greg and Lauren.
  • ✓Connectors live: Fireflies, Gmail.
  • ✓Static site repo on GitHub; deploy via Kinsta.
  • ✓Single page migrated end to end.
  • ✓Leadership accessible-UI for triggering workflows.
Week 2

First workflows.

Three repeatable Claude skills that cover most of weekly marketing motion.

⚙

Site edit from meeting

A Fireflies transcript triggers a copy or layout change; Claude opens a pull request for review.

in

LinkedIn draft

A meeting or article becomes a post draft in your voice, ready to publish or edit.

✉

Outbound email

A personalized draft per contact; queued for review in inbox.

Plus

First scheduled automation goes live; pulled from your Wednesday demo day sync.

Week 3

Outreach and content.

Test the system; small batch, measurable signals. We are not chasing volume in week three; we are looking for the first published post and case studies that came out of the new system.

One personalized email push

Mirror the MTI list approach; track replies and engagement.

One blog post, end to end

A real meeting transcript becomes a published post on the static site.

First case study drafted

Pull from existing client work; Claude assembles the narrative for review.

Week 4

Handoff and review.

Leadership drives. We document. We set the stage for greater marketing collaboration.

  • ✓Leadership runs a workflow start to finish, unassisted, in a working session.
  • ✓30 minute review with leadership; what stuck, what to drop, what is next.
  • ✓A short list of month two candidates: (Master Plan Contest?).
Day 30

What success looks like.

Site updates
< 5 mins
Active skills
3 in weekly use
Outbound shipped
1 campaign
Content shipped
1 blog post per case study
Case studies
First draft live
Leadership's question
"What's next?"

By the end of month one, leadership is no longer asking "do I trust this." The question becomes "what do we automate next."

Next steps

Ready when you are.

A short kickoff with leadership and your engineering lead to confirm scope and accounts. Week one starts the next business day.

What we need from Simbex

  • 1Greg and Lauren as the two named users.
  • 2Sign off on Kinsta as preferred static host for deploy.
  • 3Cicada will send a pre kickoff checklist before the call.

Pick a kickoff day

Monday, June 1 → Tuesday, June 2 → Wednesday, June 3 →
1 of 8