Getting started
About 30 minutes of setup gets you dashboards today and a written digest for each team next Monday. Here's the order that works, and what happens on its own after that.
1. Create your workspace
Go to Start free and enter your name, work email and organization. We email you a link; open it and press Create workspace. You're the workspace's first admin. It's free for up to 5 contributors, with no card needed.
There are no passwords. Each time you sign in, we email you a link and a 6-digit code; use whichever is easier.
2. Connect GitHub and your work tracker
After sign-up you land on Connections. Connect GitHub, which says what shipped, and wherever you track work, which says what it was for. Each one takes a few minutes:
- Connect GitHub. You'll need an owner of your GitHub organization.
- Connect Jira, with a Jira API token, or use GitHub Issues, which needs nothing more than GitHub.
As soon as one is connected, we start pulling up to two years of history. A panel on Connections shows the progress. It usually takes 5 to 30 minutes, though a large organization can take a few hours. You can close the page while it runs.
3. Add AI usage (optional)
If your developers use Claude Code or GitHub Copilot, connect them too. AI usage is shown beside delivery as context, never as a score. See Connect Claude Code and Connect GitHub Copilot.
4. Review people
The same developer shows up once in Jira, once in GitHub and once in Claude Code. We join them up by email, and list anyone we couldn't match, with the reason, for you to check. Merge the duplicates, set levels, and mark anyone outside engineering. See People, identities and teams.
5. Create teams
Team dashboards and digests need teams. In Admin → Teams, create your teams (a team can sit under another), then put each person on one from their page in Admin → People.
6. Tag your priorities
Priority alignment shows how much of each team's finished work went to what the company said mattered. Add this quarter's initiatives in Admin → Initiatives, then tag their epics in Admin → Epics. Tags stay put when Jira syncs.
7. Invite your team
On Members, invite the people who should see the numbers, as developers, managers or admins. Roles and visibility explains what each one sees.
Until every step is done, a checklist on your dashboard shows what's left.
What happens each day
| When (UTC) | What |
|---|---|
| Every 15 minutes | Claude Code usage and GitHub pull request, review and deployment changes arrive, and so do Jira changes if you add its webhook. Other commits wait for the nightly sync. |
| 2am | Every connection syncs what changed since yesterday. |
| 3am | Rework is measured for pull requests merged 21 days ago. |
| 4am | New people are matched across your tools. |
| 5am | Every metric is recalculated, so dashboards are fresh by the start of the working day. |
| Mondays, 6am | Each team with activity gets its weekly digest for the week that ended on Sunday. |
Weekly numbers cover Monday to Sunday, so a new week's figures settle on Monday morning. Copilot data runs 2–3 days behind because GitHub publishes it late.
Your first digest
The Monday after you connect, each team with activity gets a short written report: what shipped, how it lined up with your priorities, and anything worth a look. Managers get their own team's digest by email, and admins get every team's. Anyone can read their team's on the Digests page, and anyone can stop the emails in Settings → Notifications.
Stuck? Write to chris@trulyshipped.com and we'll help.
Next: Connect GitHub →