NestNarrative: Staging Lookbook Builder

Problem and target customer

Why this exists

Customer problem

Stagers assemble project photos, product links, and service explanations in separate design files and social posts. Seller prospects can admire the work but cannot explore a coherent room story or submit a consultation tied to the agent who referred them.

Who pays

Independent home stagers and small interior styling studios that win seller work through real-estate agent referrals and visual portfolios.

Business model

Monthly studio subscription with limits based on published lookbooks, collaborators, and retained lead history.

Editorial note

The core decision is to turn finished project photography into navigable proof, not to simulate rooms. Manual product tags preserve the stager's judgment and make the public page useful without claiming live retailer data.

Referral context belongs on the consultation, not in a separate spreadsheet. Capturing the agent code and originating lookbook together lets the studio understand which visual story moved a seller to act.

A compelling gallery alone is not validation. The beta should show that sellers can connect a room to their own property need and give the studio enough context for a productive first conversation.

Choose your next step

What do you need next?

Evaluate the operating tradeoffs quickly, or inspect how to build the MVP.

Evaluate this ideaSee the cost and deployment preview

Compare the three operating paths at the default workload before opening the full calculator.

See cost preview Build this ideaInspect the build blueprint

Review MVP scope, workflow, states, data rules, architecture, and acceptance criteria.

Open blueprint

Evaluation preview

What would it take to run?

Directional infrastructure estimates for the current 250 room images assumption. Open the full calculator when you are ready to change it.

Open full cost and deployment

ManagedSelected

$5-$30/ month

Managed runtime, database, and image job for lookbook publishing and lead capture.

Lowest operating effort

Lean self-hosted

$7-$28/ month

One operator-managed server handles the app, database, and image processing.

Lowest baseline cost

More control

$40-$105/ month

Separate application, database, and media capacity for a larger public portfolio.

Most separation and control

Build blueprint

Build the first paid use case

Product goal

Who it serves and what it must change

Target user: A home stager publishing project proof and a seller exploring a relevant room before requesting a consultation.
Problem: Portfolio images lack the room context, product references, and referral attribution needed to move a seller from inspiration to a useful inquiry.
Measurable outcome: A stager can publish a room lookbook with valid product tags; a seller can browse it and submit a complete consultation request that retains the referring agent code.

MVP scope

What ships now and what waits

Included

Studio editor for lookbook title, project context, rooms, captions, and publication state
Room image upload, ordering, focal point, and manual product hotspots
Product cards with retailer URL, displayed price note, availability note, and disclosure
Public lookbook browsing with room navigation and consultation CTA
Consultation form and lead inbox with referral-code attribution

Excluded

AI virtual staging
Retailer inventory synchronization
In-app product checkout
Full client project portal
Automated referral commission payouts

UX and user flow

Screens, actions, and states

Lookbook Library

Let studio staff create, duplicate, preview, publish, and archive room stories.

Create lookbookOpen draftPreviewPublish

Room Editor

Arrange photography, write context, and place product hotspots within image bounds.

Upload imageReorder roomAdd hotspotAttach product

Public Lookbook

Present the staging story and reveal tagged furnishings without obscuring the photography.

Open roomInspect itemVisit retailerRequest consultation

Consultation Inbox

Show seller context, property timing, lookbook origin, referral code, owner, and follow-up state.

Assign leadAdd noteChange statusCopy referral details

Primary flow

A stager creates a lookbook, adds project context, and uploads ordered room images.
The stager places normalized hotspots and links each to a product card with a current note and external URL.
Preview checks missing alt text, broken required fields, and hotspot bounds before publication.
A seller opens the public story through an agent referral link, explores rooms, and submits property and timing details.
The studio reviews the attributed inquiry and moves it from New to Contacted, Qualified, Booked, or Closed.

Loading, empty, and error states

Draft
Preview blocked
Published
Archived
New lead
Contacted
Qualified
Booked
Closed

Core entity outline

Entities and business rules

Lookbook

Defines one public staging story and its publication metadata.

Fields: title, slug, summary, property_type, style_tags, status, published_at
Relations: Has many Rooms, May generate many ConsultationLeads

Room

Stores an ordered scene and its editorial context.

Fields: lookbook_id, name, caption, image_key, image_alt, sort_order
Relations: Belongs to Lookbook, Has many Hotspots

Product

Describes a furnishing or decor item referenced by a hotspot.

Fields: name, retailer, external_url, display_price_note, availability_note, disclosure
Relations: Referenced by many Hotspots

Hotspot

Maps a product to a normalized point on a room image.

Fields: room_id, product_id, x_ratio, y_ratio, label
Relations: Belongs to Room, References Product

ConsultationLead

Captures seller needs and the lookbook and agent path that produced the inquiry.

Fields: lookbook_id, referral_code, name, email, property_location, timeline, budget_band, message, status, owner_id
Relations: Belongs to Lookbook, May reference ReferralPartner

Business rules

A lookbook cannot publish without a unique slug, summary, at least one room, and alt text for every room image.
Hotspot coordinates are stored as 0-to-1 ratios and must remain within image bounds at every breakpoint.
External product URLs open as clearly labeled retailer links; displayed price and availability are editorial notes, not live guarantees.
Referral attribution is captured on first valid visit and retained through consultation submission unless the user enters a different explicit code.
Archiving removes a lookbook from public navigation but preserves its lead history and source attribution.

Architecture and data flow

Components, integrations, and controls

Public portfolio

Render optimized lookbooks, room navigation, product overlays, and consultation entry.

Studio editor

Protect media, hotspot, publication, referral, and lead operations.

Application API

Validate publication, normalize hotspot data, capture attribution, and enforce lead transitions.

PostgreSQL database

Store lookbook structure, products, referrals, leads, and status history.

Object storage and image pipeline

Keep originals and generate responsive room variants.

Integrations

Object storage for room photography
Transactional email for consultation receipt and studio notification
Optional Make webhook for an approved CRM or referring-agent handoff

Data flow

An authorized upload is validated, stored under a studio prefix, and queued for responsive variants.
The editor stores room order, captions, and normalized hotspot coordinates independently from image dimensions.
Publication validates required content and makes the slug available to cached public pages.
A referral visit stores the code in a first-party session; a submitted consultation records that code and lookbook ID with the lead.

Failure handling

If image processing fails, keep the room in Media failed and block publication while allowing a replacement upload.
If a retailer link is invalid, flag the product in preview without deleting the room hotspot.
If lead email fails, preserve the inquiry in the inbox and provide a delivery retry.

Security

Authorize all studio writes server-side and isolate media keys by studio.
Validate image type and size, strip unsafe metadata, and use signed upload URLs.
Rate-limit consultation forms, escape editorial fields, and avoid exposing seller details in public analytics.

Rate limits

Limit concurrent image uploads and transformation jobs per studio.
Throttle consultation submissions by IP and email with a bot challenge after bursts.
Bound email and optional webhook retries with delivery history.

Deliverables and acceptance

Definition of done for the MVP

Deliverables

Responsive public lookbook and consultation pages
Protected library, room editor, preview, referral, and lead inbox
Schema, migrations, media adapter, and representative staged project
Responsive image processing and hotspot positioning
Tests for publication guards, attribution, permissions, and failed media

Acceptance criteria

A stager can upload two rooms, add product hotspots, preview the story, and publish a unique public slug.
Hotspots remain aligned with the intended item on phone and desktop image sizes.
A lookbook missing image alt text cannot publish and identifies the blocking room.
A consultation started from an agent-coded URL retains both the referral code and originating lookbook.
When image processing fails, the current published lookbook remains available and the failed replacement can be retried safely.

Recommended stack

Enough technology for the first version

Web application

Next.js and Tailwind CSS

Combine fast public lookbooks with a protected visual editor.

Data and auth

PostgreSQL with Auth.js

Represent ordered rooms, shared products, referrals, and lead ownership relationally.

Media

Cloudflare R2 with Sharp

Store originals and create responsive room variants with controlled cost.

Resend

Confirm consultation submissions and record failed studio notifications.

Why this is sufficient

The product is driven by image publishing, spatial tags, and source attribution. A server-rendered portfolio with relational editorial data and an explicit media pipeline is sufficient; generated imagery would weaken the trust boundary.

Not required for the MVP

LLM APIImage generation APIPayment processorRetail inventory APIVector database

Next stepTurn the blueprint into an execution plan

Copy the build prompt, model the operating cost, and choose where to deploy.

Build and ship

Execution

Build, price, and deploy the MVP

Once the blueprint is clear, use the prompt, cost model, and deployment options to start building.

Build prompt

Copy this into a builder

Build a media-forward Next.js application with a protected studio editor, PostgreSQL, and object storage. Keep product tagging manual and do not add AI room generation.

Build prompt

Your build prompt is ready

Open the prompt pack whenever you are ready to take this blueprint into your builder.

Based on the blueprintReady for your builderFollow-up steps included

Cost calculator

Model the MVP operating cost

A technical run-cost estimate for the first production version. Team, acquisition, payment fees, and business COGS are excluded.

Estimated monthly total$5-$30

$5-$30 per 250 room images

Room images managed / month250 room images

Selected pathEasiest

Pricing checkedAug 2, 2026

Cost breakdown

$5-$30 per month

Low and high values allow for usage variance and plan headroom.

Managed portfolio deployment

Managed runtime, database, and image job for lookbook publishing and lead capture.

2.5K room images included, then $5-$15 per 2.5K room images

$5-$25

Lookbook media storage

Object storage and operations for room originals and responsive variants after the free allowance.

Monthly allowance from this idea's operating profile

$0-$5

Included

Application and database hosting
Room image storage and transformation
Backups
Routine consultation email

Not included

Photography and styling labor
Retail product purchases
Domain purchase
CRM subscriptions
Legal, disclosure, or referral-policy review

Pricing basis

The estimate combines the selected infrastructure path, required operating modules, selected optional modules, and usage above included monthly allowances. Taxes and regional uplifts are excluded.

Railway pricing Cloudflare R2 pricing

Deployment options

Pick the operational tradeoff

Choose based on operating preference, not only the headline price.

EasiestRecommended

Railway

Host the public portfolio, editor, database, and image job with a short setup path.

$5-$25/month before extra media

Good fit

Small staging studio
Managed deployment
Moderate portfolio

Limitation

Image processing and storage traffic can increase usage charges.

Deploy NestNarrative

Cheapest

Vultr

Run the app, worker, and database on one small Vultr VPS with Docker Compose and explicit backups.

$7-$23/month

Good fit

Cost-sensitive launch
Single server
Technical operator

Limitation

The studio or contractor owns backups, patching, and media-job monitoring.

Deploy on Vultr View the lean VPS guide

More control

DigitalOcean

Separate application, worker, data, storage, and backup responsibilities as the workload grows.

$40-$100/month

Good fit

More lookbooks
Separated media
Operational headroom

Limitation

More services require more configuration and observability.

Explore DigitalOcean View the separated cloud guide

Start building

Prototype, automate, then deploy

Recommended route

01Vibe-coding builderPrototype the room-story journey

Use Lovable to test lookbook editing, hotspot placement, public room browsing, product detail, referral capture, and the studio lead inbox.

Open Lovable 02AutomationHandoff qualified consultations

Use Make as optional glue to send a complete consultation request to the studio's existing CRM or notify the referring agent after staff approval.

Open Make 03DeployPublish lookbooks and manage leads together

Deploy the public portfolio, protected studio editor, database, and media credentials on Railway as one maintainable application.

Open Railway

NestNarrative: Staging Lookbook Builder

Is this worth validating?

Build this if

Avoid this if

Validate first

Why this exists

Customer problem

Who pays

Business model

What do you need next?

What would it take to run?

Build the first paid use case

Who it serves and what it must change

What ships now and what waits

Included

Excluded

Screens, actions, and states

Primary flow

Loading, empty, and error states

Entities and business rules

Business rules

Components, integrations, and controls

Integrations

Data flow

Failure handling

Security

Rate limits

Definition of done for the MVP

Deliverables

Acceptance criteria

Enough technology for the first version

Next.js and Tailwind CSS

PostgreSQL with Auth.js

Cloudflare R2 with Sharp

Resend

Why this is sufficient

Not required for the MVP

Build, price, and deploy the MVP

Copy this into a builder

Your build prompt is ready

Model the MVP operating cost

Usage assumptions

$5-$30 per month

Included

Not included

Pricing basis

Pick the operational tradeoff

Railway

Good fit

Limitation

Vultr

Good fit

Limitation

DigitalOcean

Good fit

Limitation

Prototype, automate, then deploy

Related ideas

Luxury Interior Studio Client Portal & Project Tracker

Luxury Home Staging Studio with Virtual Room Proposals

Luxury Property Showcase with Virtual Tours & Private Buyer Portal

Multi-Trade Project Request Hub for GCs

AgencyOS: Agency Website & Lead Engine

Interior Designer Portfolio with 3D Mood Board Builder