Meeting Prep — Jul 16 Demo Call
Discovery Questions Internal checklist for the demo with Carlos, Tony, and Deris. Check each question off as it comes up on the call — the goal is to walk out with clear direction on scope, integration and rollout.
01
Scope & Priorities Of the 7 "Proposed" roadmap items (breadcrumb replay, exception trends, worker earnings view, audit trail, placement Gantt view, client comparison rollup, calendar view) — which 2–3 matter most for v1? Why we're asking · Keeps the next build phase focused instead of guessing what to prioritize.Is the native iOS app a v1 requirement, or can web-only launch first and mobile follow in a phase 2? Why we're asking · Mobile is a design exploration only right now — this decides if it's in scope for the estimate.
02
Geofencing & Approval Design We built hard-block geofencing (can't clock in outside the fence at all) instead of a soft-flag approach — does that match what you want, or is there a case where a worker needs an override? Why we're asking · Confirms a real design decision before it's locked into the build.Do all clients need the same dual-layer (internal + client) approval, or does it vary by client — some client-only, some internal-only, some both? Why we're asking · This is the core differentiator — worth nailing the exact shape per client.
03
Avionté Integration Can Tony share the actual API credentials/docs so we can confirm read-only sync vs. bidirectional write-back before finalizing scope? Why we're asking · Unblocks real integration planning post-demo.Should time data push back into Avionté automatically once fully approved, or does someone need to manually trigger that sync? Why we're asking · Changes the engineering scope quite a bit either way.
04
Compliance Has Noor had outside counsel review the adjustment-consent language before, or should that happen before this goes live? Why we're asking · NY/CA exposure was Carlos's own framing on the discovery call.Is the 1099/C2C vs. W-2 split (Consultant vs. Employee) the only worker-type distinction, or are there others — e.g., prevailing wage, multiple pay tiers — we should plan for? Why we're asking · Avoids a data-model rework later.
05
Rollout Which client account should be the pilot — the most complex approval chain, or the simplest, to prove the model faster? Why we're asking · Shapes what "done" looks like for the first rollout.Is there existing timesheet data — even informal or manual — that needs to be migrated in, or does everyone start clean? Why we're asking · Migration work is easy to miss in an estimate.
06
Commercial Given the fixed-cost, prototype-first model discussed — is there a budget range already in mind, so the estimate we bring back is calibrated rather than a surprise? Why we're asking · A number this far along avoids a wasted round-trip on the estimate.
© 2026 SJ Innovation LLC · 244 5th Ave, New York