noet home
Sign inSign up

Noet in practice

Watch the work,
not just the result.

Seven jobs from a founder’s or engineer’s week, each with its own trigger and its own ending. Some take a few seconds. One drives a browser while you keep working. One leaves the last button to you. Below each demo you can see the tools Noet really called.

Illustrative walkthroughs with sample data. Connect your tools or provide files to work with your own information.

01 / Bug report to reproduced issue

Watch it reproduce the bug while you keep working.

A customer says exports are broken and their records are gone. Noet opens the staging app, clicks through it and tests both claims. The export does fail, but the records are all there, so the issue it writes says exactly that.

  1. Noet reads the thread and checks Linear for a matching issue.
  2. It drives staging in the background. Drag the live view anywhere, or expand it.
  3. You approve the issue. It reports the 500 and rules out the deletion.
The Slack message
Acme can’t export their records. Getting an error, and they think their data got deleted too. Can someone take a look? Maya, #customer-reports
Starts with
Slack message
Happens in
Live computer use
Ends with
Linear issue, after you approve
Runs for
45 seconds
  • get_slack_thread
  • search_linear
  • computer_use
  • linear_action

02 / “Is the fix live?”

“Merged” isn’t “shipped”. The reply knows the difference.

A customer asks whether the webhook fix is out. The pull request is merged, so a quick answer would be yes. Noet checks the release too, finds the fix hasn’t shipped and writes the accurate reply.

  1. Noet finds the pull request behind the fix.
  2. It checks the latest release, which was cut before the merge.
  3. You read one accurate reply and press send.
The customer email
Hi Jamie, did the webhook retry fix ever go out? We’re still seeing dropped events on our side. Dana, Northwind
Starts with
Customer email
Happens in
Noet, over your inbox
Ends with
Reply sent by you
Runs for
14 seconds
  • search_github
  • browser_action
  • gmail_action

03 / Before the call

Your brief is ready before the meeting starts.

Nobody asked for anything here. A renewal call is coming up, so Noet gathers the last conversation, the open issues and what you said you’d do, then turns them into something you can read in a minute.

  1. The countdown starts without you doing anything.
  2. Email, past meetings and open issues come together.
  3. You read the brief and join.
The calendar event
Northwind renewal, 14:00 to 14:30, with Dana Reyes and Theo Lin.
Starts with
Upcoming meeting
Happens in
Calendar and brief
Ends with
You join the call
Runs for
22 seconds
  • get_calendar_events
  • search_gmail
  • search_meetings
  • search_linear
  • query_moments

04 / After the call

What you promised becomes tickets, without the duplicates.

When the recording ends, Noet finds the commitments in the transcript and drafts a ticket for each one. One of them already exists in Linear, so it’s flagged before anyone files it twice.

  1. Each commitment links back to the line it came from.
  2. Noet checks Linear and flags the duplicate.
  3. You keep two tickets and link the third.
From the transcript
Jamie: I’ll get the retry fix into Thursday’s release. Theo: Can we also get SSO logs exported? Jamie: Yes, I’ll add that this sprint.
Starts with
Recording ends
Happens in
Transcript to tickets
Ends with
Tickets you approved
Runs for
30 seconds
  • get_meeting
  • search_linear
  • linear_action

05 / Security questionnaire

41 questions answered. The three it can’t answer are flagged.

A prospect sends a spreadsheet. Noet fills it in from your SOC 2 report, policies and last year’s answers, with a source beside every cell. When your documents don’t have the answer, it asks you instead of guessing.

  1. Noet reads the spreadsheet and searches your documents.
  2. Answers appear in the cells, each with its source.
  3. Three cells stay open until you answer them.
The email
Hi Jamie, our security team needs the attached questionnaire back by Friday to keep procurement moving. Theo, Northwind
Starts with
Email with a spreadsheet
Happens in
The spreadsheet itself
Ends with
Spreadsheet with 3 cells for you
Runs for
35 seconds
  • get_gmail_message
  • runtime_execute
  • search_gdrive
  • search_indexed_files

06 / Cancel the unused tool

It does the clicking, then leaves the last button to you.

A renewal notice arrives for a tool nobody uses. Noet opens the billing portal, confirms there are no active seats and fills in the cancellation. Then it stops: when Noet is preparing work, the final button is left for you.

  1. Noet checks seat usage in the portal: zero active in 90 days.
  2. It goes through the cancellation flow and fills in the form.
  3. It stops at Cancel subscription and tells you what pressing it means.
The renewal notice
Your Workboard annual plan renews on 14 November for £600. To prevent renewal, cancel by 11 November. The Workboard team
Starts with
Renewal email
Happens in
Billing portal
Ends with
Stops at the final button
Runs for
30 seconds
  • get_gmail_message
  • computer_use

07 / “What was that error?”

The error scrolled away. Noet still has it.

You saw an error an hour ago and cleared the terminal. Press the shortcut and ask. Noet searches your Moments and answers on top of what you’re doing, with the captured screen to prove it.

  1. The overlay opens over your terminal.
  2. Noet searches what was on your screen.
  3. You get the exact error and go back to work.
What you ask
What was that Stripe error I saw earlier?
Starts with
You press ⌥ Space
Happens in
Overlay on your terminal
Ends with
Answer, nothing to review
Runs for
17 seconds
  • query_moments

Keep the final say

Prepared for you. Reviewed by you.

Check the sources, fill in missing details and review the result. Sending, submitting, cancelling or purchasing follows your confirmation settings.

Download
Noet

Continue on your Mac.

We’ll email you the download link.