Skip to content

AI Kitchen Planner

Customers describe the kitchen they want in plain words. The planner turns it into a buildable, priced kitchen and a production order, with a kitchen planner in charge.

Role
Concept, UX/UI, build
Stack
Next.js, TypeScript, React PDF
For
Kitchen studios and manufacturers
Year
2026

What it does

Custom kitchens need experienced planners to turn wishes into something that actually fits the room. That takes hours per request, and mistakes often show up only in production, where they're most expensive.

Here the customer writes an email or clicks through a short form. The planner opens a first draft that already fits the walls, respects the window and the water pipe, has a price and explains every decision.

The numbers

  • 23

    planning rules checked on every change

  • 15 min

    from brief to first proposal, target

  • 0

    prices or sizes made up by the model

Brief to first proposal

  • Planning by hand3 h
  • With the planner15 min

Estimate. The planner still reviews every plan before a customer sees an offer.

How it works

The language model only translates words into requirements and asks when something is missing. Geometry, prices and whether the kitchen can be built are decided by code, so the answer is the same every time.

  1. InputBriefEmail, online form or showroom notes
  2. AIUnderstandExtracts room, appliances and wishes, asks what's missing
  3. CodePlanSolver places the modules and explains why
  4. CodeCheck23 rules, from clearances to budget
  5. PersonApprovePlanner edits, customer approves
  6. OutputHand offQuote PDF and a production order as JSON
InputAICodePersonOutput
  • [ Next.js ]
  • [ TypeScript ]
  • [ Zustand ]
  • [ React PDF ]
  • [ Layout solver ]
  • [ Rules engine ]

Screens

1 / 5
Planner overview with pipeline value, new requests and projects by stage
Overview. New requests, the pipeline by stage and the issues the rules caught.
List of customer requests from email, configurator and showroom
Requests. Briefs from email, the configurator and the showroom, read by the AI.
Project cards with floor plan thumbnails, status, price and budget
Projects. Every plan with its status, price and budget, checked on every change.
Handoff tab with project status and the production order as JSON
Handoff. The finished plan goes to production as a structured order.
Intro showing requirements extracted from a customer brief with one open question
The intro walks through the five stages, from one sentence to a production order.

What it brings

  • Faster first offer

    Planners start from a draft that already fits instead of a blank screen.

  • Fewer surprises in production

    Rules catch a hob under the window or a tight island before anything is cut.

  • Planning around the clock

    Customers can sketch their kitchen on a Sunday evening and get a real answer.

  • Clean data for the factory

    Every part with position, size and front, ready for the production system.

Good to know

The manufacturer, catalogue and customers are fictional, and the language model is simulated with recorded answers plus an offline parser for typed text. The layout solver, all 23 rules, the pricing and the production order are real code. Going live needs real model calls, a database, mail intake and a link to the factory's system.

→

Agency ERP