Flows

Not a form. Not a chatbot. A guided process with a finish line.

A flow is the unit of work on FormWise. It walks a client through your methodology step by step (as a guided form or a guided chat) and ends in an Artifact they can edit, download, and use the same day.

Pricing Strategy Audit
Flow
Interface
SmartFormCoPilot
Step 2 of 3Pricing inputs
Business model
B2B services · retainer
Where pricing stands today
Hourly, undercutting the market
Run flow
F
Pricing Strategy Report
Generated Artifact
Positioning summary
Price architecture

One flow. Two interfaces. The same finish line. The interface is a presentation decision, not a rebuild.

Every flow captures one job your business does well (an audit, a plan, a diagnosis) and runs it the same way every time. Publish it as a SmartForm when the inputs are known upfront, or as a CoPilot when the right next question depends on the last answer. Either way it applies the same methodology, draws on the same Knowledgebases, and produces the same Artifact. Deploy it in your suite under your brand, or hand it to an agent as a skill it runs mid-conversation.

What's actually running underneath.

01

The interface

SmartForm or CoPilot: a guided form or a guided chat. The same flow underneath, chosen per audience.

02

The workflow

Prompt chains, branches, and decision logic that apply your methodology one step at a time.

03

Knowledgebases grounding

Every step can reference your Knowledgebases (frameworks, PDFs, transcripts) so the output comes from your material, not a model's guess.

04

The Artifact

Every run ends in a structured, editable, downloadable deliverable. The finish line is built in, not bolted on.

Which interface should the flow wear?

Wear the SmartForm interface when…

  • The full input set is known upfront
  • User situations are bounded and predictable
  • The output is a structured document
  • The deliverable should have the same shape every time

Wear the CoPilot interface when…

  • The right next question depends on the last answer
  • The methodology requires contextual questioning
  • The job is diagnosis, qualification, or a guided process
  • You need extracted data to trigger your stack downstream

The unit of work everything else is built on.

Describe the job to the Agent Wizard or build it by hand. Start with one diagnostic. Grow into a suite the market buys.

Start free trial

7-day free trial. Onboarding call included.