What happens, in order
- A 20-minute scoping call. You choose the hire and the sources Firstweek reads. Any role works: an AE, an engineer, an implementation lead, a relationship manager inheriting a book. Someone starting in the next 30 days.
- We set up your pilot workspace. The 30 days start here. For financial services, they start when your security review clears.
- Read-only connections. Your admin connects the tools you already use and chooses the channels, spaces and records. If someone else owns a tool, Firstweek sends them a request to approve the connection.
- Firstweek writes the artifact. It reads, summarizes at ingest and writes the actual story: the company, the team, the role and what's happening now. Every claim links to its source.
- The hiring manager approves it. In ten minutes, instead of the three hours they were never going to spend. Nothing reaches the new hire until they do.
- It lands before day one. The new hire gets it by email ahead of their start date.
- Then we talk. About whether it's worth keeping, with the artifact in hand. It's the first conversation about buying anything.
What we need from you
- A hire starting within 30 days. One hire is the pilot.
- Their hiring manager, for the review.
- Someone who can approve read-only connections to the tools you already use.
Start a pilot
Questions
No. A pilot runs on a real hire with your real tools. That is the point.
A 20-minute scoping call, a few minutes to connect the sources, and the hiring manager's review of the artifact. The writing is ours.
Slack, Confluence, Jira, Google Drive, OneDrive and SharePoint, Microsoft Teams, GitHub, HubSpot and Salesforce, through read-only connections. You choose the channels, spaces and records.
No. Firstweek reads, summarizes and forgets. Raw messages and documents are never stored; only summaries persist.
We talk about whether it's worth keeping. Nothing renews automatically, and nothing locks while we talk.