Start here

Quickstart

Configure the workspace foundation, add a client, organize delivery work, and complete a first billing workflow in Workspace369.

This quickstart gives a new workspace enough structure to complete a real client workflow. You do not need to configure every advanced module before beginning.

Before you begin

Have the following ready:

  • Your business name and contact details.
  • The teammates who need access.
  • One representative client or test client.
  • A service, product, or billing item you regularly sell.
  • The payment and communication channels your team intends to use.

1. Configure the workspace

Open Settings and review the organization profile, regional defaults, team access, subscription, and the modules your team plans to use first.

Start with the minimum required configuration. Advanced automation, accounting, inventory, and API workflows can be added after the core process is working.

See Workspace setup for a more complete checklist.

2. Add a client

Create a client record with the details your team needs for communication and billing. Add the company, contact methods, address, lead source, notes, and tags when they are relevant.

The client record becomes the shared context for projects, schedules, files, communication, estimates, invoices, payments, and activity history.

3. Create the delivery work

Create a project, task, request, or calendar event based on how the work enters your business. Assign ownership and due dates so the next action is visible.

Do not duplicate the same status in several disconnected places. Keep delivery details attached to the client and use tasks or schedules for actionable commitments.

4. Prepare billing

Create an estimate, proposal, or invoice using the client and the relevant products or services. Review recipient details, line items, totals, payment terms, and the document presentation before sending.

5. Confirm the connected history

Return to the client record and confirm that the delivery and billing activity appears in the expected context. This validates the central Workspace369 model: the team should not have to reconstruct the relationship from separate applications.

Continue from here

Once the basic flow works, continue with:

Was this article useful?

Your answer helps us decide what to clarify next.