The Checker — fieldflo-video-gap

Task: Omar, 2026-09-26 20:09 UTC — "get the checker to watch the video of the demo of the other company and make sure that everything they can do we can do as well." One grade. No worker, no rounds.

The recording: media/competitor/fieldflo_demo_43min_2026-09-20.mp4 — 43:24.97, 1280×720, h264, 30 fps (measured: ffmpeg-full -i … -f null -). Fieldflo's Dan Szigeti screen-sharing portal.fieldflo.com/demo-sales/ to the owner/the owner and Mark Chambers, 2026-09-08. Transcript profile/Fieldflo_Call_Transcript_2026-09-08.txt (512 lines) read in full before Part 1 was written.

How it was watched. The ffmpeg at ~/.local/bin/ffmpeg is the Playwright build (--disable-everything, no mp4 demuxer, no h264 decoder) and cannot open this file — it errors Invalid data found when processing input. There is no ffprobe on the box. A static ffmpeg 7.0.2 already sat in hive/checks/2026-09-26_fieldflo-video-gap_venv/bin/ ffmpeg-full; that is what cut the frames.

178 frames were cut into hive/checks/2026-09-26_fieldflo-video-gap_frames/, named f_MMSS.jpg: a 20-second grid across the whole 43 minutes (131 frames, 0 s → 2600 s) plus 70 extra cuts at seconds where the transcript says a new screen opened (the timestamp list is _frames/_times.txt; 178 unique after the grid/extras overlap). All 178 were opened and read with my own eyes — no sampling. 166 of the 178 are distinct images; the 12 repeats are genuinely static screens (the dashboard sat unchanged for stretches), which I confirmed by re-cutting 20 s / 80 s / 140 s independently and getting the same md5.

hive/checks/2026-09-26_fieldflo-video-gap_venv/bin/ffmpeg-full \
  -hide_banner -loglevel error -ss <s> -i media/competitor/fieldflo_demo_43min_2026-09-20.mp4 \
  -frames:v 1 -q:v 3 -y hive/checks/2026-09-26_fieldflo-video-gap_frames/f_MMSS.jpg
$ ls hive/checks/2026-09-26_fieldflo-video-gap_frames/*.jpg | wc -l
178
$ md5sum hive/checks/2026-09-26_fieldflo-video-gap_frames/*.jpg | awk '{print $1}' | sort -u | wc -l
166

Parts 1, 2 and 3 of this file were written before profile/Fieldflo_Call_Gap_Analysis_ 2026-09-20.md, profile/Fieldflo_Video_Frames_2026-09-20.md or profile/Master_List_ 2026-09-16.md were opened. I did not read them, and I did not read any earlier hive/checks/ file, while grading Parts 1–3. Part 4 is the only place they appear.

Everything below is demo data on both sides. Fieldflo's screen is its own sales demo (/demo-sales/); Makki's portal carries a DEMO DATA band on every page and says so.

Part 2 evidence — how the Makki portal was measured

Three things, all read-only, all re-runnable from (workspace root):

(A) The grep target is the live app, not a stale copy. Every portal JS file on disk is byte-identical to what https://makki-home.pages.dev/app/ serves, so a grep of portal/*.js is a measurement of the live site. .bak_* files are excluded from every grep in this report.

$ bash hive/checks/2026-09-26_fieldflo-video-gap_bytes.sh
SAME  app.js  71a2de55cd2c87de0a44a5247fc7f057
SAME  roles.js  441582b11c7450144f0cbe1381a2af46
SAME  forms.js  4504c8f6a1e6acfc50e8c2055fd912fc
SAME  certs.js  5cfd97e0b08665532263ea0e1efd5c74
SAME  app-ops.js · app-ops2.js · app-day.js · app-job.js · app-people.js
SAME  app-yard.js · app-forms.js · app-map.js · app-notify.js · app-import.js
SAME  index.html (served at /app/)  5cf235ae41b8fc753746ce2f7141bc3c

(B) The five demo logins were driven on the live site (Playwright, the skills/visual-qa/.venv runtime), every tab opened, the page's own text read back. 52 PNGs in hive/checks/2026-09-26_fieldflo-video-gap_shots/.

$ skills/visual-qa/.venv/bin/python hive/checks/2026-09-26_fieldflo-video-gap_live.py
== ali == tabs(16): overview·pipeline·proposals·jobs·projects·board·gantt·collections·
          payroll·quickbooks·team·tickets·safety·forms·equipment·inventory
== priya == tabs(4): overview·outstanding·toinvoice·payments
== ray == tabs(5): overview·quotes·winrate·proposals·bidactual
== sam == tabs(11): overview·startday·myjobs·schedule·board·gantt·crewcerts·safety·
          forms·equipment·materials
== dale == tabs(5): today·endofday·myschedule·mytickets·forms
== scan MK-W07 (no login) == Ivy Salcedo | Abatement Tech · Crew C | MK-W07 |
   All tickets in date | TICKETS HELD | Asbestos Worker … | Respirator Fit Test …

$ skills/visual-qa/.venv/bin/python hive/checks/2026-09-26_fieldflo-video-gap_owner.py
ali/overview: Owner / Company Overview / What is running today · then the money
ali/pipeline: Sales Pipeline / Quotes sent vs won · fiscal 2026
ali/proposals: Proposals / 603 quotes this year
ali/jobs: Jobs & P&L / Every won job with full cost breakdown
ali/projects: Project Book / 17 jobs with a book · permits, required tickets, crew readiness
ali/board: Schedule Board / Week of Mon 17 Aug · click a day to move a crew
ali/gantt: Timeline / 16 open jobs · read-only
ali/collections: Collections & AR / Money owed to the company · oldest first
ali/payroll: Payroll Approval / Week of Mon 17 Aug · 12 men · 404 h
ali/quickbooks: QuickBooks Online / the owner's accounting system · not connected
ali/team: Team & Access / 5 people · add someone by email and pick their role
ali/tickets: Tickets & Certificates / 14 men · 54 tickets on file · warned before they lapse
ali/safety: Safety & Incidents / 3 incidents · 3 corrective actions open
ali/forms: Forms / Build the forms the crews fill on site, and read what comes back
ali/equipment: Equipment & Rentals / 12 assets · 3 on rent · a code on every one
ali/inventory: Inventory / Disposal consumables on hand (bags, coveralls)

(C) A per-capability grep of the current portal source.

$ bash hive/checks/2026-09-26_fieldflo-video-gap_probe.sh

In Part 2, probe N means row N of that script, live means (B), and a bare grep … is a one-off run quoted inline.

The owner's rails, named where they apply. Two standing rules make some Fieldflo behaviour out of scope rather than missing:

• RULE #1 (nothing sends). Nothing in the hive sends, publishes or contacts anyone without Omar's explicit OK — no email, SMS, call or post to customers, suppliers, inspectors or employees. Drafts are produced; the owner sends.
• Mock-data rule (#7). Every figure is demo until Omar says the real data is connected, so live third-party integrations (QuickBooks, an SMS gateway, a weather API) are settings pages, not connections.

A row marked Out on rail is something the portal deliberately does not do because of one of those two. It is not a gap, but it is a difference the owner will notice, so each one names its rail.

Part 1 — everything Fieldflo showed on screen or said it does

207 capabilities.

Part 2 — does the Makki portal do it?

Part 3 — the gaps, ranked by how much of the demo they took up

Each line is a task, ready to paste into GO_LIVE.md. Ranked by minutes on screen and by how hard the owner reacted. Rows marked (rail) are the owner's and Omar's rule, not a missing feature — they are listed last, separately, because GO_LIVE has to decide them, not build them.

Not built — ranked

1. Training system end to end — deploy a training to the company or a division, it lands on the man's phone in his language behind a PIN, he watches, takes a quiz, and passing issues a certificate with Makki's logo that is then tracked and warned on like any other ticket. ~2 minutes of the demo (14:30–16:00), the owner: "Perfect." — Fieldflo rows 86–92.
2. Any language — a translate control that flips the whole portal, and a per-form globe, so a bilingual crew reads its own paperwork. Dan opened with it at 02:37 and showed the entire UI in Spanish; he came back to it four more times (15:00 training, 25:20 field view, 30:20 safety verification, 31:00 dailies). Nothing in the portal is translatable — Fieldflo rows 25, 26.
3. Takeoff & estimating — upload the drawings, have them auto-read into tasks and scope, pick a work type and job conditions from a template, and push the result into a proposal. 34:00–35:20; the owner: "I'll check it out… it'd be cool to see." — Fieldflo rows 182–185.
4. OSHA / OHS statutory reporting — the 300 log, the 300A summary, the 301 incident records, case classification and illness type, filtered by year and establishment, downloadable as csv and xlsx. 07:45. For Makki this is Alberta OHS and WCB, not OSHA — Fieldflo rows 46–48.
5. The full incident claim — an 11-step wizard (injured employee, damaged property, damaged equipment, what happened, employee statement, witnesses, third party, investigation report, insurance) with a % complete and a "needs review" queue that ages. Makki files an incident in one form. 07:10 — Fieldflo rows 43, 44.
6. Equipment maintenance and inspection engine — nearing-maintenance by trigger miles/km/hours, next inspections due, equipment corrective actions, an inspection form driven by equipment type with odometer, hours and OK/NO/N/A per line. 07:50 + 20:00 + 34:00, three separate visits — Fieldflo rows 51, 52, 53, 112, 115.
7. A real CRM front end — reach-outs, job walks, proposals due, leads by salesperson, a lead record with source and due date, a Clients tab and a CRM calendar. 07:55–08:20, and the leads list alone showed 158 leads / $4.2m pipeline. Makki has a quote pipeline, not a lead pipeline — Fieldflo rows 57, 58, 60, 61.
8. Task steps / hazard / control / risk rating library — the supervisor picks the task and the JHA fills its own hazards and controls; ~40 hazards in 5 groups on the review page. 29:00–30:00, and Dan called it "This is cool" — Fieldflo rows 159, 161.
9. GEO fencing and GEO tagging per job — on or off per project, with a "Geo Location Data Missing" notice. Shown as a live badge on the timesheet header. 22:00 + 26:30 — Fieldflo row 129.
10. Voice into the daily — the crew talks into the daily report instead of typing, in any language. Dan sold this as the reason the field adopts it at all ("they don't want to change… you just open it up, talk, take pictures, boom"). 31:00 — Fieldflo row 169.
11. Live weather and heat index on the JHA — current and forecast temperature, wind, humidity, OSHA heat index, each with a "have you reviewed this with the crew" question. 29:20 — Fieldflo rows 162, 163.
12. Warehouse request / fulfil loop — a request form with a verified requester, warehouse approval, delivery notes, returning items with approved quantities, and RAPID QR to add items by scanning. 20:30 — Fieldflo rows 118, 119.
13. Reporting Center — 18 named exportable reports (asset, job costing, expense, per diem, T&M, change order, waste, warehouse, project inventory, CRM, incident, injury, inspection, equipment log, form). 09:00 + 21:00 — Fieldflo rows 121, 122.
14. Admin section — form sequencer, export builder, email templates and groups, email log, imports, timesheet adjuster, portal admin. 21:00 — Fieldflo row 4.
15. Asset QR that opens a no-login inspection or an SDS — the operator scans the machine and does the check without ever logging in. Makki puts a code on every asset but the code opens nothing. 19:30 — Fieldflo rows 109, 110.
16. Equipment location map — where every vehicle, rental and piece of heavy equipment is, with rentals/heavy-equipment toggles and per-asset popups. Makki's map shows job sites, not assets. 07:50 — Fieldflo row 56.
17. Injuries-by-body-part and the 12-month incident chart — a trend line and a body diagram over 30 days vs 12 months. 07:00 — Fieldflo rows 39, 41.
18. Abatement procedure checklist on the daily — install criticals, negative pressure, construct decon, pre clean, cover fixed objects, containment, removal, bag out, final clean, clearance, tear down, demob; plus cleaning verification and cloths used. This is the most abatement-specific thing in the whole demo. 31:00 — Fieldflo rows 172, 173.
19. Containment entry log — names pre-filled, respirator used, task before, time in / time out, typed signature. 31:40 — Fieldflo row 175.
20. Employee record depth — employee number, office/division, default cost code, union name and code, payroll group, temp-labour flag, write-ups, documents on the man, linked assets, per-employee PIN flags. 08:40 + 15:51 + 17:00 — Fieldflo rows 93, 96–99, 102.
21. Cert photo on file — upload a picture of the actual ticket so the cert name on the scan opens the paper. Makki holds numbers and issuers only. 17:30 + 13:50 — Fieldflo rows 84, 103.
22. Roll Call — one click from the dashboard to who is on site right now. 03:45 — Fieldflo row 204.
23. Project Book depth — lien information, project designer, consultant, air monitoring specialist, insurance certificate, payroll information, building and owner information, custom tabs; plus prevailing wage and project phases. 22:00–23:30 — Fieldflo rows 128, 135, 136, 139.
24. Waste registers — haulers, material types, truck types, landfills as maintained lists behind the load entry. Makki records loads and tip fees but not the registers. 23:00 — Fieldflo row 137.
25. Project document folders — named folders with a role per folder, shared/gallery/offline flags, add folder and upload. Makki lists documents; it does not hold them. 24:00 — Fieldflo row 146.
26. Min/max reorder levels on inventory and the low-stock reorder trigger they drive. 19:01 — Fieldflo row 108.
27. PM-by-PM payroll approval chain with a trailing history, so payroll cannot run until named people have signed. 38:40 — Fieldflo row 200.
28. Dashboard stat tiles the owner will look for — days without injury, client count, user count, contracts-in-progress value. 06:45 — Fieldflo row 24.
29. Auditors on the JHA — up to 10 extra people signing the safety meeting with their own PIN. 28:30 — Fieldflo row 157.
30. Submit a feature idea / what's new — the in-product channel Dan used to prove they listen. 33:40 — Fieldflo row 181.
31. Evacuation plan section on the JHA, pulled from the project details. 29:30 — Fieldflo row 160.
32. HQ dashboard across branches / multiple offices — only matters when Makki runs more than one office; the owner said "we'll incorporate it across five companies that we have." 24:23 — Fieldflo rows 148, 202.
33. Export employees to CSV and bulk download of all QR codes. 13:20 — Fieldflo rows 205, 206.
34. Company page, Messages page, and the three-dots admin customisation on every list. 00:00 + 13:20 — Fieldflo rows 6, 8, 65.

Part built — ranked

35. QuickBooks — The owner asked for it by name, unprompted, at 08:00: "Connect to QuickBooks." The portal has the settings page and the sync map; it has never called QuickBooks. This is the single loudest thing in the recording and it is blocked only on the owner's QuickBooks Online login. 08:00–12:38 — Fieldflo rows 62, 63.
36. Dashboard tabs and widget set — Makki has Today's active projects, Nearing bid hours and Certificates expiring soon; it is missing the CRM / Safety / Equipment dashboard tabs, the New Projects widget, the T&M-change-orders queue and the Messages widget. 00:00–06:45 — Fieldflo rows 14, 19, 20, 21.
37. Scheduling board — Makki moves crews by day; Fieldflo shows crew projected vs crew scheduled per day per project, colour-codes projects by whether they are filled, and totals scheduled hours per man. 35:20 — Fieldflo rows 189, 190, 191.
38. Inspection engine — Makki can build an inspection form and log a result; Fieldflo walks it line by line with a photo per line and turns a "no" into an assigned corrective action automatically. 20:00 + 30:40 — Fieldflo rows 49, 114, 166, 167.
39. Project gauges and stats — Makki has bid-vs-spent rings; Fieldflo adds mandays and waste-loads gauges, days-left, and a stats panel with disciplinary actions, work delays and reportable incidents. 21:30 — Fieldflo rows 125, 126, 127.
40. Project-level settings — allow multiple timesheets, allow multiple PSI/JHA, phases, daily overtime trigger, per-project timezone, project-level form settings. 22:00 — Fieldflo row 130.
41. Job cost estimate page — Makki has cost breakdown and change orders; Fieldflo adds contract value, a % complete with a change log, labour estimate rows and inventory estimates by category. 24:00 — Fieldflo rows 141, 143.
42. Proposal editor — Makki generates a proposal document from a quote; Fieldflo edits line items with markup %, drags in text/image/PDF/signature blocks, toggles Web and PDF, sets an expiration and shows bid total / margin / profit live. 35:10 — Fieldflo rows 186, 187, 188.
43. Certificates page depth — cert photo upload, a six-field filter panel (SS last 4, union code, labor type), and the cert-name link to the scanned paper. 17:30 — Fieldflo rows 103, 107.
44. Forms lifecycle — Active / Closed / Deleted tabs, download .pdf and .zip, and the red-until-right rule on every form. 25:20 — Fieldflo rows 176, 179, 180.
45. End of day for a man who never logs in — Makki's End of Day is a login; Fieldflo's reaches the labourer on his phone with no account at all. 32:00 — Fieldflo rows 30, 178.
46. Timesheet head starts — "same as previous day" and "pull from scheduling" as explicit buttons. 25:57 — Fieldflo row 151.
47. Inventory depth — next-inspection-due column, yard/aisle location, asset tag, asset class, quick transfer, item rates (hourly/daily/weekly/monthly) and T&M cost. 19:30–20:00 — Fieldflo rows 108, 111, 112.
48. 4-week look ahead as its own view alongside the Timeline. 37:20 — Fieldflo row 194.
49. Payroll filters — office, project type, verify status, approval status. 38:20 — Fieldflo row 197.
50. Role Profiles as saved, reusable permission presets rather than five fixed roles. 08:30 — Fieldflo row 29.
51. Project Inventory Report as an exportable report rather than an on-screen panel. 21:00 — Fieldflo row 121.

Out on the owner's rail — decide, do not build

These are the only things Fieldflo does that Makki deliberately does not. Every one is RULE #1: nothing sends, publishes or contacts anyone without Omar's explicit OK, except row 62 which is the mock-data rail (#7).

• A1 (rail: RULE #1) — SMS to each labourer to verify his time and hours, and "were you injured" (Fieldflo 67, 178). 09:40, 32:00.
• A2 (rail: RULE #1) — SMS to every man on the timesheet to verify he understood the safety meeting (Fieldflo 164, 165). 30:20.
• A3 (rail: RULE #1) — SMS asking each labourer for his location at clock-in (Fieldflo 154). 27:20.
• A4 (rail: RULE #1) — "Send Verify SMS" and "Mark week approved & notify" from payroll (Fieldflo 198). 38:20.
• A5 (rail: RULE #1) — deploy a message to the whole crew or company by text or email (Fieldflo 38). 06:10.
• A6 (rail: RULE #1) — the notification digest sent as an email with Makki's logo, rather than read in the app (Fieldflo 71). 11:10.
• A7 (rail: RULE #1) — emailing the office automatically when a man without the right certs is added anyway (Fieldflo 152). 26:30.
• A8 (rail: RULE #1) — Send on a proposal, straight to the client (Fieldflo 144, 187). The portal builds the proposal and stops: "Draft — The owner sends." 24:00, 35:10.
• A9 (rail: RULE #1) — sending each employee his own schedule to his phone or email (Fieldflo 192). 35:20.
• A10 (rail: RULE #1) — "Send Forms" in the forms bulk menu (Fieldflo 179). 25:20.
• A11 (rail: RULE #1) — notifying the assignee of a corrective action, and notifying the warehouse manager of a failed equipment inspection (Fieldflo 113, 167). 20:00, 30:40.
• A12 (rail: mock-data #7) — a live QuickBooks Online connection (Fieldflo 62, 63). The page, the entity map and the fallback are built; the call is not made because the owner's login has not been given. 08:00.

The thing to say to Omar about the rail: eleven of these twelve are the same decision, not eleven decisions. Fieldflo's product is an outbound messaging machine — SMS to verify time, SMS to verify the safety meeting, SMS for the schedule, email for the digest, email for the cert warning, Send on the proposal. The owner will feel that absence before he feels any of the 34 unbuilt features, because it is what makes Fieldflo work without anyone logging in. If Omar wants parity, the question is one question: does the Makki hive get an outbound channel, and who approves each send?

Part 4 — what the three earlier analyses missed, got wrong, and what has closed since

Opened only after Parts 1–3 were written and saved: profile/Fieldflo_Call_Gap_Analysis_2026-09-20.md (169 lines), profile/Fieldflo_Video_Frames_2026-09-20.md (165 lines), profile/Master_List_2026-09-16.md Part 2 (141 tasks). Nothing in Parts 1–3 was changed after reading them.

4a. Fieldflo_Video_Frames_2026-09-20.md — 49 frames

It is accurate. I read 178 frames against its 49 and found nothing it describes that my frames contradict. Its three headline judgements are right and I reached each of them independently before opening it: the multi-language claim is a Google Translate widget, not a Fieldflo language pack; the product is written to US rules (AHERA, OSHA, Maryland and Pennsylvania county skills — nothing Alberta anywhere); and there is no phone in the whole 43 minutes, only desktop Chrome plus outbound SMS. Its closing observation — no invoice, no payment, no AR, no holdback and no QuickBooks screen in 43 minutes — is the single most useful line in any of the three files, and my 178 frames agree with it.

What its 49 frames did not reach. One frame every ~53 s, chosen by contact sheet, is a sampling method; a 20-second grid plus transcript-driven cuts reaches ten screens it missed:

1. The training quiz itself — /safety-exam-quiz/2172 (f_1540), five multiple-choice asbestos questions with Back to Training / DONE. Its §B row asserts "an embedded video and a quiz" on Dan's word at @15:31; the quiz is not in any of its 49 frames. The claim turns out true — it was just unevidenced when written.
2. The Trainings Needed page — /public/employee/trainings-needed/1563 (f_1500): thirteen trainings with Deploy Status (Deployed–Email / Deployed–SMS / Enrolled), Quiz Status and a "Go to training" link. This is Fieldflo's third no-login public page and the frames doc records only one (1410).
3. The scanned certificate opening from the scan page — /company-employee/open-certificate/employee_1563_roni-lead-cert…pdf (f_1400), a photographed Weecycle Environmental lead certificate. The doc stops at the cert list.
4. Live weather and the OSHA heat index on the JHA (f_2920) — Current 85F / 6.91mph SW / 56% humidity, Forecast 63–90F, Heat Index 88 current and 98 forecast, each with a "have you reviewed this with the crew" question. Its 2815 row lists "Weather Questions" as a section name and never opens it. This is a real Fieldflo capability that no earlier file records.
5. The employee's own "VERIFY YOUR WORKING DAY" modal (f_3200) — time and positions correct, the break attestation "according to local, state and federal regulations", "Were you injured?" with "Once you hit submit you cannot reverse an injury", then a PIN. And the supervisor's "STOP CLOCK FOR ALL" modal (f_3140) with meal and 2nd-meal start/end.
6. The notification email as delivered (f_1200) — the actual Gmail digest, ~60 rows of employee / cert name / expiry / View Cert. The doc has the settings page (1050) but never the message.
7. The equipment location map (f_0735, f_0740) — "Where are your vehicles, equipment and heavy equipment", Rentals and Heavy Equipment toggles, Map/Satellite, clustered pins, per-asset popups ("Falcons Demolition / 1 AMD Drive Northwest / Skid Steer", "Oakland Coliseum Demolition / Dump Truck / Equipment Trailer"). Its 0727 row lists the equipment widgets but not this map.
8. The CRM leads list populated (f_3440) — 158 leads · $4.2m active pipeline, ten named leads with client, status pill and value. Its 0745 is the CRM dashboard only.
9. Project Document Management (f_2400) — the folder tree itself: Air Monitoring, Company Documents, Containment Entry Logs, Contract Documents, Form Images, Inspection Checks, Manifests, Permit & Modification, Permits/Notifications, Pictures, Plans and Specs, with a Role column per folder.
10. The JHA signature block wording (f_2930) — the acknowledgement paragraph (including the COVID clause), "Add Visitor | Add Employee", an SMS-resend control and per-worker SMS SENT chips.

Two small corrections. Its 2600 row calls the per-form icons "translate, email, print and delete"; the bulk ⋯ menu I read at f_2520 is Translate to English · Download Forms .pdf · Download Forms .zip · Send Forms · Close Forms · Delete Forms — "print" is a PDF download. And it says the Reporting Center has 19 reports while the permission sheet at f_0900 names 18; both are right, from different screens (the Reporting Center tiles add Employee Timesheets, Production Tracking and Project Billing and drop Employee Sharing). Neither changes anything.

4b. Fieldflo_Call_Gap_Analysis_2026-09-20.md — six claims that are wrong today

Its rule was "every 'not built' claim was confirmed by searching the portal source". Measured against the portal as it stands today, six rows do not hold:

Two smaller ones: it files the hard-hat scan under app-people.js / certs.js — it is app.js:1589, function inspectorView(code) (right conclusion, wrong file). And its §4-C says the owner's SMS failure "was present across the whole second half of the call, not just in scheduling", citing @27:47. At @27:47 Dan only says a text is coming; the owner's complaint lands at @35:48 and @36:24. The pervasiveness is an inference, not something the owner said — and the competitive point stands without it.

What it got right that still matters. the owner is in procurement, not research ("they have approved to spend money"). The real pain is adoption, not features ("some people were using it, some people weren't, everything was out of whack"). Their SMS broke live in front of him and that is the clearest opening in 43 minutes. The hard-hat QR was the "wow" and Makki already has it — I confirmed it live today on a no-login URL. And @32:09, the owner asked out loud for an orientation video for his managers and nobody has offered him one. That ask is not a portal capability, so it does not appear in my Part 3; it should not be lost.

4c. Master_List_2026-09-16.md Part 2 — 141 tasks vs 207

It under-counts the video by about a third. It reads 141 tasks; I read 207 off 178 frames plus the full transcript. The 66-row difference is almost entirely detail a transcript cannot carry, because Dan narrated in generalities while the screen showed specifics: the OSHA 300/301 tabs with their csv and xlsx downloads and case classifications; the equipment nearing-maintenance trigger columns; the equipment and rental location map; the CRM lead record and its nine money tiles; the live weather and heat index; the notification email as delivered; the Trainings Needed page; the quiz; the JHA's five hazard groups; the proposal's margin / profit / Send; the payroll SMS-sent and verified columns. A transcript-led list systematically under-counts a screen-share.

Its page count is now one short in three places. Part 4 reads "42 pages — Owner 15 · Bookkeeper 5 · Estimator 5 · Site lead 10 · Crew 4". Driven live today the portal gives Owner 16 · Bookkeeper 5 (4 on by default) · Estimator 5 · Site lead 11 · Crew 5, because Forms was added to the owner, the site lead and the crew on 2026-09-23. The total is still 42 only because the split moved.

Five of its open holes have closed since, verified live by me today rather than taken on any file's word:

• V49 / V52 — add and renew a ticket. Live: Add a new ticket / Renew one he holds, and A renewal keeps the old ticket on file — nothing is ever deleted. Its own 09-17 correction already recorded this.
• V53 — a PDF pack of certificates. Live: <h3>Certificate pack · …</h3> with kpi("Men in the pack"), kpi("Included"), kpi("Not included").
• V61 — maintenance and repair history per machine. Live: <h3>Inspections and repair history</h3> in app-yard.js.
• V45 — skills and picking a crew by skill. Live, as in 4b.
• V62 (part of V62–V64) — loadout lists. Live: A LOADOUT LIST — what a job needs, out of the yard and back, and kpi("Ordered"), kpi("Out to site"), kpi("Came back"), kpi("Consumed"). V63 is part closed (consumption lands against the job) and V64 is still open — there is no exportable project inventory report.

And two more that no earlier file records, both since 09-20: the Form Builder (09-23, published 09-24) and tickets Edit / Delete (published 09-26, cache v25-ticketedit) — live today as To correct or delete one, open the man and use Edit or Delete on the ticket.

Still open, exactly as it says: V128/V32/V33 QuickBooks — The owner's first unprompted words on the call and still only a settings page. V104/V106/V131 the abatement paperwork — the containment log and the asbestos lines on the daily, which the owner flagged himself at @4:26 before Dan showed anything. V96 the JHA task library. V4/V136–V138 the labourer who never logs in. V130 the manager orientation video.

Its §3b is the best thing in the three files and I confirm it independently. Fieldflo showed no invoice, no payment, no accounts receivable and no holdback in 43 minutes. Makki has Collections & AR, Outstanding, To Invoice, Payments and a nightly Collector that drafts invoices. Measured live today: priya/outstanding: Outstanding Receivables / 75 invoices awaiting payment · $1.43M owed and priya/toinvoice: To Invoice / 18 finished jobs not yet billed · $561.8K. That is a whole axis Fieldflo does not have, and it should be said to the owner out loud rather than left in a file.

4d. One thing all three missed

None of the three names the shape of the difference, which 178 frames make obvious: Fieldflo is an outbound messaging machine wearing a portal. SMS to verify time, SMS to verify the safety meeting, SMS for the schedule, SMS for the location, email for the digest, email for the cert warning, email when a man is added without a ticket, Send on the proposal. Eleven of the twelve rail rows in Part 3 are that same one decision. Makki's portal is the opposite shape: everyone logs in, everything is gated at the field level, and nothing leaves the device. That is the owner's and Omar's rule, and it is defensible — but it is one decision, not eleven, and it is the first thing the owner will feel.

Fieldflo capabilities 207 — Built 68 / Part built 66 / Not built 65 / Out on rail 7 / NOT MEASURED 1 — 2026-09-26T21:37:26Z