Fieldflo demo to the owner — the workflows, from the recording (2026-09-15)

Source: profile/Fieldflo_Call_Transcript_2026-09-08.txt (Fathom, 43 min, 2026-09-08). "the owner" is the owner (Omar confirmed 2026-09-08). "Dan" is Dan Szigeti, Fieldflo co-founder, who ran the demo. "Mark" is Mark Chambers, Fieldflo BDR. Rule for this file: every claim carries the timestamp where it is said. Where the transcript is garbled, that is said. Nothing here is inferred from Fieldflo's website. Lines in the transcript starting ACTION ITEM: are Fathom's automatic notes, not speech, and are treated as such.

Written by the Makki Hive analysis seat on Omar's order. Read-only otherwise.

A. What Fieldflo demoed, flow by flow, in the order Dan showed it

Dan's own order was: log in and dashboards → roles (jumped to answer the owner) → QuickBooks and employees → training → certificates → inventory → projects, proposals, closeout → the field day → takeoff/estimating (skimmed) → scheduling and Gantt → payroll approval → price. Fieldflo's own screen and button names are in bold.

Flow 1 — Log in, branding, who sees what (@2:37, @8:30)

Log in. "Wherever you see Fieldflo, just imagine your logo and branding." (@2:37)
"Everything is built on a role and permission." Access can be restricted "to every part of your platform." (@2:37, @3:40)
"Your daily labors, they'll verify time and safety, but they'll never actually log into your platform." (@2:37)
Open an employee's profile → Employee roles → tick the tabs that person may see. Dan showed giving "Adam" payroll only, to answer the owner's accountant question. (@8:30)
"A supervisor, foreman, they'll have very limited, like view projects, you know, add forms, take pictures." (@8:54) Owner: "That's pretty much it." (@9:24)
Each employee can be sent "their own approval process": a text with their time and hours for the day and week, "Were you injured? Does everything look good?" (@9:40)

Flow 2 — The dashboard tour (@3:40 to @12:38)

Not one workflow; a run through the widgets on the owner's dashboard. In the order shown:

Today's active projects: "comes to life in real time as your supervisor foreman in the field is clocking his… crew for the day." Click into a project "and start auditing all their paperwork right from your dashboard." (@3:40)
Projects "over 50% on their bid versus actual": cost codes, labour types, bid / actual / remaining. (@5:00)
Certs: "let you know a bunch of different ways that things are getting close to expiring." (@5:00)
Employees nearing overtime, "this comes to life at 32 hours." New projects. Time and materials and change orders. (@5:31)
Audit all forms in one place ("all the safety meetings we've done across all of our branches in the last month"). (@5:31)
Deploy messages to the whole crew by text or email ("PPE week… holiday party"). (@5:31)
Map of where projects are and where employees clock in from. Last injury form. Counts of employees, clients, users. (@5:31)
Safety dashboard: incidents, near-miss, stop-work. A whole incident reporting system that walks through a claim (property damage or injury). (@5:31)
Inspection management: own or ready-made inspections; a failed item can be assigned as a corrective action to an employee, and "they'll remain on this board until they fix it." Reports and stats "for OSHA." (@5:31)
Equipment dashboard: maintenance, corrective actions on assets, inspections due, rentals to call off, what is assigned where. (@5:31)
CRM: "By no means are we Salesforce." Tracks reach-outs, job walks, proposals sent from Fieldflo, won / lost. (@5:31)
Notifications: a daily digest (twice a day if there are night shifts) and instant ones (property damage, injury, change order, no access). The digest carries the "data points that you signed up for": certs near expiry with a link to the cert area, permits near expiry, who is not doing paperwork correctly, warehouse orders pending, low inventory, scheduling conflicts. (@10:42)
"You can actually send each employee their own schedule right to their cell phone or email." (@10:42)

Flow 3 — QuickBooks and setting up an employee (@12:38 to @14:06)

The owner confirmed employees are in QuickBooks Online. (@8:00, @8:09, @12:47)
The integration "will bring in those employees, right? So you don't have to do that duplicate entry." Then "click on each employee just to… update that information." CSV import if there is no integration. (@12:48)
How every page works: "Everything is a big button or three dots." Three dots = admin customisation for that page. Big button = add something. "It's all just painting by number." (@12:48)
The moment an employee is created, "a unique QR code will be added for them." "An inspector in the field can scan their hard hat and see their active certificates right from there." (@12:48) Owner: "Oh that's great." (@14:00)
Inspectors see only active certs. The employee sees the same page including missing or expired, "so it's on them and the company." (@14:06)

Flow 4 — Employee profile, skills, training (@14:06 to @16:40)

Emergency details on the profile. (@14:06)
Training system: push a training to the whole company or a division; each employee gets it to their cell phone, enters "their secret PIN," takes it in their language. (@14:06) Owner: "Perfect." (@15:24)
Optional: "I think for $4 an employee per month" Fieldflo can drop in "over 600 videos… from Got Safety," with a quiz; a pass produces a branded certificate "that will track like any other cert." (@15:31) the owner finished the sentence: "And let you know that's been close to expiring and all that fun stuff." (@15:45)
Profile fields: employee number, name, cell, temp labour, default cost code / position, office or division, skills. Dispatchers filter by skill ("Suncor orientation or a school background check") and see an icon on the project. (@15:51) Owner: "Yeah. So they have a nice little picture, certs." (@16:35)
Training matrix: who has what certs and whether they have the right ones. Write-ups, permissions, trainings, documents, emergency contact. (@16:40)

Flow 5 — Certificates: add, renew, archive (@17:30 to @19:01)

Certificates page → three dots → Cert names to define the list of cert types. (@17:30)
Add certificate: pick the cert name, valid from, expiration, which employee, take a picture of the cert, upload. Listed alphabetically. (@17:30)
Renewals: a list of "all the ones that need to be renewed." Three dots → Renew → new valid-from and expiry. "The new one becomes active, the old one becomes archived forever." (@17:30)
Export: "create a PDF pack" of certs to send to anyone. (@17:30)
Archive is visible forever. (@18:52, @19:01) Owner: "It's pretty, pretty straightforward." (@18:46) "I haven't seen anybody else incorporate that into… their program." (@18:54)

Flow 6 — Inventory and equipment, yard to site and back (@19:01 to @21:20)

Inventory page. Big button → Add item (excavator, skid steer, sprayers). (@19:01)
Each item gets a QR code. "Put this on your assets." An operator scans it and "do an inspection right from there without even logging into Fieldflo," or reads the SDS on a chemical. (@19:01)
Item record: number, warehouse location, name, inspections, quantity, office, cost codes and rates (T&M rates can be brought in). (@19:01)
Inspections per item; a red one failed and "your warehouse manager will be notified." Questions vary by inspection type; you can build your own. Maintenance and repair history. (@19:01)
Loadout list: the PM lists what a project needs; the warehouse manager is notified with address and delivery notes, fulfils it; stock moves out of inventory and onto the project and is cost-coded, estimates versus actuals. (@19:01)
Reporting Center → Project Inventory Report: everything on a project, ordered, returned or consumed, in real time. (@19:01) Owner: "That's great." (@21:20)

Flow 7 — Setting up a job: project book, proposal, closeout (@21:26 to @24:23)

Projects come over from QuickBooks or "you just press the big button." (@21:26)
Project details "will now be your project book for everything": name, number, night shift, crew list, loss type, projected work days, scope of work, address. (@21:26)
Permits and notifications go in here "so we can let you know when they're getting close to expiring" and the field can see them. Per diem. (@21:26)
"What certs and trainings are mandatory for this project?" Set once; "when you go to schedule people, we'll make sure they have the right things. And also when they add to the timesheet." (@21:26)
Cost codes for the job, "mirror your naming conventions." Building and owner information. (@21:26)
Waste reporting: haulers, material types, truck types, landfills. Custom tabs. Templates ("for these projects, I want you to answer these questions"). Insurance. (@21:26)
Emergency contact: "Fill this out once. This will end up on your daily safety meeting every day automatically." Save. (@21:26)
Job costing estimates on the project. Proposal builder: send the proposal with bid items from Fieldflo to the client; "if it gets awarded, they'll drop in." Or add bid items by hand or from an Excel sheet. (@21:26)
Every project has its own document system. Closeout report with dailies, certs and documents in it. (@21:26) the owner, asked how he felt: "Honestly, great. It seems like a perfect fit for us… there's nothing I could think of that we would need added." (@24:07)
Dan added: branches can be tied into "an HQ dashboard." (@24:23)

Flow 8 — The field day, on the foreman's phone (@24:23 to @32:09)

This is the longest and most detailed flow in the demo.

The foreman opens the app and sees only projects, in any language (French, Spanish named). (@24:23)
Press Start day. "By hitting start day, automatically brings in the dailies that they have to fill out." For the demo project: "a timesheet, a JHA, an inspection, and a daily." (@24:23) Owner: "Yeah." (@25:39)
Timesheet first. Two head starts: three dots → Same as previous day (drops in yesterday's crew), or Pull from scheduling (drops in who dispatch scheduled). Add or delete "based on who really showed up." (@25:57)
Adding a man without the right certs: "we're going to let that supervisor know. And if someone gets added anyway… an email will get sent to you guys in the office." (@25:57)
Cost code per man, mirrors the company's codes, can be defaulted. Pick who is starting → Start. "The supervisor's controlling the timesheet. Each laborer is going to verify." (@25:57)
The labourer gets a text within seconds asking for location. Optional. (@25:57)
The office dashboard shows the project started "to the second." (@25:57, @27:47)
JHA / pre-job safety meeting. Three dots → Same as previous day, then edit ("yesterday was the ninth floor, today's the 10th"). Supervisor enters their PIN to sign. Nearest hospital. PPE requirements, personal limitations, hazards, evacuation plan (from the project details), task steps, hazards and controls. (@27:47)
A task library: "your supervisors just hit add tasks and they'll select what they're doing will automatically fill out the paperwork for them." New-day questions must be answered fresh. (@27:47)
"Anybody who is on a timesheet needs to verify that they understood that safety meeting." Each gets the whole meeting by text, translatable, to sign off on their own phone. (@27:47, @36:37)
Everyone goes to work. Inspections if wanted; a "no" or "broken" can be assigned as a corrective action to an employee, who is notified. (@27:47)
Dailies: ready-made for the industry. "Start talking into it in any language. What'd you do today?" Incident / near-miss / stop-work notifies the office at once. Goals for tomorrow and the week, meeting log, "any more asbestos that are mold detected, any abatement procedures," pictures on every daily. (@27:47)
Containment log: names already there, respirator used, task, time in, time out, signature. Unanswered fields stay red until filled. (@27:47)
End of day: back into the timesheet, who is leaving, what breaks. Everyone on the timesheet verifies by text: time correct, meals, injured, "everything looks good." (@27:47, @31:xx garbled) the owner's reaction on the timesheet: "No. No." (no questions, @27:45). His question afterwards: is there an orientation video for managers. (@32:09)

Flow 9 — Takeoff and estimating (@33:12 to @34:47), skimmed

Dan: "we just released our own takeoff and estimating system for the abatement world." (@33:12)
Walks the estimator through work type (demolition / abatement; residential / commercial / industrial), bring in files, "Fieldflo will start cooking for you," output goes "automatically… into your proposals with your bid items and your tasks," sent to the client. (@34:47)
Dan dropped it: "we can talk about that another day." (@34:47) the owner's reaction is the only cool one in the call: "I don't know if that's something our team would be interested in. I know our estimators aren't fans, but it'd be cool to see." (@34:36)

Flow 10 — Scheduling and dispatch (@34:47 to @36:37)

Dispatching system: "send each employee their own schedule." (@34:47)
Projects in the chosen time frame are listed; "you'll just pick on the schedule, the ones that you want to schedule." (@34:47)
Each employee gets their assignments on their cell phone. (@36:37)
Gantt chart "with everything that's coming up," to see people coming off a project and where more work is needed. (@36:37) Interrupted here by the owner's broken text links (see B, "What went wrong").

Flow 11 — Closeout and weekly payroll approval (@36:37 to @39:11)

End of project: "create a whole closeout report of everything you've done in that project." (@36:37)
End of week: Payroll approval. Everybody's total time, then per employee, per project, per cost code. Make fixes. (@36:37)
Output "a nice spreadsheet right for your in-house accountant." (@36:37)
Optional approval chain: "I want all of my PMs to approve their projects," with a trailing history; the payroll administrator cannot run it until the named approvers have signed. (@36:37)
"And that is Fieldflo." (@36:37)

Flow 12 — Price and next steps (@39:11 to @43:19)

Owner: "Pricing. Where are we at for pricing? How does this work?" (@39:11)
Priced "in tiers," counted on "supervisors or foremen and above," not daily labour. (@39:16)
Owner: about 10 on demolition/abatement, "10 project managers," "close to 80 employees," and "just under 15" core users. (@39:36 to @40:22)
Dan: "around like 15,000 for the year for Fieldflo with a QuickBooks integration." (@40:27)
The owner asks for a demo or trial login (@41:06). Dan: no. "If we just gave you a blank platform, there'd be no data in there." Offers to redo the demo for colleagues. (@41:24)
Dan suggests Friday; the owner says Fridays are the team meeting; Dan: "Maybe we can do that on Friday." Dan will send the video. (@42:47 to @42:51) Nothing was booked on the call.

B. The owner's own words, verbatim, by theme

Why he took the call, and what is wrong today

@2:01: "we have been trying to look for a program to use, I'll just give you a little bit of background, we have tried a couple programs that just, yeah, we found hard for our workers and our managers to use on site, and it was kind of messing us up because some people were using it, some people weren't, everything was out of whack, so when you guys contacted us, I figured, hey, we might as well give you guys a shot, see what you guys got, and if this works for us, So, we'll incorporate it across five companies that we have."
@40:46: "I do want to pitch it to our VP. We have been looking for a program, so they, they do know that we are trying to implement something and they, they have approved to spend money on a new. We because our current system is holding us back."

What his crews actually fill out

@4:26, asked if it is "a timesheet, a safety meeting, and some dailies": "Exactly. Some stuff for abatements is a little more detailed and job specific."
@25:39, asked if "a timesheet, a JHA, an inspection, and a daily" sounds similar: "Yeah."
@40:00, on what the 80 employees would do in it: "Meetings and time."

What he asked for (his only unprompted requests)

@8:00, cutting into the CRM pitch: "Connect to QuickBooks." @8:09: "Online."
@8:14: "We do have an accountant doing payroll. So I was just wondering, are we able to give, like, let's say my accountant, I just wanted to give them access to just payroll. Would they be able just like I do, am I able just to choose what they have access to?"
@32:09: "Do you guys have like an orientation video or like, like say you guys have like those things for the asbestos training? Do you guys have like an orientation video for use of the program that we can kind of share with like managers?"
@41:06: "Is there a demo login? Is there a demo login or a trial login that we can open up and we can just view?"

What he liked, in order

@8:52, roles per tab: "Okay. Wow."
@10:37, the dashboards: "No. Very, very user friendly from what I can see."
@14:00, hard-hat QR for inspectors: "Oh that's great."
@15:24, training pushed to the phone: "Perfect."
@15:45, training certificate tracked like any cert: "And let you know that's been close to expiring and all that fun stuff. Okay."
@16:35, skills icons on the project: "Yeah. So they have a nice little picture, certs."
@18:46, certificates: "Nope. Nope. It's pretty, pretty straightforward."
@18:54, cert archive / QR: "I haven't seen anybody else incorporate that into, uh, into their program."
@21:20, inventory and loadouts: "That's great."
@24:07, after project book, proposals, closeout: "Honestly, great. It seems like a perfect fit for us, to be completely honest with you. That's awesome. Yeah, there's nothing I could think of that we would need added."
@33:05: "I love how it's tailored to demolition and abatement."
@40:36, after the price: "Okay. I think, I think it's a great, I think it's a great fit for us."
@42:40: "It's a great fit. And I'll see when they have time to jump on a meeting."

Where he was cool or pushed back

@34:36, takeoff and estimating: "I'll check it out. I don't know if that's something our team would be interested in. I know our estimators aren't fans, but it'd be cool to see."
@9:24, on foremen having only "view projects, add forms, take pictures": "That's pretty much it."

What went wrong on the call

@35:48, on the test texts: "I have, but when I'm clicking on them, they're not going anywhere because it I'm not connected to the… Fieldflo app."
@36:19, asked if he saw the JHA: "No."
@36:24: "Yes, I'd verify safety, but when I was clicking it, kept saying that I'm not connected to the app and the link is not valid."
Dan: "I'll send you one from a different portal." (@36:37) The transcript never comes back to whether the second one worked.

Size and money

@39:36: "On the demolition abatement, we would probably have 10."
@39:47: "Yeah, we'd have 10 project managers on there. And then probably close to 80 employees."
@40:22: "Sorry. Yeah, we would probably be around that 15 mark, probably just under 15."
Quoted price (Dan, @40:27): "around like 15,000 for the year for Fieldflo with a QuickBooks integration." Currency not stated.
@17:17: he gave a 403 cell number on the call (full number is in the transcript; not repeated here).

Next steps, in his words

@40:46: "I do want to pitch it to our VP."
@42:27: "Yeah. Okay. I do have that original email that Mark sent me."
@42:35: "I'll run it all past our VP."
@42:49: "know Fridays, usually we have our team meetings."
He never mentioned EazyLife, the portal, or any other vendor by name.

C. Where our earlier notes are wrong or unsupported

Checked line by line against the transcript. Most of both files holds up. These do not.

`profile/Fieldflo_Competitor_Call_2026-09-08.md`

"It stayed broken for the rest of the call." Not supported. Dan said "I'll send you one from a different portal" (@36:37) and the subject never comes up again. We do not know whether the second text worked. Say "was broken on the call; no fix shown."
"Zero AI. In 43 minutes, not one agent, not one thing that does work on its own." Overstated. Dan showed or described several things that act without a person: the JHA task library that "will automatically fill out the paperwork for them" (@27:47); the emergency contact that "will end up on your daily safety meeting every day automatically" (@21:26); the takeoff tool that takes uploaded files and "will start cooking for you" then drops bid items into the proposal (@34:47); twice-daily and instant notifications (@10:42); cert and permit expiry warnings (@5:00, @21:26); warehouse and office notifications on failed inspections and missing certs (@19:01, @25:57). None of it is an "agent," and nothing in the demo chases money or writes a report from a voice note. But "nothing does work on its own" is not true and the owner will know it if we say it.
"It's a rented product, not theirs. Generic platform, their logo dropped on it." Editorial, not from the call. What Dan said is the opposite in spirit: "Wherever you see Fieldflo, just imagine your logo and branding" (@2:37), i.e. Fieldflo white-labels to the customer. The "suggestion box" point is fair (@33:12) but the "rented" framing is ours, not the transcript's.
"Fieldflo is sending: orientation/training materials + this recording, and a fixed SMS test." Partly from Fathom's auto-generated ACTION ITEM lines, not from speech. What was actually said: "I can get you some information" (@32:27), "I'll send you one from a different portal" (@36:37), "I'll send you this video" (@42:51). Close enough, but the source is weaker than the note implies.
"The Friday demo is a live deadline" / "penciled for Friday." Nothing was booked. Dan proposed Friday, the owner said Fridays are team-meeting day, Dan said "Maybe we can do that on Friday" (@42:47 to @42:51). That Friday was 2026-09-12 and is now past; we have no evidence it happened.
"the owner's #1 ask" is role-gating. That ranking is not in this transcript. The one access thing the owner asked for unprompted was payroll-only access for his accountant (@8:14). His first unprompted words were "Connect to QuickBooks" (@8:00). Both are supported; the "#1" label comes from elsewhere.
"Waste manifests." Dan said "waste reporting system": haulers, material types, truck types, landfills (@21:26). "Manifests" was never said.
"Under 15 users." Supported (@40:22), but note the sequence: the owner first said "10" on demolition/abatement, then "10 project managers," then "just under 15" (@39:36 to @40:22). The counts are rough, not a headcount.

`profile/Fieldflo_vs_Makki_Comparison.md`

Section B claims "in demo order." It is not. Actual order: dashboard tour (with safety, incidents, inspections, equipment dashboard and CRM all inside it, @3:40 to @12:38) → roles (@8:30) → QuickBooks / employees / QR (@12:38) → training (@14:06) → certificates (@17:30) → inventory (@19:01) → project book, proposals, closeout (@21:26) → the field day (@24:23) → takeoff (@33:12) → scheduling and Gantt (@34:47) → closeout, payroll (@36:37). The table puts safety and equipment after the field app and CRM near the end; both were in the opening dashboard tour.
"Fieldflo is a place to type things in; nothing in it acts on its own." Same overstatement as item 2.
Row B7 "OSHA reports." Dan did say OSHA (@5:31). Worth noting Fieldflo is US-built (Denver) and the owner is in Alberta; nothing on the call covered Alberta OHS. Not a contradiction, a gap the note does not mention.
Row B5 "each labourer gets a text to confirm hours + safety talk." Supported, but it is two texts at two times: the safety meeting sign-off in the morning (@27:47) and the hours / meals / injured check at end of day (@27:47, @9:40). The note collapses them.

Nothing in either file contradicts the price, the user count, the QuickBooks Online fact, the hard-hat QR, the no-trial refusal, or the owner's "perfect fit" line. Those are all verbatim.

D. Our three workflow slides against the video

Slides 6, 7 and 8 from profile/Deck_Copy_2026-09-15.md.

Our slide	Nearest Fieldflo flow	Matches what the owner saw?	What Fieldflo showed that our slide does not
6 — A new job, from the call to the crew (quote → proposal → job → board → ticket block)	Flow 7 project book + proposal (@21:26), Flow 10 dispatch (@34:47), Flow 8 step 4 cert warning (@25:57)	Mostly. Same shape: proposal → awarded → project → schedule → cert check.	The step between "awarded" and "schedule": setting up the project book once (permits, mandatory certs, cost codes, emergency contact) so that scheduling and the timesheet can check certs (@21:26). The owner said "perfect fit" right after this screen (@24:07). Fieldflo warns and emails rather than blocks (@25:57). Each man is sent his own schedule (@34:47, @36:37).
7 — The end of a day, start to finish (voice note → report → hours → crew confirm → questions → owner sees)	Flow 8, the field day (@24:23 to @32:09)	Partly. Ours starts at end of day with a voice note. Fieldflo's day is: Start day → timesheet → safety meeting signed by every man before work → work, inspections → daily (talk it, photos) → containment log → end-of-day timesheet → every man verifies. The owner confirmed those exact pieces twice (@4:26, @25:39).	Morning safety sign-off by each man before work (@27:47), not at end of day. "Same as previous day" and "pull from scheduling" head starts (@25:57). Job-specific abatement forms and the containment log (@27:47), which the owner flagged: "some stuff for abatements is a little more detailed and job specific" (@4:26). Photos on every daily (@27:47). Office sees the project start "to the second" (@27:47).
8 — Closing the job and getting paid (closeout → invoice drafted → you send → payment marked → owed and holdback)	Flow 11 closeout + payroll approval (@36:37)	Half. Closeout report matches (@21:26, @36:37). Fieldflo showed no invoicing, no payments, no holdbacks, nothing about money owed anywhere in 43 minutes. Steps 2 to 5 of our slide have no Fieldflo equivalent.	The weekly payroll approval → spreadsheet to the accountant, with a PM approval trail (@36:37). The owner's one unprompted access question was exactly this: the accountant seeing payroll only (@8:14). QuickBooks as the destination for the money (@8:00).

Flows Fieldflo showed that have no workflow slide of ours

Weekly payroll to the accountant (Flow 11, @36:37). The owner asked about it (@8:14). Our comparison file says a Payroll Approval screen with CSV export exists on our side (row B12), so this is a slide gap, not a build gap.
QuickBooks set-up: employees and jobs come across once (Flow 3, @12:48; Flow 7 step 1, @21:26). The owner's first words to Dan were "Connect to QuickBooks" (@8:00). Ours is "Missing (planned)" per the comparison file; it can only be a note line, honestly labelled.
Equipment out to a job and back (Flow 6, @19:01). Owner: "That's great" (@21:20). Our Equipment page exists (comparison row B8) but loadouts do not.
Inspection → corrective action → stays on the board until fixed (Flow 2 step 9, Flow 8 step 11). Our Safety page has this (comparison row B7); no slide shows it as steps.
Certificates add → renew → archive → PDF pack (Flow 5). Covered by slide 4's bottom strip per the deck notes, so not a gap on 6 to 8.
Not worth a slide: training videos ($4 upsell, @15:31), takeoff/estimating (the owner cool on it, @34:36), CRM (the owner interrupted it, @8:00).

Naming and ordering from the video that lands better

Dan's names for the day's paperwork, which the owner agreed to in his own words: timesheet, safety meeting (JHA), daily (@4:26, @25:39). Our slide 7 says "voice note," "day's report," "safety talk." Use "daily" and "timesheet"; keep "safety talk" (the owner said "safety meeting," close enough).
"Project book": Dan's phrase for the one page that holds the job (@21:26), and the screen the owner called a "perfect fit" (@24:07). Our comparison file already uses it; slide 6 does not.
"Closeout report": Dan's phrase (@21:26, @36:37). Slide 8 step 1 says "One printable report." Say "closeout report."
"Start day" as the one button that brings the right forms (@24:23). If slide 5 already uses it, slide 7 should visibly begin where it ends.
Dan's order for the whole demo was set-up → people and certs → equipment → job → field day → schedule → payroll. Ours is job → day → money. Ours is fine for an owner; the one ordering lesson is that Dan put the mandatory certs on the project before he showed the cert check on the crew (@21:26 then @25:57), so the block made sense when it appeared.