To give small and mid-sized companies AI that is grounded in their own documents, honest about what it does not know, and shipped on a website they can actually run.
01Three commitments
01Grounded
Every answer points back to a line in a document the client owns.
p.14 §2.1
Nothing is answered from general knowledge. Every answer comes from a document the client owns, and every extracted field points back to the line it came from. If a claim cannot be traced, it does not ship.
02Honest
Confidence is scored. Low-confidence output is routed to a person.
A
0.94
B
0.71
C
0.38
C → human review
A system that guesses is worse than no system. Confidence is scored, low-confidence output is routed to a person, and the assistant says when it does not know. Refusing well is a feature, not a gap.
03Owned
The repository, prompts, evaluation set and data are the client’s.
repopromptseval setdata
Client · day one
The client keeps the repository, the prompts, the evaluation set and the data. No dependency on Korpus Labs to keep the thing running.
01Grounded
Nothing is answered from general knowledge. Every answer comes from a document the client owns, and every extracted field points back to the line it came from. If a claim cannot be traced, it does not ship.
02Honest
A system that guesses is worse than no system. Confidence is scored, low-confidence output is routed to a person, and the assistant says when it does not know. Refusing well is a feature, not a gap.
03Owned
The client keeps the repository, the prompts, the evaluation set and the data. No dependency on Korpus Labs to keep the thing running.
02How we work
01
Scope first
A short scoping call establishes what documents exist, what questions get asked, and whether the problem is worth automating. Some are not, and saying so is part of the job.
02
Small first
The first delivery is narrow and real rather than broad and demonstrative.
03
Measured
Before anything goes live, it is graded against a set of questions drawn from the client’s actual inbox.
04
Handed over
Documentation, repository access and evaluation set transfer to the client at the end.
01
Scope first
A short scoping call establishes what documents exist, what questions get asked, and whether the problem is worth automating. Some are not, and saying so is part of the job.
02
Small first
The first delivery is narrow and real rather than broad and demonstrative.
03
Measured
Before anything goes live, it is graded against a set of questions drawn from the client’s actual inbox.
04
Handed over
Documentation, repository access and evaluation set transfer to the client at the end.
Some are not, and saying so is part of the job.
03Goal
Build a repeatable practice serving US clients, starting with work that can ship in weeks and moving up to work that takes months.
Near term
Websites and chat assistants for small and mid-sized businesses. Fast, well-built sites and an assistant that answers from the client’s real catalog and pricing. Short engagements, clear scope, visible results.
Medium term
Move up-market into larger and more technical companies as the portfolio and case studies build. Bigger document sets, deeper integration, longer engagements.
Throughout
Every project leaves behind an evaluation set. Quality claims are backed by measurement on the client’s own questions, not by demo footage.
Every project leaves behind an evaluation set. Quality claims come with measurements attached.