Basecamp
$9,000/year · $900/month
The complete Lorescent software product with broad institutional access and no required Story Stroll services. Annual billing is recommended and saves $1,800.
Lorescent / Procurement & data
Evaluate Lorescent before your institution invests.
Pricing, relationship scope, source boundaries, portability questions, AI governance, and the relationship between Lorescent, EverStroll Brand, Story Stroll, and Impartis should be clear before a university moves through procurement.
Start with the software
Basecamp · $9,000/year
Recommended · save $1,800 · or $900/month
Basecamp is the complete Lorescent software experience. Institutions can add defined Story Study capacity, move to Always-On Story Studies, or enter a Strategic Storytelling Partnership without changing the underlying platform.
See all relationship levelsCommercial clarity
A university should be able to understand the investment model before beginning procurement.
Lorescent publishes the software-only entry price and the higher-touch relationship levels so procurement teams can distinguish software from Story Stroll Story Studies, strategy, and production services.
Always-On Story Studies
$60,000/year
Removes the fixed annual Story Study allotment. Institutions can request Story Studies throughout the year under the standard Story Study format, managed scheduling, and Story Stroll capacity rules.
Lorescent-inclusive Partnership
From $75,000/year
The Strategic Storytelling option shown here connects Lorescent, an EverStroll Brand Account, Always-On Story Studies, strategic support, and pre-approved Story Stroll production capacity. Impartis can be included when the scope requires governed research intelligence.
Team access
Broad access included
The Institution Account is designed to support shared institutional memory without per-seat friction.
Procurement path
Invoice / PO supported
Institutions can route setup through vendor review, invoice / PO, or other required procurement steps.
Data boundaries
The institution’s archive should not become another institution’s story library.
Lorescent is designed around institution-scoped workspaces and approved source boundaries. The software relationship and Story Stroll service relationship are intentionally separable.
Institution-scoped workspaces
Lorescent is designed so normal Member and Institution Admin experiences operate inside the assigned institution rather than a shared cross-client workspace.
Institution-controlled source boundaries
The institution keeps control of its original media and source archive. Lorescent can work from approved links, pasted/imported source text, transcripts, and institution-owned delivery destinations without requiring a shared Story Stroll Drive boundary.
No cross-institution story corpus
One institution’s interviews, quotes, Evidence Moments, findings, and Story work are not presented to another institution as a shared customer corpus.
Story Stroll and Lorescent are separable
An institution can invest in Lorescent without adding Story Stroll services. Story Studies, strategy, and production are optional service layers rather than prerequisites for the software.
EverStroll submissions keep their collection provenance
A connected EverStroll Brand Account can route eligible approved Story Call submissions into Lorescent, but the material must remain identifiable as an EverStroll Story Submission with its Story Call, collection method, contributor or anonymity state, consent, rights, and source provenance intact.
Impartis stays isolated until explicitly connected
An Impartis license does not automatically expose research to Lorescent. Cross-product exchange requires a separately entitled paired institution and an explicit connection; disconnecting stops new exchange without turning the two products into a shared tenant.
Define the exit before finalizing the investment.
Portability is a procurement question, not a future surprise. The agreement should distinguish the institution’s original source archive from Lorescent-created records and state what happens at termination.
01
Original source archive
Original media and source material remain in the institution-controlled systems where they are stored; Lorescent is not positioned as ownership of the institution’s underlying media archive.
02
Lorescent-created records
Export, retention, deletion, and transition handling for Lorescent-created records should be documented in the applicable agreement before an institution enters an annual relationship.
03
Termination
Procurement teams can require a defined post-termination process covering access end dates, requested exports, retention periods, and deletion responsibilities.
04
Service separation
Ending Story Stroll production services does not inherently require ending a Lorescent Institution Account, and ending Lorescent does not transfer ownership of the institution’s underlying source archive to Story Stroll.
AI & customer data
Separate what the product does from what procurement should verify.
Lorescent can explain its AI-assisted workflow without pretending every provider, retention setting, or contractual data-use term is interchangeable. Those details should be reviewable before production use.
What does AI do?
AI assists with interpretation, retrieval, synthesis, evidence organization, and creative exploration. Human users remain responsible for verification, editorial judgment, rights, attribution, and production decisions.
Is AI output treated as institutional fact?
No. Lorescent distinguishes AI-assisted interpretation from verified source facts and keeps findings connected to inspectable evidence where available.
Does customer material become a shared Lorescent corpus?
Lorescent is designed around institution-scoped customer workspaces rather than exposing one institution’s source material or narrative intelligence to another institution.
What should procurement verify about model providers?
Provider processing, retention, model-improvement or training settings, subprocessors, and contractual data-use restrictions should be documented in the procurement packet or applicable agreement before production use.
Procurement packet
What an institutional review should be able to request.
The goal is to make evaluation concrete: scope, security, data terms, vendor setup, and the optional Story Stroll service relationship should be documented rather than left to verbal assurances.
Pricing and scope
Annual platform rate, included access, optional Story Studies, and any Lorescent-inclusive Strategic Storytelling production allotment.
Relationship level
Whether the institution is purchasing Basecamp software, defined Story Studies through Happy Valley or Chimney Rock, Always-On Story Studies with managed capacity, or the Lorescent-inclusive Strategic Storytelling Partnership shown on this site. Story Stroll may scope other partnership structures separately.
Security materials
Institution-scoped access, roles, source and storage boundaries, tenant-isolation approach, rights provenance, and available security documentation.
Data terms
Source handling, customer-data use, AI-provider processing, retention, export, deletion, termination, and any institution-required contractual language.
Vendor setup
W-9/vendor records, invoice or PO requirements, authorized contacts, security review workflow, and any institution-specific procurement requirements.
Storyverse relationship
Which elements are Lorescent software, an EverStroll Brand Account, defined or Always-On Story Stroll Story Studies, strategy or production, and whether Impartis is included in the applicable scope. EverStroll-to-Lorescent and Impartis-to-Lorescent exchange each require explicit institutional connection and preserve their own provenance boundaries.
Reference & product-development rights
Pilot participation should not be treated as permission to use an institution’s name, logo, testimonial, case study, or source material as a public reference. Any reference or co-development rights should be separately documented in writing.
Security review
Security posture is documented separately from certifications.
Review current access controls, institution-owned source/storage boundaries, evidence provenance, rights workflows, AI boundaries, and the distinction between certifications and institution-specific regulatory obligations.
Make the decision with the terms visible.
Review public pricing, start with Basecamp, or begin vendor and security review before entering a broader annual relationship.