Professional Services

Professional Services engagement methodology

Flomenco Professional Services is project-based help to design, integrate, and cut over production media workflows on Flo. Engagements typically run 8 to 12 weeks from kickoff to a first production workflow.

An active Flo subscription is not required before an engagement begins. Many teams start with discovery and architecture while procurement or subscription setup runs in parallel.

What you get

Workflow architecture mapped to your systems of record
Integrations across storage, rights, metadata, and delivery tools
Team enablement for producers, ops, and approvers
A phased cutover plan that keeps day-to-day operations running
Optional handoff into Managed Services for ongoing ops

Engagement phases

Phases overlap where it helps. Week bands are indicative and finalized at kickoff.

Phase	Focus	Indicative weeks	What you leave with
Discover	Systems, workflows, success criteria, constraints	1-2	Scoped outcomes, stakeholder map, prioritized workflow list
Design	Architecture, data mappings, connectors, security	2-5	Target design, integration plan, environment plan
Build & Integrate	Workflows, accelerators, test environments	4-9	Working workflows in a controlled environment
Validate & Cutover	UAT, parallel run, first production workflow	8-12	First production workflow live, cutover checklist, runbook

Weekly checkpoints keep your stakeholders aligned on progress, findings, and scope decisions.

Sample timeline (8-12 weeks)

Weeks 1-2: Kickoff workshops. Document as-is paths, systems of record, approvals, and exception handling. Agree success criteria for the first production workflow.
Weeks 2-5: Design the to-be architecture. Map metadata and events. Confirm connectors, credentials, and security review needs. Stand up environments.
Weeks 4-9: Build workflows with Flomenco accelerators where they fit. Integrate rights, title metadata, storage, and distribution endpoints. Iterate with your SMEs in demos.
Weeks 8-12: UAT and parallel run. Cut over the first production workflow. Document operating procedures. Decide whether to expand scope or move into Managed Services.

Larger migrations or multi-business-unit rollouts may extend beyond 12 weeks. The first production workflow still targets the 8-12 week window whenever scope allows.

Accelerators and connectors

Engagements reuse Flomenco-built connectors, templates, and patterns so you are not starting from a blank canvas. Common systems include:

Rights and metadata: Rightsline, Fabric, EIDR, Gracenote, Metadat-AI
Storage and transfer: Amazon S3, Google Drive, Box, Dropbox, Aspera
Production and ops: Autodesk Flow Production Tracking, Airtable, Smartsheet
Media processing and playback: Amazon MediaConvert, Chunkify, Twelve Labs, Accurate Player, Cantemo
Other enterprise tools: and additional systems scoped during Discover

Your stack may differ. Discover confirms what we reuse as-is versus what we customize.

Professional Services vs Managed Services

	Professional Services	Managed Services
Model	Project-based	Ongoing coverage
Goal	Design, integrate, cut over	Monitor, handle exceptions, improve
When	Kickoff through first production (and scoped expansions)	After production, or in parallel for mature stacks
Support tickets	Not the primary channel	Complements product support per your agreement

Professional Services is not a support retainer. If you need day-2 ops after cutover, we scope Managed Services separately.

Next step

Book a discovery call and we will recommend a scoped Professional Services engagement, Managed Services, or a blend based on your library size and rollout timeline.