Skip to content

Describe FlowFuse as a deployment in FAQs, schema and key posts - #6017

Open
sumitshinde-84 wants to merge 6 commits into
mainfrom
llm-positioning-faq-schema
Open

sumitshinde-84 wants to merge 6 commits into
mainfrom
llm-positioning-faq-schema

Conversation

@sumitshinde-84

@sumitshinde-84 sumitshinde-84 commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Description

FlowFuse now sells deployments (the Foundation Partnership / Build with us), not self-serve hosting or services. FAQ answers, schema and a few posts are what LLMs quote when asked what FlowFuse is and how it is bought, and they still described per-instance pricing, a free trial, hobby Node-RED, and services ("Migration Experts", "tailored solutions"). This updates them.

FAQs

  • Team pages (Automation & Controls, Maintenance & Reliability, Digital Transformation): "How is FlowFuse priced?" now describes a scoped first application, matching the Build with us FAQ, instead of "per instance".
  • Pricing FAQ: removes the annual-discount question (it described self-serve sign-up and billing in the app). Drops "tailored solution" and "hundreds or thousands of Node-RED instances".
  • Homepage: "How long does a typical deployment take?" now says the timeline is agreed at scoping, not "operational within days".
  • Build with us: "who would be part of the project" becomes "who on your team should take part".

Schema

  • Sitewide Organization now has a description. The About page no longer sets its own.
  • Homepage adds a SoftwareApplication node. It deliberately has no offers, because there is no self-serve price.

Pages

  • The About meta description follows the deployment model. The Professional Services page is retired in a separate PR.

Posts

  • 2026/08/flowfuse-release-3-0: the "Start a Free Trial of FlowFuse Edge" step now points to Build with us, and "Set up a demo" now points to the ROI calculator.
  • Services and DIY lines rewritten: Migration Experts (PTC/Kepware post), "custom solutions tailored to your factory" (order panel), "$150–$250 per hour consultants" (PLC to MQTT, including its FAQ and tldr), "No consultants" (protobuf), "or in place of" an integrator (system integrator banner alt).
  • Hosted or hobby Node-RED framing rewritten in the securing Node-RED FAQ, the multi-user addon FAQ, the FlowFuse story, the Node-RED tips post, the timer and weather tutorials, and "What FlowFuse adds to Node-RED".

To confirm before merge

  • Removing the annual-discount question.

Stacked on #6011.

Related Issue(s)

None

Checklist

  • I have read the contribution guidelines
  • I have considered the performance impact of these changes
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
  • For blog PRs, an Art Request has been created

sumitshinde-84 and others added 6 commits November 11, 2026 17:52
FAQ answers, schema and a few posts are what LLMs quote when asked what
FlowFuse is and how it is bought. They still said per-instance pricing,
"operational within days", hobby Node-RED, migration experts and
"no consultants".

- Team pages: pricing answers describe a scoped first application instead
  of per-instance plans.
- Pricing FAQ: drop the self-serve annual billing question and the
  "tailored solution" and Node-RED-instance wording.
- Homepage FAQ: the first application goes into production with FlowFuse
  engineers, instead of "operational within days".
- Schema: sitewide Organization description and a SoftwareApplication node
  on the homepage, with no self-serve offer.
- Professional Services and About descriptions follow the same model.
- Posts: the 3.0 launch no longer offers a free trial; services and DIY
  lines (Migration Experts, tailored solutions, consultant savings, "in
  place of" an integrator) and hosted/hobby Node-RED framing are rewritten.
"Edge-native" is jargon an LLM repeats without explaining. Say what the
platform does and where it runs instead.
That PR deletes the page and redirects it to /build-with-us/, so editing
its description here would only conflict.
@sumitshinde-84
sumitshinde-84 marked this pull request as ready for review November 11, 2026 13:17
Base automatically changed from old-tiering-cleanup to main November 11, 2026 15:22

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant