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 · Project examples

Inspect the work behind the project story

Explore a fictional launch project with a saved plan, reviewed time, a budget and an added client request. Inspect each record to see how Keystone connects the work with its next decision.

Explore the workspace See pricing

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

Keystone Plan with three scheduled launch tasks and one added workshop request.
Fictional Northstar Studio project in the actual local Plan UI, captured 2 November 2026. The added request is unscheduled; task status does not establish client acceptance.

Northstar Studio launch pack

The plan contains research, a launch article and a client review milestone. Inspect the saved tasks and dates, then compare the List and Timeline views. The same project gives each screen a concrete purpose.

A request for an extra workshop

A client asks for an additional workshop. Compare that request with the recorded agreement and retain the manager’s decision. The separate scope-review example demonstrates a fictional request and human review, not a real client dispute or an accuracy result.

Time and budget review

The fictional project records 1h 30m at USD 100 per hour, then uses explicitly identified self-approval. Its approved recorded value is USD 150 against a USD 2,000 budget. This is not independent approval, a payment or a complete project-profitability calculation.

Saved deliverables and acceptance

A separate Client-tab example shows saved article/deck references, copied findings and the completion’s client-decision state. Findings remain advisory. A reference opens the current authorised source; it is not a complete historical file copy. Adding a reference later does not establish which file a client accepted earlier.

Use the example to ask better questions

Inspect the saved records and the caption beside each screen. Check which controls belong to your plan, whether a review decision is recorded and which version a reference points to. Follow the complete guide to try the same steps with your own safe test project.

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.

Keystone Plan with three scheduled launch tasks and one added workshop request.
Fictional Northstar Studio project in the actual local Plan UI, captured 2 November 2026. The added request is unscheduled; task status does not establish client acceptance.
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.
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.
Client tab with included launch work and an added workshop recorded as extra work.
Three launch tasks are manager-classified as included work; the onsite workshop is recorded separately as extra work. This is a fictional local manual decision, not an AI accuracy or legal-correctness result.
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