Fohlio, Programa and the FF&E lifecycle gap they leave open

The category of software that helps interior designers build FF&E specifications has grown substantially in the last five years. Tools like Fohlio and Programa have addressed real pain in the design industry: the manual process of assembling specification documents — visiting supplier sites, copying product data into spreadsheets, organising by room type — is time-consuming, error-prone and unsuitable for the quality of work designers are being asked to do.

These are genuine improvements. Designers who use them save real time and produce more consistent, well-documented specifications. That has genuine downstream value: a well-documented specification makes procurement faster, reduces misorders, and produces a better O&M handover document.

The question is what happens after the handover. And this is where the current generation of design-phase tools consistently stops.

What Fohlio does well

Fohlio is one of the most established tools in the hospitality FF&E specification space, with relationships across major hotel brands and a product that has been refined through real hospitality project workflows.

Its core strengths are in the design and procurement phase:

• Specification management. Building and organising product specifications by room type, project phase and location. The interface is designed for design firm workflows, with import capabilities that reduce manual data entry for product records.

• Product libraries. Curated product data from major hospitality suppliers, reducing the time to find and record standard specification data.

• Procurement coordination. Fohlio's "Spec Hub" includes AI-assisted URL ingestion for pulling product data from supplier pages. Their procurement module facilitates coordination between the design firm and procurement companies.

• Brand relationships. Fohlio has established relationships with major brands including Marriott and Accor, which means it is already embedded in some hospitality project workflows at scale.

What Fohlio is less focused on is what happens to the specification after the hotel opens. The platform's frame of reference is the project lifecycle — from design brief to handover. The hotel operator is the recipient of the output, not a user of the platform.

What Programa does well

Programa is a more recently emerged tool with a strong following among boutique and residential-crossover design firms. Its approach is similar to Fohlio's — specification management, product sourcing, project documentation — but with a design-first aesthetic and a user experience that has been praised for its clarity.

Programa's "Smart Fill" feature addresses the same URL-to-spec problem that Fohlio's Spec Hub does: reducing the manual transcription step for product data entry. For designers who work across hospitality and residential, Programa's flexibility across project types is a practical advantage.

Like Fohlio, Programa's scope is the design project. The handover output is a completed specification document; the platform's relationship with the hotel operator ends there.

The lifecycle gap

Neither tool is designed to serve the hotel operator after handover. That's not a criticism — they're built for designers, and they do what designers need. But it creates a structural gap that the hotel operator inherits.

The specification built in Fohlio or Programa produces an excellent handover document. Once that document is delivered, it becomes the hotel's operational record — typically a PDF or a set of exported documents that the hotel has no way to update as items are replaced, no way to query for current availability, and no way to connect to the replacement workflow.

The data that took a design firm two weeks to build (and that the design software made faster to produce) effectively dies at handover. The hotel receives the document, files it somewhere, and proceeds to manage its FF&E through the same combination of memory, email and manual reference that it would have used without any of the upstream data investment.

This isn't a gap that design-phase tools are well-placed to close, because closing it requires a different buyer relationship. The designer is the user and buyer of Fohlio and Programa. The hotel operator is not. For a tool to serve the hotel operator through the operational lifecycle, the hotel operator needs to be the customer — which means a different commercial model and a different product scope.

What closing the gap requires

The lifecycle gap — between handover and the first replacement cycle — requires a platform that serves both the design phase and the operational phase with the same underlying data. The designer builds the specification; the hotel inherits it as a live, queryable record rather than a document; when items need replacing, the specification is immediately available; when items are replaced, the record updates.

This is the lifecycle loop: the design firm's output becomes the hotel's starting data, and the hotel's operational record stays current through the replacement workflow. No seam between design and operations; no PDF that starts dying at handover.

Controlbook is built on this model. Designers build specifications in the platform; hotels inherit a live record; the replacement workflow surfaces the specification when needed and updates it when changes are made. If you want to see how that differs from the design-phase-only approach, book a demo.

Frequently asked questions

Is Controlbook in competition with Fohlio and Programa?

In the design-phase specification market, yes — we provide a tool for building hotel specifications. But our primary focus is the operational lifecycle that follows: the hotel operator's experience of managing and replacing FF&E after handover. Fohlio and Programa are strong tools for design-phase specification; the gap they leave is in the operational lifecycle. Controlbook is built specifically to span both.

Can Controlbook import specifications built in Fohlio or Programa?

We can work with exported data from other specification tools — CSV exports, structured PDFs, and other formats — as the basis for building the live asset record. The quality of the import depends on the format and completeness of the export. If you've used another tool for the design phase and want to bring that data into a live operational record, book a demo to discuss what's involved for your specific documentation.

Would a hotel with Fohlio-built specifications need to rebuild them in Controlbook?

Not necessarily. The goal is a live, queryable record that reflects the current state of the hotel's FF&E. Whether that record is built from scratch, imported from an existing specification tool, or assembled from an existing O&M manual depends on what's available. The starting point is wherever the best specification data currently exists; the end point is a live record that the hotel's operational team can use and maintain.