Solutions

Case studies

Six example scenes in each domain. Choose a domain, then scroll.

1 / 6

Example scenarios

The partner call and the waiting experiment

“We agreed the next experiment on a call with our partner on Tuesday. By Friday half the action items had no owner, and the experiment is still waiting.”

What usually happens

Notes stay in a meeting tool, and someone is meant to copy the action items into a tracker and the call into the CRM.

What SI 42 does

  1. 1An agent reads the notes from Granola and drafts the summary, action items and next steps, each with a suggested owner.
  2. 2You approve, edit or reassign each one, and approved items become tasks with owners.
  3. 3The meeting is filed against the partner in the CRM.

The outcome

Every decision from the call leaves with an owner, and the partner's record shows the call.

Mixed results, the stop rule and the data you may use

“The results came back mixed, nobody agreed whether we said we would stop, and we nearly booked lab time on a dataset we were not licensed to use.”

What usually happens

The hypothesis and stop criteria sit in a slide deck, results are discussed in chat, and data licence terms sit in a contract folder.

What SI 42 does

  1. 1The investigation holds the hypothesis, success criteria and stop criteria.
  2. 2Each result is added as evidence that supports, contradicts or is inconclusive, with its method, limits and rights (permitted, restricted or unknown).
  3. 3A proposed experiment, drafted by an agent or a scientist, must answer every open contradiction, and a request for lab review needs a prediction built on data with permitted rights; you record the decision to continue, revise or stop.

The outcome

You decide to continue or stop against criteria set before the data came in, using only data you may use.

The reagent that expires before the run

“The run was booked for next week. On the day the key reagent lot had expired, the cells we prepared were wasted, and we paid for rush shipping on a new lot.”

What usually happens

Lots, expiry dates and prices live in a spreadsheet that nobody checks against the run schedule.

What SI 42 does

  1. 1SI 42 ties each protocol to the reagents it uses and each draw to its lot and experiment; each lot carries its cost.
  2. 2An agent flags a scheduled run that needs a lot expiring first and drafts a reorder when a lot reaches its threshold, citing how fast you use it.
  3. 3You approve the supply request with its vendor, quantity and price, and receiving it creates the new lot.

The outcome

You find the expiring lot a week early and buy the next one at the normal price.

The model a partner asked about

“A licensing partner asked how we ranked our candidates. We could not reproduce the model, so the term sheet waited while we rebuilt it.”

What usually happens

Models are trained in notebooks, the version that mattered is whichever file was saved last, and model spend shows up on a card statement.

What SI 42 does

  1. 1SI 42 ties every trial to its code version, parameters and dataset hash, and the chosen model points back to the trial that produced it.
  2. 2The cost of each model call is recorded against its experiment, and a project budget with a warning level and a stop level halts the agent's search at the stop level.
  3. 3You choose the model you will stand behind and what goes to the partner.

The outcome

You can show a partner where a ranking came from, and model spend stays inside the budget you set.

The IP assignment nobody signed

“An investor's lawyer asked whether everyone who worked on the invention had signed an IP assignment. We could not say, and the round paused while we searched for paperwork.”

What usually happens

Assignments sit in offer-letter folders, and nobody compares them with who is on the team.

What SI 42 does

  1. 1The IP board keeps your patents and trademarks with filing and renewal dates, and pulls filing status from USPTO when connected.
  2. 2An agent checks every active person in your people list for a signed IP-assignment document and lists who is missing.
  3. 3Before you name a product or file, it runs a clearance search on USPTO and EPO and lists possible conflicts for your counsel.

The outcome

When diligence asks who signed, you have the list and the gaps.

The grant deadline found too late

“We found an SBIR topic that fit our work a few days before it closed, so the application went in thin, with half our preliminary data left out.”

What usually happens

Someone checks agency sites when they remember, and deadlines live in one person's calendar.

What SI 42 does

  1. 1The grants board pulls open SBIR and STTR solicitations from sbir.gov, and you search them by keyword and agency.
  2. 2Add one to your pipeline and move the application from prospect to drafting, review and submitted, with its deadline; Home lists what is due soon.
  3. 3The investigation with your preliminary results, its evidence and its decisions, is in the same app for the people writing the application.

The outcome

You see a fitting solicitation while there is still time to write a full application.

The deviation raised on the CDMO call

“A deviation came up on the weekly CDMO call and was written up days later from memory. By then the batch it hit had slipped, and the work order behind it was at risk before finance heard.”

What usually happens

The deviation lives in meeting notes until someone opens a form in the quality system, and the CDMO tracker and contracts sit somewhere else.

What SI 42 does

  1. 1An agent drafts the call's next steps.
  2. 2A next step about the problem goes to the quality events register as a deviation candidate linked to the meeting, and goes no further until a person confirms it; a next step that names the CDMO arrives in the CDMO board to accept as a commitment.
  3. 3When a batch is at risk, the CDMO board adds up the signed agreements linked to that batch or its program.

The outcome

A deviation candidate is ready the day it is raised and becomes a record when approved, and you can see what money depends on the batch it hit.

The CAPA closed without a root cause

“A supplier lot failed incoming checks. The CAPA was closed with no root cause, the same material failed again, and we paid for a second lot we could not use.”

What usually happens

A spreadsheet lets anyone mark a CAPA closed, and the supplier hears about it in an email nobody reviewed.

What SI 42 does

  1. 1In SI 42 a CAPA cannot close without a root cause and a corrective action, and nothing closes without a named approver; the close form lists what is missing.
  2. 2The supplier board scores each supplier on delivery, price variance and rejection rate, so repeat rejections show before the next order.
  3. 3An agent drafts the email asking the supplier for its corrective action, and it passes a buyer review and a second approval before it goes.

The outcome

A closed CAPA has its root cause and action, and the supplier's score shows the problem before you reorder.

Which SOP version and which agreement applied

“A partner's auditor asked which SOP version and which quality agreement were in force on the day of a batch. We spent the audit searching files named final_v3.”

What usually happens

SOPs sit in a shared drive with the version in the file name, and agreements sit in a contracts folder.

What SI 42 does

  1. 1SI 42 keeps each SOP with its owner and status, and each version with a change summary, author, approver and effective and retired dates; SOPs due for review are listed and a weekly digest names them.
  2. 2The CDMO board keeps each agreement (MSA, quality agreement, work order, supply agreement) with its effective and expiry dates and warns when one in force ends soon.
  3. 3An agent drafts the digest; you set each new version's effective date.

The outcome

You can say which SOP version and which agreement applied on any date, recorded in SI 42.

The guidance page that changed quietly

“A regulator updated a guidance page and nobody noticed until a consultant mentioned it, so the plan for our stage was rewritten in a rush the week investors asked about it.”

What usually happens

Someone is meant to check regulator sites now and then, and the stage plan lives in a slide deck.

What SI 42 does

  1. 1SI 42 watches the regulator pages you choose, flags a page whose text changed, and shows the start of the new text; a signed-in person marks it reviewed.
  2. 2Stage-plan items and terms that cite the page are flagged, and an agent drafts the revised text side by side with the current text.
  3. 3You accept, edit or reject each revision.

The outcome

You hear about a changed source when it changes, and the plan you show investors is current.

The material change that raised the cost

“Quality approved a material change, and we found at quarter end that it raised the product cost, after we had already quoted the old price.”

What usually happens

Quality records the change; finance finds the cost when the invoices arrive.

What SI 42 does

  1. 1Record the change as a change control in the quality events register, with its owner, reason and approver.
  2. 2In the costing board, substitute the material in the formula or set its new price; SI 42 recomputes the cost and final price of every formula that uses it, including formulas nested inside others.
  3. 3An agent drafts one summary for you to send of formulas that moved beyond your threshold, with the variance against your frozen baseline, and you decide the new price.

The outcome

You know what a change costs before you quote, not at quarter end.

The investor update that went out late

“Our investor update went out late because the runway figure, the program news and the investor list were in three different places, and a follow-on conversation went cold.”

What usually happens

The founder pulls cash from the bank, decisions from memory and the list from a spreadsheet, the night before.

What SI 42 does

  1. 1The fundraising board shows runway and monthly burn from the finance board's forecast, plus the cap table and the investor pipeline.
  2. 2Program decisions arrive from meetings as next steps an agent drafted and you approved, each with an owner.
  3. 3You write the update letter, choose investors by stage, status or fit, and schedule or send it; each send is logged against the investor.

The outcome

The update goes out on time with current numbers and the decisions behind them.

The late CDMO item that moves a batch

“The CDMO promised a document by Friday. It slipped, the batch date moved, and the work order behind that batch was at risk before finance heard.”

What usually happens

A tracker lists open items with due dates but no link to the batches or the contracts that depend on them.

What SI 42 does

  1. 1SI 42 imports your existing tracker; each commitment has an owner, a due date and its CDMO.
  2. 2Add need-by dates to batches, and the Batches view shows which late items put which batch at risk, on both sides; the money tiles add up the signed agreements tied to those batches.
  3. 3For a late item an agent drafts the chaser; you approve it and send it from your own mail.

The outcome

You see the late item, and the money behind the batch, before the batch moves.

The call where both sides heard different deadlines

“We agreed next steps on a call with the CDMO. They never reached the tracker, each side remembered a different deadline, and we approved their next invoice without knowing what was still open.”

What usually happens

Someone writes up the call when they get to it, and finance approves CDMO bills without seeing the tracker.

What SI 42 does

  1. 1Next steps from the meeting that name the CDMO arrive in SI 42 to accept or dismiss, with the quote they came from.
  2. 2Bills in the finance board are matched to the CDMO by its billing names, so each CDMO shows contract value, invoiced and paid next to what it still owes you.
  3. 3For a late item an agent drafts the chaser; you approve it and send it from your own mail.

The outcome

What was agreed on the call is what is tracked, and you see open work before you pay.

The supplier that started slipping

“A supplier started shipping late, rejections climbed and prices crept up. We noticed when a material ran short before a batch and paid extra for a rush order elsewhere.”

What usually happens

Purchase orders and delivery dates sit in email and a spreadsheet.

What SI 42 does

  1. 1SI 42 keeps suppliers, materials and purchase orders, lists overdue deliveries, and scores each supplier on delivery, price variance and rejection rate.
  2. 2Lot-level inventory shows what is left and what expires soon.
  3. 3Any email to a supplier, drafted by an agent, passes a buyer review and a second approval before it goes.

The outcome

You see a supplier slipping, in time and in price, before a material runs short.

The critical step nobody could confirm

“A critical step needed a supervisor, nobody running the batch knew which step it was, and the batch was held while its materials sat on the shelf.”

What usually happens

Steps are printed from a document, and run notes and yields are written up afterwards.

What SI 42 does

  1. 1SI 42 keeps the steps for each product version, marks the critical control points that need a supervisor, records the run and any deviation raised, and flags low yield.
  2. 2The costing board holds each product formula's cost at its batch size, in the same app, so the team can weigh a low-yield run against what the batch cost.
  3. 3An agent drafts the low-yield flag; a person decides what happens to the batch.

The outcome

Everyone running the batch sees which steps need a supervisor, and a low-yield run is flagged with its cost in view.

The price we kept quoting

“Our material costs moved with the exchange rate and a supplier increase, and we kept quoting last quarter's price until the margin was gone.”

What usually happens

The price list is a spreadsheet updated once a year, and cost changes reach it only when someone asks.

What SI 42 does

  1. 1The costing board holds your materials, priced in a base currency or locally, and each product formula with its batch size, margin and overhead; cost rolls up from materials through nested formulas to the final price.
  2. 2Each morning it takes the exchange rate (from your rate source or entered by hand) and the supplier price sheet, reprices every formula, and an agent drafts one summary for you to send of formulas that moved beyond your threshold.
  3. 3You review the movers and the variance against your baseline and set the new price.

The outcome

Your quoted price is repriced every day for you to approve.

The invoice paid twice

“We paid the same supplier invoice twice and paid more than our costing assumed for a key material, and found both at year-end close.”

What usually happens

Invoices are checked by eye against the PO, if there is time.

What SI 42 does

  1. 1Purchases and payments are recorded with supplier, item, PO and invoice numbers, and received quantity.
  2. 2Each day an agent compares every purchase price with the expected price from your bill of materials and flags variance beyond your tolerance; it also flags duplicate invoices, suppliers with no reference, quantities received short of what was billed, and split payments.
  3. 3You acknowledge, clear or confirm each flag.

The outcome

A duplicate invoice or an overpriced material is flagged the day after it is recorded, not at year end.

Youapproves next steps and owners