Gather the signed record
Upload the agreement and amendments that define an active customer relationship.
In development · Contract obligations
Turn signed contracts into visible responsibilities.
We’re building a obligations copilot for small companies managing customer contracts. Find the promises, deadlines, and notice requirements that need an owner after signature.
Source-linked findings · Human review at each step
REVIEW BRIEF / 001ILLUSTRATIVE EXAMPLE
A renewal notice date needs an owner
Fictional documents · sample findingHuman review
What the sample evidence says
A fictional agreement requires written notice before renewal; its amendment changes the service term.
Planned output: links to supporting passagesA specific next step
Review both clauses and confirm the applicable notice date before adding a task.
Workflow preview · Illustrative documents and findings
Sources → findings → reviewed actions
DESIGNED FOROperations teams at small B2B companies
The product workflow
Make the evidence easier to use.
Planned inputs: Executed customer agreements, amendments, and approved internal policies. The first release will focus on one repeatable workflow, with people reviewing the result.
Extract what needs attention
Claude will identify obligations, link each finding to a clause, and flag ambiguous or conflicting terms.
Assign a reviewed action list
An operator approves owners, dates, and tasks before exporting the obligations register.
Built around evidence
Every finding should be reviewable.
The planned Claude integration will read source documents, reason across relevant passages, and produce structured drafts with references and open questions.
Clear sourcesLink the reasoning to the document passages that support it, and flag missing evidence.
A deliberate review stepOperators will review clause references and approve responsibilities, dates, and any customer notices.
A focused first releaseDocument uploads and reviewed exports first. Connected-system integrations will be considered after the core workflow works.
Product development
A focused first release.
What is the product designed for?
Operations teams at small B2B companies. The workflow brings relevant documents, source-linked findings, and reviewed next steps into one packet.
What is on the roadmap?
The first release will support executed customer agreements, amendments, and approved internal policies, structured findings with citations, and reviewed exports. Connected-system integrations will follow the core document workflow.
How can I help shape the workflow?
Share the document review, questions, and handoffs your team repeats. We’re focusing development on a practical workflow that fits how your business operates.
A clearer workflow starts here.
Share the documents, questions, and handoffs that slow your team down.