Custom ERP for an Interiors Businessour work

We built an interior design and installation business the system it runs on. Sales, design, costing, purchasing, the warehouse, finance and the install crews share one platform, built to replace a patchwork of tools and department spreadsheets.

Illustration of four layered ERP screens: overview, costing, install and purchasing

The Challenge One job, typed into seven or eight systems

Every job passed through seven departments. Planners re-entered the same details in one system after another, and buyers retyped items from spreadsheets because the tools didn’t talk to each other.

The platform One system, enquiry to install

The platform covers CRM, briefing, design scheduling, costing and quotations, purchasing, the warehouse, finance and install operations. Each department has its own screens, and they all work from the same job record.

A product chosen for a room becomes an order line, then a purchase order, then stock in a warehouse location, then an item on the pick list for an install visit. The details are entered once and carried through.

Illustration of a weekly install board with visits and crews

How it works One job, start to finish

From enquiry to a written brief

Sales staff record each customer with its regions, sites, plots and contacts. Every job gets a brief of up to 13 sections, which change with the type of job, and the finished brief goes out as a PDF.

A calendar for the studio

Managers schedule designers on a weekly calendar and see each person’s workload. The system suggests how long each task should take and warns when two tasks overlap.

Room by room, to a quotation

Designers and specifiers choose products for each room against budget groups, and markup and margin are worked out as they go. A quotation can carry several options, and generating it locks the sell values.

From specification to purchase order

Released items land on the order list, where each line has one of more than 30 statuses that track it from release to install. Buyers raise purchase orders from the list, and any change to the specification after release is flagged on the line.

Goods in to goods out

The warehouse books deliveries in against purchase orders and gives stock a location. Flat-pack and workshop queues show what has to be built before a job loads, and pick lists and load manifests come from the same data.

Crews, vans and visits

Operations planners see every visit with a red, amber or green status. They drag visits onto days, tick the installers on site each day, and publish the week. Stock is released for picking once operations has authorised the job.

Invoices matched to orders

Supplier invoices are matched against purchase orders, and anything that doesn’t match is queued for someone to resolve. Overhead purchases follow approval routes set by department and amount.

Illustration of a job margin screen comparing briefed, quoted, signed-off and live margin

Purchasing Every order line in one list

The order list does the job the purchasing spreadsheets used to do. Buyers see every line for every live job, with its loading date and status.

  • Quick filters for lines loading this week or next
  • Lines at risk of missing their loading date are flagged
  • Items to buy and items from stock sit in the same list
  • Queries stay on the line they are about
Illustration of an order list with status counts and order lines

How the project ran A prototype staff could try first

1

Call

We began by talking through how a job moves across the business and where it stalls.

2

Brief

Each department sent the spreadsheets and documents it worked from, and we wrote down the rules behind them.

3

Proof of concept

We built a clickable prototype of the costing, purchasing, warehouse, finance and install screens, so staff could try their working day on screen.

4

Validation

The people who would use each module went through the prototype with us and told us what was wrong. We wrote down the rules we agreed.

5

Production

The prototype and the written rules became the specification. Each module is built and tested behind its own switch, and turned on when the department is ready.

6

Ongoing development

Feedback from each team comes in as tickets and goes out in small releases, while the next module goes through the same steps.

Engineering Built for a business that depends on it

The platform tracks orders and stock for the whole company and feeds its accounts, so most of the engineering is about keeping the figures right.

The Results Most of the business runs on it

  • Almost all of the platform is live with the client’s staff, and the remaining modules go live shortly.
  • A job is entered once and followed from enquiry to install.
  • It replaces the patchwork of tools and department spreadsheets the business ran on.

Running your business on spreadsheets and tools that don’t talk to each other?

Book a 20-minute call. We’ll talk through how your work flows and what a system built around it would cover.