Capabilities
What krtiq does, stated plainly.
One page, no narrative. Each capability is described by the mechanism behind it, so you can judge whether it fits your portfolio before you talk to anyone.
Getting contracts in
Connected sources
Pull agreements from where they already live.
krtiq connects to Gmail, Outlook, Google Drive, and Microsoft file storage and imports agreements from them, so adoption does not begin with a migration project.
Out-of-order ingestion
Add documents in any order.
krtiq revises earlier machine conclusions when a later document explains them, so an amendment that arrives before its base agreement still resolves correctly.
No tagging or taxonomy
Nobody labels documents.
Document type, counterparty, and the role a document plays in its agreement family are inferred during extraction rather than entered by a person.
Configurable fields
Extract the terms your business actually tracks.
Field definitions are configuration rather than code, so adding a field does not require an engineering change.
Understanding the agreement
Agreement families
Group a base agreement with everything that changes it.
krtiq resolves the references between documents to connect an MSA with its amendments, addenda, order forms, and renewals, and keeps separate families with the same counterparty apart.
Effective terms
See the term in force, not four versions of it.
krtiq traces the family's amendment chain in effective-date order and reports the current value together with the document that last set it.
Buy side and sell side
One portfolio for what you owe and what you are owed.
Agreements are modelled from both sides of the relationship, so supplier commitments and customer commitments live in the same portfolio without being confused for each other.
Relationship graph
Query how documents relate, not just what they say.
Relationships are stored as typed, time-bounded edges - amends, supplements, renews, terminates, governs - so a question can ask what was true on a given date.
Asking and verifying
Plain-language questions
Ask the portfolio without learning a query language.
Questions are answered against accepted current terms rather than by searching raw text, so the answer reflects amendments that have already been applied.
Clause search
Find a concept, not a keyword.
Structured filters and semantic matching run together, so a search returns contracts that express the same idea in different words.
Relational queries
Answer questions about how agreements changed.
Relationship questions compile to a constrained graph query over a fixed set of relationship types. Generated code never reaches the database.
Evidence on every value
Open the clause behind any number.
Each extracted value keeps the clause, document, and location that produced it, so a finding can be checked against the source rather than trusted.
Visible uncertainty
Know which answers are settled.
Every value carries one of six states - ready, incomplete, proposed, disputed, missing, or rejected - instead of presenting a low-confidence guess in the same voice as a confirmed term.
Protected decisions
Your corrections survive reprocessing.
A decision a person has confirmed is never overwritten by later machine processing, and the reasoning behind it stays attached to the agreement.
Acting on it
Obligations register
Dated commitments that stay correct.
Obligations are derived from accepted current terms, so an amendment that changes a notice period moves the deadline, and each obligation cites the document that establishes it.
Renewals and notice periods
See what is coming before it lapses.
Renewal and notice dates are computed from the governing term rather than from a date typed into a tracker, so they follow the amendment that changed them.
Risk findings
Surface the terms worth arguing about.
Findings are scored across the portfolio so exposure can be ranked instead of read contract by contract.
Anomaly detection
Notice the agreement that does not look like the others.
krtiq compares terms across comparable agreements and raises the ones that depart from the pattern.
Playbook comparison
Measure drift from your standard positions.
Agreements are compared against your own standard positions to show where a negotiated term departs from the playbook.
Running it safely
Tenant isolation
Your portfolio is your own.
Every record is scoped to an organisation, and queries are constrained to that scope rather than filtered after the fact.
Role-based access
Control who sees what.
Access is granted by role, and plan limits are enforced in the backend rather than hidden in the interface.
Audit trail
Reconstruct how a conclusion was reached.
Decisions, corrections, and the evidence behind them are recorded, so the history of a term can be replayed later.
No training on your contracts
Your agreements are not used to improve a model.
Contract text is processed through enterprise model APIs whose terms exclude customer content from model training.
See krtiq on your workflow