Install Raven together

45 minutes. One of us on the call with you. You run Raven's elicitation, we watch. You get live support, we learn what's breaking on real machines.

What the call is for

You

You get past the rough edges of a cold install. You ask the questions you'd otherwise have to email about. You end the call with a foundational library in place and a sense of how Raven fits into your actual workflow.

Us

We watch how you answer Raven's elicitation questions, which is the single highest-signal thing we can do at this stage. Every call teaches us something the repo issues don't.

What to bring

  • Your codebase (or at least access to it).
  • Any product docs you've got, however scattered. Notion, a README, a Google Doc, a whiteboard photo. Raven works with what you have.
  • A working Claude subscription. Max if you're planning to ship code alongside the library; Pro is fine if you're just setting up the library for now.
  • A sense of what you're trying to build. Not a pitch deck. Just enough that we can calibrate the elicitation to your actual project.

What you'll walk away with

A working installation of Raven, pointed at your real codebase.

The foundational tier of your library populated. Brand voice, product scope, the decisions you've already made.

A direct line to both of us for the next 30 days. You can email or Slack when something breaks or when you want to go deeper into the valuable and nice-to-have tiers.

Design partner status. That means free, rough edges, and a seat in the room as Alexandria evolves.

Book it

One question we'll ask before the call:

In one sentence: what's the project or team situation where Alexandria would most move the needle for you right now?