Furniture.

Expert data and AI advisory for furniture brands, retail, rental and FF&E.

Book a checkpoint

Free, 30 minutes. Bring one thing that's stuck.

This is for you if...

Every piece of furniture has a different story in every system.

Inventory and utilisation by warehouse are not visible in one place.

The same product carries different data on every channel.

Rental pieces going out, coming back, getting refurbished and retiring are tracked by hand.

Information gets lost between the quote and the order, and demand forecasting runs on gut feel.

Where furniture operations break.

We grew up in a family furniture business. These are the five failures we see most, in roughly this order.

Building with unclear ROI

What did we get for this?
Tech spend, last 18 months
PaidGot back
Demand forecasting$90k?$540k
Product data sync$55k?$290k
Quote to order$60k?$310k
Fleet tracking$65k?$360k
Refurbishment planning$40k?$200k
Total$310k?$1.7M

Eighteen months of roadmap and real spend, and nobody can point at the number it moved.

Inconsistent data

How many of this sofa do we have?
???
?????
Webshop129
Warehouse99
Showroom149

The warehouse, the webshop and the showroom each hold a different figure for the same SKU, and reconciling them is somebody's Monday morning.

Inconsistent business logic

What does “Available” mean?
Webshop
Warehouse
Sales
Rental
Anything not sold out
On the shelf today
On the shelf or on order
Back and refurbished
On shelf, unreserved
Warehouse decides

Available, on order and lead time each mean something different to sales, the warehouse and finance.

Errors customers find first

Who found out first?
Customer10:15

I ordered this sofa last week and now you're telling me it's sold out?

You10:30

Sorry about that, checking with the warehouse

Alert08:47

Last SOF-3310 just sold. It's still live on the webshop.

You08:52

Taken down. Nobody else ordered it.

A sold-out piece stays on sale and a rental comes back damaged, with nothing flagging either one.

A stack your vendor holds

Who holds the keys?
Your vendorYou
Webshop
Quoting tool
Fleet tracker
Data warehouse
Warehouse integrations

Every new channel, warehouse or supplier queues behind a roadmap you do not control.

What fixing it looks like.

The checkpoint call decides which of these you actually need.

Case study.

EUR 2.5M a month lost inside a spreadsheet

Quick-commerce operator, 200+ warehouses

EUR 2.5Mno longer leaking in supplier payments, monthly

A quick-commerce company running over 200 warehouses had outgrown its systems. Master data, inventory, supplier ordering and fulfilment all lived in ungoverned Google Sheets, so procure-to-pay was stuck, demand forecasting couldn't run, and supplier orders didn't match deliveries or invoices. The gap was costing an estimated EUR 2.5M a month. A unified commercial ops platform, integrated with suppliers' systems, gave all of it one governed home.

What changed

  • 80% of fulfilment data entry automated
  • -35% order errors
  • Forecasting and analytics running on governed data

How we help you.

Start with a free call. From there we either run a full value iteration on your stack and hand you the plan, or we stay on as your fractional CTO for data and AI.

  • Checkpoint

    Free, 30 minutes

    Bring one thing that's stuck. We tell you what's wrong with it and what to do first.

    Book a checkpoint
  • Value Iteration

    Scoped engagement, one-off

    We analyse your whole stack and build a pragmatic plan: what's broken, what to fix first, and who should own it. Your team or any vendor you hire can run it.

  • In the Loop

    Ongoing, fractional

    We work with you a few hours a week on what moves the strategy: prioritisation, vendor calls, architecture decisions and hiring.

Questions we get asked.

You get a senior technical decision-maker for a few hours a week, without the hire. In practice that means deciding what to build and in what order, choosing between tools and vendors, setting how your product and inventory data is modelled, and unblocking the decisions your team cannot make on its own.

Usually yes. The lifecycle needs a clear set of states, an owner for each one, and one place that records them. That can often sit alongside the systems you already run. We work out what the ERP can hold and what needs to live next to it.

At the source. Pick the one place each field is authored, give it an owner, and let every channel read from there. Cleaning up channel by channel only moves the disagreement around, and it comes back with the next range.

Most of the loss happens at the handoff, where the quote holds detail the order system has no field for, so somebody retypes what they think matters. We settle what has to carry through, per line and per project, and then connect the two around that.

Only once the data underneath it is modelled properly. Most forecasting failures come from stock, orders and lead times being recorded differently across systems. A better model on that data produces confident wrong answers. Fix the data and a fairly ordinary forecast starts working.

We specify it, sequence it, and stay close while it gets built. The building is done by your own team or by a vendor you choose. Staying close means we write the specs, sit in the vendor calls, review what comes back against what was asked for, and re-sequence when something turns out harder than it looked. That keeps you able to drop us and keep going, which is the point.

The checkpoint call is free. A scoped engagement is quoted once we know what we are looking at, and ongoing advisory is a monthly arrangement. If we think you do not need us, we say so on the call before anything is quoted.

Let's get started.