Skip to updates
DevLaunch home

Collect better client briefs and keep approvals moving.

FlowForms 1.1 brings team access, saved answers, branching questions, assigned approvals, PDF and Excel downloads, and more reliable connections to your other tools.

A useful form does more than collect answers. It helps a client finish their brief, gives the right teammate the next decision, and makes those answers easy to use. FlowForms 1.1 puts those steps together in one update and one download. The screenshots below use fictional Northstar Studio and Juniper Studio examples in the real app.

  • Give teammates the right access and clients a private way to finish later.
  • Ask relevant questions, then route each new brief to a named reviewer.
  • Download useful reports and follow deliveries to your connected services.
See who has the next decision and when it is due. All people and client details shown are fictional examples.

Give each teammate the access they need.

Invite colleagues into a workspace as administrators, editors, reviewers or viewers. Editors build and publish forms, reviewers decide the requests assigned to them, and viewers read responses and download reports. Owners control administrator access.

A workspace is shared with its members. Use separate workspaces for clients whose forms and answers must stay apart. Invitation links last seven days, are tied to the invited email, and can be revoked.

Choose access for the work each person does. Fictional Northstar Studio team.

Let a client save their place and come back.

A client can save their answers and copy a private resume link before leaving. Opening it again restores their saved answers and position, including on another device. They get seven days to finish before the link expires.

The link gives access to that response, so share it privately. An administrator can revoke it from the saved response. FlowForms does not email the link automatically.

Save progress without starting the brief again. The link and budget shown belong to the fictional local example.

Ask questions that fit the project.

Branching rules send someone to a later question or straight to submission based on answers they have already given. People can skip questions that do not apply, and a required question on the skipped route will not stop them finishing.

The builder shows the source question, condition and destination together. Try both routes in Preview before publishing. Answers on a skipped route are left out of the submitted response.

Build the route around a relevant answer. Fictional client-intake example.

Turn a submission into an assigned decision.

Add review and approval steps to a form, then follow new submissions in the approval inbox. Each request shows its reviewer, deadline and current status. Reviewers can approve or reject with a note; administrators can reassign a request when someone else needs to handle it.

For more involved work, use conditions, parallel reviews or a return to an earlier review step. The history records what happened and who acted. If an assignment does not match a current teammate, the request waits for an administrator to choose someone.

Notification steps record a message in the inbox. Email, payment and signature workflow steps are confirmations of work completed in another service; they do not send an email, charge a client or perform a legal signing process for you.

See the decision and the steps that followed it. Fictional project brief.

Take the answers into your next conversation.

Download an individual response as a PDF, or export responses into an Excel workbook or CSV file. A PDF is useful for a project folder or kickoff meeting; a spreadsheet makes it easier to review several incoming briefs together.

Reports keep the question labels from the version each person answered. Renaming a question later does not rewrite an older response. Spreadsheet exports include up to 5,000 responses within the export size limit.

Download one brief or export the response list. Fictional campaign answers shown.

Keep a readable copy of an individual brief.

The response PDF includes the submitted answers, form version and date. It is a textual report rather than a bundle of uploaded attachments. If a character cannot be represented in its PDF font, use Excel or CSV to keep the complete original text.

This is the PDF downloaded from the app, shown with fictional client details.

Know whether your connected tool received the update.

Connect a form to a service that accepts webhooks, such as your own CRM or automation workflow. FlowForms sends new submission and approval events, then shows whether each delivery succeeded. Temporary failures retry automatically.

An administrator sets up and enables the destination. They can disable it, replace its signing key, or review a failed event before sending it again. Your receiving tool should recognize repeated events so a retry does not create duplicate work.

Check delivery status for each event. This example uses a local test receiver with fictional data.

Bring existing forms forward carefully.

Existing forms and historical answers are kept when your installer follows the included upgrade guide. A saved response continues using the form version it originally opened, even if you publish a new version while the client is working.

Installations updating from 1.0 need the included sign-in and ownership setup. Old saved links from that version are not accepted; those clients need to start a new response. Review existing workflow assignments before collecting new submissions.

Try it in your own workspace.

  1. Download the single FlowForms 1.1.1 ZIP from your portal and follow the included installation or upgrade guide.
  2. Create a workspace, invite a teammate and choose the access they need.
  3. Add a relevant branch and a project-lead review step to a sample form, then publish it.
  4. Fill in the sample as a client, save the private link, reopen it and finish the response.
  5. Approve the request, download its PDF or Excel report, and enable a connected service when your installer has set up its receiver.