Back to home

Cueston for project management software

A project management tool is chosen by one person and judged by a team. Cueston helps the teams who build them get the first project set up, the rest of the team invited, and each person to the views and automations they’d otherwise never find, with guidance triggered by role, plan and what each person has done so far.

Why project management teams use Cueston

A project tool is only useful once the team works in it. Cueston walks the person who signed up through a first project and the invites, gives each invited teammate a short start on the task they were sent, and tells long-time users what changed after a release. Your product team runs it; your engineers add one snippet and a few events.

Why project management tools are hard to adopt

One person signs up, and the product only works if others follow. Whoever tried it has to create a project, add tasks and invite the team before anyone sees the value. If they stop at an empty board, the trial ends with nothing for the team to judge.

Most users arrive by invitation. A teammate or a client clicks a link to one task, with no idea how the product works and no reason to explore it. If that first visit is confusing, they reply by email instead, and the tool never becomes where the work happens.

And the product keeps growing. Views, automations, integrations, dashboards: each release adds something the people who’d benefit most never open, because they learned the product long ago and stopped looking.

What a guest invited to one task sees on their first visit: the first of two tour steps, on the real button. The person who invited them, and everyone else on the project, doesn’t see it.

The rules behind it, set in the editor:

  • User role equals guest
  • First seen less than 7 days ago
  • Pages: */tasks/*
  • Frequency: once

Who uses your project tool, and what to show them

WhoWhere they get stuckWhat to show them
Whoever signed upAn empty workspace: no projects, no tasks, no team, and a trial running out.A setup checklist: create a project, add tasks, invite a teammate. Each item ticks off when your app reports it done and starts a tour.
Invited teammatesThey arrive from an email link to one task and have never seen the product.A two-step tour on the page they land on, for people first seen in the last 7 days, once per person.
Guests and clientsThey need to comment or approve, nothing more, but see the whole interface.Tooltips on the comment box and the approve button, shown only to the guest role.
Project leads and adminsTimelines, dashboards and automations they don’t know exist.A short tour of one feature at a time, for leads who haven’t used it yet: event “automation created”, not at all.
Long-time users after a releaseA new view or a moved menu in a product they use every day.An announcement in the help hub’s What’s new, shown once as a banner, with a button that starts a tour of the change.

A first-month plan for a new workspace

Five moments, each with the Cueston item that fits it. Every new workspace gets them, because they’re triggered by role and by what each person has done so far, not by customer.

  1. Sign-up: a checklist to a working project

    Create a project, add tasks, pick a view, invite one teammate. Each item starts a tour and ticks off when your app reports it done.

    Built with: Checklist, tours, events

  2. First invite: a short start for each teammate

    Two steps on the task they were sent: where to post an update and how to mark it done. Shown to people first seen in the last 7 days, once per person, whoever invited them.

    Built with: Tour, audience rules, frequency

  3. Week one: nudge the next invite

    A banner for the person who signed up if they’ve invited fewer than two people in 7 days, linking to the invite page. It stops showing once they have.

    Built with: Banner, event rule

  4. Week three: the feature they haven’t found

    A tour of automations or dashboards for project leads who haven’t created one yet. One feature per tour, and the workspace’s interruption limits stop them piling up.

    Built with: Tour, event rule, interruption limits

  5. Every release: what’s new, inside the product

    An announcement in the help hub’s What’s new feed, shown once as a banner to the people it’s for, with a button that starts a tour of the change.

    Built with: Announcement, tour

What a project management tool needs from a tour tool

Triggers from what people did, or didn’t

Your app reports events, such as a project created or a teammate invited, with Cueston.track or through Segment. Audience rules then match people who did an event at least or fewer than some number of times in some days, or not at all; who finished or dismissed another tour; and who was first or last seen some days ago. See Who sees it.

Guests, members and admins see different things

Pass the role, permissions and plan when someone signs in. Guest tips go only to guests, admin tours only to admins, and upgrade banners only to plans without the feature. Save the groups you use often as segments, such as “trial owners in week one”, and reuse them on any item.

Guidance that survives weekly releases

Project tools ship often, and a release can move the element a tour step points at. Broken targets lists each step that couldn’t find its element, with the missing selector and how many people missed it, and workspace admins get a daily email. Try changes on your staging app before production, and roll back to the last good version in one click.

Out of the way while people work

Workspace limits cap how many pop-ups one person gets per visit and per day, and how long to wait between them; when several qualify, the highest priority goes first. Someone who closes guidance within 2 seconds twice in 14 days gets at most one pop-up a day until those closes are older. Tooltips and beacons don’t count toward the limits. See When and how often.

Help at the moment someone struggles

On paid plans, with the AI assistant on your site and friction detection turned on, Cueston notices struggle that rarely happens when things go well: clicking a disabled button, clicking the same thing again and again, going back and forth between pages. Stuck points lists where it happens, and you can turn each one into a tip that only the people who struggle there see. It records which signal happened, the element and the page, never what people type.

Proof it worked

Give the invite banner a goal, such as “teammate invited”, and hold back a control group of up to 50%. Cueston shows whether the people who saw it reached the goal more often, and whether the difference is significant at 95% confidence. See Goals and experiments.

Every language your customers work in

Guidance can be in 11 languages, translated by hand, by machine as a first draft, or through a CSV or XLIFF file for your translators. See Languages.

When Cueston isn’t the right fit

  • You’re rolling out a project tool you bought to your own company. Cueston runs where you can add its script, which means a product you build. For software you bought, look at a digital adoption platform that runs as a browser extension.
  • Most of your users work in your native mobile app. Cueston is for web apps.

Frequently asked questions

Can invited teammates get a different start from the person who signed up?▾

Yes. Pass something that tells them apart when someone signs in, such as a guest role or a custom attribute like joined_by: "invite", and combine it with first seen less than 7 days ago. The person who signed up gets the setup checklist; everyone invited later gets a short tour of the page they land on.

Can we nudge people who haven’t invited their team?▾

Yes. Your app reports an event, for example with Cueston.track("teammate invited"), and a banner’s audience rule says the person did it fewer than 2 times in the last 7 days. Once they invite, they stop matching and the banner stops showing.

We ship every week. Will tours break?▾

Tour steps point at elements on the page, so point them at elements with a stable id or data attribute. When a step can’t find its element, Cueston lists it under Broken targets with how many people missed it, and emails workspace admins daily. Every published version is kept, so you can roll a change back.

Can we announce new features inside the product?▾

Yes. Announcements are a changelog inside your product: a headline, the news, an optional image and a button that opens a page or starts a tour. They’re listed in the help hub’s What’s new feed and can also show once as a banner or pop-up. Nobody sees one before its publish date, so you can prepare it ahead of the release.

Will guidance get in the way of people’s work?▾

You set the limits: how many pop-ups one person gets per visit and per day, and how long to wait between them. Someone who closes guidance within 2 seconds twice in 14 days gets at most one pop-up a day. Tooltips and beacons don’t count toward the limits.

How much does it cost for a project management tool?▾

Paid plans are $39, $79 and $199 a month, billed yearly, and each includes a number of monthly active users across all your customers. Everyone your app identifies counts once in a month they visit, guests included, so estimate from the people who sign in each month. There’s also a free plan, and the pricing page lists what each plan includes.

Can we use Cueston to roll out a project tool we bought?▾

No. Cueston shows guidance in apps where you can add its script, which means a product you build. To guide your own team through software you bought, you need a digital adoption platform that runs as a browser extension on their computers.

Get the second person into every new workspace

Free to start. Add the snippet, report the invite event, and put a setup checklist in front of your next sign-up.