Use cases

Real work, with the decision always yours.

Each case shows what you ask, what Kruvo does, where it stops for you and what you get back. Three of them run in the browser, with your consent.

06
Use cases
03
BrowserComing soon
Browser · CalendarBrowser · Coming soon

Log the week's hours in the timesheet portal

Consultant, Friday 17:40

You ask

Fill in my timesheet for this week from my calendar and stop before submitting.

Kruvo does
  1. Asks once to use timesheets.example.com, then opens it in Kruvo's own browser profile.
  2. Reads the week's calendar and enters each day's hours and project codes.
  3. Shows every step in the live panel; you can pause or take over at any moment.
Stops for you

Submit is a sensitive action: the form waits for your click.

You get

Timesheet filled and a summary of hours per project.

Browser · FilesBrowser · Coming soon

Reconcile supplier invoices against the spreadsheet

Finance, month end

You ask

Compare the invoices in the supplier portal with invoices.xlsx and list every difference.

Kruvo does
  1. Opens the supplier portal after your consent and reads the invoice list.
  2. Compares amounts, dates and references with the spreadsheet in your workspace.
  3. Prepares the differences with a link to each source.
Stops for you

Any download from the portal asks first; nothing is paid or approved.

You get

differences.xlsx with a row per mismatch.

Jira · GitHub · Browser · SlackBrowser · Coming soon

Publish the weekly status report on the intranet

Engineering lead, Monday

You ask

Draft this week's status from Jira and GitHub, post it on the intranet page and tell #team.

Kruvo does
  1. Collects closed issues, open risks and merged pull requests from Jira and GitHub.
  2. Writes the report in the team's template and links every claim to its source.
  3. Opens the intranet in Kruvo's browser after your consent and places the draft on the page.
Stops for you

Publishing the page and sending to Slack stop for approval; you read the draft first.

You get

Published page, one Slack message, sources attached.

Terminal · Files · Specialist coworker

Review a repository for vulnerabilities

Developer, before a release

You ask

Review this repository for security issues and propose fixes.

Kruvo does
  1. The security coworker reads the code and dependency manifests in the workspace.
  2. Runs read-only checks in the terminal and rates each finding.
  3. Drafts a fix for each confirmed issue.
Stops for you

Writing to the repository and running installers wait for your approval.

You get

security-review.md with findings, severity and proposed patches.

Automation · Telegram · Gmail · Calendar

A morning briefing on your phone

Founder, 08:00

You ask

Every weekday at 8, send me what matters today: calendar, new emails that need me and open approvals.

Kruvo does
  1. Runs on schedule in a designated desktop session.
  2. Reads the calendar and the inbox and drafts a short briefing.
  3. Delivers it to Telegram with the approvals that are waiting.
Stops for you

Unattended runs cannot approve themselves; you decide from the phone.

You get

One message before your first meeting.

Gmail · Outlook

Triage the inbox and draft the simple replies

Operations, after lunch

You ask

Sort today's inbox, archive newsletters and draft replies to the simple requests.

Kruvo does
  1. Groups messages by what they need: reply, forward, wait, archive.
  2. Drafts replies in your tone for the routine ones.
  3. Leaves anything ambiguous for you with a one-line summary.
Stops for you

Sending is always a human click; drafts wait in the mailbox.

You get

A clean inbox and drafts ready to send.

What Kruvo never does on its own

  • Pay, transfer money, sign in with your credentials or change permissions.
  • Send, publish or delete permanently without a human click.
  • Use your everyday browser or act on a site you have not allowed.

Coming soonThe browser cases arrive with the next release.

Download Kruvo