Getting started: find tools that fit your team
Describe your team in one sentence, and Juukbox gives you a feed of matching products in order of fit, with Otis beside it to help you narrow things down.
4 min read
Get more out of Juukbox, and see how it compares next to the other ways of choosing software.
Describe your team in one sentence, and Juukbox gives you a feed of matching products in order of fit, with Otis beside it to help you narrow things down.
4 min read
Juukbox checks every product against what your team actually needs, puts the best fits first, and shows you why each one fits.
4 min read
Otis is the assistant that sits beside your feed: tell it what you need, ask it about the products in front of you, and your Decision Profile and feed follow along.
4 min read
Your Decision Profile is the list of requirements Juukbox matches products against, and you can build it by talking to Otis or by editing it yourself.
4 min read
Tell Otis what your team needs and Juukbox lists matching products in order of best fit.
The price on the card is rarely what you pay, so here is how to read per-seat and flat pricing, plan tiers, seat minimums, yearly billing and add-ons, and work out the real cost for your team.
6 min read
When clients are part of the project, your tool has to show them the right things, hide the rest, track the hours you bill, and keep each budget honest, so here is what to check before you commit.
8 min read
Gantt charts, dependencies, baselines and workload views are where planning tools differ most, so here is what each one does, which plan has it, and when a simple board is all you need.
7 min read
If your project connects systems like a CRM, an ERP, or a pile of APIs, the tool you track it in needs to connect too, so here is what to check before you commit.
6 min read
8:39
AirtableMade by Juukbox
7:25
Microsoft PlannerMade by Juukbox
7:38
SmartsheetMade by Juukbox

Ivan Zhao wanted everyone, not just programmers, to shape their own tools. It took a failed first version, a company cut to two people, and a year of rebuilding in Japan.
4 min read

Joel Spolsky couldn't tell what his own team was working on. A list of five things didn't fix it. A wall of sticky notes did, and then the team refused to let it become a tool only programmers could use.
7 min read