On 2026-10-06, HubSpot, Inc. filed a Form 8-K with the SEC under Item 2.05.
The filing discloses a board-authorized restructuring affecting approximately 7% of its workforce. Estimated restructuring charges are $65 million to $75 million. Role eliminations are expected to be substantially complete by the end of HubSpot's first fiscal quarter of 2027.
Business Insider named the same pattern the same morning at Nike, Meta, and GitLab. Workforce reductions announced weeks or months before affected employees are identified. Attorney Kevin Zwetsch, paraphrased in that piece, called the window a tool to encourage voluntary departures. That is one employment attorney's reading, not an agency or court finding.
That is the employee story. The consultant's story sits one step underneath it.
Her decision is the renewal. The counterparty is the person at the client who signs it. The date is the renewal notice, and a restructuring can move it.
Translation: her sponsor may be inside the uncertainty window. The record of what she built lives on the client's side.
The problem
Her point of contact at a restructuring client is her sponsor, her reviewer, her procurement signer, the operator who runs her shared drive.
The dated artifacts of what she built for them live on the client's side. A client-provisioned Slack. A client-provisioned shared drive. A vendor portal. A project-management tool she accessed as a guest.
When access closes, those artifacts stop being retrievable.
That is The Unpriced Proof Gap with a calendar attached. Her proof exists. It is on the client's side. And the clock started the day the 8-K hit, not the day her contract ends.
If this reads as recognition, that is accurate information. Name it, then open one file this week.
What has not worked
The brag document. Compliments, project names, half-finished bullets. A folder of fragments is not a record of an engagement.
Waiting for the renewal conversation. By then the sponsor may already be gone, and the shared drive may already be deprovisioned.
None of this is a personal failing. Nobody teaches it.
The solution: a Record Pull Index
Five categories. One page. One two-hour block this week.
Category 1. The engagement record. The signed MSA. The latest SOW. Approved change orders by date and ID. The current scope statement in writing. Start date and current end date. Named points of contact on the client side.
Category 2. The dated-deliverable record. Every deliverable shipped under the current SOW. For each one: filename, date shipped, named recipient, acceptance evidence, one line of attribution (self, shared workstream, team). Where it lives on the client's side is captured as a URL or path. Not re-exported.
Category 3. The invoice record. Every invoice issued under this engagement. Invoice number, line items, period covered, submitted date, paid date or current aging, and the dated written approval that triggered it.
Category 4. The communications-of-record record. Written approvals, written scope changes, written praise, written course corrections. Tied to the deliverable they relate to. Casual chat messages are not communications-of-record. Emails tied to deliverables and procurement-system notes are.
Category 5. The portfolio-asset record. Her own method artifacts that happen to live inside the client's systems. The strategy memo. The framework. The dashboard. The diagram. Screenshotted, dated, filed on her own drive next to the deliverable it supports.
The client's record of the engagement and her record of her contribution are not the same record. See the difference?
Whether she may copy or keep any specific artifact is a question for her counsel.
This post is not legal, tax, or benefits advice.
The example: a two-hour block
This is an illustration, not a client.
A solopreneur has been engaged for eight months as a fractional operations lead at a mid-cap tech company. Her SOW runs through January. Her renewal conversation was scheduled for late November.
On 2026-10-06 she opens her inbox and sees two things. A Google Alert on her client's 8-K. A one-line note from her sponsor rescheduling their Thursday standing meeting.
She blocks two hours the same day.
She captures the MSA, the SOW, and the three change orders. She lists the twelve deliverables and the six invoices, each with its fields. She pulls the written approvals and leaves the chat messages alone. She screenshots the framework she authored at kickoff, dates it, and files it on her own drive.
She writes a one-page index. She does not value anything.
Translation: the client's HR holds the headcount. Her Record Pull Index holds the record of what the headcount paid for.
Your template
Copy this. Fill one category today.
RECORD PULL INDEX | Dated: ________
Engagement record
MSA signed on: ______ SOW effective: ______ to ______
Change orders (dates and IDs): ______________
Points of contact (role, name, email): ______________
Dated deliverables (current SOW)
For each: Filename ______ Date ______ Recipient ______
Acceptance evidence ______
Attribution (self / shared / team) ______
Where it lives on client side (URL or path) ______
Invoice record
For each: Number ______ Period ______ to ______
Line items ______
Submitted ______ Paid or aging ______
Dated written approval that triggered it ______
Communications of record
For each: Date ______ From ______
Subject or thread ID ______
Tied to deliverable ______
Portfolio assets
For each: Artifact ______ Date authored ______
Where it lives on client side ______
Where I filed my own dated copy ______
Contract-limit note (routes to counsel) ______
Index filed in: ______________
What the record does not do
The index proves what she built, when, and for whom.
It does not tell her what that record is worth to this client at renewal. Documentation is not valuation.
The renewal number comes from valuing the documented record. A well-documented engagement is a well-organized donation until someone values it.
Before the renewal notice goes out, have the record valued, so the number on it is hers and not last year's.