What’s a Build Day?

A one-day hackathon inside a customer’s office, built alongside experts and run by Cerebral Valley

Customer leadersJudge the builds and createa path to productionCerebral ValleyRuns the room, check-in to awardsCustomer buildersTeams tackling one real problemfor their organizationPlatform expertsYour own peoplebuilding alongside all day
Customer leadersJudge the builds and createa path to productionCustomer buildersTeams tackling one real problemfor their organizationCerebral ValleyRuns the room, check-in to awardsPlatform expertsYour own peoplebuilding alongside all day
  • Customer buildersTeams tackling one real problem for their organization
  • Platform expertsYour own people building alongside all day
  • Customer leadersJudge the builds and create a path to production
  • Cerebral ValleyRuns the room, check-in to awards
Length
30+
Builders
Building time
6weeks
Lead time

How a Build Day runs

  1. When
    When

    Run it the day after the AI tools go live

    Internal tools connected, platform experts in the room. A team is never easier to steer

  2. 6 weeks out
    6 weeks out

    The customer brings the room. Cerebral Valley runs the rest

    Six weeks from yes to demos

    The customer

    • Office space and a logistics contact
    • WiFi, IT access, approved tools
    • A champion to fill the room, and leaders to judge

    The AI platform

    • Goals and metrics, set with the customer
    • Licenses and access, live
    • Platform experts in the room, and prizes for the winners

    Cerebral Valley

    • Event architecture and crafting
    • Venue, AV, catering, IT logistics
    • Challenge brief and materials
    • Invites and reminders
    • Signage and merch delivery
    • Submissions and scoring
    • On-site production
  3. Build Day08:00
    Build Day · 08:00

    Six hours of building

    Each team rebuilds one real task from its own week

    6hof buildingDoors and breakfastKickoff and live demoJudging with customer leadersFinalist demosAwards and next steps
    Sample run of show
    1. 08:00Doors and breakfast1h
    2. 09:00Kickoff and live demo45m
    3. 09:45Build, platform experts on the floor6h
    4. 15:45Judging with customer leaders45m
    5. 16:30Finalist demos30m
    6. 17:00Awards and next steps20m
  4. Build Day15:45
    Build Day · 15:45

    Every build states the hours it saves

    Customer leaders and platform experts score them together, then the finalists demo

    Sample results, top 4 of 18 buildsHours saved a week
    Support triage agentCustomer Experience31.5
    Contract redline assistantLegal24.0
    Incident postmortem drafterPlatform Engineering17.5
    Month-end reconciliationFinance12.0
  5. After
    After

    What stays with the customer

    The best builds get a path to production

    Working use cases

    Tied to what leadership asked for

    Hours saved

    Estimated per workflow

    New skills

    Learned on real work

    Champions

    Back in their own teams

Results from recent Build Days

Weekly AI usage

Large retailer

+110%

Three days after the Build Day

Hours saved a year

Travel company

~2,250

Self-reported, across six projects

Builders in the room

Cybersecurity company

80

Across 23 projects

People one build will reach

Software company

~400

Expected by its builder

Builds kept by their teams

Financial services

85%

11 of 13 teams

Roadmap audit run in

Media company

about 13 minutes

Versus roughly 10 hours by hand

Plan a Build Day with Cerebral Valley

For an AI platform planning one for a customer, or a customer booking its own. It starts with a scoping call

Large retailer

Case studyLarge retailer

107 prototypes in one day

A large retailer invited the whole company to a Build Day. About 280 people built on problems from their own work, alongside the AI platform’s experts

Prototypes built

107

In one day

Builders

~280

In the office and remote

Hours saved a week

~550

Self-reported by 69 teams

Weekly active users

+110%

Three days after

256 problems on the table before anyone built

Before the day, attendees sent in the problem they wanted to fix and the hours it costs them each week. 52 people without a team were matched into 13 new ones

Problems submitted

256

From more than 20 departments

Hours a week spent on them

~990

Self-reported

New to the tools

58%

Of in-person attendees

One brief: build something you can use tomorrow

Every team got the same brief: build something you or your team can adopt and use the next day. Business teams built in the office, and most engineers joined remotely

Built in the office

54

Half of all builds

Built remotely

47

44% of all builds

Built by hybrid teams

6

6% of all builds

Three and a half hours of building

A CEO keynote and a guided exercise came first, then three and a half hours to build before demos

  1. 08:00IT setup help
  2. MorningCEO keynote, then a guided exercise
  3. 10:30Build3h 30m
  4. 14:00Demos
  5. 15:00Leadership session with the platform team

107 builds from every part of the business

45 people built solo and 62 teams of two to ten built together. More than half started from scratch, and five in six were for work outside technology and data

  1. Product creation, design and production23
  2. Technology and data18
  3. Marketing, growth and creative17
  4. Supply chain, planning and wholesale14
  5. Finance and accounting13
  6. Ecommerce, merchandising and customer service11
  7. Retail4
  8. People2
  9. Other5

104 of 107 teams plan to keep using their build

Asked on the day whether they would use it next week, 53 teams said yes and 51 said yes with more work. Three days later, weekly active users on the platform were up 110%

Median time saved a week

5hrs

Per team, self-reported by 69 teams

Estimated users per build

10

Median across 58 teams

Ready for production

13

Builds, by the team’s own account

“This has been the single most transformative thing for our company & it happened in one day.”
President, large retailer · On the day