Templates vs custom
Start fast with a proven baseline, then shape workflows to match how your company actually runs.
Templates
A template is a head start: common steps, sensible defaults, and less setup on day one. Use them when the process is standard across your firm or when you are new to the product and want to see a working pattern first.
Custom
Custom workflows are where openFlow leaves rigid tools behind: duplicate a template, rename and reorder steps, add branches, and save a definition that matches your operating style—not only what shipped in the box.
A practical rollout
Most teams don’t need a “big bang” design session. This sequence gets you to a firm standard in a week or two of real use.
Start close to what you need
Pick the template that best matches the process you already run in email and spreadsheets.Run it for real
Complete one or two full cycles. Note every workaround, handoff, or “we always fix this in chat” moment.Tighten the flow
Fewer steps where work was redundant. Clearer owners where the queue was fuzzy. Add stages only if they change decisions.Make it the default
Save the result as your firm’s standard so new work starts from the same improved baseline every time.
Why it matters for competitive work
Task-based tools rarely model your process end to end. When workflows are yours to express, the way you differentiate—speed, quality, compliance—can show up in how work actually runs, not only in training decks.
Start from a template, make it yours
Pricing, trial length, and limits—then talk to us for rollout questions.