> ## Documentation Index
> Fetch the complete documentation index at: https://visaflo.ca/knowledge-base/llms.txt
> Use this file to discover all available pages before exploring further.

# Launch Your Firm

> Turn VisaFlo's product model into a repeatable intake and case-delivery workflow for your team.

## Start with one case type

Choose the case type your firm handles most often or one with a clear, repeatable process. Launching every case type at once creates inconsistent templates, folders, and client instructions. Prove one path first, then duplicate the pattern deliberately.

## Define the operating decisions

Write down the answers before configuring features:

1. Which lead outcomes does the team use: new, qualified, consultation booked, retained, or closed?
2. Who can create a client and case?
3. What information must be collected before a case is ready for review?
4. Which tasks are mandatory, who owns them, and what counts as complete?
5. Which files, status updates, and requests can the client see?
6. Who reviews generated documents before signature or submission?

These decisions become your lead stages, questionnaire fields, case template, workflow, and client messages.

## Build the minimum viable workflow

Configure only the pieces needed to serve the first case type well:

| Workflow element       | Recommended first version                                                      |
| ---------------------- | ------------------------------------------------------------------------------ |
| Lead intake            | One lead form or a clear manual entry rule.                                    |
| Client and case        | One owner, one case type, and a consistent naming convention.                  |
| Information collection | One questionnaire with only the information needed for the next review.        |
| File structure         | A small set of folders that separates client evidence from generated outputs.  |
| Team work              | A reusable workflow with a clear owner and due date for every action.          |
| Client communication   | One invitation message, one follow-up pattern, and one portal visibility rule. |

## Run a controlled pilot

Use a non-production case or one appropriate live case with the people who will actually do the work. Walk through the process as both staff and client:

1. Submit or create the lead.
2. Convert or create the client and case.
3. Send the questionnaire invitation.
4. Upload and organize a document.
5. Create and complete an internal task.
6. Generate a document only after checking the source facts.
7. Review what the client can see.

Capture every handoff that requires a side message, spreadsheet, or memory. Those gaps are the next workflow or documentation improvements to make.

## Make the process durable

After the pilot, publish a short internal standard for the case type: naming rules, required fields, folder structure, task owners, client message templates, and review checkpoints. Then train the team against the standard and make it the default for the next case type.

## Continue building

* [Collect leads](/knowledge-base/leads/collect-leads)
* [Create a case](/knowledge-base/cases/creating-a-case)
* [Send a questionnaire](/knowledge-base/questionnaires/send-invitation)
* [Set up workflows](/knowledge-base/faq/how-tasks-reminders-workflows-deadlines-and-case-statuses-work)
* [Create letters and agreements](/knowledge-base/settings/letters-and-agreements)