All use cases

Communications department

Order forms — without a folder tree

The service where visitors order forms starts out as a tree of how you sorted them, plus five copies of the same page: Form 1, Form 2 … No visitor searches that way.

The guide has one page for one form — which, and how many — and the visitor adds more. The form is found with a search field that searches your list; the review shows every form on its own, and the order is submitted as a case — the row in your list says how many forms and copies. Advanced, built the simple way.

The gain: one page to maintain instead of five, and a list that lives with you — not in the guide.

Try it as a visitor Rebuild it

See how it was built

The order, in a minute and a half

The editor's single page, the visitor's two forms, the review and the email.

The film in text
  1. The editor's page: which form, and how many. A checkbox lets the visitor add more.
  2. The visitor types a few letters — the field searches your list, nobody browses a tree. And adds another.
  3. Delivery details go on another page: name, address, email.
  4. The review shows every form on its own; Change takes the visitor back with everything kept.
  5. The confirmation says how many: three copies, two forms.

Would something like this be useful where you work?

Flowweaver is still being built. If you would like to try it, or to tell me about a problem you would like to solve, you are welcome to get in touch.

Register your interest

Why Flowweaver exists