ful·crum
/ˈfʊl.krəm/ · noun
The point of support on which a lever turns — where a small force becomes a large movement.
Digital product studio
Before we build it,we find what’sworth building.
Fulcrum9 starts where most studios don’t: with the problem. We observe, question and find the point of leverage — then design, build and grow the product that moves it.
- 01Problem
- 02Understanding
- 03Leverage
- 04Product
- 05Movement
01Why “Fulcrum”
“Give me a place to stand, and I will move the Earth.”
It was never about pushing harder. It’s about where you push.
Every product has a point like that. Finding it is our work — and it’s where every project we take on begins.
02Why “9”
Nine principles. Two verbs.
The 9 isn’t decoration. It’s how we think: four principles to understand, four to make — and one in the middle, where understanding turns into leverage.
Observe
- 01
Problem before product
We don’t take the brief as the problem. We look for the problem inside the brief.
- 02
Context is the data
Users, markets, behaviour, systems. A problem only makes sense where it lives.
- 03
Question the obvious
The most expensive assumptions are the ones nobody wrote down.
- 04
Connect the signals
Insight rarely sits in one place. It shows up where observations meet.
The point05
Find the leverage
Of everything we could do, find the one move that changes the most — then commit to it.
Build
- 06
Make it tangible early
A prototype settles more arguments than a meeting ever will.
- 07
Design is the decision
How it works and how it feels are the same question, answered together.
- 08
Build to learn
Ship small, measure honestly, and let evidence choose the next step.
- 09
Own the outcome
We stay past launch. A product is a beginning, not a delivery.
03What we do
Before the first line of code. After the last.
Code is one part of a product, not the whole of it. We work across the entire line — from the first question to the hundredth release.
- 01
Discover
Understand the problem, the people, the market and the opportunity before proposing anything.
- 02
Define
Turn what we’ve observed into a clear direction: what to build, for whom, and why now.
- 03
Design
Shape the experience, structure and visual language until the product makes sense in someone’s hands.
- First line of codeLaunchWhere code lives04
Build
Architecture and engineering that hold up under real use — web, mobile, backend and integrations.
- 05
Validate
Test assumptions with real users, measure what actually happens, and let evidence steer.
- 06
Evolve
Launch is a starting line. We keep improving, scaling and looking for the next point of leverage.
04Two sides
Two ways we create movement.
With partners
Product Studio
For founders, businesses, organisations and teams with a problem worth solving. We join early, shape the product with you, and build it properly.
- Discovery & strategy
- Product design
- Engineering
- Growth after launch
On our own
Owned Products
We spot opportunities, form a hypothesis and build products that Fulcrum9 owns. We carry the risk — and we keep everything we learn.
- Independent ventures
- Our capital, our risk
- Long-term ownership
- Lessons fed back
The balance is deliberate. Owning products keeps our partner work honest. Partner work keeps our own products grounded.
05Fulcrum9 Lab
Products we conceive, build and own.
Our own portfolio runs on the same loop we use with partners. Some products are being observed, some are being built, all of them are teaching us something.
Meridian
Operations
Field teams still coordinate through spreadsheets and group chats.
BuildLumen
Learning
People finish courses but can’t show what they can actually do.
HypothesisAtlas
Commerce
Small merchants lose repeat customers they never knew they had.
Observe- Have a problem that should be a product? Tell us.
06Why we exist
Most products don’t fail in the code. They fail earlier — the moment someone decides what to build without understanding why.
Fulcrum9 exists to slow down at the start, so everything after it can move faster. We’re a small team of product thinkers, designers and engineers who would rather ask one more question than build one more feature nobody needs.
That’s the whole method. It isn’t a phase we sell — it’s a loop we run, on every product, for as long as it lives.
- 01Observe
- 02Question
- 03Connect
- 04Find the point
- 05Design
- 06Build
- 07Learn
- 08Repeat
07Start a conversation
Start with the problem.
Not a brief, not a spec, not a quote request. Tell us what you’re trying to solve, what you’ve noticed, or what isn’t working — we’ll take it from there.
Or write to us directlyhello@fulcrum9.com