Document & data connections
Wire the platform into where your cost history already lives.
Past quotations, invoices, and cost records rarely live in one place. Craftsheart doesn't ask you to migrate them - it reads them where they already sit, keeps them current, and treats them as the ground truth every new estimate is built from.
what this does
The first thing the engine needs is your project history. Not a template library, not a rate card, not a benchmark set - your own quotes, your own invoices, your own delivered costs. Connections keep that history flowing in as it grows.
No manual rate cards
You are not maintaining a spreadsheet of material and labour rates. The engine reads what things actually cost, from what you actually bought.
Continuous ingestion
New quotes, invoices, and cost records feed in as they land. The next estimate reflects last month's reality, not last quarter's.
Read-only by default
Connections are pull-based and read-only. Craftsheart never writes back into your finance systems unless you explicitly wire that up.
a worked example
One connection. Every past quote it touches.
A single connection to your finance folder can surface hundreds of past project records - each becomes a candidate reference for future estimates.
Finance / Projects folder
connected 3 minutes ago - read-only
Quotations - 2024148 files indexed
Invoices - 2024312 files indexed
Cost sheets - 202484 files indexed
Quotations - 2023162 files indexed
Invoices - 2023341 files indexed
Site reports - 202496 files indexed
total indexed1,243 past project records - now available to ground new estimates
how it fits
Part of the loop, not a bolt-on.
- Reference candidates for the AI cost estimation step come from these connections - nowhere else. The engine can't ground an estimate in something you haven't connected.
- Cost-driver analysis uses the ingested invoices to know what "comparable" actually looks like at the line-item level.
- Margin and win-rate intelligence tracks outcomes across the same connected history, so the feedback loop closes on real data.
- Adding new connection sources - or removing old ones - takes effect on the next estimate, not on a quarterly refresh cycle.
keep exploring