Ship faster. Hear your customers louder.
For software and SaaS teams and technical founders. Commits and pull requests attach to the tasks they close, releases become a changelog your customers can read, feature requests are voted on in one place, and the CRM keeps the pipeline and each account's health beside the work. The monthly investor update starts as a draft from the numbers you keep, and nobody receives it until a person approves and sends it.
29 tools switched on for this trade at setup. Untick any you don't need.Default project tabs
Backlog and Deployments replace List, Calendar and Budget: product work is groomed from a backlog and shipped in releases.
Projects created on day one
- Product
- Growth
- Operations
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.
09:05
the standup reads the board, not a round of updates
Everyone posts what they did, what is next and what is in the way, or types /standup in chat. Blockers surface for the whole team rather than in a thread. The pull request merged overnight has already attached itself to the task its branch named, and the task moved when it merged.
13:30
a customer asks for the same thing for the fourth time
The request goes into Upvote, where customers and colleagues vote on it rather than repeat it, and the board shows which requests have the most voices behind them. On the call, the sentence the customer used is kept with the date and the minute it was said, so the product decision cites the customer rather than somebody's memory of them.
17:40
what shipped is written down once
Deployments records what went out to which environment. The changelog entry is written from the release rather than from scratch, and on the first of the month Investor Updates drafts the update from the metrics you track month by month. It stays a draft until a person reads it, edits it, approves it and sends it.
How Startups & SaaS actually runs.
Each of these is a project in Navalo - 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.
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.
GitHub
Link 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 the task it names.
- Commits and pull requests on the task they name
- A merge can move or close the task
- One repository per project, or several
- Deployments records what shipped where
Upvote
One board for feature requests, where people vote instead of repeating themselves, so the list you plan from is ordered by how many asked.
- A request is posted once and voted on
- Sorted by votes, filtered by status
- Planned and shipped states the asker can see
- Links to the task that delivers it
Investor Updates & Metrics
The company's metrics month by month, and a monthly investor update Ava drafts from them. A person approves it and sends it; nothing goes out on its own.
- Metrics kept month by month, with snapshots
- A first draft written from your own numbers
- Edited, approved and sent by a person
- Never sent automatically
These sit on top of the whole product.
- Every call lands its tasks on the right board, dated, assigned and linked back to the minute they came from, and running the analysis a second time duplicates nothing
- Deployments and the Changelog turn what shipped into a record your customers can read
- The CRM keeps leads, accounts and opportunities beside the work, with each account's health on the account itself; the Lead Enricher fills in a company from its domain
- Competitor Watch keeps what you know about each rival in one place, and the Content Calendar plans what you publish
- Retrospectives is a board with voting, and Standups ships with the /standup command
- Strategy holds the goals the roadmap answers to, and a project shows which goals it moves
- Every workspace also gets the core: Announcements, Forms, Polls & Surveys, Kudos, Standups, Approvals, Checklists & SOPs, Recurring Tasks, the Decision Log, the Timeline, Hands-On Scheduling, Notes, the Corkboard, the Handbook, the Policy Library, Structures, Navalo Signatures, Conversation Stats and Budgets
- Bring the board you are on today across: live imports from Jira, Asana, Trello and Linear, or paste a CSV or JSON export from anything else, monday.com included
The honest edges.
- There is no applicant-tracking system. Hiring is a board with an interview steer on the recorder.
- Retrospectives is a board with voting. Last sprint's unfinished actions do not carry themselves into the next retro.
- An investor update is a draft until a person approves and sends it. Navalo does not send it on a schedule, and the metrics are the numbers you enter or import, not a live feed from your billing system.
- 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.
- Navalo holds no SOC 2, ISO 27001 or HIPAA attestation and does not claim one.
Built for the way your trade actually runs.
The ones buyers ask first.
What do we pick at setup?
Does this replace GitHub?
Will it send our investor update for us?
Can we bring the board we already have across?
Open a workspace that already knows Startups & SaaS.
Answer what your organisation does, review what gets installed, and start with the boards, meetings, chat and calendar already in the right shape.
Free to start · No credit card required