Cerebral Valley × Anthropic · For account teams

Claude Build Day

A one-day activation inside your customer's office. Their builders bring real problems, Anthropic brings the experts, and Cerebral Valley handles the rest.

For a limited group of Anthropic's fastest-growing customers.

Sample run of show One weekday · On-site
  1. Doors, breakfast, check-in
  2. Kickoff and live Claude demo
  3. Teams lock in a real problem
  4. Build, with Anthropic on the floor
  5. Submissions close
  6. Backroom judging with customer leaders
  7. Finalist demos on stage
  8. Awards and next steps

About

A Claude Build Day is a hands-on, outcome-driven activation, like a hackathon, that turns a customer's Claude momentum into real projects, built and demoed in a single day.

  • 1Day, at their office
  • 50+Builders in the room
  • 0Logistics on your plate

When to run a Build Day

Claude Code panel on stage in front of a full audience

01. Usage is taking off

Claude is live and a group of builders is already leaning in. A Build Day turns scattered power users into a room of shipped projects and internal champions.

Packed room for a keynote featuring Anthropic

02. The stack just connected

The rollout is done and Claude is wired into their internal tools and data. This is the moment a day of building lands hardest.

A builder holding the first place trophy from an internal hackathon with Anthropic

03. An account moment is coming

An expansion, renewal, or strategic initiative is on the calendar. A Build Day puts working proof in front of leadership right when it counts.

What the account walks away with

  1. 01

    High-value use cases

    Working builds tied to leadership priorities, ready for other teams to adopt.

  2. 02

    Measured efficiency

    Estimated hours saved per workflow, compared against the current way of working.

  3. 03

    Hands-on upskilling

    People earlier in their Claude journey learn on their own real work.

  4. 04

    Internal champions

    Builders from across the org take what they learned back to their teams.

What happens on the day

Take a real task your team does today, use Claude to improve it, and demonstrate the difference.

  1. Kick off

    Anthropic or an internal champion demos a workflow built for this audience.

  2. Pick a real problem

    Teams choose a problem they're facing in their own work and define what success looks like.

  3. Build

    Hands-on building all day, with Anthropic representatives and mentors on the floor.

  4. Demo

    Teams submit and present. Anthropic and customer leaders judge together.

  5. Take it home

    Winners take home Anthropic prizes, and the best projects get a path to production.

Who does what

You make the intro. We handle everything else.

Every Build Day has three owners. Here's the split.

Anthropic

The relationship
  • Make the intro and own the account
  • Set goals and success metrics with the customer
  • Confirm Claude licenses and access are live
  • Confirm the customer NDA covers Cerebral Valley
  • Representatives in the room, building with attendees
  • Kickoff demo and judges
  • Prizes for the winners

The customer

The room
  • Office space and a logistics contact
  • An internal champion who gets the right builders there
  • WiFi, IT access, and approved tools ready
  • An internal channel for attendee comms
  • Leaders to judge, mentor, or speak

Cerebral Valley

Everything else
  • Event architecture tuned to the account's goals
  • Logistics coordination with the customer's team: venue, AV, catering, and IT
  • Challenge brief and builder materials
  • Invites, reminders, and attendee comms
  • Signage, merch delivery, and judge gifts
  • Submissions, judging rounds, and scoring
  • Run of show, travel, setup, and on-site production

If the customer can't cover something on their list, we cover it.

Six weeks from yes to demo day.

Six weeks is the ideal lead time, and we can compress to four for a speedy kickoff. Your part is mostly the first week: an intro, a scoping call, and the customer kickoff.

  • Anthropic
  • Customer
  • CV
  1. T-6 weeks

    Scope the opportunity

    We meet your account team, then draft the plan you share with the customer.

    ACV
  2. T-5 weeks

    Customer kickoff call

    Thirty minutes to lock goals, audience, and a logistics contact.

    ACCV
  3. T-4 weeks

    Logistics start

    Venue, catering, AV, and IT planning with the customer's team.

    CCV
  4. T-3 weeks

    Invites go out

    Builders, judges, and mentors get the invite through the customer's champion.

    CCV
  5. T-2 weeks

    Content and vendors locked

    Kickoff content and builder resources drafted with Anthropic.

    ACV
  6. T-1 week

    Builders get ready

    Attendees get everything they need to walk in ready to build.

    CV
  7. T-2 days

    CV on-site

    Walkthrough, AV dry run, and IT checks.

    CV
  8. Build Day

    Everyone in the room

    Kickoff to awards in one day.

    ACCV
  9. After

    Follow-up

    A recap and follow-up sessions to keep projects moving.

    ACV

FAQ

Which accounts are a good fit?

Customers with Claude live for the people who would attend, a growing base of active users, and an internal champion who can get builders in the room. Strong fits usually have an expansion, renewal, or strategic initiative coming up.

What's NOT the right time to activate?

Wait until there's an internal champion and Claude is connected to their internal tools. Pass if builders can't access Claude yet, or if it's an executive summit or a group under 50.

How many people attend?

50 or more builders. The room is set by the customer's goals: top power users, nominations from each business unit, power users paired with newer users, or an idea-submission process where the best ideas earn a seat.

Does it have to be in person?

In-office is the default and works best. When adoption is brand new, we run a virtual workshop first and then an in-person build. For teams spread across sites, we run a city tour or a cross-office competition. Fully virtual is a fallback, focused on build time rather than sessions.

What do builders work on?

Real problems from their own work. We set a theme with the customer: saving hours, hours saved per token, something their team can use tomorrow, a use case leadership has named, or connecting Claude to their internal stack. Submissions capture hours saved and who benefits, so outcomes are measurable.

What about security, data, and NDAs?

We confirm Anthropic's NDA with the customer covers Cerebral Valley before planning starts. The customer's IT team approves tools and data access ahead of time, and the submission form can live inside their systems if they prefer.

What happens after the event?

A recap for both teams, plus help setting up follow-up sessions with key teams, internal AI user groups led by finalists, and introductions to Anthropic's champion network.

Who is Cerebral Valley?

CV is the world's premier AI ecosystem. We've worked with Anthropic since the launch of Claude 2, producing public events with their team like Built with Opus 4.7, Built with Opus 4.6, Built with Claude: Life Sciences, and the Claude Build Day for startups. See more on our showcase.

Have an account that's ready?

Tell us about your customer. We'll reach out to chat.

Request a Build Day