Fully managed
The Floui team builds, maintains, and evolves the integrations.
- Integrations run by the Floui team
- Your team stays on the business
- Adjustments when systems change
Operating models
Choose how to run the integrations: with the Floui team, or self-serve with your team.
With the Floui team, or self-serve with your team.
Contact
Model
Fully managed
Integrations run by the Floui team.
Floui team day to dayBuilds, maintains, and evolves
Your team stays on the businessLess operational load
Model
Self-serve
Your team runs it; Floui trains and supports.
Your team in the builderControl of the solution
Product + CSTraining and support
Two models. Equal weight.
Same platform. What changes is who runs the integrations day to day.
Self-serve
Your team runs the platform; Floui supports with training and support (Product + CS).
- Control in the builder
- Platform training and support
- Specialists when you need them
Included in each model.
Fully managed
- Build and go-live of the integrations
- Day-to-day maintenance and adjustments
- Evolution of the agreed backlog
- Follow-up with the Floui team
Self-serve
- Training to run the platform
- Platform support (Product + CS)
- Low-code builder, and code when you need it
- Specialists on demand, by agreement
How it works. Four steps.
The cycle is the same. What changes is who runs each step.
Alignment
Systems, scope, and who runs the day to day.
Both: Floui and the customer define the model.
Build
Workflows, tests, and go-live.
Fully managed: the Floui team.Self-serve: your team; Floui supports the ramp-up.
Operations
Monitor, adjust, and keep it running.
Fully managed: the Floui team.Self-serve: your team in the console.
Evolution
Backlog, new workflows, and system changes.
Fully managed: Floui delivers what was agreed.Self-serve: your team prioritizes and builds.
When to choose each one.
Fully managed fits if
- The internal team is lean, or focused on the business
- You want go-live without standing up an operations team
- The integrations are critical and need ongoing follow-up
Self-serve fits if
- There is internal capacity to run the platform
- The team wants full control over the workflows
- You prefer to build and evolve at your own pace
When scope grows.
Allocation or additional PS, by agreement
The team covers the demand of the model. Large projects, high-complexity projects, or projects that follow the methodology of the customer may need partial or full allocation, or Professional Services — agreed separately.
Who does what.
Day-to-day roles.
| Activity | Fully managed | Self-serve |
|---|---|---|
| Build and publish workflows | Floui | Customer |
| Monitor and adjust | Floui | Customer |
| Prioritize the backlog | Customer + Floui | Customer |
| Platform training | Included in the follow-up | Floui (Product + CS) |
| Platform support | Floui | Floui |
| Dedicated projects / expanded scope | By agreement | By agreement |
Switching between models.
You can change the path
A customer can start fully managed and move to self-serve later — or the reverse. The change is agreed with the team, at the pace of the operation. It is not a product button; it is an operational agreement.
FAQ
Which operating models does Floui offer?
Two main paths, depending on the plan: the specialist team builds and maintains the integrations for you, or your team runs the platform self-serve in the low-code builder. You can combine both and shift the balance over time.
Is the specialist team included, depending on the plan?
On several plans, yes: the platform and the specialist team come together, depending on the plan. How much is fully managed versus self-serve — and the follow-up scope — changes by scenario and by the project agreement. It is not unlimited scope or hours. Talk to a specialist for the detail.
Can I start fully managed and take over operations later?
Yes. Many teams start with a specialist on the design and the go-live of the workflows, then run and evolve them on the platform — when the plan and the team capacity allow. The reverse works too: if demand grows, the Floui team can take on more of the operation, by agreement.
What changes if I run it self-serve?
Your team uses the low-code builder, workspaces, logs, and alerts to create, adjust, and follow the workflows. The specialist team stays available depending on the plan, for occasional support or more complex workflows. If a connector is missing, we review it and can build it on demand, subject to the third-party API and a connectivity check.
Let’s point to the right model.
A specialist reviews the scenario and suggests fully managed or self-serve.