How 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.
The situation
On paper the team optimizes bioreactor titer and purification recovery. In practice, the Director started one February Tuesday with twelve forwarded sales emails, four support messages about a partner's failed lot, six Slack DMs from QC flagging a deviation, and an unwatched regulatory call recording. None of it was in Jira. Most of it needed to be. Inbound was running her day, and she knew it.
The team had tried the obvious fixes: a shared triage channel, a rotating inbound owner, a Notion form for sales. Every fix added a step and none stuck, because the requests were not the problem. The translation was. Someone with the science had to read each message and rewrite it as a scoped ticket before any of the other nine people could touch it. Ten to fifteen times a day.
The turn
The morning brief did the first level of work: it reads the previous 18 hours of email, Slack, and meeting transcripts and returns a ranked list of what needs a decision. By week four it had learned the second level, the one that actually changed her mornings: separating decide-this-now from this-can-wait-for-you. The brief stopped presenting everything and started presenting judgment.
Prose-to-ticket handled the rest. The PD ops lead drops a sales paragraph into Second Axis and gets back a Jira ticket with title, scope, acceptance criteria, an estimate, and a link to the source message. She reviews it, edits maybe one line, pushes it. The first live test converted a backlog of eleven inbound requests in under twenty minutes.
“I wasn't running a lab. I was running an inbox. Now the brief tells me what needs me and what can wait, and the difference between those two lists is my morning back.”
How Second Axis fits
A morning brief with two levels
Level one reads the last 18 hours and ranks what needs a decision. Level two, learned over weeks, separates what needs her now from what can wait.
Prose to scoped Jira ticket in 90 seconds
Inbound paragraphs become tickets with title, scope, acceptance criteria, an estimate, and a link back to the source message.
Scoping for internal PD projects
A scientist's proposal goes in as a paragraph and comes back as a scoped mini-project with hypothesis, success criteria, and a resource plan.
Compounding org memory
Why a deviation was accepted, why one clone won, why a step was skipped: captured once, findable by the whole team months later.
Results
| Area | Before | After |
|---|---|---|
| Inbound request to scoped Jira ticket | ~14 min | 90 sec |
| Director's morning triage window | ~2 hrs | 25 min |
| Tickets closed per month, same headcount | Baseline | +38% |
| Customer requests past 48-hr first response | ~6 / mo | 0 |
| Internal projects stalled for lack of scope | 5 in prior quarter | 0 |
What came next
The Director's mornings now start in the lab, not the inbox. The hours came back as time with her scientists and her manufacturing partners, which she calls the part of the job that actually moves the program.
Company details anonymized at the customer's request.