A research desk.
Built as a system.
Auctus Sapiens brings together data collection, quantitative analysis, AI writing, and publishing in a recurring research workflow.
A clearer view.
A traceable argument.
From source material to a structured brief: the evidence, the interpretation, and the questions still open.
- The product
- Auctus Sapiens
- The work
- Recurring research & publishing
- The relationship
- Built and operated in-house
Good research is
a recurring process.
A briefing depends on more than a well-written essay. Inputs need to arrive, calculations need to reconcile, evidence needs to remain accessible, and an issue needs to reach the reader in a consistent format.
The system is designed to make that chain repeatable. It combines deterministic code for structured operations with a language model for synthesis and prose.
Put each task
in the right place.
Data collection, charts, screens, statistical models, the paper-trading engine, typesetting, and delivery are handled in code. The writing stage uses a language model with the research context provided to it.
This creates a useful separation of responsibilities: calculations remain reproducible, while the model works on interpretation and communication.
From source material
to a published brief.
Collect
Gather source data and assemble the inputs for the issue.
Calculate
Run the screens, models, and charts in deterministic code.
Synthesize
Give the writer structured results and research context for the narrative.
Publish
Typeset and deliver a consistent email and broadsheet publication.
What this demonstrates.
A recurring process can combine AI reasoning with conventional software. The interesting engineering is the connection between the stages: the inputs each step receives, the responsibility it holds, and the record it leaves.
This is our own product, presented as an example of the practice’s work. The preview illustrates its publication format; it is not a customer result or a claim of investment performance.
What carries into
an operating workflow.
The same design questions apply to a service inbox, a document review process, or a weekly management report: which steps are deterministic, where does interpretation help, and where must a person approve the action?
A client deployment gets its own permissions, acceptance criteria, and human review requirements, defined around the actual business process.
Read the technical accountWhat would you put
back in motion?
Bring a recurring task, a slow handoff, or a growing backlog.
We’ll help you find a practical place to start.