Beta waitlist open

One directory for everyone on your team

Team Directory gives growing teams one place to find accurate colleague information — role, department, location, skills, and who to ask, without the side-channel messages.

Teams can't find each other.

When there's no single source of truth for who's who, every new hire and cross-functional project loses time to the same unanswered question: "Who handles X?"

No trusted home for people data

Names, roles, reporting lines, and skills live across Slack, Notion, spreadsheets, and memory — none of which stay accurate or up to date.

The wrong person is always the bottleneck

Wasted time on unanswered "who does X?" questions across product, design, engineering, and CS — the information gap slows every decision.

Growing teams feel it first

At 20+ people, the directory that used to fit in one person's head stops working. New hires struggle to find teammates, and managers lose visibility.

Quick questions become long delays

Each lookup that should take 10 seconds turns into a multi-hour interruption chain — and nobody builds a directory when they're already overwhelmed.

From waitlist to workspace directory

Joining the beta means you help shape the Team Directory alongside the product team — and your team gets early access before general availability.

1

Sign up for the waitlist

Tell us a little about your organisation so we can match you to the right cohort. We'll ask about team size, current tooling, and the challenges you're solving.

2

We'll define the first cohort

The first launch cohort is still being defined. Selected teams will be notified with details on timing, onboarding, and what's expected from beta participants.

3

Set up your directory

Import or configure your team's profile fields — name, role, department, location, skills, and reporting line. Set permissions so the right people can view and edit.

4

Share feedback and shape what ships next

Beta participants get direct access to the product team. Your feedback decides what goes into the next release — this is a co-building partnership, not a preview.

What's included and what's deferred

The beta focuses on profile fields and permission controls. Every item here is grounded in the current scope — nothing has been promised beyond what's listed.

Included in the beta

  • Centralised profiles with core fields: name, role, department, location, skills, reporting line
  • Role-based permission controls — admin vs. member access, public vs. private visibility
  • Onboarding flow for first-launch cohort participants
  • Direct feedback channel to the product team

Explicitly deferred (future backlog)

  • Nice-to-have profile fields not agreed in the initial scope
  • Integrations with external HRIS or identity providers
  • Advanced directory analytics and reporting
To be confirmed: Launch date, cohort size and selection criteria, pricing (if any), and the final list of must-have profile fields. All of these are being defined during the beta planning phase.

Join the Team Directory beta waitlist

Fill in the form below and we'll be in touch when cohort details are confirmed.

By submitting this form, you agree to be contacted about the Team Directory beta. We will not share your information. This form does not submit data — your request will be processed when we launch.

Frequently asked questions

Answers to common questions about the Team Directory beta programme.

When does the beta launch?

The first launch cohort is still being defined. Selected participants will be notified with timing details once the cohort criteria and onboarding flow are confirmed. Launch date: To be confirmed.

Who is this beta for?

The Team Directory beta is designed for operations and people leaders at growing teams — companies that have outgrown informal "who does what" knowledge and need a single source of truth for colleague information.

How much will it cost?

Pricing has not been announced. Beta participants will receive details about any applicable terms before the programme begins. Pricing: To be confirmed.

How long does the beta last?

The beta duration has not been finalised. Participants will be informed of the expected timeline when they are onboarded into the first cohort. Duration: To be confirmed.

What information will I need to set up my directory?

The beta focuses on core profile fields: name, role, department, location, skills, and reporting line. You'll also configure who can view and edit each field through the permission controls. No external integrations are required to start.

Can my whole team access it during the beta?

Access during the beta will be scoped to the agreed cohort criteria. Full details on who can view and edit the directory will be shared when your team is onboarded. Participant access model: To be confirmed.

How do I give feedback?

Beta participants get a direct channel to the product team. Your feedback on what's working, what's missing, and what should ship next will shape the roadmap.

What happens after the beta ends?

Transition plans from beta to general availability are being developed. Beta participants will be informed of next steps and any applicable terms before the programme concludes. Post-beta transition: To be confirmed.