A product tracker shaped like a strategy tool and priced like a task manager. One ranked backlog, effort measured against your objectives, and the customer feedback loop closed for you — not left for someone to remember.
No card. Nothing to import. Your first objective takes a minute.
Most small teams collect feedback fine and never close the loop, because closing it is a chore nobody owns. Aimloop makes the chore one button, and nags you until you press it.
Customers vote and ask on your public roadmap. Slack messages become requests with a slash command. Paste anything else. Each one keeps who asked and what they said.
Attach a request to an existing item or promote it into a new one. Demand rolls into the score, so what customers actually want moves up the list.
Every item hangs off an objective. Work that hangs off nothing is called out as unaligned, and the Strategy view shows where effort really went.
Mark it shipped. Aimloop already knows who was waiting, writes each of them a note quoting their own words, and sends it.
Each objective carries the share of effort you meant to give it. Aimloop measures what it actually got. The gap is the number that starts the right argument — before the quarter is over, not in the retro.
No hours, no FTE model. A t-shirt size per item is enough to see the shape of the quarter.
Nobody on a team of six wants to log hours, and nobody believes the numbers when they do. Green, stretched, or at capacity is honest, takes a second to set, and is enough for Aimloop to flag the person carrying three things at once.
Three lists mean three arguments about what's next. Aimloop keeps one, ranked by (demand + impact) × confidence ÷ effort, where demand counts the customers who asked — weighted by who they are.
The formula is one function. When real usage tells you something better, change it.
When an item ships, Aimloop knows exactly who was waiting for it and what they said. It drafts each person their own note, quoting them, and sends it — or hands you a mailto with everyone already addressed if you'd rather send it yourself.
The people who asked and were never told show up on Pulse until they are.
Publish only the items you choose, in customer-facing words — Aimloop nags you if an internal title leaks. Customers vote, ask for things, and leave an email to be told when it ships. Votes feed the score; requests land in triage.
Detail, owners, scores and estimates never cross the line. The portal can reach exactly three things: read the board, vote, ask.
Voted? Leave your email and we'll tell you when it ships.
Enterprise product tools sell objectives, allocation and feedback loops at enterprise prices. Task managers sell tickets. Aimloop is the smallest honest version of the first set, at the second price.
| Capability | Enterprise product suites | Task managers | Aimloop |
|---|---|---|---|
| Work tied to strategic objectives | Yes | Rarely, or a paid tier | Yes |
| Intended vs. actual effort per goal | Yes | No | Yes |
| Capacity and under-funding alerts | Yes, with an FTE model | No | Yes, from a traffic light |
| Customer requests scored into the backlog | Yes | Via plugins | Yes |
| Public roadmap with voting | Often an add-on | No | Yes, on the free plan |
| “You asked, we shipped” notes, per requester | Sometimes | No | Yes, written for you |
| Audit history | Enterprise tier | Enterprise tier | Pro |
| Price | Per seat, priced for enterprises | Per seat, cheap | Flat per workspace |
Honest about what it isn't: Aimloop links to your tickets in GitHub, Linear or Jira. It does not sync them. Nobody should maintain two trackers, and we'd rather say so than fake it.
Per-seat pricing punishes the exact behaviour a product tracker needs: everyone in it. So we don't do it.
Prices in USD. Pro billing opens shortly — start on Free today and there is nothing to migrate.
No, and it doesn't pretend to. Engineers keep their tracker. Each Aimloop item carries a link to the ticket where the work happens. Aimloop is where the why lives — the objective, the customers who asked, and the note that goes out when it ships.
Three ways, none of which require anyone to remember to type: customers submit and vote on your public roadmap, a Slack slash command or mention captures a message as a request, and you can paste anything else — a support ticket, a call note — in a few seconds.
Only what you explicitly publish, and only its customer-facing wording, status and vote count. Owners, scores, effort, estimates and internal notes cannot be reached from the portal. It's a deliberately narrow door.
In a Postgres database in the United States, with each workspace isolated from every other at the database level — not just in application code. Your workspace can't see another's, and the app can't be talked into it.
No. Free is three seats forever. Pro is a flat monthly price per workspace with as many people as you like, and you can stop any month.
Aimloop is built by a small team in North Carolina that got tired of paying strategy-suite prices for a spreadsheet's worth of objectives. Every feature is the smallest honest version of something we used to pay a lot more for. Questions go to support@aimloop.io; a person answers.
Three seats, every feature, no card. Your first objective takes a minute; the first “we shipped it” note writes itself.