We built Daybook for one client to show what AI inside your own tools looks like. It lives in Slack, Teams or WhatsApp and has read the whole project: Procore, drawings, contracts, photos, voice notes and email. It answers with the source cited, drafts the paperwork, and knows what you paid for everything.
$14,220. That is 5% of $284,400 claimed to date across claims 1 to 6. Half is due for release at practical completion under clause 42.3, the rest at the end of the defects period.
Drafted RFI 119 in Procore: 250PFC lintel shown on S-301 Rev E is not in the steel fabricator's commitment. Photo attached, A-301 and S-301 referenced. Ball in court: structural engineer. Waiting for your approval before it sends.
You type, speak, or drop a photo in the project channel. Daybook does the rest. It runs today on live projects for a client.
Procore: RFIs, budget by cost code, commitments, invoices and their PDFs, drawings, specs, submittals, daily logs, photos, punch lists, meetings. Documents you drop in: PDF, Word, text, CSV. The project mailbox. Site photos, zoomed to the detail. Voice notes, transcribed.
Who holds the ball on RFI 41. What the contract says about delay. What changed between revisions. What is committed against a cost code and what is left. Every answer cites the page, the record or the email it came from.
Drafts RFIs from a sentence or a photo. Uploads files to Procore. Writes reports out as PDF, Word, HTML or CSV, delivered into the channel. Compares a site photo against the drawing.
Every supplier invoice read line by line. Ask what you paid for a skip bin in March, from whom, and whether the GST was right. Flags mismatches between invoices, Procore and the ledger.
Slack today. Microsoft Teams and WhatsApp next. One channel per project, and it scopes itself to that project. Direct messages for private questions. English and Hebrew.
Only the people on your list can use it. It never approves an invoice, never sends an email, never changes a record. Drafts only. A person signs off.
Running for a client today. Nothing on this list is a roadmap.
Numbers from real runs. Client not named. Read the case studies.
Fixed setup, then a flat monthly fee for the company, not per seat. Prices exclude GST.
Two weeks. We connect Procore, your mailbox and your chat tool, index the documents for every live project, and put your people on the list. You are asking it questions by day three.
Every project, every user on your list, all model usage included. We keep it running through Procore changes and add one improvement a month. Cancel any time.
Something Daybook does not do yet: a dashboard, an integration, an automation particular to how you run jobs. Scoped and fixed price. See what we have built.
No. Daybook reads and writes to the Procore you already have. It also runs without Procore, on documents alone.
Your documents stay in your accounts. Voice is transcribed locally. The model providers we use do not train on your data, and for sensitive projects it runs inside your own cloud account.
Every answer cites its source so you can check in one click. It only creates drafts. A person approves anything that goes into Procore or out to a client.
Only people you put on the list. It works in project channels and direct messages, in English and Hebrew, and scopes itself to the project the channel belongs to.
Approve invoices, send email, or change records. Scanned image-only PDFs are indexed but weak. Excel is read as data, not formulas. Teams and WhatsApp are next.
Daybook is built by Itay in Sydney. It started as a tool for one client and grew into the thing on this page.
Before that: [years] years in [construction finance / software / both]. You deal with the person who writes the code.
Twenty minutes. Bring a Procore login or a folder of drawings and contracts. We connect it live and you ask it questions.
Book a demo