Noots.ai alpha is live. Expect some bugs while we polish, and tell us when you meet one.Report a bug

Noots.aiNoots.ai

Standups, decisions and the quarter's goals, on the board, not in a doc.

Async standups the team posts instead of attends, with an AI teammate that can write the first draft from the board. A decision register where every entry keeps the sentence somebody actually said, and the minute they said it. The quarter's goals with their key results rolling up as the numbers move, a handbook that outlives its first author, and a wall for the whiteboard session. Pick General Purpose at setup - it is the startup shape, down to the name of its own org type - and all of it is queued for you.

7 apps queued at setup - untick any of them before you finish
Start freeHow extensions work
A new project in this workspace

Default project tabs

OverviewBoardListTimelineFilesMeetingsCalendarMembersCapacity

The standard set with Budget off - a team without a client fee or a rate card opens it on nothing. Add it back on any project from its tab strip.

Projects created on day one

  • Product
  • Operations
  • Growth
A day on the tools

What changes, in the hours it actually changes.

Three moments from an ordinary week. Every one of them is a thing the product does, not a thing it could be configured to do one day.

01

09:05

the standup nobody had to attend

Everyone posts what they did, what is next and what is blocking them in Standups, and the blockers are surfaced for the whole team rather than buried in a thread. Put the Standup teammate on a daily schedule and it writes the first draft for you, straight off the board: who is moving what, what is queued behind it, and which cards are past their date. It reads the board, so it can only report what is on the board - which is the point.

02

14:40

the sprint call ends and the board is already right

Cards move column from what was said. Work that already existed is edited instead of duplicated. Sub-steps somebody enumerated out loud become a checklist on the card they belong to. Decisions come out by name with the sentence that settled them, and one click jumps to the minute it was said. What the analysis genuinely cannot settle becomes one question to the person who can, answered with a tick, a name or a line.

03

17:20

a key result moves, and the reason is on the record

The planning session ends and a key result gets its new number in Goals & OKRs, so the objective's progress moves with it where the whole company can read it rather than the three people who were in the room. The decision that moved it is already in the Decision Log with the sentence that settled it, so next quarter's argument starts from a record and not from memory. The onboarding page in Codex gets the paragraph it was missing, and the sketch from the whiteboard goes on the Corkboard with a thread under it. Link a repo and the commit that carries the work attaches itself to the task by its key; a merged pull request can close it.

The shape of the work

How Software & Startups actually runs.

Each of these is a project in Noots - its own board, tab strip, meetings, calendar and members. They are not pre-built modules and we will not pretend they are: what the industry gives you is the right defaults around them.

01Discovery & user research
02Goals & prioritisation
03Sprint delivery
04Release & deployment
05Incidents & on-call
06Retros & incident reviews
07Hiring & onboarding
08Fundraising & investor updates
Made for Software & Startups

The three that do the heavy lifting.

Choose this industry during setup and its tools are queued for you. Review the list, drop anything you don't want, and the workspace initialises with the rest already working - or install any one of them on its own, later, from the marketplace.

Standups

Replace the daily status meeting with async check-ins - what you did, what is next, what is blocking you - with blockers surfaced for the whole team instead of read out to it.

What it doesQueued at setup
  • Async daily check-ins, posted rather than attended
  • Blockers surfaced for the team, not buried in a thread
  • An AI teammate can draft it from the open work, grouped by owner
  • Put that teammate on a schedule and it delivers to the people you name

Decision Log

An org-scoped register of the calls your team has made, with the context behind each one and its status - so nobody re-litigates a settled question six months later.

What it doesQueued at setup
  • The decision, the context, and who made it
  • Decisions recorded from a meeting keep a verbatim quote
  • One click jumps to the moment it was said
  • Searchable long after the people who were there have moved on

Goals & OKRs

The quarter's objectives with measurable key results under each, a start value and a target on every one, and progress that rolls up on its own as people update the numbers - a north star the whole company can read rather than a slide somebody re-exports.

What it doesQueued at setup
  • An objective is a sentence; a key result is a number with a start and a target
  • Progress rolls up from the key results as they are updated
  • Readable by the whole workspace, not just the product team
  • Sits beside the boards doing the work, not in another tool
And everything else

These sit on top of the whole product.

  • Run a meeting's analysis a second time and nothing duplicates: it matches the cards it already made - including the ones you deleted - before it creates anything
  • Every call lands its tasks on the right board, dated, assigned and linked back to the minute they came from - and one meeting can update several projects at once
  • Codex is the handbook a ten-person company writes on the day the eleventh joins: onboarding, how-we-deploy, the on-call runbook, as searchable pages with an author and a time on every edit
  • Notes are freeform pages on a project for the half-written brief and the diagram; the Corkboard is the whiteboard session kept - notes you drag, a pen, a thread on any note
  • Offered at setup, one tick each: Upvote for the feature requests customers keep sending, Retrospectives with voting, Announcements with read receipts, Kudos, and GitHub
  • GitHub: link a repo and any commit or pull request naming a task key attaches itself to that task, and a merged pull request can close it
  • Recording a customer call or an interview? The recorder offers a steer for each - what to listen for - so the write-up is shaped for that conversation rather than for a status meeting
  • A channel per project and per team, with voice, video and screen share that survive navigating away
  • Bring the board you are on today across: live imports from Jira, Asana, Trello, monday.com and Linear, or paste a CSV or JSON export from anything else
See the full platform
What we don't claim

The honest edges.

  • There is no applicant-tracking system and no investor-update template. Hiring is a board with an Interview steer on the recorder; the monthly update is a Codex page you write, with the numbers coming from Goals & OKRs or a chart you asked Hoot for.
  • There is no “Startups” answer on the setup screen. You pick General Purpose, which is the same thing under its older name - the workspace opens with Product, Operations and Growth, and the tab strip drops Budget because a team with no client fee opens it on nothing.
  • A decision is linked to the meeting and the minute it was said. It is not linked to the pull request that implemented it: GitHub attaches commits and pull requests to tasks by task key, and nothing joins a commit to a decision.
  • Retrospectives is a board with voting. Last sprint's unfinished actions do not carry themselves into the next retro, and there is no reserved-capacity lane that schedules improvement work for you.
  • The Standup teammate writes from the board - what is in progress, what is queued, what is past its date. It does not read your pull requests, your calendar or who is on leave.
  • Noots holds no SOC 2, ISO 27001 or HIPAA attestation and does not claim one. An approval or a decision recorded here is a durable record beside the work, with a name and a time on it; whether your auditor accepts it is between you and your auditor.
Other industries

Built for the way your trade actually runs.

IT & Managed ServicesSLA clocks that only run in your working hours, a warning before the target passes rather than a badge after, hours that become invoices, and alerts that open the ticket themselves.
Engineering & ConstructionA daily log that takes under two minutes, toolbox talks signed by name, certification warnings before a ticket lapses, and RFIs that show their age and whose answer they wait on.
Healthcare AdministrationRotating twelve-hour blocks in place of a nine-to-five week, a redaction pass over meeting text, and an append-only compliance log.
Every extensionHow the extensions system works, and the full catalogue of what a workspace can install.
Questions

The ones buyers ask first.

Which industry do we choose at setup?
General Purpose. It is the startup shape rather than the absence of one - its own definition inside Noots calls it a startup - and it opens the workspace with Product, Operations and Growth, a short list of workspace apps queued and pre-checked (the hero above counts them live), and a project tab strip with Budget switched off, because a team with no client fee and no rate card opens that tab on nothing. Add Budget back on any single project from its tab strip, and change your industry later from Org settings if the shape of the company changes.
Can we bring the board we already have across?
Yes, live, from Jira, Asana, Trello, monday.com and Linear: the importer reads the board and turns it into a real project with its columns and one task per issue. Anything else comes across as a pasted CSV or JSON export, which lands the same way. Credentials for the live importers are never stored; they are used for the pull and discarded.
We are hiring. Where does that live?
On a board, honestly. A Hiring project with a column per stage, the candidate as a card, and the interviews recorded with the Interview steer so the write-up is about the candidate rather than about a meeting. Noots is not an applicant-tracking system: there is no careers page, no application form and no offer letter in it, and this page will not pretend there is.
What happens if we re-run the analysis on a meeting?
Nothing duplicates. The second pass reads the meeting once, matches what it finds against the cards already on the board, against the tasks this meeting itself created - deleted ones included, which is why deleting a card it made does not invite it back - and against the questions still waiting on an answer, all before it creates anything. That reconciliation is the whole design of the pipeline rather than a de-duplication pass bolted onto the end of it.
Can the standup write itself?
The draft can. Standups is an async check-in board your team posts to, and separately there is a Standup teammate that reads the open work and writes an update grouped by owner: what each person is moving, what is queued behind it, and what is past its date. Put it on a schedule and it runs and notifies the people you list. Two honest edges: it reads the board and nothing else - not pull requests, not the calendar, not who is on leave - and putting a teammate on a schedule needs the Configure AI permission, the same one that governs Autopilot's cadence.
Does this replace GitHub?
No, and it does not try to. It links to it: connect a repository and any commit or pull request that names a task key attaches itself to that task, a merged pull request can move or close it, and the Deployments app records what shipped to which environment beside the work that produced it. The code stays where it is.
Our approvals happen in chat and our auditor is unimpressed. Does this fix that?
It gives you a record with a name and a time on it, in the same workspace as the work, instead of a message somebody has to go and find. Approvals route a sign-off to a named approver against the task itself; the Decision Log holds the decisions with their context; and a decision that came out of a meeting keeps the verbatim sentence that settled it. What we will not tell you is that this satisfies a control: Noots holds no SOC 2 attestation, and what your auditor accepts as evidence is their call, not ours.

Open a workspace that already knows Software & Startups.

Answer what your organisation does, review what gets installed, and start with the boards, meetings, chat and calendar already in the right shape.

Start freeSee every industry

Free to start · No credit card required