For leaders with one big bet

Know what to build before you build it.

A two-day, in-person workshop for leaders facing one high-stakes product decision. Your team builds a working prototype, tests it with real customers, and leaves with a decision you can defend.

30-minute call. No obligation.

A product team working through a prototype together on laptops

“Based more on logic and data, than wishful thinking, Skysoclear have been a pleasure to work with.”

Pawan Saunya

Pawan Saunya

Co-founder, gomi

End of testimonial.

Sound familiar?

“We've got a launch in May and we still haven't agreed what we're announcing.”

Every year there's a moment when the business goes public: a conference stand, a board demo, a big announcement. Competitors seem to ship faster than ever, and leadership has noticed. The team is keen to start, but nobody can say which idea deserves the date.

The decision: Of the ideas on the table, which one do we take to May?

“We've been building this for a year and no customer has used it.”

The team's been heads down, building to the plan, and internal demos go well. Then the first real test session happens, and customers struggle with things nobody expected. The deadline's closer, the budget's mostly spent, and nobody knows whether more of the same will fix it.

The decision: Do we carry on with the plan, or stop and change course?

“Everything on the backlog is urgent, and we've got six months to show change.”

There's a long list of big bets and each one has a sponsor. Whatever goes first sets the tone for the year, and getting the order wrong means spending it on the wrong thing.

The decision: Of our three biggest bets, which one goes first?

“We need our next big thing, and we can't wait two years for it.”

The product works and most customers stay, but growth has stalled. Competitors are shipping AI features and you haven't yet. A two-year transformation isn't on the table. You need one project that proves the team can move quickly.

The decision: Do we back this AI idea as our next big bet, or keep improving what we've got?

The problem isn’t ideas. It’s deciding.

Each of these is stuck in the same place: a decision being argued about instead of tested. Building used to be the slow, expensive part, so teams planned carefully and built once. AI has made building fast and cheap. The hard part now is knowing what’s worth building.

Introducing the Build Loop. Two days, in person, with the people who can make the call. Four modes: Frame, Create, Validate, Decide. You go from opinion to evidence to a decision.

How it works

Frame, create, validate, decide.

The Build Loop, refined over 200+ design sprints and 1,000+ user tests. Four modes that move you from an ambiguous brief to a decision backed by evidence. In a Build Loop, we run it once, fast.

01 · Frame · Day 1 · Morning

Frame the bet

Define the metric, the users, the evidence, and what you’d have to see to know it’s working.

The Frame is the foundation. Get this wrong and the rest of the loop chases shadows.

We define the metric that needs to move (and why), identify the users affected, gather the evidence the problem is real, and form a hypothesis we can actually test the very next day.

The Frame lives on one canvas: short enough that your team writes it without us, structured enough that your sponsor can read it and commit.

02 · Create · Day 1 · Afternoon

Build the prototype

Your team prototypes it. In hours, not weeks.

Create is where AI tooling earns its keep. Your team scopes the minimum testable build and prototypes it, with us alongside. Whatever AI tooling you already use.

What used to take a sprint takes an afternoon. The point isn’t speed for speed’s sake. It’s that fast prototypes let us validate the Frame before any expensive engineering commits.

By the end of Create you have something real enough that a user will respond to it like the finished product.

03 · Validate · Day 2 · Morning

Test with real users

Test with real users. Observe behaviour, not opinions.

Validation is where opinions stop and reality starts. Your team puts the prototype in front of five customers and watches what they actually do.

Not surveys. Not ‘would you use this?’. Direct behavioural observation. Drop-offs, hesitation, confusion, surprise: the moments the team needs to see with their own eyes.

Agents run the prototype overnight first, at volume, to find where it structurally breaks. That means your five real sessions aren’t spent discovering a broken button. They’re spent finding out whether anyone wants it.

We document what we observe as evidence, clean enough to anchor the next decision, raw enough that the team trusts it.

04 · Decide · Day 2 · Afternoon

Make the call

Ship, improve, pivot or stop. Walk out with a 90-day plan.

Decide is where the Build Loop pays off. The evidence is in. Now we commit.

Ship: the evidence holds, commit. Improve: the direction is right and the execution isn’t. Pivot: the opportunity is real but you had the shape wrong. Stop: the evidence says no, and you move on with reasoning the board can defend.

You leave with a 90-day plan, a sponsor-ready decision doc, and the templates to run the next one without us.

What you leave with

Four artefacts the team keeps.

Most workshops leave you with a wall of sticky notes and a deck. A Build Loop leaves you with four things your team keeps.

01

A working prototype

Built with AI tools in the room, not sketched in a design file. Real enough that a user will respond to it like the finished product.

02

Behavioural evidence

Five customer sessions, run on day two. Clips and notes the team trusts because they watched it happen.

03

A 90-day plan

The next 90 days in order (ship, improve, pivot or stop), with reasoning your sponsor can defend.

04

The Build Loop toolkit

The method, the Frame Canvas, a validation script and the decision document template. Your team runs the next loop without us.

In practice

What a Build Loop looks like.

A snapshot of a Build Loop in the room: framing the bet, building the prototype, watching real users, and making the call.

Day 1 · Morning

Framing the bet

We agree the metric that needs to move, the users involved, the evidence on the table, and the hypothesis we’ll test: a Frame the sponsor can sign off.

Why it’s different

Not a design sprint, a hack day or another deck.

Most high-stakes product decisions stall in the same place: a slide, a steering committee, a quarter of refinement before anything reaches a user. We replace that with two days of evidence-gathering work, and a decision the team made with their own eyes. We’ve tried the other formats. Here’s where each one stops.

Built for how teams build now

Design sprints came from a time when building was slow, so most of the week went on sketching and a fake prototype. With AI, your team builds a working one in an afternoon, so the time goes on testing and deciding.

A decision, not innovation theatre

Hack days and innovation sessions are fun, but what they produce rarely reaches a roadmap. A Build Loop ends with a recorded decision, a 90-day plan and a backlog the team can start on Monday.

Evidence, not opinion

The call rests on a sharp frame, a working prototype and what real customers actually did. Not on what a competitor shipped, and not on the loudest voice in the room.

Who’s behind it

Practitioner first. Coach second.

I’m Ross Chapman. I’ve been Head of UX at PensionBee, Product Director at Marsh, and Managing Director of a product studio. I’ve also worked as an outside partner for companies including Quilter, Wood Mackenzie and Sikoia. So I’ve sat on both sides: inside the team that has to deliver, and brought in to help it decide.

Too often I’ve watched good teams handed a roadmap instead of being asked what their customers need. The Build Loop puts customer evidence in front of the people who decide. I use AI on real client work every day, and the Build Loop is built around it.

More about how I work

What people say

From the people we’ve worked with.

“We walked in looking for clarity. We walked out with a validated path and real decisions we could act on. That's the difference the loop makes.”

Jon Lee

Jon Lee

Partner, Digital Practice, Oliver Wyman

“Working with Skysoclear was transformative for Sentrisk. Their ability to navigate the environment and set the team up for success made all the difference.”

Cory Cruser

Cory Cruser

Partner, Oliver Wyman

“We were very happy with progress and look forward to the realisation of what we worked on and sharing it more widely.”

Amy Simpson

Amy Simpson

Product Owner, Wood Mackenzie

“We genuinely appreciate the time and effort dedicated to Sikoia. It’s been very valuable and we are grateful for what’s been achieved.”

Alexis Rog

Alexis Rog

CEO, Sikoia

“They made what could be a stressful process utterly enjoyable. Consummate professionals capable of leading complex projects with multiple stakeholders.”

Paul Moynihan

Paul Moynihan

Founder, We Find Venues

“They made time for me immediately. We jumped on a call, I explained what we needed doing, and within a couple of hours they had sent me over a first iteration. They immediately understood exactly what we were trying to do.”

Hannah Parvaz

Hannah Parvaz

Head of Growth, Curio

Suitability

Is a Build Loop right for you?

A Build Loop runs in person, with the people who can make the call. It works best when these are true:

It’s right for you if

  • You have one decision that matters, and a date it has to be made by
  • The person who makes the call can be in the room
  • There’s still time for the answer to change what you do

It isn’t, yet, if

  • You already know what to build. Just build it
  • The decision’s made and you need it signed off
  • Your date is weeks away. You need a delivery partner

Not sure yet? Frame your decision first. Five questions, fifteen minutes, free.

Frame your decision→

Pricing

One price for the Build Loop.

The Build Loop

£9,000

One-off. Two days, end to end.

Two days in person, the full Build Loop

A working prototype, built by your team with us alongside

Five customer sessions, designed and run

A sponsor-ready decision document

A 90-day plan and a prioritised backlog

The Build Loop toolkit, to run the next one yourselves

Venue included

50% secures your dates. The balance is invoiced at the end of day two, payable within 14 days.

Next available dates: mid-February 2027

Talk it through →

Logistics

Venue

Included. We find and book a space near your office, so your team is away from their desks and the day job. UK only, for now.

Customers

Five for day two. Bring your own, or we'll recruit them for you, at cost.

Travel + stay

Our travel and accommodation are billed at cost.

Team size

4–8 people. Four to six is the sweet spot.

Who decides

The person who makes the call is in the room for both days. Whoever holds the budget opens day one and hears the result at the end of day two.

Bring

The decision, whatever evidence you already have, and someone comfortable building with AI.

What’s included: Facilitation by Ross, the venue, the prototype build, designing and running the customer sessions, the decision document and the Build Loop toolkit.

Not in scope: We don’t become your PM, we don’t ship production software, and we don’t guarantee the hypothesis will land. We do guarantee you’ll know either way.

FAQ

Common questions.

Talk it through

Tell us the decision you’re stuck on.

£9,000 for the Build Loop, venue included. No obligation. Tell us what you’re weighing up and we’ll come back within one working day. Next available dates: mid-February 2027.

  1. 1You send us the decision
  2. 2A 30-minute call to work out whether it’s right for a loop
  3. 3We write the scope, then walk you through it on a second call
  4. 450% holds your dates, the balance after
Your part in this decision

Ross reads every message and replies within one working day.

© 2026 Skysoclear Ltd. Registered address: Skysoclear, 20 Wenlock Road, London, England, N1 7GU. Privacy · Terms · Contact

Existing client? Login