From Friday Call to Monday Demo: Building an Education Cloud Experience with Claude

The Challenge: A Monday Deadline Called In on Friday Afternoon

Friday, 4pm. An education customer from our network called asking for a demo of Education Cloud — not just the core cloud, but separate Experience Cloud portals layered on top, to show an end-to-end experience.

Education has long been a natural extension of our work in the impact sector, and we'd been building on Education Cloud for months. We were glad to take it on. The catch was the timeline: it needed to be in front of their customer by Monday, end of day.

What Needed to Come Together:

• A Full Core Build: A working Education Cloud foundation, not just a set of talking points.
• Four External Portals: Separate Experience Cloud portals, each mocked up to show a distinct part of the journey.
• One Connected Story: End-to-end flows linking the internal experience to every external portal, so the demo read as a single system rather than disconnected pieces.
• Design Fidelity: The build had to follow Salesforce's Lightning Design System properly, not approximate it.
• A Working Weekend: All of it, start to finish, between Friday afternoon and Monday morning.

Normally, a brief like this is a "let's push the timeline" conversation. This time, we didn't have to have it.

The Solution: Claude in the Driver's Seat

As an Anthropic Claude partner alongside our Salesforce partnership, we put Claude in the driver's seat for the build.

1. The Internal Experience, Built First

We started with the core Education Cloud experience — the internal user journey the rest of the demo would hang off. Getting this right early gave every downstream portal a consistent foundation to build from.

2. Four External Portals, Mocked Up in Parallel

With the core in place, we used Claude to build out all four external Experience Cloud portal mockups, each one following Salesforce's Lightning Design System so the demo felt native to the platform rather than bolted on.

3. End-to-End Flows Connecting Every Piece

The individual portals were only half the story. We built the flows that connected the internal experience to each external portal, so a customer walking through the demo would see one coherent journey, not four separate systems.

4. A Working Solution, Not a Clickable Prototype

The bar we set for the weekend wasn't "looks convincing." It was "does what it's supposed to do." By Monday morning, that's what we had — a working solution, ready to present, not a mockup dressed up to look like one.

The Outcome: A Weekend That Became an Opportunity

• Delivered on Time, Fully Built: Design and build, done inside a single weekend, from Friday afternoon to Monday morning.
• Four Portals, One Story: All four external Experience Cloud portals came together with the internal build into a single, connected demo.
• Design Standards Held: The build followed Salesforce's Lightning Design System throughout, so nothing about the pace showed in the polish.
• A Working Demo, Not a Mockup: What we presented Monday was functional, not simulated.
• Immediate Customer Reaction: The customer's response said it all — they were excited enough to book the next session on the spot.

If you're navigating something similar — tight timelines, ambitious scope, or you're just curious what's possible when these two platforms work together — let's talk.