THE PRODUCT, UP CLOSE

Make a plan.
Keep the whole story.

From the first requirement to the next review. Explore the work, conversations, documents and insights that help your team move forward together.

REQUIREMENTv3

A smoother first day.

Give every customer a clear path from sign-up to their first project.

Acceptance criteria, agreed
RELEASE

The onboarding pilot

A delivery window for the plan
DELIVERYIn review

Build the welcome experience

The requirement, the work and the next step.

SSam · Ready for review
01 / PLAN

Make the outcome clear.
Give the work its place.

Define what you need to deliver, organize the parts of the product and choose the next delivery window. Requirements, modules and cycles give everyone the same starting point.

Start with tasks when that is enough. Bring in the richer planning model as the project grows.

WHAT
A report customers can take awayv3

PDF and CSV match the report.

WHERE
Reporting & exports
WHEN
Pilot releasev0.9
RequirementEnhancementFeature requestChange request
SprintPhaseMilestoneRelease
01

Define the outcome

Requirements hold the statement, acceptance criteria, owner and priority. Keep amendments as versions, connect delivery tasks, and distinguish enhancements, feature requests and change requests.

02

Give it a home

Modules organize a capability or product area. Group related requirements and work so a team can see the part of the product it owns.

03

Choose the delivery window

Use sprints, phases, milestones or versioned releases. See dates, status, progress and the tasks included in each cycle.

See it in Keep · Requirements, versions, delivery, modules and cycles
Read the walkthrough

A real Keep requirement with its statement, acceptance criteria, owner and details rail, followed by versions, delivery tasks, modules and cycles.

  1. Browse the requirement stream and open the export feature request.
  2. Read acceptance criteria, open Versions, then inspect its Delivery tasks.
  3. See the Reporting & exports sample module in Plan.
  4. Explore the cycle cards and clear the status filter to see the complete set.

Recorded in Keep with sample data. Silent video.

Continue to Work

02 / WORK

Know what’s next.
See what’s getting done.

Turn the plan into tasks, bugs and chores. Give the work an owner, make blockers visible and keep each handoff connected to the reason it exists.

Choose the view that helps today: a focused list, a Kanban board or a Gantt timeline.

Your agent can pick up the work and leave the handoff. Your team sees what changed, even when you haven’t opened Keep.

Open
Task · Build the exportOwner · Due Friday
Chore · Prepare the pilotOwner · Due Friday
In progress
Bug · Fix column orderOwner · Due Friday
In review
Task · Check the PDFOwner · Due Friday
01

Choose your view

Move between list, Kanban and Gantt. Filter the work, open a quick preview and keep the wider project in view.

02

Make the next step clear

Tasks, bugs and chores have owners, priorities and due dates. Subtasks and blockers explain what can move and what is waiting.

03

Keep the handoff connected

Trace a task to its requirement, cycle and supporting records. Your team and connected agents work with the same project context.

See it in Keep · Kanban, card details and quick preview
Read the walkthrough

The real Keep Kanban board showing in-progress, review, blocked and done cards for Customer onboarding.

  1. See the work for the current cycle across status columns.
  2. Read owners, due dates, subtasks and blocking records directly on the cards.
  3. Open a quick preview of the PDF export task.

Recorded in Keep with sample data. Silent video.

Continue to Mobile

KEEP GOES WHERE YOU GO

Built for a phone,
not shrunk onto one.

It is the same workspace you open in a browser, laid out for one thumb.

Keep Home on a phone in a sample workspace: a greeting and a box to ask for what you need, two suggestions — review one pending approval, draft the cycle status update — then My time with 20m logged this week and the start of My queue.
Home
Keep’s Work board on a phone in a sample workspace, showing the Blocked lane of Customer onboarding: thirteen cards in view, four blocked, and three cards — self-serve billing blocked on the Stripe webhook and two days late, an SSO handoff, and the export job queue — each with a Move button.
Work · Board
Keep’s Journal on a phone in a sample workspace: the stream grouped by day, with feedback sent from a website about the per-person cost, a standup note, and a published update about what lands before GA.
Journal
Check what needs you

Your queue, the hours you have logged and the approvals waiting, without opening a laptop.

Move the work along

Open a card, change its state, leave a reply or log the time you just spent.

Read what changed

The journal in one column: decisions, updates, questions and feedback as they land.

The same board, in your hand.

The board gives you one lane at a time, each card with the move it needs. Check your queue, change a state, leave a reply or log the time you just spent.

Continue to Journal

03 / JOURNAL

Keep the reasons
behind the work.

A project is more than its task list. Keep the decisions, notes, questions, risks, feedback and updates that explain how you got here.

Stream turns those distinct records into a readable story, with the connections still attached.

NoteDecisionUpdateFeedbackQuestionRiskMeeting
ObservationThe customer needs a complete export.
DecisionInclude PDF and CSV in the pilot.
Open questionWhich columns should be included?
ProgressThe export is ready for review.
01

Different records, different jobs

Notes keep the observation. Decisions keep the choice and rationale. Updates share progress; questions and risks keep the unresolved work visible.

02

Read the story as a stream

Follow dated entries, open the detail and explore linked records. Feedback and meeting outcomes stay alongside the work they explain.

See it in Keep · Journal Stream, a decision and its linked risk
Read the walkthrough

Journal Stream shows dated project updates, decisions and questions beside the story-so-far summary.

  1. Read the project as a dated stream of conversations and updates.
  2. See what needs an answer and what the team has decided.
  3. Open the export decision to read its context, then view its linked risk.

Recorded in Keep with sample data. Silent video.

Continue to Artifacts

04 / ARTIFACTS

Everything you make.
A home of its own.

Give documents, files and finished work a place to live. Keep artifacts independently in Docs, organize a collection or bring them into a project.

Share the work with the people who need it, including people who do not use Keep.

Explore documents and sharing
LAUNCH COLLECTION

The pilot brief.

A clear starting point for the team.

Document · v3
Pilot overview.pdf
Welcome page.html
Discovery notes · Google Docs
Password · Expiry · Revoke
01

More than attachments

Write Markdown documents, upload PDFs and other files, save links, or preview HTML and JSX. Artifacts can live in Docs independently or belong to a project.

02

Keep it organized

Use collections and document versions to keep the working material and finished output together. Connect an artifact to the records it supports.

03

Share with the right people

Create links with optional passwords and expiry, and revoke them when needed. A public artifact link needs no Keep login; Google embeds retain Google permissions.

See it in Keep · Artifact previews and sharing controls
Read the walkthrough

Customer onboarding artifacts displayed as document, file, link and embed preview cards.

  1. Browse documents, files, links and embeds in the project.
  2. Open the export specification and its document preview.
  3. Create a share link with an optional password and expiry.

Recorded in Keep with sample data. Silent video.

Continue to Feedback Agent

05 / FEEDBACK AGENT

Show the team
exactly what you mean.

A visitor points to an element, annotates the screenshot and sends feedback from your website. No Keep login needed.

Your team gets the page context and the next conversation. The visitor can return to their own report and status.

See the widget and installation guide
FIELDWORK / A SAMPLE WEBSITE

A weekend away.

1From $240 per person

“Could you show the per-person cost before checkout?”

Idea · Screenshot attached
01

Capture where it happens

Drop the widget into your website. Select an element, capture the page and annotate the screenshot so the team can see the issue.

02

Turn a comment into context

Send a bug, idea or question without a Keep login. Page context and the screenshot arrive with the report.

03

Keep the reporter in the loop

The reporter can revisit their own submissions and status in the same browser. Your team can connect the requirement or follow-up work.

See it in Keep · Capture, annotate, submit and follow up

Continue to Time

06 / TIME

Your week.
Your time, accounted for.

Start with the My time widget on Home. Open your week, see where the hours went and follow an entry back to the work.

Log time yourself or let a connected working session record it. Your own time and the wider project each have a view.

My timeThis week

9h 30mlogged this week

Review the exportToday · Acceptance criteria checked
45m
01

Your week, at a glance

Open My time from the Home widget. See your weekly total, daily bars, days logged and the projects you spent time on.

02

Log it, or track a working session

Enter a duration and note against a record. The Keep plugin can also meter an active work session, with checkpoints and pauses. Both record your time against the work.

03

Go from totals to entries

Move between weeks, narrow by project and open the record behind an entry. Team views and the Time report give a broader reading where your permissions allow.

See it in Keep · Home’s My time widget, weekly history and project filters
Read the walkthrough

Keep’s My time page with a seven-day bar chart, weekly total, project breakdown, log form and dated entries.

  1. Start with the My time widget beside the welcome greeting.
  2. Open the Log time dock to see today’s entries without leaving Home.
  3. Open your week to see totals, daily bars and dated entries.
  4. Move to the previous week and inspect its logged work.
  5. Filter to Customer onboarding while keeping your own time in view.

Recorded in Keep with sample data. Silent video.

Continue to Reports

07 / REPORTS

The project, in focus.
Ready for the next review.

Understand progress, revisit decisions, review risks and account for time. Reports bring the project’s records into a form you can read, discuss and keep.

A current view helps you act now. A captured project report keeps the reading from that moment.

Project reportOverview · Details
Decision logChoice · Rationale
Risk registerRisk · Response · Outcome
Time reportPerson · Record · Cycle
01

A report for the conversation

Choose Project report, Decision log, Risk register or Time report. Each gives a different reading of the same underlying project.

02

Keep a point in time

Choose a reporting window and move between Overview and Details. Capture a project report as an artifact when you need a record of that reading.

03

Follow the evidence

Read the records behind progress, decisions and risks. The Time report groups logged hours by person, task, requirement and cycle, with entries available as CSV.

See it in Keep · Report gallery, Project overview and details, then Time report
Read the walkthrough

The real Keep Project report with progress, work in flight, blockers and a previous-window comparison.

  1. Choose from Project report, Decision log, Risk register and Time report.
  2. Open the Project report and select Last 7 days.
  3. Switch from Overview to Details, then return to the overview.
  4. Open the separate Time report to explore logged work.

Recorded in Keep with sample data. Silent video.

Continue to Insights

08 / INSIGHTS

See the pattern.
Find the next thing to act on.

See what is moving, what is waiting and how work is distributed. Charts give the overview; the records behind them give you somewhere to go next.

Explore Work, Journal and Deliverables, with a time range for the charts that measure change.

WHAT’S MOVINGOpened Closed
RisksQuestionsFeedbackDecisions
WorkJournalDeliverables
01

See what is moving

Compare tasks opened and closed, the status mix, work by cycle and cycle burndown. Change the time range for time-based charts.

02

See what needs attention

Explore Journal and Deliverables alongside Work. Open risks, questions, feedback and decisions stay visible in the project’s summary.

03

Open the records behind a chart

Supported chart cards open a detailed breakdown. Move from the overview to the items that need a conversation or a next step.

See it in Keep · Work charts, Journal, Deliverables and a record breakdown
Read the walkthrough

Keep Insights shows task trends, status mix, work by cycle and charts for Journal and Deliverables.

  1. Read Work charts and change the time range.
  2. Switch to Journal for its record mix and open risks.
  3. Explore Deliverables to see artifact activity.
  4. Return to Work and open the task-status breakdown.

Recorded in Keep with sample data. Silent video.

Continue to Ask

JUST ASK · WITHOUT OPENING KEEP

Almost anything you do in Keep,
you can do by asking.

Not only questions. File an idea, log a bug, open a task, see where someone’s hours went, share a document. Almost anything you do in Keep, you can do by asking the assistant you already talk to.

Capture it

An idea becomes a requirement.

  • I have an idea — let customers export the per-person cost before checkout.Opens a requirement in the project
  • Log a bug: the export drops the last column.A bug, on the requirement it belongs to
  • Create a task for Priya to review the invite flow, due Friday.A task with an owner and a date

Catch up

An update, without chasing anyone.

  • How is Customer onboarding going this week?Reads the cycle and the records in it
  • What did Alex work on yesterday?Recent activity, by person
  • What shipped in the last release?The release cycle and its notes

Account for time

How long it took, and who worked on it.

  • How long did ONB-180 take?Time entries on one task
  • How much time did Jordan log on the export work?Time by person
  • Log 45 minutes on ONB-126.An entry against your own week

Find and share

Open it, or share it on a link.

  • Open the export spec.Reads the artifact and its version
  • Share the project report as a link that expires Friday.A share link with an expiry
  • Post an update: the pilot is ready for review.An update the team can read

Example requests. A few owner-only actions stay in the app — creating a project, or emptying the recycle bin.

Connect your AI tools
Example conversation Where things stand
You

Where is Customer onboarding this week, and who has been on the export?

Your assistant

Sprint 2 — activation polish. Thirteen cards in view: three in review, two done, four of them blocked.

Two need someone: ONB-131, self-serve billing, waiting on the Stripe webhook and two days late. ONB-182, the export job queue, blocked and due Sep 30.

ONB-180, render the report as PDF, has eleven hours logged so far — the last two by Alex Rivera.

Read from the project’s own records, not from a summary someone wrote
Example conversation An idea, then the work
You

Idea: let customers export the per-person cost before checkout. File it for Customer onboarding.

Your assistant

Filed in Customer onboarding as a requirement. It is open, and it is waiting for you there.

ONB-188Open

Show the per-person cost before checkout.

Created via agent · just nowRequirement · v1

Then: Create a task for it, for Priya.

ONB-189Open

Add the per-person cost to the export

Created via agent · just nowTask · Linked to ONB-188

How it works. Your assistant connects to Keep over MCP: you sign in once, approve the connection, and from then on it acts as you, inside your own permissions. Set it up in Claude, ChatGPT and Gemini CLI, and in other assistants that support remote MCP connectors. Availability can depend on your client version and your team’s settings.

Setup guides
09 / CONNECT

Your agent.
Already at home.

Work from your AI client with the project context your team sees. The connection gives access; the Keep plugin gives the agent guidance for how your project works.

Install and connect Keep
01Your AI clientCoding or conversation
02Your permissionApprove the connection
03Your projectShared records and context
01

Choose your client

Use a compatible coding or conversational AI client. The connection guide covers Claude, Claude Code, Cursor, VS Code, ChatGPT, Codex, Gemini CLI, Antigravity, Devin Desktop and Zed.

02

Authorize your workspace

Sign in and approve the connection. Your existing permissions determine the records and actions the agent can access.

03

Bring context into the conversation

Ask your agent to inspect a requirement, pick up a task or save a document. Install the Keep plugin for its project workflows and guidance.

Not only questions: file an idea, log a bug, open a task, see where someone’s hours went, or share a document with a link. Almost anything you do in Keep, you can do by asking the assistant you already talk to — it acts as you, inside your own permissions. See what that looks like

PRIVATE BETA · BY INVITATION

Bring a real project.

Bring your team and your AI agents into one shared workspace. Sign in to your workspace or request access.