UX Research & Concept · Prefabricated Housing · 1 Designer, 3 Devs · Hackathon · 2026 · 1.5 days
After the showroom consultation, the advisor had to manually transfer handwritten notes into three separate systems. Scan2Configure turns scanning into an accurate, complete outfitting, with no rework.
WeberHaus · Scan2Configure
A tablet tool for the WeberHaus advisor: scan exhibits, check dependencies live, see prices instantly — and sync with WeKo, CAD, and the myWeberHaus Designer.
Case study
Scan2Configure digitizes the physical outfitting at WeberHaus. Instead of noting preferences by hand and transferring them into multiple systems afterward, the advisor captures them by scan — right at the exhibit, in the flow of conversation.
The Challenge
Two root problems slow down the outfitting today:
Requirement: reduce effort and errors — from clipboard notes to digital scanner capture. The result: an application with fully integrated synchronization across all three systems.
On top of that: for details and special requests, the advisor had to physically leave the consultation — the catalog and other documents were only accessible in the office, not in the selection hall.
„At the sample, the customer and I move fast — but afterward I re-enter every single line into three systems by hand."Synthesized advisor hypothesis · no interview transcript Assumption/unvalidated
Problem layers
Layer 1 — during the conversation
The handwritten notes on the selection were error-prone; special requests required a trip to the office.
Layer 2 — after the conversation Core problem
Manual, unchecked, repeated transfer into three separate systems.
Layer 3 — after closing optional
The customer sometimes waited several weeks for the contract documents — on paper, sent by mail (risk of loss); further time passed until the signed copy was returned.
HMW
How might we capture the outfitting so that correct, complete data lands in every system without manual post-processing?
Process
Mapped the current selection process along the advisor's role: clipboard capture, data only in the office, manual repeated transfer into three target systems.
Surveyed the configurator and sampling landscape via a rapid AI analysis (hackathon time pressure): Cyncly, palette CAD, Roomle, Tulip, automotive configurators.
Reframed from a "capture tool" to "frictionless scan-as-capture"; sharpened the selection advisor persona.
Designed the scan-to-cart flow, live dependency check, price feedback, and sync logic as an MVP.
Structured scope into 3 phases — with explicit prioritization reasoning for what comes first and what waits.
Goal: Fast entry into the consultation with no technical hurdles.
Goal: Fast, error-free capture within the flow of conversation.
Goal: No incomplete configurations, but no hard block.
Goal: Full control over the configuration.
Goal: Close the consultation with a professional handover record.
Goal: Customer can discuss decisions at their own pace.
Goal: Consultation works even without a network connection.
The five active interactions from the nine-step showroom walkthrough (steps 2, 4, 6, 7, 8) — steps where the system reacts automatically (recognizing the item, calculating quantity) don't count as an interaction.
Competition
Two separate competitive fields: fixtures/sampling tools (B2B, like Scan2Configure itself) and customer-facing 3D house configurators (end-customer self-service, as WeberHaus already offers today).
B2B fixtures & sampling tools Assumption: AI-generated
Prefab-home configurators for end customers Market comparison
Real-time price display throughout the entire planning process — instant, transparent cost control.
Configurator 2.0 with AR feature: photorealistic 3D projection of the house onto your own plot.
Intuitive to use, playful experimentation, save & PDF export.
Wide range of configurable house types — semi-detached, terraced, bungalow.
None of the four is built for the advisor-led showroom moment — that's exactly where Scan2Configure comes in, not in end-customer self-service.
Findings
Distilled from the competitive analysis — hypotheses, not a tested positioning. Assumption/unvalidated
Scan2Configure isn't another configurator — it's the missing handoff layer between the physical showroom and the digital systems that today have to be manually filled in afterward.
Market gaps / differentiation
Insights
Consulting at the sample and working the systems are two separate worlds; the follow-up and office work around the selection eats up the time.
→ One tool brings both together: scan at the exhibit, the system fills itself in — rework is minimized.
Product dependencies need to be checked — in the showroom, the advisor has no way to do this and must rely entirely on their own knowledge and experience (illustrative example: flooring ↔ underfloor heating).
→ Live dependency check on add; conflicts are explained, not just flagged.
WeKo, CAD, and Designer are each maintained by hand today. Pure digitization (scanning instead of a clipboard) would only solve a small part — the real lever is bringing them together.
→ Deliberately chosen: one cart as the single source of truth; sync status visible per system, push instead of retyping.
Price and feasibility feedback should arrive at conversational speed — assumed as a design principle, not tested.
→ Optimistic UI with an instant price delta; sync happens in the background, errors are non-blocking.
Personas
Two personas, derived from requirements documents and industry knowledge — not from conducted interviews. Assumption/unvalidated
„The sample is right in front of us — the system has to follow that, not the other way around." Assumption/unvalidated
„I want to see what my decision costs — right now." Assumption/unvalidated
Scan2Configure is explicitly not a customer-facing self-service tool. The customer is a co-viewer (Phase-2 feature "Customer Mirror"), not a user.
Journey: Before / After
Current vs. target state, side by side — including the emotional shift from consultation to closing. Assumption/unvalidated
The Solution
Scan the exhibit — one tap adds it to the cart.
Look up details & special requests right at the point of consultation — all data digital, no trip to the office.
A dependency conflict is explained and offered a resolution.
Sync status per target system: WeKo, CAD, Designer.
The record, exported as a PDF handout to take home.
One cart as the single source of truth — the three systems follow it, instead of being retyped.
Information Architecture
One advisor flow (customer search → project → scan → cart → review), a separate admin path for back office and catalog maintenance.
Module overview — 15 features
Navigation structure
Data flow & single source of truth
Prioritization
Derived from user sentiment and strategic analysis, each feature assigned to a rollout phase using three guiding questions. Logic is traceable, sequence untested
Hard core — nothing after this works without it.
Highest perceived value for customer and advisor.
The cart needs an owner.
Directly delivers on the 80%-rework hypothesis.
Pareto principle instead of a full rule engine.
A second screen for the customer — Phase-2 candidate.
Which guiding question decides which rollout phase
Explicitly NOT in the MVP
Decisions
Directly resolves the media break; highest job-to-be-done value.
Calculation is the first system the live consultation touches.
Strong value, but hardware-/setup-dependent; not MVP-critical.
High technical coupling; only makes sense once the cart-as-source-of-truth is stable.
No signal from the groundwork, not a real job-to-be-done; distracts from the flow of conversation.
✕ CutUsability Evaluation
Expert review against Nielsen's 10 heuristics — not a study with real users.
What already works, and what's missing in the current implementation.
Heuristic assessment — not a formal WCAG 2.1 audit.
Design Review
Under hackathon time pressure, coding and the interaction concept ran in parallel — the MVP was built while the concept was still taking shape, not after it. The result: implementation and UX concept drifted apart in several places.
A rework wasn't possible before the deadline. So I ran a focused design review, prioritized the most critical deviations, and translated the key corrections into one reference screen — a concrete target for the intended interaction logic, without a full MVP rebuild.
The MVP used red and green for selections and interactive elements regardless of system state, weakening both as status signals.
→ UX decision: red and green are reserved for error and success only — selection and interaction get a neutral hierarchy.
Every room looked selectable; users only learned a room didn't fit the scanned item after choosing it.
→ UX decision: availability is checked as part of the scan — incompatible rooms are disabled immediately, so only valid options can be chosen.
Design refinement in progress: the mockup proves the interaction model — prevent invalid choices instead of explaining them afterward — the visual layer still needs to catch up with the design system: lighter contours, less weight, a calmer hierarchy. In progress
The Pitch
Status quo → solution vision → live demo. Presented by Team HomeWork (Heinrich, Martin, Gilbert, Verena) to the hackathon jury.
wasted by today's process Estimate
„Consultation quality rises when technology works invisibly in the background."
Outcome
Scan2Configure doesn't just solve the capture problem — it solves the real problem behind it: the laborious, error-prone post-processing. Deliberately without collected metrics; these statements are directional and backed by a proof of concept.
A proof of concept supports that the system can deliver these improvements.
A concept and strategy package: product vision, competitive analysis, a prioritized feature roadmap (3 phases), and a scan-to-cart MVP concept with live dependency checking and three-system sync — plus a proof of concept. No production rollout.
Sharpen the personas with real advisor and homeowner interviews, test the dependency logic against the real product catalog, and walk through the sync failure cases (WeKo/CAD/Designer) with the system owners — before building.