Workflow-specific products Content, decks, briefs, proposals, legal, and sales each have a clearer buying path.
Review before delivery Draft, edit, collaborate, approve, and export in the same workspace.
Security + procurement path Security policy, support, and Azure Marketplace buying are public.
Microsoft AI Partner Azure Marketplace G2

Gixo Keystone · Product tour

Follow one project from the plan to the client’s decision

Northstar Studio is preparing a launch pack for a fictional client. The team has a delivery plan, a review milestone and a request for one extra deliverable. Follow the same project through the workspace.

Inspect project examples See pricing

Project access, your subscription and the current release determine which controls are available.

Timeline with the launch-task dependency sequence and an unscheduled request.
Actual local Timeline with dated tasks and dependencies. The warning identifies the request without dates. Calculations do not silently change saved task dates.

1. Start with the agreed work

Create a project from a blank plan, a saved template or a supported source. Name the project clearly. Add a review milestone and the tasks needed to reach it. If you bring accepted scope from Arc, review the captured sections before you create the project.

2. Plan the next action

In Plan, add an owner and due date to each task. Switch between List, Board and Timeline without maintaining separate task lists. Use the task panel for details and discussion. Save or discard an open edit before moving to another tab.

3. Record and review time

In Time, record the date, task, duration and billable details. Use Send week for approval to submit the week’s entries for review. The reviewer’s decision preserves the submitted record. Approved time is distinct from drafts and pending submissions.

4. Review the commercial picture

In Money, inspect the project’s budgets and commercial records. Review approved recorded value by currency and check incomplete-rate notices. Prepare the supported invoicing export when the records are ready for your invoicing process.

5. Resolve the added request

In Client, compare the request with the agreed scope and record whether it belongs in the work or needs a separate agreement. Keep the reason. Review any proposed change before confirming it; an AI suggestion, when available, is an input to that decision.

6. Finish the work and record the decision

Complete the milestone only when its work is ready. Review any saved deliverable references and findings, then use the separate client-decision flow. Talk keeps project discussion alongside the work. A saved finding or a completed task does not establish acceptance.

Inspect the work

A fictional project in the actual workspace

These examples use fictional data in an isolated local preview. Each caption explains what its screen establishes. They do not represent a customer result.

A retained one-hour-thirty-minute entry with USD 150 recorded value and identified self-approval.
Fictional 1h 30m entry at USD 100/hour, explicitly self-approved in the local fixture. This demonstrates retained recorded value, not independent review or payroll.
Money showing USD 150 approved recorded value against a USD 2,000 budget.
The local example records USD 150 against a USD 2,000 budget. The balance is not cash spend, recognised revenue or accounting profit.
Saved article and deck references with advisory findings and no client acceptance recorded.
Fictional saved-version references and synthetic producer findings in the actual Client UI. No client acceptance is recorded in this example; copied findings do not establish requirement coverage.

Product copy reviewed 2 November 2026.

More from Gixo

Keep exploring