Run your first useful business workflow
Choose a practical customer, sales, delivery, billing or marketing workflow and put it into use with your team.
Updated October 10, 2026 3 min read
Choose work your team repeats and needs to do reliably: answering an inquiry, following up on a proposal, starting an engagement or collecting an outstanding invoice. Command Center connects that work to customer records and gives the next person enough information to act.
Start with one complete example before expanding the workspace. The first success should be something a colleague can use, such as an assigned callback or a kickoff checklist attached to the agreed engagement.

Choose the work to improve
For sales, agree who owns an inquiry and when the next contact should happen. For delivery, specify the kickoff tasks and who needs to complete them. For billing, use a controlled invoice and define how the team handles a payment promise or dispute. For marketing, start with a page or audience your team can review.
Walk through the client lifecycle demo to see how those areas connect. Use an industry recipe when it better matches your process.
Put one workflow into use
- Write down the starting situation, owner, required information and useful outcome. For an inspection inquiry, the outcome could be a dated callback attached to the correct homeowner.
- Open Get started and Setup. Prepare the workspace and only the connections that job needs.
- Use a small, authorized set of records. Carry out the workflow and have the receiving teammate find the resulting work without a separate explanation.
- Add AI when its role is clear. It can prepare a response or checklist from available context, while the team retains the decisions required by the action policy.
- Review what still takes copying, searching or chasing. Give your implementer that specific gap rather than requesting an unrelated feature.
Agree who operates the system
Name the people responsible for workspace administration, business decisions, provider accounts, updates, backups and recovery. A self-hosted installation needs a technical owner. A managed implementation needs a written scope covering setup, support, handoff and costs.
Hosting, database, email and model usage can incur costs. Choose the accounts and spending authority before enabling the connected workflow.
What to check
The demo uses fictional records and simulated business effects. Verify your own sign-in, saved records, permissions and required provider before using customer information. An invoice being sent and a payment being received are separate events.
Next: Set up the workspace and use the first-value checklist.