# Solutions

Explore solutions on Runlume by industry, tag, and keyword. Review the business context, app combination, and implementation boundaries.

> Runlume provides platform capabilities, independent business apps, and professional services that can be combined as needed. Features, allowances, and delivery scope follow the selected plan or service agreement. Official apps can be selected independently; collaboration follows configured integrations and authorization boundaries.

Original page: https://runlume.app/en/solutions

## [From brand presence to order fulfilment](https://runlume.app/en/solutions/business-loop)

Platform app practice

Connect brand presence, content, discovery, customer follow-up, and fulfilment with Site, CMS, GEO, CRM, and Orders. One business solution on Runlume, not the limits of the platform.

## Where should business collaboration start?

### Should we connect every system or start with one workflow?

Start with a defined workflow, such as website leads moving into customer follow-up and order fulfilment. Identify the participating systems, data scope, owners, and acceptance criteria before expanding collaboration.

### Does every cross-system workflow need an agent?

No. Systems can call APIs and exchange events directly through authorized connections. Agents suit tasks that require interpretation, capability coordination, and follow-up. Both approaches respect account, app-instance, and data-access boundaries.

### Do the illustrated workflows define a project’s deliverables?

The examples illustrate how systems can work together. Actual scope depends on existing systems, interfaces, and business requirements. Deliverables, timelines, acceptance criteria, and responsibilities follow the agreed solution and contract.

## Related pages

- [Platform](https://runlume.app/en/platform)
- [Official apps](https://runlume.app/en/apps)
- [Developers](https://runlume.app/en/developers)
- [About Runlume](https://runlume.app/en/about)