How the AI interior design platform works
VITADOMUS is designed to operate as an intelligent interior architect, personal design adviser, spatial planner, product researcher and purchasing assistant in one connected platform.
It does not simply take a picture of a room and generate a beautiful alternative. It understands the occupants, measures the space, searches real retailer catalogues, checks that things fit and can be delivered, and keeps the whole proposal inside the customer’s budget and timescale.
Concept / technical operating model · proposed capabilities, not a claim of live AI or retailer integrations. Chapters 01–15 explain the supplied operating model; chapter 16 adds the intelligence layer a real build needs; chapter 17 checks the 16 Vision stages for gaps.
Interprets what people need.
Coherent alternatives that fit lives and buildings.
Real goods from approved retailers, never invented.
Dimensions, cost, delivery tested and uncertainty stated.
The complete intelligence process
One connected pipeline, not one clever model: five stages that turn a conversation into a purchasable design.
VITADOMUS is built to behave like an interior architect, spatial planner, product researcher and purchasing assistant in one connected platform. It does not simply take a photo of a room and paint a prettier one.
AI interprets and recommends. Structured data, geometry, calculations and retailer evidence decide what is actually feasible and available.
The pipeline (tap each step)
Why several services, not one model
Understands requests, asks clarifying questions, writes explanations.
Recognises style, objects, finishes and openings in photographs.
Tests collisions, clearances, door swings and routes with real numbers.
Finds genuine records by meaning, appearance and exact filters.
Balances budget, deadline, fit and design coherence.
Renders plans and images, labelled by how reliable they are.
An image generator cannot reliably know whether a sofa is genuinely available, fits up a staircase, or arrives within two weeks. Those answers must come from data and calculation, which is why the proposal is assembled from specialised services.
Collect and interpret customer information
Turn an unstructured request into a structured, editable design brief.
The customer may start with a single sentence, or upload images, plans, measurements and inspiration. VITADOMUS converts whatever arrives into a structured design brief.
“I want to redecorate my living room. It feels dark and cluttered. I like modern interiors, but I don’t know what will look good. I have about £3,000 to spend.”
What the AI extracts from conversation
| Customer statement | AI interpretation | Design implication |
|---|---|---|
| “My room is always dark.” | Daylight and perceived brightness concern | Examine window positions, surfaces and artificial lighting |
| “We have two children and a dog.” | Family use; durability needs | Robust, easy-to-clean finishes and storage |
| “I work from home.” | Additional activity requirement | Investigate workspace and task-lighting options |
| “I hate clutter.” | Storage and organisation priority | Integrated storage; reduced visual complexity |
| “Keep my existing sofa.” | Fixed product constraint | Measure and preserve the existing sofa |
| “I love this Pinterest image.” | Visual design reference | Extract colours, proportions, shapes and materials |
| “I only buy from established retailers.” | Supplier restriction | Search only the permitted retailers |
| “Everything must be ready in four weeks.” | Delivery constraint | Prioritise qualifying delivery options; flag unknown lead times |
The system must distinguish the two. Keeping an existing sofa may be mandatory; preferring oak furniture may be flexible. That distinction drives every later decision (see chapter 04).
Reasoning from lifestyle
“We are a family of four. We watch films in the evening, entertain friends at weekends and need somewhere the children can play. We prefer a calm interior, with little maintenance.”
- Comfortable viewing positions and sufficient seating.
- Circulation that stays usable when guests are present.
- Concealed or easily accessible toy storage.
- Materials suitable for frequent use.
- Adjustable lighting for different activities.
- Furniture arrangements that avoid unnecessary obstruction.
It also recognises trade-offs. A large sectional improves seating but reduces play space and circulation. Rather than choosing silently, VITADOMUS presents two alternatives and explains the compromise.
Analysis is based on information the customer voluntarily provides, not on unsupported personality assessments or hidden assumptions about age, culture or background.
Analyse photographs, floor plans and physical measurements
Build a measurable digital model of the property that software can test, not just an image that looks right.
VITADOMUS needs to understand not just what a room looks like, but what it physically contains and where objects can go.
2D spatial model
Walls, openings, furniture zones, measurements and circulation.
3D room model
Room volume, furniture placement, heights and spatial relationships.
Understanding different inputs
| Input | What VITADOMUS does |
|---|---|
| Room photograph | Recognises visible furniture, finishes, openings, lighting and design character |
| Dimensioned floor plan | Extracts room geometry, scale and labelled measurements |
| Architectural CAD / BIM | Imports usable geometry and structured information where supported |
| LiDAR room scan | Reconstructs surfaces, openings and identified objects |
| Phone video | Analyses a guided walkthrough and flags what needs confirming |
| Voice instructions | Converts speech into room descriptions, dimensions and requirements |
| Manual measurements | Constructs a mathematical room model from the numbers supplied |
Apple’s RoomPlan framework can capture room geometry and objects on compatible devices and produce structured 3D-ready output, and can combine several rooms. But not every photo or scan yields trustworthy dimensions: a photograph with no reliable scale reference is not a survey.
Constructing the room model
For a rectangular room the system may receive: length 4,000 mm · width 3,000 mm · ceiling 2,400 mm · door on the front wall · window on the right wall · radiator under the window · existing sofa and television. It turns these into objects with coordinates, dimensions and relationships.
| Room object | Stored information |
|---|---|
| Wall 01 | Start/end coordinates, length, height, finish |
| Door 01 | Position, width, height, opening direction |
| Window 01 | Position, width, height, sill level |
| Radiator 01 | Position, width, depth, clearance needed |
| Sofa 01 | Dimensions, orientation, location, keep/replace status |
| Room 01 | Floor area, geometry, household use, design priorities |
Provenance: where did each number come from?
Every measurement carries a status and a source. Even customer-measured dimensions stay subject to the customer’s confirmation before anything is bought.
Asking only what matters
“You have provided the room dimensions and window location, but I still need the clear door opening width to assess furniture delivery. Can you measure this?”
The spatial engine asks only questions relevant to the decision in hand, and the customer can correct dimensions directly on the floor plan.
Generate an architectural and interior design strategy
Work like an interior designer: set constraints, test arrangements, apply design knowledge, explain the reasoning.
Once the brief and room model exist, the AI translates them into design possibilities. This is where VITADOMUS should behave more like a designer than an image generator.
4.1 Establish a hierarchy of constraints
| Category | Examples | Treatment |
|---|---|---|
| Mandatory physical constraints | Existing walls, opening locations, furniture geometry | Must be respected |
| Safety / technical constraints | Clearances, stability, electrical or ventilation requirements | Apply appropriate rules and review |
| Customer non-negotiables | Keep dining table, exclude retailers, stay under budget | Respect, or flag as infeasible |
| Customer preferences | Warm minimalist style, walnut finishes, curved furniture | Optimise where feasible |
| Optional enhancements | Feature lighting, artwork, accessories | Include only if suitable and affordable |
A preferred layout that violates a hard constraint is rejected, not rewarded for looking attractive.
4.2 Develop and test alternative arrangements
A spatial-planning engine generates arrangements and tests each one against the project objectives and physical requirements. For a living room it might compare:
- Sofa opposite the television.
- Sofa against the longer wall to increase circulation.
- Two smaller seating pieces instead of one large sofa.
- A multifunctional storage-and-media wall.
- A flexible arrangement that supports different household activities.
4.3 Apply interior design knowledge
Not every principle is a legal or technical standard. VITADOMUS should distinguish four classes: binding requirements, recognised technical guidance, professional design practice and subjective taste, and label advice accordingly.
4.4 Produce an explainable proposal
“I recommend positioning the sofa along the longer wall because this preserves more central floor space, keeps a clearer route to the door and leaves room for a reading chair. I have selected a warm neutral palette to support your calm atmosphere.”
The exact conclusion depends on real dimensions and the customer’s priorities. What never changes is that the reason is shown, so the customer can challenge it.
How VITADOMUS searches for actual retailer products
Real product intelligence: zero fabricated product records.
VITADOMUS should never ask a language model to invent a shopping list from training data. It retrieves actual product records from authorised retailer sources. This is one of the most important parts of the business.
The retrieval flow
Final choices are traceable retailer listings. Concepts without a qualifying match remain concepts.
5.1 Where does product information come from?
A dedicated VITADOMUS Retail Intelligence Engine would use several sourcing methods, each with different permission and data quality:
Retailer interfaces supply product records, variants, images, prices and stock. For example Shopify’s Storefront API exposes variants, SKUs, pricing and an availability flag; access depends on each merchant.
Networks such as Awin distribute participating merchants’ feeds: names, descriptions, prices, images and links, with extra fields depending on the feed.
Richer data: packaged dimensions, finishes, installation and assembly instructions, CAD/3D models, product families, regional delivery. Most valuable for kitchens, bathrooms, tiles, flooring, lighting and made-to-order furniture.
Good for discovery only. Appearing in a search result does not grant permission to reuse photos, scrape a catalogue, claim an integration or treat a listing as live stock.
Google’s merchant product-data specification defines fields such as price, availability and identifiers, but that does not give a general third-party app unrestricted access to every seller’s Merchant Center data.
5.2 How retailer selection works
“Only search established retailers delivering within the UK. I don’t want products from unverified marketplace sellers.”
The retailer policy is applied first, restricting which catalogues and sellers are eligible. Approved brands such as IKEA, John Lewis or Dunelm would be included only where suitable authorised data exists; a retailer’s reputation alone does not establish a live integration. If the customer instead allows independent sellers, the system assesses seller identity, authenticity evidence, returns and delivery policies and reputation signals. The customer stays in control of which suppliers are acceptable.
5.3 Understanding an uploaded product photograph
If the customer uploads a Pinterest image of a green curved sofa, computer vision extracts a specification:
| Feature | AI-extracted characteristic |
|---|---|
| Product type | Sofa |
| Shape | Curved / organic |
| Colour | Dark green |
| Fabric appearance | Velvet-like upholstery |
| Style | Contemporary organic |
| Configuration | Approximately three seats |
| Visual details | Low back, rounded arms, soft silhouette |
The image is turned into a numerical representation (an image embedding) so similar catalogue photos can be found even when retailers use different words. A text search finds “curved green velvet three-seat sofa”; a visual search may also surface a “moss upholstered crescent couch”. Crucially, visual similarity is only the first stage: a lookalike can still be the wrong size, out of stock, too expensive or impossible to deliver.
5.4 Hard filters versus ranking preferences
| Check | Example | Result |
|---|---|---|
| Authenticity | No traceable product ID or retailer page | Exclude from the verified shopping list |
| Retailer policy | Seller not permitted by the customer | Exclude |
| Geometry | Product cannot fit the proposed placement | Reject layout/product combination |
| Budget | Entire scheme exceeds a mandatory cap | Revise or reject |
| Availability | Confirmed unavailable | Exclude from purchasable options |
| Delivery | Cannot meet a mandatory deadline | Reject or flag for the customer |
| Visual appearance | Similar but different fabric or shape | Retain with disclosed mismatch |
| Missing measurements | Door width unknown | Retain provisionally; access unverified |
5.5 What a final product record contains
| Field | Purpose |
|---|---|
| Product name and model | Precise identification |
| SKU / variant ID | Distinguish colour, size and configuration |
| Retailer and seller | Where it is sold |
| Product URL | Direct link to the actual listing |
| Product images | Visual matching |
| Dimensions | Room-fit assessment |
| Packaged dimensions (if supplied) | Delivery-access assessment |
| Material and finish | Specification matching |
| Current price and currency | Budget |
| Availability status | Procurement confidence |
| Delivery region and lead time | Project scheduling |
| Data source and checked timestamp | Auditability |
| Match explanation | Why the AI selected it |
A product missing critical information must never be silently upgraded to “verified”. It remains a provisional candidate awaiting customer or supplier confirmation.
5.6 Keeping information current
- Import permitted product data regularly.
- Normalise and index the records.
- Detect changed prices, availability and variants.
- Refresh shortlisted products before showing purchase recommendations.
- Recheck selected products when the customer proceeds to buy.
- Warn if a selected product has vanished or become more expensive.
An affiliate feed might refresh daily or faster depending on the supplier’s terms; other APIs allow checks nearer purchase time. Only the retailer’s live checkout can ultimately establish the real order price, availability and deliverability.
Select the best combination of products, not just individual items
A constraint-based optimiser treats the sofa, rug, table, lighting, storage and paint as one coordinated design.
Finding a suitable sofa is only part of the problem. The sofa, rug, table, lighting, storage, paint and finishes must work together as one complete design.
Illustrative product weighting
S = Σ ( wᵢ × qᵢ )
S is the overall suitability score, wᵢ the importance of each criterion and qᵢ the candidate’s measured or assessed performance on it. The customer can raise the importance of cost, durability, appearance or delivery speed. These weights are illustrative, not a validated industry standard.
A high score never overrides an unmet mandatory requirement. An oversized sofa cannot become acceptable simply because it looks beautiful and is inexpensive.
Try it: scoring versus hard constraints
Scoring playground
Relationships the optimiser also checks
- Does the rug fit under the seating arrangement?
- Do furniture heights and proportions work together?
- Are the selected colours compatible?
- Does the flooring suit the expected wear?
- Does the lighting support the room’s activities?
- Are materials and finishes consistent?
- Does the whole selection remain within budget?
This makes VITADOMUS more than a product recommender: it becomes a whole-room design coordinator.
Verify dimensions and the entire delivery route
Room fit and delivery access are two different questions. Unknown measurements are never verified access.
This should be one of VITADOMUS’s most distinctive technical functions: proving the item fits the room and can physically get there.
A · Room-fit assessment
Dimensioned furniture objects are placed inside the measured room geometry.
- Wall intersections
- Furniture collisions
- Door-swing conflicts
- Circulation obstructions
- Project-specific clearances
B · Delivery-route assessment
The customer identifies the route from the delivery entrance to the destination room.
- Exterior doors and internal clear openings
- Hallway widths and turns
- Stair widths, landings, headroom
- Lift dimensions
- Package size and weight; assembly or carrying in parts
Try it: test a delivery route
Route checker
A sophisticated version would simulate the movement and rotation of a 3D package through the route. A basic width comparison is a useful first check but is not enough for corners or staircases.
Where dimensions are missing or a full manoeuvring simulation cannot be performed reliably, VITADOMUS shows “Delivery access not confirmed” rather than promising that the item will fit. Apple itself describes camera-based measurements as approximate, which is why customer verification stays in the loop.
Calculate the complete design cost
A full project budget, not just the sum of furniture prices.
For each selected item the system determines quantity, unit price and the extra costs around it, then assembles the whole project total.
For materials sold by area (flooring, tiles) it estimates quantities from the room model and applies allowances for cuts, waste, pack sizes and installation requirements.
Illustrative £3,000 living-room allocation
Budget simulator
Example allocations only, not a quotation or a list of sourced products. Real projects use verified retailer prices, delivery charges, relevant taxes and supported installation estimates.
- If the customer’s chosen sofa costs £300 more than the previous pick, the system recalculates the project total and shows the effect on the remaining allowance.
- It may suggest a lower-cost table or rug, but only if those items are not locked by the customer.
- If the scheme cannot satisfy both budget and mandatory requirements, it explains the conflict and asks which constraint the customer is prepared to change.
Generate the final design using selected real products
A coordinated presentation in which every visible object maps to a genuine retailer record.
Once a feasible product shortlist exists, VITADOMUS creates the coordinated interior presentation.
Design visualisation
Shows the approved arrangement and intended finishes.
Product & material schedule
Identifies actual products, quantities and finishes.
The visualisation engine should use retailer-provided 3D models where licensed and available. If none exist, geometry can be reconstructed from dimensions and approved product imagery, with the limitation disclosed.
Three honesty levels for every image
Geometry and finish are supported by adequate retailer data.
The product is real, but its 3D appearance is estimated.
A creative illustration that is not a guaranteed picture of what will arrive.
This prevents the classic failure: an AI image looks exceptional while the purchased items differ substantially. The customer can select any product in the design and see its genuine retailer record.
What happens when the customer changes something?
A design dependency system re-plans only what a change actually affects.
VITADOMUS needs a design dependency system. A change must not regenerate the whole room arbitrarily.
“I don’t like this sofa anymore. Find a darker green one, but keep my rug and stay within my budget.”
The project stores relationships between objects. Changing the sofa may affect rug size, coffee-table clearance, viewing distance, lighting and the colour palette; it must not automatically change the kitchen floor tiles or another unrelated room.
Every approved revision becomes a saved design version, so customers can compare or restore earlier proposals.
Detailed example: one customer journey
Eleven stages from a first sentence to a ready-to-order schedule.
A hypothetical customer: Redesign my living room.
“My living room is 4 m by 3 m. I live with my partner and our dog. We watch films and sometimes work from the sofa. I want a contemporary, calm interior with a green sofa, new flooring and better storage. Budget £3,000. We live in the UK and want the room completed within four weeks.”
| Stage | VITADOMUS processing | What the customer receives |
|---|---|---|
| 1 · Understand | Extracts household, activities, style, constraints and budget | Personalised brief |
| 2 · Measure | Turns room inputs into geometry; requests missing door/window data | Editable room plan |
| 3 · Explore | Produces suitable layout and style directions | Proposed arrangements |
| 4 · Search | Queries authorised UK retailer data for actual matching products | Genuine product candidates |
| 5 · Filter | Applies dimensions, retailer policy, budget and availability | Shortlisted options |
| 6 · Check | Assesses placement and available delivery-route geometry | Fit and uncertainty report |
| 7 · Coordinate | Selects compatible materials, colours, lighting and furniture | Integrated design scheme |
| 8 · Optimise | Calculates the total; identifies over-budget or late items | Budgeted alternatives |
| 9 · Present | Produces images, plans and detailed specifications | Design package |
| 10 · Revise | Responds to feedback and recalculates affected items | Updated proposal |
| 11 · Purchase | Refreshes retailer data and provides purchase links | Ready-to-order schedule, subject to retailer confirmation |
When nothing qualifies
“I haven’t found a verified product that satisfies all your requirements. You can widen the retailer selection, increase the budget, choose a smaller sofa or extend the delivery deadline.”
The system must never invent a product to fill that gap.
The technical architecture behind VITADOMUS
Interconnected services around one shared source of truth.
VITADOMUS is designed around a set of interconnected services that all read and write the same project record.
| Component | Main role | Suggested technical approach |
|---|---|---|
| Customer application | Website, mobile experience, guided AI conversation | Responsive web app / PWA |
| Language intelligence | Understand requests; ask clarifying questions | Multimodal language model with structured outputs |
| Visual intelligence | Recognise style, objects, surfaces, image references | Vision models and image embeddings |
| Spatial engine | Geometry, clearances, collisions, arrangements | 2D/3D geometry and constraint algorithms |
| Design knowledge engine | Design principles and contextual recommendations | Curated rules, retrieval and AI reasoning |
| Product intelligence | Search authentic retailer records; normalise specs | Retail APIs, authorised feeds, structured database |
| Recommendation engine | Match products by visual and functional suitability | Semantic search plus exact filters and optimisation |
| Cost and logistics engine | Quantity, budget, delivery, feasibility | Deterministic calculations and supplier data |
| Visualisation engine | Plans and interior presentations | 3D rendering and AI-assisted imagery |
| Project intelligence | Save designs, revisions, choices, product evidence | Secure database, object storage, version history |
| Security and governance | Permissions, privacy, audit trail, consent | Identity, access control, encryption, policy enforcement |
A shared source of truth
A product must not exist only as text in a chat transcript. It needs a unique identity linked to its room, position, quantity, retailer, design version and supporting evidence.
This makes the project editable, auditable and reusable.
“I want to replace my living room rug. Keep everything else, find something more durable and spend no more than £250.”
Six months later VITADOMUS can retrieve the approved arrangement, product details, palette and preferences, then search for currently available compatible replacements, without rebuilding the project from memory.
How much autonomy should the AI have?
Intelligent assistance with customer control, not an autonomous shopping agent making financial commitments.
The platform is given several levels of authority. The more irreversible the action, the more explicit the customer’s consent must be.
| Action | Automation policy | Level |
|---|---|---|
| Interpret a customer’s design brief | AI may perform automatically | Automatic |
| Recommend layouts and palettes | AI may propose automatically | Automatic |
| Search approved catalogues | Automatic, within permissions and limits | Automatic |
| Calculate dimensions and totals | Automatic where input data is adequate | Automatic |
| Replace proposed items | Automatic within a draft; customer approval before finalising | Draft only |
| Change a locked customer choice | Requires customer authorisation | Customer approves |
| Declare an item physically suitable | Requires supported measurements and applicable checks | Evidence needed |
| Place an order or take payment | Requires explicit customer action and checkout confirmation | Explicit action |
| Share customer data with third parties | Requires an appropriate legal basis and authorisation | Explicit action |
Social-media connections and lifestyle profiling need extra safeguards. The ICO recognises social-network and lifestyle data in profiling and expects lawful bases, transparency, accuracy controls and data minimisation.
UK advertising guidance (CAP/ASA) requires affiliate marketing to be clearly identifiable where the rules apply, so commercial relationships must not secretly distort the recommendation ranking.
What should be built first?
Prove one complete customer journey for one room with a small set of reliable retailer feeds.
The full ambition is technically substantial, so development is separated into practical levels.
| Capability | First commercial MVP | Advanced version |
|---|---|---|
| AI lifestyle conversation | Yes | Personalised long-term profile |
| Manual room dimensions | Yes | Multi-room spatial intelligence |
| Floor-plan / photo uploads | Yes | Automated reconstruction and correction |
| LiDAR scanning | Later | Supported-device native capture |
| Design proposals | Initial concepts and layouts | Detailed product-aware 3D |
| Real product catalogue | Small set of authorised UK retailers | Broad multi-retailer, multi-country coverage |
| Product matching | Style, dimensions, budget | Multimodal matching with stronger verification |
| Fit assessment | Basic geometry and clear warnings | Complex delivery-route simulation |
| Budget calculator | Yes | Whole-house financial and procurement planning |
| Adaptive changes | Targeted substitutions and recalculation | Advanced design dependency optimisation |
| Purchasing | Direct retailer links | Deeper checkout/fulfilment integrations by agreement |
A few hundred well-structured products, adequate for the initial design categories, may be more useful than millions of poorly described listings with missing dimensions. The required catalogue size is to be established in testing.
Not AI generation. It is obtaining high-quality retailer data, maintaining accurate product identities, matching products to physical spaces and coordinating the final design without introducing errors.
The ultimate VITADOMUS operating principle
Four distinctions, one living digital interior model.
Interprets what people need, even when they cannot express it in architectural language.
Develops coherent alternatives that reflect occupants’ lifestyles, preferences and the building’s physical conditions.
Retrieves actual goods from approved retailers instead of fabricating attractive suggestions.
Tests dimensions, procurement conditions, costs and delivery access, and honestly states what remains uncertain.
The long-term objective is a living digital interior model that customers can continually adapt. Every room, product, material, design decision and approved modification becomes part of an evolving property record.
From understanding your life to designing your real home. The customer describes their needs, the platform understands their space, AI develops appropriate designs, real retailers supply the products, and structured checks help make the project achievable.
Real Product Intelligence + Spatial Fit + Adaptive Design. The underlying AI models and scanning technologies can be integrated from specialist providers; the commercial advantage is how VITADOMUS connects them into one dependable design and procurement process.
This is a proposed technical operating model, not a claim that the complete AI, retailer-integration, scanning or procurement service is currently operational.
The intelligence layer: what a real build also needs
Beyond the source text: the safeguards, loops and measurements that make the model dependable in production.
The operating model describes what VITADOMUS does. A production system also needs the layer below: how it knows it is right, what it does when it is not, and how it improves.
Every fact (a dimension, a price, a style judgement) stores its source, timestamp and a confidence band. The interface shows traffic-light certainty, and anything amber or red blocks a “verified” label.
Removing a wall, an extension, listed or conservation-area property, structural or party-wall questions, gas, electrics or fire safety should route to a qualified human (architect, surveyor, installer), not to the AI.
Design is not finished at purchase. Flooring before furniture, paint before curtains, lead times and fitters create an order of works and a delivery plan that must fit the deadline.
Delivery tracking, damage and returns, substitutions when stock disappears, and a snagging list. The project record stays live so a failed delivery re-enters the loop.
A test set of rooms with known measurements and known retailer data. Track dimension error, match precision, the delivery false-positive rate (must be near zero), budget accuracy, price drift and “invented product” red-team tests.
Conflicting dimensions, unreadable plans, retailer outage, stale feeds. Each has a defined behaviour: state what is uncertain, narrow the claim, ask one question, never guess silently.
Photos of homes are sensitive. Consent ledger, data minimisation, retention limits, deletion, a data-protection impact assessment, and extra care around children and precise location.
Disclose affiliate links and sponsored placements; keep ranking independent of commission; give the customer a visible “why this product” explanation.
Step-free routes, turning space, reach heights, contrast, plus plain-language, dyslexia-friendly outputs. Design for older and disabled occupants, not only the average one.
Prefer keeping and reusing existing items, repair and second-hand sources, durable materials and lower-carbon options, shown as an optional lens.
When several rooms are designed, a shared palette, material continuity and consistent flooring decisions prevent a house of unrelated rooms.
Partners, family or a hired designer can comment and approve. Roles and version history show who changed what.
LiDAR is not universal. A guided non-LiDAR route (tape measure, photo with reference object, video) must reach acceptable accuracy.
Record the outcome: did it fit, was it delivered, did the customer keep it? Corrected dimensions and fit outcomes become a proprietary dataset competitors cannot copy.
Make uncertainty visible, keep humans in control of irreversible steps, and let every number point back to its source.
What is missing from the Vision 16 stages
A gap analysis: every capability in the operating model checked against the 16 Vision stages.
The Vision stages describe the customer experience very well. The operating model adds the rules, evidence and safeguards underneath it. This table checks one against the other.
| Capability in the operating model | Model ch. | Vision stage | Status | What is missing / how to close it |
|---|---|---|---|---|
| Conversation turned into a structured brief | 02 | 10 · 1 | Partial | Vision has the optional “Tell us about yourself” step but no explicit brief object, AI interpretation table or requirement-versus-preference split. |
| Constraint hierarchy (mandatory, safety, non-negotiable, preference, optional) | 02 · 04 | 14 | Partial | Locks appear only at change time. Define the five classes at the start so every later step knows what may not move. |
| Multi-format capture: photo, plan, LiDAR, manual, drawing | 03 | 6 | Covered | Stage 6 covers these well. Add CAD/BIM import, guided phone video and voice dictation. |
| Measurement provenance (customer / imported / scan / unknown) | 03 | 7 | Partial | Stage 7 shows reliability; add a visible source label and status on every dimension. |
| Room as objects with coordinates and relationships | 03 | 6 · 7 | Partial | Describe the object model (walls, doors, windows, radiators, furniture) that the geometry engine tests. |
| Asks only for missing information that matters | 03 | 7 | Covered | Covered by “AI flags the gaps”. |
| Alternative layouts generated and compared with trade-offs | 04 | 9 · 11 | Partial | Add a step that shows two or three arrangements with the compromise explained. |
| Explainable proposal (the “why”) | 04 | 11 | Missing | Add reasons beside every recommendation so the customer can challenge them. |
| Design knowledge classed: binding / guidance / practice / taste | 04 | 11 | Partial | Stage 11 lists principles; label which are regulations and which are taste. |
| Where product data comes from (APIs, feeds, partnerships, listings) | 05 | 3 · 4 | Partial | Vision promises real products but not how data is sourced, licensed or kept honest. |
| Normalised catalogue and full product record (SKU, provenance, timestamp) | 05 | 3 · 15 | Missing | Add the product-record concept to stages 3 and 15. |
| Photo-to-product visual matching | 05 | 2 | Partial | Stage 2 reads a photo; add matching to catalogue items and disclosed mismatches. |
| Hard filters versus ranking; provisional items stay provisional | 05 | 4 | Partial | Stage 4 scores trust; add the filter table and the “provisional, not verified” state. |
| Never invent a product: honest no-match response | 05 · 11 | 4 | Missing | Add the “nothing qualifies” outcome with options (widen, increase budget, smaller item, extend date). |
| Freshness: recheck price and stock before purchase | 05 | 15 | Missing | Add a refresh at purchase time and warnings for price rise or stock loss. |
| Whole-scheme optimisation with weights and relationships | 06 | 13 · 14 | Missing | Stage 13 re-plans to budget only. Add multi-criteria scoring and relationship checks between products. |
| Room-fit and delivery-route verification | 07 | 8 | Covered | Strong coverage in stage 8. Add “Delivery access not confirmed” as an explicit state. |
| Complete project cost (quantities, waste, delivery, fitting, contingency) | 08 | 13 · 15 | Partial | Add quantity and waste allowances, fitting estimates and a contingency line. |
| Honest visual levels: exact / approximate / concept | 09 | 15 | Missing | Label every visual with its reliability level. |
| Dependency-aware changes and saved versions | 10 | 14 | Covered | Covered by locks and versions; show which objects a change touches. |
| The customer journey as an ordered, testable flow | 11 | all | Covered | The 16 stages already form the journey. |
| Architecture and shared project record | 12 | 16 | Partial | Stage 16 shows the digital twin; add the data model and services behind it. |
| Autonomy levels and explicit consent for orders and payments | 13 | 12 | Missing | Add an “AI can / customer must” table and a payment-confirmation rule. |
| Privacy, consent and profiling safeguards (ICO) | 13 | 12 | Partial | Stage 12 is optional-by-design; add lawful basis, minimisation and consent record. |
| Affiliate and commission transparency (CAP / ASA) | 13 | 4 | Missing | Add disclosure and an independence rule for ranking. |
| Build-first roadmap: MVP versus advanced | 14 | 16 | Missing | Add the phasing so the customer-facing promise matches what is live. |
| Core principle and promise | 15 | 1 | Covered | Concept stage states the intent; add the four distinctions. |
Recommended additions to the Vision
Make the brief a visible object and sort every requirement into five classes before any design starts.
Show where product data comes from, the product record, and the recheck at purchase.
Two or three arrangements with reasons, and weighted scoring that never overrides a hard rule.
What the AI may do alone, what needs approval, consent records and affiliate disclosure.
Exact, approximate and concept labels; the no-invention rule and its fallback message.
Order of works, installers, delivery tracking, returns and snagging.
MVP scope, the retailer set to start with, and the metrics that prove it works.
With these seven additions the Vision grows from 16 to 23 stages and every chapter of the operating model has a visible home in the customer story.