Browse this guidePlan your first project
Using ProvenienceUpdated 2026-11-12

Plan your first project

Provenience is in development. You cannot sign up for a working project workspace from this site yet, but you can work out whether the planned workflow fits how your business operates.

Start with one piece of work

Choose something with a clear beginning and end: a remodel, an agency delivery, a consulting engagement. It should have a known set of people and enough communication that finding past decisions is already a chore.

A project has its own roster. The business's shared Site phone number and email address capture conversations across projects; with a customer on a conversation, the customers' one shared active project decides, whoever else is on it. Several shared active projects or none wait for an administrator. Without a customer, every registered participant must share the job: one shared active project files there, several go to the Review Queue, and none is company-level. A project may optionally have its own phone number and email address. Provenience will not collect every conversation across unrelated personal accounts.

Write down three questions

Use questions you already spend time answering. For example:

These questions make the value concrete. A useful result includes records and sources someone can check, rather than simply a confident summary.

Decide what you need to collect

Map each question to its evidence: calls, texts, email, or imported meeting transcripts, and make sure the people involved are on the project's roster. If the answer lives inside a drawing or spreadsheet, remember that Phase 1 stores and catalogs files without interpreting their contents.

Business systems such as accounting or job management take a separate, read-only integration path. There is no fixed supported-vendor list yet. Note the systems you depend on rather than assuming a connector exists.

Give review an owner

Choose a business administrator who knows the work and can resolve unknown senders, unclear categories, and imported recordings. The Review Queue is a regular part of the planned workflow. It is how uncertain records get a human decision.

Phase 1 questions are asked by a business administrator. If your first use case requires a customer portal, different staff permissions, or automated actions in another system, it reaches beyond the initial scope.

Define the close-out

Decide when the work is finished and who will confirm the expectations and actual outcomes collected across it. That review creates a reliable historical record. Automatic cross-project benchmarks and forecasts are deferred.

See the full picture

Read the project walkthrough, explore the capability library, or look at application ideas. Developers can also run the current local substrate; it is not yet a complete project workspace.