Three ways in.
One team all the way through.
Each one starts small, with a fixed price and a clear end. Which one you need usually becomes obvious in the first conversation.
Two weeks. A fixed fee. The problem, named.
Before anyone builds anything, it’s worth knowing what’s actually wrong. We talk to your customers, go through your product or service the way they do, and find where value is leaking out.
- The problem, stated plainly — on one page you could forward to your board
- The evidence behind it
- The three fixes worth doing, ranked by value against effort
- A costed plan for the first one
You keep it whether or not we work together afterwards.
- Days 1–2Learning the businessYour team, your numbers, your version of what’s wrong.
- Days 3–6Talking to your customersSix to ten conversations. This is where the real answer usually turns up.
- Days 7–8Going through it end to endAs a customer would, noting every point it gets harder than it should.
- Days 9–10Writing it up, talking it throughA clear document and an honest conversation. No slide theatre.
From idea to something real, in weeks.
A working product you can put in front of users, partners and investors — not a slide deck. We shape the idea with you, design it, test it with real people, and build the version that proves it.
- A working prototype, live and shareable
- Evidence from real users on what works and what doesn’t
- Designs and code you own outright
- A plan for what version two should be — and what it would cost
Everything we make is yours. No lock-in.
- Week 1Shape itWho it’s for, the one job it has to do, and what to leave out of version one.
- Weeks 2–3Design and testFlows and screens, put in front of real users before a line of production code.
- Weeks 4–6Build itA working prototype — web or mobile — that does the core job for real.
Fixed scope. Fixed price. Done properly.
For when you know broadly what you need — a new website, a booking flow that actually converts, an app, an internal tool — and want it designed and built by people who’ll ask why before they ask what.
- A site, app or tool that’s designed and built — not just one or the other
- Set up so you can update it yourself
- Handover and training for your team
- Support after launch if you want it
No surprise invoices. The price is the price.
- FirstA short scoping callWhat it needs to do, who it’s for, and what “working” looks like.
- ThenA fixed quoteOne price, one timeline, written in plain English.
- AfterDesign, build, launchYou see it working early, and often, until it’s live.
Keep going together
Most work doesn’t end at launch. If you want a product partner rather than a one-off project, FigLabs works a set number of days a month — as your product and design function, or alongside the team you already have. It also covers gaps: a vacancy, parental leave, the stretch between one lead leaving and the next arriving.
What we’ll need from you
Things people ask
Who actually does the work?
Hakan leads every project and does most of the design and build personally. Where a project needs a specialism outside the studio, we bring in people we’ve worked with before — named up front — and FigLabs stays accountable for the result either way.
We already have a design or tech team. What would you do?
Usually one defined piece they know needs doing and haven’t had a clear month for — an unowned journey, a prototype, a research programme, or an independent read they can put in front of leadership. The first conversation is with your team, not about them.
Do we own what you build?
Yes. Designs, code, research — all of it is yours once paid for, and it’s set up so another team could pick it up.
We’ve been burned by agencies before.
Almost everyone has, usually because a big programme was sold before anyone understood the problem. That’s why every way in here starts small, with a fixed price and a clear end.
What if we don’t know which one we need?
That’s what the free call is for. It usually becomes obvious in the first ten minutes.
Come with a mess.
Leave with a plan.
Thirty minutes, no charge, no pitch. Tell us what’s not working — or what you want to build — and we’ll tell you straight whether we can help. If we can’t, we’ll tell you who might.