Product system

One project.
Every working layer.

Project identity, rooms, sourcing, suppliers, documents, visual review, client access, notes, and output stay connected inside one operating project.

Live project data

One shared operational state.

Version history

Current stays explicit.

Client visible

The studio controls the view.

PROJECT OPERATING MODEL01 / 05
DesignerFlow project state with project identity, visual, rooms, and working context
01StructureRooms + lists
02Working dataItems + suppliers
03ReviewDocs + renderings
04SharingClient + comments
05DeliveryQuote + mobile
Connected project

Not eight disconnected tools.

Each working layer inherits the same project context, then passes useful information forward.

01ProjectIdentity + current state
02RoomsSpatial structure
03Lists / ItemsSelections + cost
04SuppliersSource + contact
05Docs / VisualsEvidence + versions
06ClientVisibility + comments
07OutputQuote + delivery
01
Project + Rooms

What is happening in the project right now?

Project identity and room structure establish the context for everything that follows. Lists, activity, media, and documents remain readable as one project state.

DesignerFlow whole-project structure with complete Rooms, Items, and supplier context panelsDesignerFlow whole-project structure with complete Rooms, Items, and supplier context panels
Project state

Identity, status, collaborators, and current work.

Rooms + lists

Spatial context and sourcing scope stay attached.

Recent activity

The latest project changes remain visible.

02
Items + Sourcing

Where does every product belong?

A populated Items Workspace connects the product image and source to its room, list, supplier, reference, quantity, VAT, margin, and status.

Populated DesignerFlow Items Workspace with complete lists, rooms, working table, item rows, and inspectorPopulated DesignerFlow Items Workspace with complete lists, rooms, working table, item rows, and inspector
Source URL

Product context starts at the original source.

BOQ / FF&E

Room, list, unit, cost, and status remain structured.

Project supplier

Supplier memory stays reusable.

03
Supplier memory

Who supplied this, and where did it come from?

Supplier records stop being fragments in inboxes and spreadsheets. Contact, category, website, and project relationships stay available for the next decision.

DesignerFlow Suppliers and Vendors interface with import, shared-library controls, supplier records, categories, contacts, and websitesDesignerFlow Suppliers and Vendors interface with import, shared-library controls, supplier records, categories, contacts, and websites
PROJECT SUPPLIER

Source once. Reuse the relationship.

The item and supplier remain connected to the project record, while the library builds studio memory across projects.

Shared library

Names, contacts, categories, and source websites.

04
Renderings + Documents

Which version is current, and can the client review it?

Visual revisions and technical documents keep their context. The current version stays explicit while earlier work and conversation remain accessible.

DesignerFlow rendering viewer with the complete rendering, current version, version history, and review context
Current version

The active visual stays explicit.

Version history

Earlier revisions remain available.

DesignerFlow document review workspace with a technical PDF, client-visible context, toolbar, and studio-client comments together
Document review

Technical PDFs and client-visible conversation share one review surface.

05
Client collaboration

What does the client see, and what stays inside the studio?

The studio publishes a curated project view. Shared media, documents, lists, and comments stay useful to the client without exposing internal working information.

DesignerFlow client project overview with client-safe project content
Real DesignerFlow client mobile project overview with complete app navigation
CLIENT VIEWProject overview · Restaurant Mozza
ACCESS CONTROL
DesignerFlow external access controls for client and vendor project visibility

Studio inside. Clients curated. Project and shared-list access stay explicit.

06
Notes + Activity

What changed since yesterday?

Project Notes hold the working context. Activity records the visible trail, so the next decision begins with the project rather than another status meeting.

DesignerFlow recent project activity and project note history
Project Notes

Working notes remain attached to the project.

Project history

Recent changes can be read without reconstructing them from messages.

“The project remembers where the work moved.”
07
Output + Mobile

What does the supplier need, and can the project travel?

Current project selections become a supplier-ready Quote PDF. The same studio and client project remains available on mobile where review, sourcing, and site work happen.

QUOTE PDF
Current August 2026 DesignerFlow Quote Request with blockstudio branding, Villa Espresso, filters, populated rows, quantities, units, vendors, brands, and links

Live project selections become a structured request without rebuilding the schedule by hand.

Real DesignerFlow Studio mobile Items Workspace with complete bottom navigation
STUDIOItems Workspace · Villa Espresso
Real DesignerFlow Client mobile project view with complete bottom navigation
CLIENTProject view · Restaurant Mozza
One operating project

The project stays connected from first room to final output.

Start with one active project. No payment method required.

Start freeAsk about fit