Welcome to Agentic Collections & Acquisitions thatbuys the title the campus keeps borrowing.

The demand signals exist all over the record, and nothing connects them at decision time. Risely's agents feed usage, turnaways, loan repeats, and syllabus adoption into one board. The collections librarian approves every order, every renewal, and every cut.

Acquisition board · renewal season

signals arriving

· turnaway posted · a nursing student hit the user limit

· usage report landed · the bundle nobody opens

· loan repeat counted · the sixth borrow this year

Nursing research database

expand

40 turnaways land every month, and the program keeps growing

Aggregator bundle · $29K

renegotiate

3% usage · the worst usage per dollar on the board

Monograph · borrowed 6 times via ILL

purchase drafted

owning it costs less than the seventh borrow

Every case lands with the collections librarian, receipts attached.

ready before the vendor calls

Every demand signal lands on one board.

Usage, turnaways, loan repeats, and syllabus adoption live in different systems and never meet at decision time. Risely's agents pull them onto one acquisition board, sorted by the strength of the case.

Four systems, one board

connecting

Usage reports

what gets opened, per database

Turnaways

who hit a limit and bounced

Loan repeats

what keeps getting borrowed

Syllabus adoption

what courses assign

One acquisition board sorts every title by the strength of its case.

The signals always existed. They just never met at decision time.

The expansion case is written before the complaints are.

The nursing database turns students away 40 times a month while the program keeps growing. Risely's agents draft the expansion case with both curves attached.

Nursing research database

expand

turnaways, term over term · now 40 a month

The turnaway curve matches the program's enrollment curve
Expansion case drafted with both curves attached

The case is written the year the demand curve says so, before a complaint reaches the dean.

The renewal call starts from the library's own numbers.

The $29K bundle sits at 3% usage, and the vendor already knows its price. Risely's agents put the usage-per-dollar line on every renewal before the call, so the negotiation starts even.

Aggregator bundle · up for renewal

renegotiate

$29K

what the bundle costs

3%

how much of it gets used

Usage per dollar ranks every renewal line before the vendor calls.

The vendor knows its price. Now the library knows its usage, and the negotiation starts even.

Borrowing six times proves the purchase.

A title that keeps coming back through interlibrary loan costs less to own than to borrow again. Risely's agents run that math and draft the order for the collections librarian to approve.

One title gets borrowed again and again

0 of 6 this year

each block is one interlibrary loan of the same title

Owning it costs less than the seventh borrow, so the purchase is drafted for the collections librarian.

The collection grows exactly where borrowing proved the need.

One turnaway posts. The case re-runs.

A turnaway, a loan repeat, a syllabus that adopts a title mid-term. Any of them changes what the budget should buy, and every one runs the same way.

  1. A turnaway posts

    a nursing student hits the user limit

  2. The demand curve updates

    the expansion case recomputes

  3. The renewal stance shifts

    the idle bundle funds the fix

  4. The librarian reviews one case

    receipts attached

  5. The budget follows demand

    before the vendor calls

What changes, and how it runs.

Every dollar follows a demand signal

Usage, turnaways, and repeats make the case before intuition does.

Every renewal starts from the library's numbers

The usage-per-dollar line is on the table before the vendor calls.

The collection grows where borrowing proved the need

The repeat purchase drafts itself, and a librarian signs it.

The technical read

Connects read-only to usage reports, the ILL record, and the acquisitions system to start

The collections librarian approves every order and every cut

Every action lands on an append-only log

SOC 2 Type IIFERPAGDPR

Runs alongside what you have. Nothing rips out.