Case Studies
How product and technical teams put Second Axis to work, with the numbers behind each rollout.
How a Denver ed-tech company standardized AI across four PMs without slipping a release
A learning-content platform in the $5-8M ARR range ran a disciplined ship cadence: two-week sprints, releases timed to semester breaks. AI adoption was ahead of the curve and completely inconsistent. Ninety days after rollout, tool-evaluation time per PM dropped 83% and no release date moved.
Read the case studyHealth tech, clinical-stage biotechHow a biotech process development team cut morning triage from two hours to 25 minutes
A clinical-stage biotech in North Carolina's Research Triangle was losing every morning to inbound from sales, support, and QC. Six weeks after rollout, triage took 25 minutes, ticket throughput was up 38% on the same headcount, and no customer request had waited past 48 hours.
Read the case studyHealth tech, care coordinationHow a care-coordination startup rolled out AI workflows inside HIPAA constraints
Security had frozen every AI tool request for a year at this Columbus health-tech company, and shadow usage was spreading anyway. Reviewing one platform once, instead of eight tools separately, got the team from freeze to approved rollout in six weeks, with shadow-AI accounts down from eleven to zero.
Read the case studyCybersecurity, threat detectionHow a threat-detection startup stopped losing a week to every exec review
Before every board and exec review, this Atlanta security company's three PMs spent days reconstructing what had been decided, shipped, and learned. Now a decision log records all of it as it happens, and a bot trained on that log answers the questions execs actually ask. QBR prep fell from two weeks to two days.
Read the case studyCybersecurity, compliance automationHow a compliance-automation startup stopped selling features it wasn't building
Founder-led sales at this Boston security company kept surfacing commitments the two PMs first heard about after signature: four in one quarter, each a fire drill. Twelve weeks after moving deal asks and scoping into one shared record, post-signature surprises hit zero and cycle time on roadmap-dependent deals fell 21%.
Read the case studyLogistics, freight technologyHow a Chicago logistics platform turned three Claude power users into a shared org memory
A freight-tech company's team had adopted Claude organically until every dashboard in every meeting was a Claude document. The knowledge lived in individual chat histories. A three-person pilot moved it into shared memory: customer analysis dropped from hours to minutes and new-PM ramp time halved, at lower monthly spend.
Read the case studyLogistics, freight visibilityHow a Memphis freight-visibility team stopped letting inbound run its day
A Staff PM at a 45-person freight-visibility company started every day in reaction mode: carrier escalations, integration questions, and a platform-team dependency she could not see into. A morning brief plus queryable roadmaps flipped the ratio: deep-work hours doubled and cross-team status meetings dropped by half.
Read the case studyAgri-tech, farm management softwareHow an agri-tech CPO replaced the loudest-call roadmap with full-season signal
At a Des Moines farm-management software company, the roadmap had a recency problem: whatever the last angry dealer call said, the roadmap did. Synthesizing a full season of grower and agronomist feedback changed the picture, and two of the quarter's top three priorities turned out to be things nobody had escalated loudly.
Read the case studyAgri-tech, agronomy intelligenceHow a Boise agri-tech team put real evals around its crop-recommendation model
An agronomy platform's nitrogen recommendations are the product, and updates shipped on spot checks and gut feel. After a bad regional miss, the team built an eval suite and an experiment log inside the workspace. Every model change now runs 340 regression cases first, and two bad releases were caught before a grower saw them.
Read the case study